[Bug 1803476] Re: After reboot, snap-confine has elevated permissions and is not confined but should be
Apparmor breaks kubernetes on my host. Why should I need apparmor to run snapd? That seems like a pretty significant bug/limitation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803476 Title: After reboot, snap-confine has elevated permissions and is not confined but should be To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1803476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756785] [NEW] lxcfs startup failues because fuse directory not empty
Public bug reported: During start-up, I get about 8 complaints that LXCFS is starting and stopping, until it goes red and says it failed. The lxcfs.service unit journal contains a number of these: Mar 18 21:12:36 ripper systemd[1]: lxcfs.service: Unit entered failed state. Mar 18 21:12:36 ripper systemd[1]: lxcfs.service: Failed with result 'exit-code'. Mar 18 21:12:36 ripper systemd[1]: lxcfs.service: Service hold-off time over, scheduling restart. Mar 18 21:12:36 ripper systemd[1]: Stopped FUSE filesystem for LXC. Mar 18 21:12:36 ripper systemd[1]: Started FUSE filesystem for LXC. Mar 18 21:12:37 ripper lxcfs[1539]: hierarchies: Mar 18 21:12:37 ripper lxcfs[1539]: 0: fd: 5: hugetlb Mar 18 21:12:37 ripper lxcfs[1539]: 1: fd: 6: cpu,cpuacct Mar 18 21:12:37 ripper lxcfs[1539]: 2: fd: 7: cpuset Mar 18 21:12:37 ripper lxcfs[1539]: 3: fd: 8: blkio Mar 18 21:12:37 ripper lxcfs[1539]: 4: fd: 9: rdma Mar 18 21:12:37 ripper lxcfs[1539]: 5: fd: 10: pids Mar 18 21:12:37 ripper lxcfs[1539]: 6: fd: 11: memory Mar 18 21:12:37 ripper lxcfs[1539]: 7: fd: 12: freezer Mar 18 21:12:37 ripper lxcfs[1539]: 8: fd: 13: perf_event Mar 18 21:12:37 ripper lxcfs[1539]: 9: fd: 14: net_cls,net_prio Mar 18 21:12:37 ripper lxcfs[1539]: 10: fd: 15: devices Mar 18 21:12:37 ripper lxcfs[1539]: 11: fd: 16: name=systemd Mar 18 21:12:37 ripper lxcfs[1539]: 12: fd: 17: unified Mar 18 21:12:37 ripper lxcfs[1539]: fuse: mountpoint is not empty Mar 18 21:12:37 ripper lxcfs[1539]: fuse: if you are sure this is safe, use the 'nonempty' mount option Mar 18 21:12:37 ripper systemd[1]: lxcfs.service: Main process exited, code=exited, status=1/FAILURE Mar 18 21:12:37 ripper fusermount[1580]: /bin/fusermount: failed to unmount /var/lib/lxcfs: Invalid argument Mar 18 21:12:37 ripper systemd[1]: lxcfs.service: Unit entered failed state. Looking at /var/lib/lxcfs, it does, in fact, contain two directories "cgroup" and "proc" So, either: 1) This should only start once, but it's started multiple times, or 2) This directory should be empty but the script fails to make it so ls -l /var/lib/lxcfs shows: [21:26] jwatte@ripper:~$ ls -la /var/lib/lxcfs/ total 16 drwxr-xr-x 4 root root 4096 Aug 26 2017 ./ drwxr-xr-x 69 root root 4096 Mar 18 21:10 ../ drwxr-xr-x 13 root root 4096 Aug 26 2017 cgroup/ dr-xr-xr-x 2 root root 4096 Aug 26 2017 proc/ So, something somewhere made this directory non-empty, and now it fails every time on start. (I sure didn't put anything here!) August 26 matches when I first installed this system, at the time running 17.04. I recommend making the startup script simply nuke the contents of this directory. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: lxcfs 2.0.8-0ubuntu1~17.10.2 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 18 21:23:52 2018 InstallationDate: Installed on 2017-08-26 (204 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: lxcfs UpgradeStatus: Upgraded to artful on 2018-02-05 (41 days ago) ** Affects: lxcfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756785 Title: lxcfs startup failues because fuse directory not empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1756785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747827] Re: alt-tab no longer lets me switch between terminal windows
Yes, this bug should move to gnome-shell -- I'm using the default in ubuntu-17.10, which is gnome-shell. ** Package changed: unity (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747827 Title: alt-tab no longer lets me switch between terminal windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747827] Re: alt-tab no longer lets me switch between terminal windows
That's not useful, because the switching time is way too slow. Installing the AlternateTab Gnome extension gives me the behavior I want. You might consider that a work-around, but I fail to see how this so-common use case could be so drastically broken. It's almost as if the GUI designers aren't really using a variety of computers, or haven't been using them for a long time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747827 Title: alt-tab no longer lets me switch between terminal windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1747827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748511] Re: Xorg crash
Thanks for the questions 1) Removing the kernel parameter causes the same problem (plus, shutdown doesn't work.) 2) I cannot take the graphics card out of the laptop, but I uninstalled the nouveau package xserver-xorg-video-nouveau. This may have improved things; see below! 3) This is on a fresh install of 17.10 on a freshly partitioned/formatted disk. 4) When I log in to an Xorg session (after removing the nouveau xorg driver,) the desktop takes a long time to appear. The computer is largely unresponsive to mouse/keyboard for many seconds, then becomes responsive for a second, then goes unresponsive again; this repeats a few times, before the desktop entirely locks up (and a SSH shell also is locked up at that point.) However, pointing on the touchscreen will move the cursor in this state; moving the touchpad does not move the cursor, and nothing can be clicked/interacted with. Regarding 2) after logging into a default session (Wayland,) with the nouveau Xorg driver removed, but the nouveau kernel module still loaded (despite blacklisting,) it has not crashed my desktop yet. vainfo seems to think that I have accelerated video decoding, and glxgears runs at 60 fps in full screen, so perhaps this is 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/1748511 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1748511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748514] [NEW] DNS doesn't work
Public bug reported: I am running a fresh install of Ubuntu Desktop 17.10 on a Dell XPS 15 9560 laptop. I'm using an external Thunderbolt dock to connect to wired Ethernet. I have additionally installed openssh-server on the system. When I boot the system as normal, NetworkManager ends up creating a resolv.conf file that contains "nameserver 127.0.1.1" However, with this file, DNS doesn't work -- "ping www.google.com" doesn't resolve, web pages don't resolve, ubuntu update doesn't find servers, and so forth. If I do the following, the system works fine: "mv /etc/resolv.conf /etc/resolv.conf.old" "echo 'nameserver 8.8.8.8' > /etc/resolv.conf" But I have to re-do this every time I boot. I have configured manual DNS as 8.8.8.8,8.8.4.4 in the properties for the Wired network connection. It also doesn't work if I use the default DHCP servers (Comcast, who poisons DNS for their customers so I generally don't use that.) My DHCP server is a MikroTik Routerboard Router/Access point (I'm using wired Ethernet for now.) Other wired machines on the same network work fine, including older versions of Ubuntu with DNS set to 8.8.8.8. netstat -naplt udp doesn't show anything listening on port 53 locally, I don't know of that's expected or not for whatever the 127.0.1.1 proxy is. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 9 10:53:31 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-02-09 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) IpRoute: default via 10.0.0.1 dev enxa44cc88a6c8b proto static metric 100 10.0.0.0/8 dev enxa44cc88a6c8b proto kernel scope link src 10.0.0.40 metric 100 169.254.0.0/16 dev enxa44cc88a6c8b scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 b5405fe6-c553-3491-a172-711c8a3e1717 802-3-ethernet 1518202258 Fri 09 Feb 2018 10:50:58 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes enxa44cc88a6c8b activated /org/freedesktop/NetworkManager/ActiveConnection/2 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enxa44cc88a6c8b ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 b5405fe6-c553-3491-a172-711c8a3e1717 /org/freedesktop/NetworkManager/ActiveConnection/2 wlp2s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748514 Title: DNS doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748511] [NEW] Xorg crash
Public bug reported: I've installed ubuntu desktop 17.10 amd64 from scratch in UEFI mode on a Dell XPS 15 9560 laptop. This laptop comes with i915 built-in graphics, as well as an NVIDIA 1050 GPU, but I am not trying to make the NVIDIA work yet, and have blacklisted nouveau. I'm using xorg 1:7.7+19ubuntu3 xserver-xorg-video-intel/artful,now 2:2.99.917+git20170309-0ubuntu1 amd64 I have to set acpi_rev_override=5 in the kernel boot parameters, because rev 6 causes other bugs (hang on shutdown, for example.) I'm using whatever the default desktop (presumably Gnome) and compositor are for a ubuntu desktop install. I can boot to login; I can log in to desktop, but shortly after desktop login, the screen goes black, and after a little while, I'm back at the login screen. Logging in again, works, but at that point, I believe I'm in "dumb software mode." ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 9 10:45:29 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] InstallationDate: Installed on 2018-02-09 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 15 9560 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=4305e654-6011-4413-ac27-724450f22361 ro quiet splash acpi_rev_override=5 vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful crash ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748511 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1748511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747827] [NEW] alt-tab no longer lets me switch between terminal windows
Public bug reported: I typically use multiple terminal windows, rather than tabs within terminal windows, because I find that the context of the visible part of the overlapping windows is highly useful. Up to 17.04, I could use alt-tab to switch between different windows that were each running a terminal instance. As of 17.10, I can only switch between "the current terminal focus window" and "other apps" -- other terminal windows are not part of the alt-tab "ring" Especially going back and forth between the two latest terminal windows with a single alt-tab is crucial to a productive workflow, and all OS-es I've used have supported this for the last 20 years. Except now, I'm expected to Alt-tab a few times to get "back" to terminal, then press arrow-down and arrow-right to select another terminal window. Wot? That's not helpful. This fundamentally breaks my workflow, and is not something I can live with. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: unity 7.5.0+17.10.20171010-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..42.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:42:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 6 20:30:28 2018 DistUpgraded: 2018-02-05 15:47:10,383 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-42-generic, x86_64: installed bbswitch, 0.8, 4.13.0-32-generic, x86_64: installed nvidia-384, 384.111, 4.10.0-42-generic, x86_64: installed nvidia-384, 384.111, 4.13.0-32-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85ea] InstallationDate: Installed on 2017-08-26 (164 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/nvm--vg0-root ro rd.driver.blacklist=nouveau SourcePackage: unity UpgradeStatus: Upgraded to artful on 2018-02-05 (1 days ago) dmi.bios.date: 08/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0318 dmi.board.asset.tag: Default string dmi.board.name: PRIME X399-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0318:bd08/11/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX399-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747827 Title: alt-tab no longer lets me switch between terminal windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1747827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745869] [NEW] do-release-upgrade fails because mirrors don't have both amd64 and arm64 architectures
Public bug reported: do-release-upgrade fails. I'm told this may be because I have multiarch added arm64 support to do cross compilation to arm64 targets, and many mirrors only support amd64/i386 architectures. Unfortunately, do-release-upgrade swaps out my sources.list, and there is no command line option to tell it to use the main ubuntu repository, so I have no idea how to work around this problem. Meanwhile, I'm now stuck with an old, unsupported OS version. The do-release-upgrader seems to run in some sub-window mode where I can't scroll back, and thus can't copy/paste all of the output, but I captured the beginning and end bits. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ubuntu-release-upgrader-core 1:17.04.10 ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.10 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity:Unity7 Date: Sun Jan 28 11:30:30 2018 InstallationDate: Installed on 2017-08-26 (154 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to zesty on 2018-01-28 (0 days ago) VarLogDistupgradeAptlog: Log time: 2018-01-27 17:47:11.670316 Log time: 2018-01-27 17:47:15.555128 Log time: 2018-01-27 17:47:46.586111 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade zesty ** Attachment added: "beginning and end of output of do-release-upgrade" https://bugs.launchpad.net/bugs/1745869/+attachment/5044647/+files/log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745869 Title: do-release-upgrade fails because mirrors don't have both amd64 and arm64 architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1745869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714810] Re: gnome-terminal shrinks window to nothing
I already confirmed the "non-symmetric" behavior: > the following padding does NOT cause the problem: > padding: 1px 1px 1px 1px; > The following padding DOES cause the problem: > padding: 2px 1px 1px 1px; Regarding scrollbars with un-filled space, I guess Linux will keep sucking on the desktop for the foreseeable future for political reasons :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714810 Title: gnome-terminal shrinks window to nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1714810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714810] Re: gnome-terminal shrinks window to nothing
Thanks for the pointer! The window in the screen shot is taken with zero configured padding. The green strip between the gray vim background and the orange scroll bar is all ugly padding added by gnome-terminal. It sounds from your description as if the real problem is in "vte" which is used by gnome-terminal? Note that, in the worst of cases, when I maximize a window and get a green border on the bottom, I will sometimes get a line of text "stuck" there, and it's inaccessible by any normal editor commands or cursor movement. I can't reproduce this on demand (yet) though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714810 Title: gnome-terminal shrinks window to nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1714810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714810] Re: gnome-terminal shrinks window to nothing
Thanks for your answer! Yes, the ugly margin is there even when not maximizing the terminal and even when not using a css override file. (I removed the css override so I can keep working.) I'm attaching a screen shot (the ugly border is only on the right side, probably scroll bar related?) Also worthy of note (sorry, spaced on this last time): I installed this as Ubuntu Server, and then added the desktop by doing sudo apt install ubuntu-desktop. I have also installed the NVIDIA CUDA tools, which installs the NVIDIA 375 driver. Interestingly, my control panels don't have any option to select default window chrome sizes or font sizes, although the Terminal application itself does. I wonder if ubuntu-desktop doesn't actually include *everything* it needs. (I also noted that gnome-screenshot wasn't installed by default; I had to install it manually.) The version of ubuntu-desktop is 1.379 and the version of unity is 7.5.0+17.04.20170407.1-0ubuntu1 Regarding "symmetric" margins, the following padding does NOT cause the problem: padding: 1px 1px 1px 1px; The following padding DOES cause the problem: padding: 2px 1px 1px 1px; ** Attachment added: "screen shot of ugly margin and versions" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1714810/+attachment/4944285/+files/Screenshot%20from%202017-09-04%2010-34-02.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714810 Title: gnome-terminal shrinks window to nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1714810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714810] Re: gnome-terminal shrinks window to nothing
output of "dpkg -l" ** Attachment added: "dpkg -l" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1714810/+attachment/4944298/+files/dpkg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714810 Title: gnome-terminal shrinks window to nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1714810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714810] Re: gnome-terminal shrinks window to nothing
Output of "lshw" ** Attachment added: "lshw" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1714810/+attachment/4944297/+files/hw.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714810 Title: gnome-terminal shrinks window to nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1714810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714810] [NEW] gnome-terminal shrinks window to nothing
Public bug reported:
Using Ubuntu 17.04, vim, in gnome-terminal. Default everythings from the
desktop install, default Theme. The only change is the default window
size in the settings -- I have it at 149x48. This bug happens even with
the default 80x24 window size. The font is the default (not overridden)
Monospace Regular 12.
When running vim in gnome-terminal, there is an ugly margin of terminal-
background color on the right/bottom of the terminal window. My vim
background is gray, my terminal background is green, vim displays gray
background but there is a green border just slightly slimmer than one
character cell on the right/bottom. This also happens for other terminal
programs (including the shell) if they set the background color of
output.
In an attempt to at least make this less ugly, I tried to add some
padding to the terminal to center the drawable area that vim paints with
the background. I added the following to my gtk.css:
$ cat .config/gtk-3.0/gtk.css
vte-terminal {
padding: 8px 8px 5px 1px;
}
Now, when I open gnome-terminal, it keeps resizing itself to be shorter
in the Y axis, one line at a time, until it is only one line high. It's
almost like an animation of the window height, collapsing the window to
be very short. After it stops there, I can manually snap the terminal to
top/bottom edges of the screen, and it will stay there, but trying to
resize it will just keep shrinking the height.
This bug is about the resizing behavior. My totally uneducated guess is
that there's some off-by-one error when allocating space for the
terminal window contents. Terminal calculates contents, sets the window,
measures contents, decides to attempt to "snap" to size of character
cell, rounds down, window gets shorter, terminal measures contents,
decides to attempt to "snap" to size of character cell, rounds down,
window gets shorter, ...
If that is, indeed, the case, then the other bug (the ugly border) may
be caused by the same problem, but I will file a separate bug for that.
$ lsb_release -rd
Description:Ubuntu 17.04
Release:17.04
$ apt-cache policy gnome-terminal
gnome-terminal:
Installed: 3.20.2-1ubuntu8
Candidate: 3.20.2-1ubuntu8
** Affects: gnome-terminal (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "screen capture showing the bug"
https://bugs.launchpad.net/bugs/1714810/+attachment/4943672/+files/2017-09-03-gnome-terminal-2017-09-03_10.44.05.mp4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714810
Title:
gnome-terminal shrinks window to nothing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1714810/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1501345] Re: linux-image-3.13.0-65-generic breaks serial communication
This bug is back in kernel 4.8 series. I'm seeing it in pyserial, using the Cura 2.4 application, on current Ubuntu 16.04 LTS install. ** Also affects: linux-lts-xenial (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/1501345 Title: linux-image-3.13.0-65-generic breaks serial communication To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1501345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 795615] [NEW] Supplied version of Erlang is 2 years old and contains exploitable bugs
Public bug reported: Binary package hint: erlang The version of Erlang supplied with Ubuntu has been version R13B3 at least since 10.04 LTS. The latest available Erlang version is R14B3 (with R14B4 soon coming out), which is many bug fixes and several feature improvements further along. There exists exploitable bugs in R13B3 (you may be able to cause growing store problems running servers out of memory, say), so this may possibly be security related in addition to just staying with the times. I highly recommend you update the included erlang and OTP packages to R14B4 for 11.10, especially if that is going to be another LTS release. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: erlang 1:13.b.3-dfsg-2ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Date: Fri Jun 10 09:17:29 2011 InstallationMedia: Xubuntu 11.04 Natty Narwhal - Release i386 (20110426.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: erlang UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: erlang (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug erlang i386 natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/795615 Title: Supplied version of Erlang is 2 years old and contains exploitable bugs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/erlang/+bug/795615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 795615] Re: Supplied version of Erlang is 2 years old and contains exploitable bugs
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/795615 Title: Supplied version of Erlang is 2 years old and contains exploitable bugs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/erlang/+bug/795615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 542543] Re: Access denied for user 'root'@'localhost' to database SOMEDB
I have a very similar problem. I'm running Ubuntu 10.04 LTS with mysql 5.1. I have not created any users other than the defaults. Server version: 5.1.41-3ubuntu12.1 (Ubuntu) I can do this: mysql mysql create database foobar; I can't do this: mysql grant create temporary tables on *.* to public; ERROR 1045 (28000): Access denied for user ''@'localhost' (using password: NO) Here are all grants: mysql show grants; +--+ | Grants for @localhost | +--+ | GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, RELOAD, SHUTDOWN, PROCESS, FILE, REFERENCES, INDEX, ALTER, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE, CREATE USER ON *.* TO ''@'localhost' WITH GRANT OPTION | +--+ 1 row in set (0.00 sec) Something seems to be somewhat off in the packet setup, though: # grep -C2 mysql /var/log/daemon.log: Jul 7 16:37:18 jwatte-hello-ubuntu init: apport post-stop process (883) terminated with status 1 Jul 7 16:37:18 jwatte-hello-ubuntu acpid: waiting for events: event logging is off Jul 7 16:37:18 jwatte-hello-ubuntu /etc/mysql/debian-start[917]: Upgrading MySQL tables if necessary. Jul 7 16:37:18 jwatte-hello-ubuntu /etc/mysql/debian-start[920]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored Jul 7 16:37:18 jwatte-hello-ubuntu /etc/mysql/debian-start[920]: Looking for 'mysql' as: /usr/bin/mysql Jul 7 16:37:18 jwatte-hello-ubuntu /etc/mysql/debian-start[920]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Jul 7 16:37:18 jwatte-hello-ubuntu /etc/mysql/debian-start[920]: Running 'mysqlcheck' with connection arguments: '--port=3306' '--socket=/var/run/mysqld/mysqld.sock' '--host=localhost' '--socket=/var/run/mysqld/mysqld.sock' '--host=localhost' '--socket=/var/run/mysqld/mysqld.sock' Jul 7 16:37:18 jwatte-hello-ubuntu /etc/mysql/debian-start[920]: /usr/bin/mysqlcheck: Got error: 1045: Access denied for user 'debian-sys-maint'@'localhost' (using password: YES) when trying to connect Jul 7 16:37:18 jwatte-hello-ubuntu /etc/mysql/debian-start[920]: FATAL ERROR: Upgrade failed Jul 7 16:37:18 jwatte-hello-ubuntu /etc/mysql/debian-start[929]: Checking for insecure root accounts. Jul 7 16:37:18 jwatte-hello-ubuntu acpid: client connected from 934[0:0] Jul 7 16:37:18 jwatte-hello-ubuntu acpid: 1 client rule loaded -- Access denied for user 'root'@'localhost' to database SOMEDB https://bugs.launchpad.net/bugs/542543 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 542543] Re: Access denied for user 'root'@'localhost' to database SOMEDB
I have a very similar problem. I'm running Ubuntu 10.04 LTS with mysql 5.1. I have not created any users other than the defaults. Server version: 5.1.41-3ubuntu12.1 (Ubuntu) I can do this: mysql mysql create database foobar; I can't do this: mysql grant create temporary tables on *.* to public; ERROR 1045 (28000): Access denied for user ''@'localhost' (using password: NO) Here are all grants: mysql show grants; +--+ | Grants for @localhost | +--+ | GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, RELOAD, SHUTDOWN, PROCESS, FILE, REFERENCES, INDEX, ALTER, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE, CREATE USER ON *.* TO ''@'localhost' WITH GRANT OPTION | +--+ 1 row in set (0.00 sec) Something seems to be somewhat off in the packet setup, though: # grep -C2 mysql /var/log/daemon.log: Jul 7 16:37:18 jwatte-hello-ubuntu init: apport post-stop process (883) terminated with status 1 Jul 7 16:37:18 jwatte-hello-ubuntu acpid: waiting for events: event logging is off Jul 7 16:37:18 jwatte-hello-ubuntu /etc/mysql/debian-start[917]: Upgrading MySQL tables if necessary. Jul 7 16:37:18 jwatte-hello-ubuntu /etc/mysql/debian-start[920]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored Jul 7 16:37:18 jwatte-hello-ubuntu /etc/mysql/debian-start[920]: Looking for 'mysql' as: /usr/bin/mysql Jul 7 16:37:18 jwatte-hello-ubuntu /etc/mysql/debian-start[920]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Jul 7 16:37:18 jwatte-hello-ubuntu /etc/mysql/debian-start[920]: Running 'mysqlcheck' with connection arguments: '--port=3306' '--socket=/var/run/mysqld/mysqld.sock' '--host=localhost' '--socket=/var/run/mysqld/mysqld.sock' '--host=localhost' '--socket=/var/run/mysqld/mysqld.sock' Jul 7 16:37:18 jwatte-hello-ubuntu /etc/mysql/debian-start[920]: /usr/bin/mysqlcheck: Got error: 1045: Access denied for user 'debian-sys-maint'@'localhost' (using password: YES) when trying to connect Jul 7 16:37:18 jwatte-hello-ubuntu /etc/mysql/debian-start[920]: FATAL ERROR: Upgrade failed Jul 7 16:37:18 jwatte-hello-ubuntu /etc/mysql/debian-start[929]: Checking for insecure root accounts. Jul 7 16:37:18 jwatte-hello-ubuntu acpid: client connected from 934[0:0] Jul 7 16:37:18 jwatte-hello-ubuntu acpid: 1 client rule loaded -- Access denied for user 'root'@'localhost' to database SOMEDB https://bugs.launchpad.net/bugs/542543 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 440179] Re: service fails to start/stop/restart networking daemon
I am also stuck on this problem. I installed 10.04 LTS x64 in a basic (text mode) install on a VMWare vCenter virtual machine. The initial machine works. When I clone this machine, and boot the clone, the clone does not get working networking. As part of trying to diagnose/fix this, I'm running into the same problem with cryptic error messages. I *think* it has something to do with trying to run these commands while something in networking is still trying to start in the background, because waiting for five minutes and re-trying, I get another message (about eth0 not being a recognized interface) -- service fails to start/stop/restart networking daemon https://bugs.launchpad.net/bugs/440179 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 440179] Re: service fails to start/stop/restart networking daemon
More information. Apparently, the system has gotten into a confused state: initctl list | grep network shows: network-interface (lo) start/running network-interface (eth1) start/running network-interface-security start/running networking stop/waiting ifup eth1 prints: Ignoring unknown inteface eth1=eth1 grep eth1 /var/log/boot shows: udev: renamed network interface eth0 to eth1 Again, this may be more of a cause than a symptom of the networking service refusing to start, and the error messages being really poor. This is on 10.04 LTS x64 with a very basic text-mode install -- service fails to start/stop/restart networking daemon https://bugs.launchpad.net/bugs/440179 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
