[Bug 1785176] Re: GnuPG 1.4.23 released on 2018-06-11, addresses CVE-2017-7526
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785176 Title: GnuPG 1.4.23 released on 2018-06-11, addresses CVE-2017-7526 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1785176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758428] Re: Subprocesses of StartProgramInGuest fail when creating temporary files
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/open-vm-tools/+git/open-vm-tools/+merge/352237 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758428 Title: Subprocesses of StartProgramInGuest fail when creating temporary files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1758428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784921] Re: xHCI host controller not responding, assume dead
Awesome ! Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784921 Title: xHCI host controller not responding, assume dead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784638] Re: Merge latest Open-vm-tools from Debian and check if we can go for 10.3
Testing complete by VMWare and good for both planned target releases. Also packaging review complete. Uploaded to cosmic now => track at https://launchpad.net/ubuntu/+source /open-vm-tools/2:10.3.0-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784638 Title: Merge latest Open-vm-tools from Debian and check if we can go for 10.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1784638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783325] Re: Rabbitmq-server times out during server startup
Blame output: 2min 42.650s solr.service 1min 30.057s rabbitmq-server.service 1min 25.356s shibd.service 1min 18.921s kong.service 1min 13.311s postgresql@9.5-main.service 47.776s apache2.service 22.732s cloud-init-local.service 22.192s snapd.service 21.243s lwsmd.service 13.928s accounts-daemon.service 12.658s lxd-containers.service 10.374s mdadm.service 10.362s grub-common.service 10.143s iscsid.service 9.820s dnsmasq.service 8.827s systemd-logind.service 8.790s cloud-config.service 8.669s rsyslog.service 8.541s rc-local.service 8.515s tomcat8.service 8.327s systemd-journald.service 8.326s dev-vda1.device 7.493s ssh.service 6.214s apparmor.service 5.841s apt-daily.service 4.500s systemd-tmpfiles-setup.service 3.542s polkitd.service 2.698s user@998.service 2.618s snapd.seeded.service 2.490s open-iscsi.service 2.378s irqbalance.service 2.332s console-setup.service 2.157s lvm2-monitor.service 2.130s systemd-journal-flush.service 2.067s systemd-modules-load.service 2.060s cloud-init.service 1.978s systemd-tmpfiles-setup-dev.service 1.630s cloud-final.service 1.439s apport.service 1.380s systemd-user-sessions.service 1.353s postgresql.service 1.350s networking.service 1.191s systemd-udevd.service 1.142s keyboard-setup.service 1.062s resolvconf.service 982ms setvtrgb.service 747ms sysstat.service 652ms systemd-remount-fs.service 510ms systemd-sysctl.service 435ms kmod-static-nodes.service 429ms ufw.service 383ms systemd-udev-trigger.service 186ms user@919603791.service 115ms systemd-random-seed.service 93ms systemd-update-utmp.service 91ms systemd-timesyncd.service 79ms ondemand.service 77ms snapd.socket 69ms plymouth-read-write.service 53ms lxd.socket 49ms dev-mqueue.mount 43ms dev-hugepages.mount 36ms plymouth-quit.service 35ms sys-kernel-debug.mount 23ms systemd-update-utmp-runlevel.service 22ms sys-fs-fuse-connections.mount 15ms plymouth-quit-wait.service Critical-chain output: graphical.target @3min 31.194s └─multi-user.target @3min 31.193s └─solr.service @48.542s +2min 42.650s └─remote-fs.target @48.534s └─remote-fs-pre.target @48.530s └─open-iscsi.service @46.036s +2.490s └─iscsid.service @35.889s +10.143s └─network-online.target @35.886s └─cloud-init.service @33.748s +2.060s └─networking.service @32.395s +1.350s └─network-pre.target @32.375s └─cloud-init-local.service @9.641s +22.732s └─systemd-remount-fs.service @5.950s +652ms └─systemd-journald.socket @5.853s └─-.mount @4.350s └─system.slice @5.845s └─-.slice @4.350s -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783325 Title: Rabbitmq-server times out during server startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1783325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783651] Re: Please enable CONFIG_PAGE_POISONING
I've built and tested 4.15 and the latest 4.18 with the following configs: CONFIG_PAGE_POISONING=y CONFIG_PAGE_POISONING_ZERO=y CONFIG_PAGE_POISONING_NO_SANITY=y Attached is a libreoffice spreadsheet with the test results comparing kernels without the config, with the config and with the config with page_poison=1 for the 4.18 and 4.15 kernels. I ran nearly 200 stress-ng stress tests and gathered the throughput (based on bogo ops per second on the usr+sys time consumed) for each stress test. Each of the stress tests were run for 60 seconds on an idle 8 thread Xeon i7-3770. The bogo-ops data was then normalized against the kernel that didn't have the config changes. The data to look at is the geometric means of all the normalized test results: 4.18 kernel, geometric mean of normalized bogo/ops throughput: No page poisoning: 1.000 Config page poisoning: 1.003 Config page poionsing + page_poison=1: 0.991 4.15 kernel, geometric mean of normalized bogo/ops throughput: No page poisoning: 1.000 Config page poisoning: 1.025 Config page poionsing + page_poison=1: 0.977 where > 1.000 shows more throughput and < 1.000 shows degraded throughput So it appears that enabling page poisoning configs does not degrade performance and setting page_poison=1 degrades performance by a very small amount. ** Attachment added: "libreoffice spreadsheet with test results data" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783651/+attachment/5170997/+files/kernel-poison-page-analysis.ods ** Changed in: linux (Ubuntu Cosmic) Assignee: Colin Ian King (colin-king) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783651 Title: Please enable CONFIG_PAGE_POISONING To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779863] Re: Ubuntu nodejs package isn't ABI compatible with mainline nodejs.
I'm sorry, but I must heavily disagree with the assessment here, and I am asking you to reconsider your "won't fix". No breakage is possible since there can't be existing native modules built manually by people due to this other bug, which is the corollary of this present one: https://github.com/nodejs/node-gyp/issues/1415 - node-gyp may be able to fix this in the future somehow and detect and use the system's headers in the case of a mismatch, but it's currently not the case. Basically, node's build system is exposing OpenSSL 1.0 headers to native addons at build time, which are themselves API compatible with the prebuilt OpenSSL 1.1 library. Therefore, it's impossible to currently build any native addon manually on Ubuntu's nodejs that depend on OpenSSL. In other words, you can't break existing native modules built by people, because people can't build native modules *due to this bug*. Your rejection is based on an uroboros where you don't want to fix the problem because you're afraid of breaking people that do not exist due to the problem you're rejecting to fix. If you prefer, I can file a new bug to talk about the fact that you can't currently build native addons that depend on OpenSSL due to mismatching building headers from nodejs' build system and the API you're exposing, but this really is the same resolution than this current bug here. ** Bug watch added: github.com/nodejs/node-gyp/issues #1415 https://github.com/nodejs/node-gyp/issues/1415 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779863 Title: Ubuntu nodejs package isn't ABI compatible with mainline nodejs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1779863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628868] Re: init.d scripts loop between cups and plymouth
This is not a bug in plymouth's init script; it is intentional that plymouth depends on '$all', since this script runs to stop the plymouth frontend after the rest of the init scripts have run. It is a bug in the cups init script on the original user's system; however, that init script was not the init script included in the cups- daemon package in Ubuntu 16.04. The cups-daemon package ships a /etc/init.d/cups which does not depend on plymouth. So this is also invalid for cups. It is still a bug in the part of the system that enforced insserv. ** Changed in: plymouth (Ubuntu) Status: Confirmed => Invalid ** Changed in: cups (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628868 Title: init.d scripts loop between cups and plymouth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1628868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628868] AUTO: Holger Willenborg is out of the office / ist nicht im Büro (returning 27.08.2018)
I am out of the office until 27.08.2018.
Note: This is an automated response to your message "[Bug 1628868] Re:
init.d scripts loop between cups and plymouth [{EXTERNAL}]" sent on
03.08.2018 06:43:20.
This is the only notification you will receive while this person is away.
-
Ultima Holding GmbH
Sitz: Münster Westfalen - HRB 16045 Amtsgericht Münster
Geschäftsführer: Dr. Max Padberg
** Attachment added: "arm_footer_ohneWWW.png"
https://bugs.launchpad.net/bugs/1628868/+attachment/5170996/+files/arm_footer_ohneWWW.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628868
Title:
init.d scripts loop between cups and plymouth
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1628868/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785174] [NEW] nvidia driver - does not resume from suspend
Public bug reported: The same as always: System gets to sleep (systemctl suspend), when pressing a key to resume from sleep, the system will power up (fans and hard disk can be heard), but screens remain dark. Not even terminals can be accessed (ctrl-alt-F2...6). No problem with nouveau driver this time... ubuntu GNOME 18.04, clean install Fujitsu-Siemens Celsius WT-380 nvidia GT 630 two monitors - MY GUESS IS THAT THIS IS IS AN IMPORTANT ASPECT Tried nvidia340, 390 and 396 - all the same result. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Description changed: The same as always: System gets to sleep (hibernate), when pressing a key to resume from sleep, the system will power up (fans and hard disk can be heard), but screens remain dark. Not even terminals can be accessed (ctrl-alt-F2...6). No problem with nouveau driver this time... ubuntu GNOME 18.04, clean install Fujitsu-Siemens Celsius WT-380 nvidia GT 630 + two monitors - MY GUESS IS THAT THIS IS IS AN IMPORTANT ASPECT Tried nvidia340, 390 and 396 - all the same result. ** Summary changed: - nvidia driver - does not resume from hibernate + nvidia driver - does not resume from suspend ** Description changed: The same as always: - System gets to sleep (hibernate), when pressing a key to resume from sleep, the system will power up (fans and hard disk can be heard), but screens remain dark. Not even terminals can be accessed (ctrl-alt-F2...6). + System gets to sleep (systemctl suspend), when pressing a key to resume from sleep, the system will power up (fans and hard disk can be heard), but screens remain dark. Not even terminals can be accessed (ctrl-alt-F2...6). No problem with nouveau driver this time... ubuntu GNOME 18.04, clean install Fujitsu-Siemens Celsius WT-380 nvidia GT 630 two monitors - MY GUESS IS THAT THIS IS IS AN IMPORTANT ASPECT Tried nvidia340, 390 and 396 - all the same result. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785174 Title: nvidia driver - does not resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1785174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730272] Re: package systemd-sysv 234-2ubuntu12.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
As per last comment, removing systemd-shim solves this. "Me too" subscribers, please review whether this solves the problem for you also. It's fairly likely that your problem is actually different; look for other bugs with similar symptoms. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730272 Title: package systemd-sysv 234-2ubuntu12.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1730272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728365] Re: package systemd-sysv 232-21ubuntu7.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
DpkgTerminalLog.txt contains this snippet near the end: dpkg: considering removing systemd-shim in favour of systemd-sysv ... dpkg: systemd-shim is not properly installed; ignoring any dependencies on it dpkg: yes, will remove systemd-shim in favour of systemd-sysv Preparing to unpack .../systemd-sysv_232-21ubuntu7.1_amd64.deb ... Unpacking systemd-sysv (232-21ubuntu7.1) over (229-4ubuntu20) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing archive /var/cache/apt/archives/systemd-sysv_232-21ubuntu7.1_amd64.deb (--unpack): subprocess installed post-removal script returned error exit status 2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728365 Title: package systemd-sysv 232-21ubuntu7.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767568] Re: Console DPMS Nonfunctional in Ubuntu Server 18.04
After revisiting this issue I was able to find a solution, via the setterm command. This is based on the guidance posted at https://superuser.com/questions/152347/change-linux-console-screen- blanking-behavior For my system I created a new file in /etc/rc.local with the following contents: #!/bin/bash setterm -blank 5 Followed by the following command to register rc.local in systemd: sudo systemctl enable rc.local Alternatively, I could have set a boot parameter: consoleblank=Y (Y in seconds, 0 to disable) to the kernel commandline by adding it to the parameter lists in /etc/default/grub, either GRUB_CMDLINE_LINUX or GRUB_CMDLINE_LINUX_DEFAULT In any event console blanking does work now and this bug can probably be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 388632] Re: lftp crashes while mirroring https
On Fri, Aug 03, 2018 at 02:26:59AM -, Noël Köthe wrote: > I'm closing this old bug because I didn't get any equal problem reports > in Debian and last comment/confirmation is more than 7 years old. > > If you disagree please tell me/us. Thanks for cleaning this up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/388632 Title: lftp crashes while mirroring https To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lftp/+bug/388632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 12646] Re: Does not go into the background
fixed. You need to use the suspend command. ** Changed in: lftp (Ubuntu) Status: Confirmed => Fix Released ** Changed in: lftp (Ubuntu) Assignee: (unassigned) => Noël Köthe (noel) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/12646 Title: Does not go into the background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lftp/+bug/12646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603567] Re: package udev 229-4ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
DpkgTerminalLog.txt contains this: > addgroup: The group `systemd-journal' already exists as a system group. Exiting. This appears to be a duplicate of LP#1570310. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603567 Title: package udev 229-4ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1603567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628868] Re: init.d scripts loop between cups and plymouth
** Summary changed: - package udev 229-4ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 + init.d scripts loop between cups and plymouth -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628868 Title: init.d scripts loop between cups and plymouth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1628868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687864] Re: auto-login and "privacy -> auto screen lock -> disable" do not work
After a clean install of bionic, the system behaved as expected for some days. Now, I get autologin after system boot, but have to type my password after resume from sleep again. It happens with nvidia and nouveau driver. ** Changed in: gnome-control-center (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687864 Title: auto-login and "privacy -> auto screen lock -> disable" do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1687864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785165] Re: firmware update on fwupdate version 10-3 not work on AMI's firmware
That patch alone shouldn't turn on ux capsule upgrades. Are you sure it's all that is needed? In my opinion it would be better to jump up to fwupdate 12 rather than just the single bandaid. Also AMI is the IBV used in some other OEM boxes with no problem. This must be specific to some implementation. You will probably want to specify which boxes need this for SRU verification. ** Also affects: fwupdate-signed (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/1785165 Title: firmware update on fwupdate version 10-3 not work on AMI's firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1785165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785171] [NEW] Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection
Public bug reported: I've turned up many, many new server and workstation systems over the years on both Linux and Windows. Never seen anything like this behaviour I'm witnessing on Ubuntu Server 18.04 before where I simply lose Internet connectivity while using a browser. Ethernet interfaces usually either work or they don't work. I've configured the Intel I219-V Ethernet interface (wired Ethernet connection, there is no wifi on this system) using the e1000e driver for Ubuntu. The Ethernet connection is configured to use NetworkManager via Netplan on Ubuntu 18.04 LTS Server version. ASRock Z370m Pro4 motherboard. The Ethernet interface will drop the Internet connectivity when I'm using either the Firefox or Chrome browser. It usually happens when I'm using the search features of the browser. I can't figure out what would cause this type of behaviour. When the Internet connection drops, the only way to get back Internet connectivity is to disconnect the wired connection using the Ubuntu features and then re-connect (this restarts the NetworkManager service I notice). In the NetworkManager logs I do notice an "auth" error about a file or directory not found. I've never seen that before. Note: The auth error does not coincide with the loss of Internet connectivity, but it does proceed it. Often there can be many hours between the auth error and the actual loss of Internet connectivity. After I reconnect the connection (via re-starting the NetworkManager service) all will be fine for up to a day or so, but then I stress test it with a bunch of searches using the browser and usually I can get the Internet connectivity to drop again. Repeat the disconnect and reconnect process again (aka re-start NetworkManager) and the Internet connectivity will be fine again. The longest I've seen it go without an "Internet connectivity drop" issue is about 36 hours. I notice that the e1000e driver does not list the I219-V as a supported Ethernet interface in the Intel documentation for the Linux version of the driver. I'm not sure why that is. The I219-V is supposed to used another driver, but it's not clear there's a Linux version for of the driver for the I219-V. I'm really disappointed that I've run into this issue with Ubuntu Server LTS 18.04 on this motherboard. I had CentOS Server 7.4 (my standard server OS, a great Linux distro) on this same motherboard for a week with no issues, so I know the motherboard and the I219-V Ethernet interface are 100% good hardware wise and can work properly. CentOS 7.4 uses NetworkManager as the default for managing the Ethernet interface. The only reason I'm using Ubuntu Server 18.04 on this motherboard is because of a specific package that Ubuntu has a newer packaged version than CentOS. CentOS is extremely stable when it comes to basic server functionality. Hopefully, this bug with the I219-V Ethernet interface using the e1000e drive for Linux can be verified and a fix rolled out. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: e1000e ethernet networkmanager -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785171 Title: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1785171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784299] Re: linux: 3.13.0-154.204 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784299 Title: linux: 3.13.0-154.204 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
*** This bug is a duplicate of bug 1735594 *** https://bugs.launchpad.net/bugs/1735594 This bug, or what I believe to be this bug and not 1735594, cropped up for me in an update on July 24, 2018 to kernel 4.4.0-131. Have spent the last week + searching the web and residing trying to figure things out and have landed here. I am running Ubuntu 16.04 LTS on an old Acer Extensa 4420 with AMDS TK-57 processor and on board Nvidia 1250 video. System boots into login screen just fine, but any attempt to Login, either Gnome or Ubuntu gets me to a wallpaper only with a mouse cursor. Messages flash up on the screen but do not stay long enough for me to interact with them. Initially one of the said Compiz crashed, but after the first reboot (holding the power switch down), that message no longer appears. I can boot into Grub and duplicate issue with any of the 7 older kernels I have. Can drop to system prompt from GRUB but am too inexperience to know what to do then. This is being posted form another computer running Windows as laptop is currently unusable, and after many years of reliable Ubuntu service. Please help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1741447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1688143] Re: Stop disabling bluetooth!
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1688143 Title: Stop disabling bluetooth! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1688143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774642] Re: cups sees Xerox Phaser 3330 but doesnot print
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774642 Title: cups sees Xerox Phaser 3330 but doesnot print To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1774642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774890] Re: Stopping typing every second when prompted for a password.
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774890 Title: Stopping typing every second when prompted for a password. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1774890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772682] Re: No sound for Dell Inspiron 5758
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772682 Title: No sound for Dell Inspiron 5758 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774784] Re: tras escribir la constraseña de usuario, gnome-shell, no arranca usando el perfil Community Theme.
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774784 Title: tras escribir la constraseña de usuario, gnome-shell, no arranca usando el perfil Community Theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774811] Re: bug
[Expired for postfix (Ubuntu) because there has been no activity for 60 days.] ** Changed in: postfix (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774811 Title: bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1774811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785165] Re: firmware update on fwupdate version 10-3 not work on AMI's firmware
The attachment "0001-Let-s-see-if-this-works-with-that-number- smaller.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785165 Title: firmware update on fwupdate version 10-3 not work on AMI's firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1785165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785167] Re: package dovecot-core 1:2.2.22-1ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785167 Title: package dovecot-core 1:2.2.22-1ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1785167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422253] Re: gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed: (window->display->focus_window != window)") from g_assertion_message_expr() from meta_window_unmanage() fro
** Also affects: gnome-shell (Ubuntu Bionic)
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/1422253
Title:
gnome-shell crashed with SIGABRT in g_assertion_message("assertion
failed: (window->display->focus_window != window)") from
g_assertion_message_expr() from meta_window_unmanage() from
handle_other_xevent()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1422253/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723615] Re: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
** Also affects: mutter (Ubuntu Bionic) 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/1723615 Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1723615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785167] [NEW] package dovecot-core 1:2.2.22-1ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: package dovecot-core 1:2.2.22-1ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: dovecot-core 1:2.2.22-1ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: dovecot-pop3d: Purge NULL: ConfigurePending Architecture: amd64 Date: Fri Aug 3 00:50:17 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-07-30 (3 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: dovecot Title: package dovecot-core 1:2.2.22-1ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dovecot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785167 Title: package dovecot-core 1:2.2.22-1ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1785167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784398] Re: Changing monitor settings crashes on meta_window_wayland_move_resize_internal
** Also affects: gnome-shell (Ubuntu Bionic) 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/1784398 Title: Changing monitor settings crashes on meta_window_wayland_move_resize_internal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1784398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767956] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_new() from meta_monitor_manager_kms_initable_init() from g_initable_new_valist() from g_initable_new() from meta_backend_create_monit
** Also affects: gnome-shell (Ubuntu Bionic) 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/1767956 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_new() from meta_monitor_manager_kms_initable_init() from g_initable_new_valist() from g_initable_new() from meta_backend_create_monitor_manager() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Bionic) 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/1754949 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772831] Re: gnome-control-center does not respond after we set the resolution 320x180
** Also affects: gnome-control-center (Ubuntu Bionic) 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/1772831 Title: gnome-control-center does not respond after we set the resolution 320x180 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1772831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783396] Re: linux: 4.17.0-6.7 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: New => Confirmed ** Tags removed: block-proposed-cosmic ** Tags removed: block-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783396 Title: linux: 4.17.0-6.7 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1783396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784542] Re: Realtek ethernet not functional on 4.15.0-29.31
** Description changed: When using ethernet (Realtek RTL8111/8168/8411 using built-in r8169 driver v2.3LK-NAPI), dhclient stuck at DHCPDISCOVER. When using static IP, nm shows it's connected, but I can't ping anywhere. This issue only shows up in 4.15.0-29.31. I tried the following versions without issue: 1) 4.18.0-041800rc7 2) 4.16.0-041600 3) 4.15.0-23 4) 4.15.0-20 - No issue on wifi (Intel 7260 iwlwifi) and USB ethernet (Dell D3100 - Dock). + No issue on wifi (Intel 7260 iwlwifi), USB ethernet (Dell D3100 Dock) + and USB ethernet (generic adapter using r8152 driver). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: daniel 1771 F pulseaudio - /dev/snd/controlC0: daniel 1771 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: daniel 1771 F pulseaudio + /dev/snd/controlC0: daniel 1771 F pulseaudio CurrentDesktop: MATE Date: Tue Jul 31 14:42:31 2018 HibernationDevice: RESUME=UUID=efa14060-79a3-4f5d-99a5-9bb5f7e840d6 InstallationDate: Installed on 2018-07-08 (22 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 7537 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash i915.enable_psr=0 vt.handoff=1 RelatedPackageVersions: - linux-restricted-modules-4.15.0-29-generic N/A - linux-backports-modules-4.15.0-29-generic N/A - linux-firmware 1.173.1 + linux-restricted-modules-4.15.0-29-generic N/A + linux-backports-modules-4.15.0-29-generic N/A + linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 07PF9F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784542 Title: Realtek ethernet not functional on 4.15.0-29.31 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785166] [NEW] no se puede instalar el paquete <> en <>. El sistema instalado no podra arrancar sin el cargador de arranque de GRUB.
Public bug reported: no se puede instalar el paquete <> en <>. El sistema instalado no podra arrancar sin el cargador de arranque de GRUB. ya para terminar de instalar me aparece este error. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 2 21:48:09 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=es_HN.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_HN.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785166 Title: no se puede instalar el paquete <> en <>. El sistema instalado no podra arrancar sin el cargador de arranque de GRUB. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1785166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785165] Re: firmware update on fwupdate version 10-3 not work on AMI's firmware
** Description changed: [Rationale] - The commited patch, Handle ux capsule updates, https://github.com/rhboot/fwupdate/commit/2561423dd68622dcf8a7542709f332edb517d34e, change to calculate CapsuleBlockDesc Length = CapsuleHeader.CapsuleImageSize + HeaderSize, but on AMI BIOS image which is without capsule header. Fwudpate package on 18.04(version 10-3) included the "Handle ux capsule updates" and cause those machine with AMI firmware cannot do firmware update. + The commited patch, Handle ux capsule updates, https://github.com/rhboot/fwupdate/commit/2561423dd68622dcf8a7542709f332edb517d34e, change to calculate CapsuleBlockDesc Length = CapsuleHeader.CapsuleImageSize + HeaderSize, but on AMI BIOS image which is without capsule header. Fwudpate package on 18.04(version 10-3) included the "Handle ux capsule updates" causes those machine with AMI firmware cannot do firmware update. The fixed patch have been committed, https://github.com/rhboot/fwupdate/commit/863db45c246acd2cbeff0b4e32d3a8312475ff6a and fix the incorrect cbd_length. [Impact] Machines with AMI's firmware cannot do firmware update. [Test cases] 1. install ubuntu 18.04 on AMI's bios machine. 2. get the update firmware 3. See if this machine support firmware update, #sudo fwudpate -s 4. get the update GUID #sudo fwupdate -l 5. do firmeare update #sudo -a GUID firmware.bin 6. reboot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785165 Title: firmware update on fwupdate version 10-3 not work on AMI's firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1785165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785165] [NEW] firmware update on fwupdate version 10-3 not work on AMI's firmware
Public bug reported: [Rationale] The commited patch, Handle ux capsule updates, https://github.com/rhboot/fwupdate/commit/2561423dd68622dcf8a7542709f332edb517d34e, change to calculate CapsuleBlockDesc Length = CapsuleHeader.CapsuleImageSize + HeaderSize, but on AMI BIOS image which is without capsule header. Fwudpate package on 18.04(version 10-3) included the "Handle ux capsule updates" and cause those machine with AMI firmware cannot do firmware update. The fixed patch have been committed, https://github.com/rhboot/fwupdate/commit/863db45c246acd2cbeff0b4e32d3a8312475ff6a and fix the incorrect cbd_length. [Impact] Machines with AMI's firmware cannot do firmware update. [Test cases] 1. install ubuntu 18.04 on AMI's bios machine. 2. get the update firmware 3. See if this machine support firmware update, #sudo fwudpate -s 4. get the update GUID #sudo fwupdate -l 5. do firmeare update #sudo -a GUID firmware.bin 6. reboot ** Affects: fwupdate (Ubuntu) Importance: Undecided Status: New ** Description changed: [Rationale] - The commited patch, Handle ux capsule updates, https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1785033, change to calculate CapsuleBlockDesc Length = CapsuleHeader.CapsuleImageSize + HeaderSize, but on AMI BIOS image which is without capsule header. Fwudpate package on 18.04(version 10-3) included the "Handle ux capsule updates" and cause those machine with AMI firmware cannot do firmware update. + The commited patch, Handle ux capsule updates, https://github.com/rhboot/fwupdate/commit/2561423dd68622dcf8a7542709f332edb517d34e, change to calculate CapsuleBlockDesc Length = CapsuleHeader.CapsuleImageSize + HeaderSize, but on AMI BIOS image which is without capsule header. Fwudpate package on 18.04(version 10-3) included the "Handle ux capsule updates" and cause those machine with AMI firmware cannot do firmware update. The fixed patch have been committed, https://github.com/rhboot/fwupdate/commit/863db45c246acd2cbeff0b4e32d3a8312475ff6a and fix the incorrect cbd_length. [Impact] Machines with AMI's firmware cannot do firmware update. [Test cases] 1. install ubuntu 18.04 on AMI's bios machine. 2. get the update firmware 3. See if this machine support firmware update, -#sudo fwudpate -s + #sudo fwudpate -s 4. get the update GUID -#sudo fwupdate -l + #sudo fwupdate -l 5. do firmeare update -#sudo -a GUID firmware.bin + #sudo -a GUID firmware.bin 6. reboot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785165 Title: firmware update on fwupdate version 10-3 not work on AMI's firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1785165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785165] Re: firmware update on fwupdate version 10-3 not work on AMI's firmware
Attached the fixed patch ** Patch added: "0001-Let-s-see-if-this-works-with-that-number-smaller.patch" https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1785165/+attachment/5170974/+files/0001-Let-s-see-if-this-works-with-that-number-smaller.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785165 Title: firmware update on fwupdate version 10-3 not work on AMI's firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1785165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589418] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589418 Title: udisksd high CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589418] Re: udisksd high CPU usage
present in 16.04 ** Changed in: linux (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589418 Title: udisksd high CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777776] Re: Ubuntu documentation for sssd/kerberos does not authenticate authentication server
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/176 Title: Ubuntu documentation for sssd/kerberos does not authenticate authentication server To manage notifications about this bug go to: https://bugs.launchpad.net/serverguide/+bug/176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720788] Re: zooming out when trim margins is active gets stuck between 100% and Fit Width
I also experience this behaviour (thank you for describing how to work around it!), though my educated guess is that this is an upstream problem, i.e. it should be reported to the KDE developers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720788 Title: zooming out when trim margins is active gets stuck between 100% and Fit Width To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/okular/+bug/1720788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720788] Re: zooming out when trim margins is active gets stuck between 100% and Fit Width
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: okular (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720788 Title: zooming out when trim margins is active gets stuck between 100% and Fit Width To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/okular/+bug/1720788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779715] Re: USN-3629-3: partially applies to MariaDB too
MariaDB 10.0.36-0ubuntu0.16.04.1 is now also available in git. All tests have passed and it is ready for upload to Xenial. Note that MariaDB 10.0.36 was released only a few days ago and has more CVE's fixed than just the USN mentioned in the title. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779715 Title: USN-3629-3: partially applies to MariaDB too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.0/+bug/1779715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785093] Re: RecursionError error in call_adjusted()
** Summary changed: -
[Bug 388632] Re: lftp crashes while mirroring https
I'm closing this old bug because I didn't get any equal problem reports in Debian and last comment/confirmation is more than 7 years old. If you disagree please tell me/us. thx for reporting. ** Changed in: lftp (Ubuntu) Status: Confirmed => Fix Released ** Changed in: lftp (Ubuntu) Assignee: (unassigned) => Noël Köthe (noel) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/388632 Title: lftp crashes while mirroring https To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lftp/+bug/388632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785157] [NEW] external (letsencrypt) certs failing to parse due to pyasn1
Public bug reported: attempting a clean installation of freeipa-server on bionic using letsencrypt certs passed as arguments fails with an error similar to: not in asn1Spec: encoding iso-8859-1> The ipa-server-certinstall command failed I was able to bypass this by downgrading pyasn1 and pyasn1-modules: rm -rf /usr/lib/python2.7/dist-packages/pyasn1 rm -rf /usr/lib/python2.7/dist-packages/pyasn1-0.4.2.egg-info/ rm -rf /usr/lib/python2.7/dist-packages/pyasn1_modules rm -rf /usr/lib/python2.7/dist-packages/pyasn1_modules-0.2.1.egg-info apt install python-pip pip install pyasn1==0.2.3 pip install pyasn1-modules==0.0.9 After that, installation is able to proceed with letsencrypt certificates passed in. ** Affects: freeipa (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/1785157 Title: external (letsencrypt) certs failing to parse due to pyasn1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1785157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769485] Re: freeipa install server fails - cannot start apache server with SSL
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: freeipa (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769485 Title: freeipa install server fails - cannot start apache server with SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1769485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779715] Re: USN-3629-3: partially applies to MariaDB too
MariaDB 5.5.61-1ubuntu0.14.04.1 is now also available in git. All tests have passed and it is ready for upload to Trusty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779715 Title: USN-3629-3: partially applies to MariaDB too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.0/+bug/1779715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785090] Re: Graphics rendering is buggy
Can you please take a screenshot (PrtScn) or a photo of the problem and attach it here? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785090 Title: Graphics rendering is buggy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1785090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782152] Re: GDM blocks SIGUSR1 used in PAM scripts
Yes. The fix for this bug is in 3.28.2-3ubuntu4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782152 Title: GDM blocks SIGUSR1 used in PAM scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782152] Re: GDM blocks SIGUSR1 used in PAM scripts
Did Alberto release the fix there and just forget to document it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782152 Title: GDM blocks SIGUSR1 used in PAM scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458947] Re: QinHeng Electronics CH345 MIDI adapter triggers error
** Tags added: xenial ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458947 Title: QinHeng Electronics CH345 MIDI adapter triggers error To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1458947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
jMyles, does your keyboard also stop responding to everything, including the Windows key? If so then that sounds like your shell is frozen, which is a different bug. In that case please open a new bug by running: ubuntu-bug gnome-shell on the machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785033] Re: GRUB needs to support 64-bit efi linear frame buffer address
** Description changed: [Rationale] More firmwares support above 4G mmio configureation and the EFI Graphics Output Protocol can return a 64-bit linear frame buffer address have been implemented in some firmware/BIOS. Grub2 currently only pass 32-bit framebuffer base to kernel. The Linux kernel has already added support to handle 64-bit linear framebuffer address in the efifb driver now. So GRUB2 should support 64-bit EFI linear frame buffer address. [Impact] Some machines block booting with firmware/bios implemented 64-bit EFI linear frame buffer address,due to Grub passing incorrect(only 32-bit) EFI linear frame buffer. [Test cases] - Need Bios/Firmware support, + Need Bios/Firmware support, 1) Make sure the machine with the Bios implemented 64-bit EFI linear frame buffer address. some machine need to enable above 4G mmio on bios setup menu. 2) Boot up. - [Solution] - A patch has been commited and accepted by maintainer + A patch has been committed and accepted by maintainer http://git.savannah.gnu.org/cgit/grub.git/commit/?id=886edba8770ccbc3def0af2a7d6b346d00d0af2f -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785033 Title: GRUB needs to support 64-bit efi linear frame buffer address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1785033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776671] Re: virtualbox 5.2.12-dfsg-2 ADT test failure with linux 4.17.0-2.3
This bug was fixed in the package virtualbox - 5.2.16-dfsg-3build1 --- virtualbox (5.2.16-dfsg-3build1) cosmic; urgency=high * No change rebuild against older qt/xorg abi. -- Dimitri John Ledkov Thu, 02 Aug 2018 21:46:26 +0100 ** Changed in: virtualbox (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776671 Title: virtualbox 5.2.12-dfsg-2 ADT test failure with linux 4.17.0-2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1776671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622730] Re: No sound on headphones after suspend
I can confirm this exact same problem still exists today. Is there any easy workaround for this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622730 Title: No sound on headphones after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1622730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785153] [NEW] Ubuntu didn't install because grub did not install
Private bug reported: The same installation media worked on another computer a few minutes ago ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 2 18:04:25 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu ** Information type changed from Public to Private -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785153 Title: Ubuntu didn't install because grub did not install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1785153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785154] [NEW] libsystemd-dev dependencies not satisfied
Public bug reported: "Following packages lacks these dependencies: libsystemd-dev : Depends: libsystemd0 (= 237-3ubuntu10) but version 237-3ubuntu10.3 is going to be installed" ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libsystemd-dev (not installed) Uname: Linux 4.18.0-999-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Aug 3 03:02:02 2018 InstallationDate: Installed on 2017-01-12 (567 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-07-24 (9 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic 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/1785154 Title: libsystemd-dev dependencies not satisfied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1785154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754289] Re: git review list fails with newer gerrit versions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: git-review (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754289 Title: git review list fails with newer gerrit versions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/git-review/+bug/1754289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785021] Re: fix this problem at installation
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public ** Changed in: grub-installer (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785021 Title: fix this problem at installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1785021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785024] Re: It gives error
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785024 Title: It gives error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1785024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785024]
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. the specific steps or actions you took that caused you to encounter the problem, 2. the behavior you expected, and 3. the behavior you actually encountered (in as much detail as possible). Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785024 Title: It gives error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1785024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785021]
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. the specific steps or actions you took that caused you to encounter the problem, 2. the behavior you expected, and 3. the behavior you actually encountered (in as much detail as possible). Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785021 Title: fix this problem at installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1785021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784065] Re: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger
Confirming that with new glib2.0 - 2.48.2-0ubuntu4 in updates repository, I could now easily do the 14.04 to 16.04 upgrade. Thanks to all who made this fix happen quickly! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784065 Title: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1784065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1709889] Re: Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time.
But that new lp bug is sparse on details too can all comments be pushed through on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785081 ? What exactly is happening with the bionic kernel, and what is the expectation here? The comments in this bug report from cking still stand imho. Unless there is something else new? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1709889 Title: Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1709889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782085] Re: Kernel panic, iSCSI, Unable to handle kernel pointer dereference in virtual kernel address space
** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** Changed in: ubuntu-z-systems Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782085 Title: Kernel panic,iSCSI,Unable to handle kernel pointer dereference in virtual kernel address space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1782085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782085] Comment bridged from LTC Bugzilla
--- Comment From finne...@us.ibm.com 2018-08-02 19:53 EDT--- This bugzilla defect can be closed. No new occurrences of kernel panic since updating kernel from 4.15.0-15-generic to 4.15.0-23-generic on 07162018 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782085 Title: Kernel panic,iSCSI,Unable to handle kernel pointer dereference in virtual kernel address space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1782085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760621] Re: Tab freezes when I exit the shell
I second flan_suse's comment; having a backport of this bug to the Ubuntu repositories seems like the right thing to do. I'd be happy to get involved to help, but I've never contributed a Ubuntu patch before, so I'd need quite a bit of handholding to move forward. Is there someone on the Guake maintainer team who could give me some pointers? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760621 Title: Tab freezes when I exit the shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/guake/+bug/1760621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783252] Re: gcc on ppc64le has bogus r30 register handling, as exposed by greenlet 0.4.14 will not build on ppc64le
yes, please see https://wiki.ubuntu.com/StableReleaseUpdates In terms of https://wiki.ubuntu.com/StableReleaseUpdates#Procedure this bug has passed step 4, and is awaiting step 5. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783252 Title: gcc on ppc64le has bogus r30 register handling, as exposed by greenlet 0.4.14 will not build on ppc64le To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1783252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767817] Re: Full text search does not work
Hi ! I have the same issue as I stated here : https://askubuntu.com/questions/1061855/ubuntu-18-04-and-tracker-files- properly-indexed-but-not-searchable-in-gs-naut 1. I installed tracker 2. I indexed all my data (as indicated on the command line by "tracker status" / "tracker daemon") 3. I checked whether everything was properly indexed by making some queries on the command line based on the content of some text files : the command line "tracker search" command did yield the right results 4. I made the same searches from Nautilus : they yielded no result : Nautilus (and thus the shell) only seem to use the "mlocate" database and not the tracker one. Hypothesis : the fact Ubuntu makes use of Nautilus 3.26 while the rest of the Gnome stack is 3.28 ? Actually, did anyone manage to get Nautilus 3.26 (and thus Gnome Shell with the nautilus search provider) from Ubuntu 18.04 to use the result of the tracker indexing ? I checked all possible settings in dconf- editor and found no relevant option. Cheers :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767817 Title: Full text search does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1664935] Re: VirtualBox crashed with SIGABRT in qt_message_fatal()
@see https://askubuntu.com/questions/1044292/virtualbox-will-not- install-on-fresh-copy-of-ubuntu-18-04 The suggested fix worked for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1664935 Title: VirtualBox crashed with SIGABRT in qt_message_fatal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1664935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673406] Re: VirtualBox crashed with SIGABRT in QMessageLogger::fatal()
*** This bug is a duplicate of bug 1664935 *** https://bugs.launchpad.net/bugs/1664935 @see https://askubuntu.com/questions/1044292/virtualbox-will-not- install-on-fresh-copy-of-ubuntu-18-04 The suggested fix worked for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673406 Title: VirtualBox crashed with SIGABRT in QMessageLogger::fatal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1673406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785143] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1785143/+attachment/5170959/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785143 Title: xfce4-settings-manager crashed with SIGSEGV in gtk_drag_finish() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1785143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785143] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1785143/+attachment/5170958/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785143 Title: xfce4-settings-manager crashed with SIGSEGV in gtk_drag_finish() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1785143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785143] xfce4-settings-manager crashed with SIGSEGV in gtk_drag_finish()
StacktraceTop: gtk_drag_finish (context=0x8, success=0, del=0, time=6) at ../../../../gtk/gtkdnd.c:961 gtk_drag_drop_finished (info=0x560a3ecfbd60, result=result@entry=GTK_DRAG_RESULT_TIMEOUT_EXPIRED, time=) at ../../../../gtk/gtkdnd.c:2593 gtk_drag_abort_timeout (data=) at ../../../../gtk/gtkdnd.c:3265 gdk_threads_dispatch (data=0x560a3ea53f20, data@entry=) at ../../../../gdk/gdk.c:755 g_timeout_dispatch (source=source@entry=0x560a3ecdeac0, callback=, user_data=) at ../../../../glib/gmain.c:4650 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785143 Title: xfce4-settings-manager crashed with SIGSEGV in gtk_drag_finish() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1785143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785143] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1785143/+attachment/5170960/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1785143/+attachment/5170946/+files/CoreDump.gz ** Changed in: xfce4-settings (Ubuntu) Importance: Undecided => Medium ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785143 Title: xfce4-settings-manager crashed with SIGSEGV in gtk_drag_finish() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1785143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780501] Re: Traceback calling Vte.Terminal.feed_child()
** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780501 Title: Traceback calling Vte.Terminal.feed_child() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1780501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782323] Re: -c:v copy renders audio and video out of sync
As said, this is a known limitation of MPlayer, the interesting question is if other players show A/V desync. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782323 Title: -c:v copy renders audio and video out of sync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1782323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785143] [NEW] xfce4-settings-manager crashed with SIGSEGV in gtk_drag_finish()
Public bug reported: I was changing some options in the Window Manager settings (xfwm4 4.13.1). It started behaving strangely - when I clicked somewhere in the Window Manager settings window it brought me back to the main settings window, I clicked on Window Manager icon, WM settings window showed up and the crash report opened. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xfce4-settings 4.13.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Aug 3 00:59:43 2018 ExecutablePath: /usr/bin/xfce4-settings-manager InstallationDate: Installed on 2018-08-01 (1 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180801) ProcCmdline: xfce4-settings-manager SegvAnalysis: Segfault happened at: 0x7f088d2db1ed : mov (%rbx),%rdx PC (0x7f088d2db1ed) ok source "(%rbx)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: xfce4-settings StacktraceTop: gtk_drag_finish () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: xfce4-settings-manager crashed with SIGSEGV in gtk_drag_finish() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: xfce4-settings (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash cosmic ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785143 Title: xfce4-settings-manager crashed with SIGSEGV in gtk_drag_finish() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1785143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785126] Re: package shim-signed 1.34.9.2+13-0ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1776271 *** https://bugs.launchpad.net/bugs/1776271 ** This bug has been marked a duplicate of bug 1776271 Could not prepare Boot variable: No space left on device (package shim-signed 1.34.9+13-0ubuntu2 [origin: Ubuntu] failed to install/upgrade: Unterprozess installed shim-signed package post-installation script gab den Fehler-Ausgangsstatus 1 zurück) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785126 Title: package shim-signed 1.34.9.2+13-0ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1785126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785144] [NEW] /usr/lib/gnome-terminal/gnome-terminal-server:11:gtk_widget_get_toplevel:gtk_main_do_event:gdk_event_source_dispatch:g_main_dispatch:g_main_context_dispatch
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-terminal. This problem was most recently seen with package version 3.18.3-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/533baf10eb4eebaf140d791f6b612b140c44b36d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: xenial yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785144 Title: /usr/lib/gnome-terminal/gnome-terminal- server:11:gtk_widget_get_toplevel:gtk_main_do_event:gdk_event_source_dispatch:g_main_dispatch:g_main_context_dispatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1785144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780501] Re: Traceback calling Vte.Terminal.feed_child()
Here is a crash in terminator which occurs with the version of vte2.91 in bionic-updates: https://errors.ubuntu.com/problem/13b5b72882f409d035b674102f45b0eae419ab2d Here are some in guake: https://errors.ubuntu.com/problem/a15ca647934a403f748dad5b3400f805a59a0de7 (count of 52) https://errors.ubuntu.com/problem/8f1005750706310a47d63b1eaae0b6e823a9194f (count of 93) https://errors.ubuntu.com/problem/6607888ac9d7c05d5785334483ea2cfe22f9e158 (count of 64) Looking at the guake crashes I was able to recreate the crash using the following command: /usr/bin/guake -n -r htop -e htop I then upgraded to the versions of gir1.2-vte-2.91, libvte-2.91-0, and libvte-2.91-common in -proposed and those also fixed this crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780501 Title: Traceback calling Vte.Terminal.feed_child() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1780501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780606] Re: NetworkManager not able to manage WWAN devices in 18.04 server
** Merge proposal linked: https://code.launchpad.net/~awe/network-manager/+git/ubuntu/+merge/352119 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780606 Title: NetworkManager not able to manage WWAN devices in 18.04 server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1780606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785135] Re: package grub-efi-amd64-signed 1.93.3+2.02-2ubuntu8.2 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785135 Title: package grub-efi-amd64-signed 1.93.3+2.02-2ubuntu8.2 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1785135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785079] Re: Xorg crashed with SIGABRT in _pixman_implementation_lookup_composite()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785079 Title: Xorg crashed with SIGABRT in _pixman_implementation_lookup_composite() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1785079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 658268] Re: [Maverick] F-Spot shows no thumbnails, crashes on picture view if image paths contain non-latin characters
** Changed in: f-spot Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/658268 Title: [Maverick] F-Spot shows no thumbnails, crashes on picture view if image paths contain non-latin characters To manage notifications about this bug go to: https://bugs.launchpad.net/f-spot/+bug/658268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785107] Re: Ghostscript and pstoedit versions not compatible in 18.04 Bionic Beaver
Launchpad has imported 2 comments from the remote bug at http://bugs.ghostscript.com/show_bug.cgi?id=698652. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-10-10T00:45:32+00:00 Reinhard-nissl wrote: Hi, News.htm doesn't mention deprecating DELAYBIND as incompatible change. Bye. Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1785107/comments/0 On 2017-10-10T01:28:31+00:00 Ken Sharp wrote: (In reply to Reinhard Nißl from comment #0) > Hi, > > News.htm doesn't mention deprecating DELAYBIND as incompatible change. This doesn't really seem like an incompatible change to me. As the log message for the commit implementing the change notes, we don't believe DELAYBIND does anything useful which cannot be achieved another way. In addition, if you do use DELAYBIND then it will give you a warning, and you can use REALLYDELAYBIND instead, so the functionality is not lost. As the warning message states, anyone using this switch is encouraged to contact us and discuss it. I'd suggest you do that (but please don't raise a bug report for it, its not a bug). Finally, this is a documentation issue, and we won't change news.htm now that the release is complete. If you feel strongly about this then I would urge you to download the release candidates in future and let us know about issues before we complete a release. Reply at: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1785107/comments/1 ** Changed in: pstoedit Status: Unknown => Won't Fix ** Changed in: pstoedit Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785107 Title: Ghostscript and pstoedit versions not compatible in 18.04 Bionic Beaver To manage notifications about this bug go to: https://bugs.launchpad.net/pstoedit/+bug/1785107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785134] [NEW] ubuntu-release-upgrader crashed with TypeError: Vte.Terminal.feed_child() takes exactly 2 arguments (3 given)
*** This bug is a duplicate of bug 1780501 *** https://bugs.launchpad.net/bugs/1780501 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding ubuntu-release-upgrader. This problem was most recently seen with package version 1:18.04.21, the problem page at https://errors.ubuntu.com/problem/ab19b4d0aa976de73376a7d3bd100d2c28fe6589 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785134 Title: ubuntu-release-upgrader crashed with TypeError: Vte.Terminal.feed_child() takes exactly 2 arguments (3 given) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1785134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785134] Re: ubuntu-release-upgrader crashed with TypeError: Vte.Terminal.feed_child() takes exactly 2 arguments (3 given)
*** This bug is a duplicate of bug 1780501 *** https://bugs.launchpad.net/bugs/1780501 ** This bug has been marked a duplicate of bug 1780501 Traceback calling Vte.Terminal.feed_child() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785134 Title: ubuntu-release-upgrader crashed with TypeError: Vte.Terminal.feed_child() takes exactly 2 arguments (3 given) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1785134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785135] [NEW] package grub-efi-amd64-signed 1.93.3+2.02-2ubuntu8.2 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit stat
Public bug reported: b ProblemType: Package DistroRelease: Ubuntu 18.04 Package: grub-efi-amd64-signed 1.93.3+2.02-2ubuntu8.2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Aug 2 14:32:58 2018 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-01-13 (1297 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.93.3+2.02-2ubuntu8.2 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-07-06 (27 days ago) ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785135 Title: package grub-efi-amd64-signed 1.93.3+2.02-2ubuntu8.2 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1785135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777178] Re: nyx (tor monitor) should depend on python3-distutils
** Changed in: nyx (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777178 Title: nyx (tor monitor) should depend on python3-distutils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nyx/+bug/1777178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712661] Re: gnome-shell crash using ubuntu-dock with dual monitors
** Description changed: + [ Description ] + + Using Ubuntu 17.04 on a laptop with an external display on its right + hand side all is well with dash-to-dock provided the laptop display is + set to the primary display. However if I set the external display to be + the primary display (with dash-to-dock disabled) then as soon as I + enable it gnome-shell crashes and I am logged off. See attached excerpt + from syslog. I have to remove .local/share/gnome-shell in order to + recover the situation. + + [ Test case ] + + Plug an external monitor to a laptop, with the external monitor on the + right side and configure the externals primary monitor. + + Login and Logout + + Gnome shell shouold not crash. + + [ Regression Potential ] + + The dock won't be temporarily shown in a monitor + + + --- + To replicate on Artful daily on a laptop, plug in an external monitor with the external monitor to the right of the laptop and configure the external monitor as the primary display. On configuration it works ok, but on logging out and back in gnome-shell crashes. The problem is only seen if the external monitor is the primary display. I think it likely that this is the same issue reported for dash-to-dock: https://github.com/micheleg/dash-to-dock/issues/493 - ProblemType: Bug - DistroRelease: Ubuntu 17.10 + ProblemType: BugDistroRelease: Ubuntu 17.10 Package: gnome-shell-extension-ubuntu-dock 0.3 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 23 20:29:17 2017 InstallationDate: Installed on 2017-08-22 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170821) - PackageArchitecture: all - SourcePackage: gnome-shell-extension-ubuntu-dock + PackageArchitecture: allSourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712661 Title: gnome-shell crash using ubuntu-dock with dual monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1712661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785126] Re: package shim-signed 1.34.9.2+13-0ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785126 Title: package shim-signed 1.34.9.2+13-0ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1785126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785126] [NEW] package shim-signed 1.34.9.2+13-0ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: occurred during auto-update cycle ProblemType: Package DistroRelease: Ubuntu 18.04 Package: shim-signed 1.34.9.2+13-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or directory: '/proc/sys/kernel/moksbstate_disabled' ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: chromium-codecs-ffmpeg-extra:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu Aug 2 06:33:51 2018 DpkgHistoryLog: Start-Date: 2018-08-02 06:33:30 Commandline: /usr/bin/unattended-upgrade Upgrade: chromium-codecs-ffmpeg-extra:amd64 (67.0.3396.99-0ubuntu0.18.04.1, 68.0.3440.75-0ubuntu0.18.04.1) EFITables: Jul 22 21:16:41 opiumden kernel: efi: EFI v2.00 by American Megatrends Jul 22 21:16:41 opiumden kernel: efi: SMBIOS=0xcf63bd98 ACPI=0xcf5d5000 ACPI 2.0=0xcf5d5000 MPS=0xfcb60 Jul 22 21:16:41 opiumden kernel: secureboot: Secure boot could not be determined (mode 0) Jul 22 21:17:31 opiumden fwupd[2122]: disabling plugin because: failed to startup uefi: UEFI firmware updating not supported ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-06-16 (47 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: shim-signed Title: package shim-signed 1.34.9.2+13-0ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785126 Title: package shim-signed 1.34.9.2+13-0ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1785126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
