[Bug 1820866] Re: File dialog extremely slow scanning network mounts
Ubuntu 20.04 does not have this problem any more. I did a few tests (even shutting down the server for which I had a share bookmarked). The various different scenarios I tested all behaved as I would expect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820866 Title: File dialog extremely slow scanning network mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1820866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828273] Re: Framebuffer setting in GRUB_CMDLINE_LINUX_DEFAULT has no effect
Yet another comment I found said that the following would work, but it did not: systemctl set-default -f multi-user.target Take into account that this is Ubuntu Server 18.04. Server operating system should not rely on graphics cards, so it should be possible to boot Ubuntu Server without a framebuffer. Is there a systemd service which I can blacklist to avoid the framebuffer being created? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828273 Title: Framebuffer setting in GRUB_CMDLINE_LINUX_DEFAULT has no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1828273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828273] Re: Framebuffer setting in GRUB_CMDLINE_LINUX_DEFAULT has no effect
Found another page stating that vga=0 should be in GRUB_CMDLINE_LINUX_DEFAULT - this does not work either. Another page states that you should enable GRUB_TERMINAL=console, this does not work. Another page says you should add "blacklist vga16fb" in /etc/modprobe.d /blacklist-framebuffer.conf, this does not work Is there any way I can destroy /dev/fb0 or onload efifb after Linux has booted? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828273 Title: Framebuffer setting in GRUB_CMDLINE_LINUX_DEFAULT has no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1828273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828273] Re: Framebuffer setting in GRUB_CMDLINE_LINUX_DEFAULT has no effect
I found another comment online and tried it: I added "blacklist efifb" to /etc/modprobe.d/blacklist-framebuffer.conf. I then executed "update- initramfs -u" followed by "update-grub" and rebooted. Still no joy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828273 Title: Framebuffer setting in GRUB_CMDLINE_LINUX_DEFAULT has no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1828273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828273] [NEW] Framebuffer setting in GRUB_CMDLINE_LINUX_DEFAULT has no effect
Public bug reported: I have an Ubuntu Server 18.04 installation with KVM and a guest OS to which a AMD video card needs to be passed through. It worked great for about 9 months and after a recent Ubuntu upgrade, efifb grabs the video card irrespective of the linux command line. The commnand line that worked before is: GRUB_CMDLINE_LINUX_DEFAULT="amd_iommu=on iommu=pt pci_stubs=1106:3483 vga=normal nofb nomodeset video=efifb:off" Currently, this is the command line (changes I made based on searching the web for hours): GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on iommu=pt earlymodules=vfio-pci pci_stubs=1106:3483 vga=normal nofb nomodeset video=vesafb:off,efifb:off gfxpayload=text" The current active kernel options (proc/cmdline) BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=a83137ad-9598-4dc2-aca9-7ab19d17d3c0 ro quiet amd_iommu=on iommu=pt earlymodules=vfio-pci pci_stubs=1106:3483 vga=normal nofb nomodeset video=vesafb:on,efifb:off gfxpayload=text This is verified by syslog: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=a83137ad-9598-4dc2-aca9-7ab19d17d3c0 ro quiet amd_iommu=on iommu=pt earlymodules=vfio-pci pci_stubs=1106:3483 vga=normal nofb nomodeset video=vesafb:on,efifb:off gfxpayload=text According to one of the web sites I found, any (or all) of the following options should disable the frame buffer: vga=normal nofb nomodeset video=vesafb:on,efifb:off Yet, a framebuffer is still created crw-rw 1 root video 29, 0 May 8 18:26 /dev/fb0 Memory locked by efifb (grep -B 5 -A 5 "26[:]00" /proc/iomem) e000-fec2 : PCI Bus :00 e000-f01f : PCI Bus :26 e000-efff : :26:00.0 e000-e01e : efifb f000-f01f : :26:00.0 f000-f01f : vfio-pci Yet, vfio driver is successfully loaded for this device: (ls /sys/bus/pci/drivers/vfio-pci/) /sys/bus/pci/drivers/vfio-pci/:26:00.0 /sys/bus/pci/drivers/vfio-pci/:26:00.1 Any help on how efifb can be blocked from loading will be greatly appreciated. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: grub2-common 2.02-2ubuntu8.13 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 8 19:32:36 2019 InstallationDate: Installed on 2017-01-12 (846 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: grub2 UpgradeStatus: Upgraded to bionic on 2018-09-27 (223 days ago) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 bionic urgent -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828273 Title: Framebuffer setting in GRUB_CMDLINE_LINUX_DEFAULT has no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1828273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827493] [NEW] Radeon RX560 driver does not install on KVM guest
Public bug reported: System information: Ubuntu 18.04 LTS (server edition) with kernel 4.15.0-47-generic x86_64 Software: qemu-kvm: Installed: 1:2.11+dfsg-1ubuntu7.12 Hardware: Motherboard: X370 Killer SLI CPU: AMD Ryzen 7 1800X PCI device: 26:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/560] (rev e5) 26:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aae0 This server has a Windows 10 pro guest OS which has two PCI devices passed to it. This pass-through has worked fine for just over nine months after a problem (launchpad bug 1781891) experienced when upgrading from Ubuntu 17.10. Fortunately with the help of people responding the the bug report, the problem was resolved. Unfortunately after some upgrades (Windows guest upgrades, upgrade to RDP server on Windows guest as well as apt upgrades on the host OS), the GPU of the passed-through AMD RX560 was not used by the CAD system (BricsCAD and BricsCAD shape) any more. The GPU was still listed on the task manager under the Performance tab. In order to fix the problem, I uninstalled the Radeon driver, downloaded the latest version and tried to install it. The installation did not complete after several attempts, each time hanging the Windows guest OS to the point where I had to reset the guest. I also tried to re-install the older version (of which I kept the installer). Also note that I had to use the cleanup application shipped with the AMD Radeon driver and reboot before attempting a fresh install. During some of the attempts, I had to remove the PCI devices from the guest in order to get Windows booting again - at which time I have the opportunity to clean up the AMD drivers before rebooting with PCI devices passed through again. At this time I need instructions to get the proper logging for someone to help me figure out where the problem is. So please advise on how to get any relevant information. From a previous bug report, I was able to determine a memory clash between host and client by issuing the following command: grep -B 5 -A 5 "26[:]" /proc/iomem However, at this point I am not getting any results. This may be because I need to do this just after attempting a driver install. Please advise if this is the case. Any help would be greatly appreciated. ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: urgent ** Project changed: launchpad-report-tool => qemu-kvm (Ubuntu) ** Summary changed: - Radeon RX560 driver does not install on KVM client + Radeon RX560 driver does not install on KVM guest -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827493 Title: Radeon RX560 driver does not install on KVM guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1827493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820866] [NEW] File dialog extremely slow
Public bug reported: >From any application where you have a "save as" or "open" option, the dialog displays, but it takes forever. I have a i5 with 16GB RAM and 2 SSD's, so the machine is not slow. However, if I use gedit and click open / Other documents it takes 6 to 7 seconds before the file dialog is properly displayed. This does not even get better with reuse. I opened gedit just now and the first time it took 7 seconds. Then I pressed Cancel and repeated the process - it still took more than 6 seconds before the dialog was properly displayed. Often I would only see "Other locations" and then default places (Home, Documents etc) and bookmarks (I have about 8 bookmarks of which 2 are network shares) are displayed. These items are added one by one - maybe one every half second. Often it takes a few seconds before the first location other than "Other Locations" is displayed. Even the file panel is not immediate at first and you can see how lines are added one by one. Take into account that my home folder is on an SSD, so populating a file list should be lightning fast. I have looked at the CPU activity, but it does not go over about 10% during display of open and close dialogs. Just be aware that this is not specific to gedit - all applications using gnome file dialog has the same problem. Please see the attached screen recording. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 19 16:14:16 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['nohotcor...@azuri.free.fr', 'weather-extens...@xeked.com', 'openweather-extens...@jenslody.de']" b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2018-12-02 (107 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 bionic ** Attachment added: "Screen recording of gedit open and close" https://bugs.launchpad.net/bugs/1820866/+attachment/5247541/+files/slow%20screen.mkv -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820866 Title: File dialog extremely slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798251] Re: Cannot boot from USB pen drive
** Package changed: linux (Ubuntu) => usb-creator (Ubuntu) ** Changed in: usb-creator (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798251 Title: Cannot boot from USB pen drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1798251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798251] Re: Cannot boot from USB pen drive
I have been able to successfully create a USB drive that boots Ubuntu 18 ISO images. The web site that I used for information is https://www.splitbrain.org/blog/2012-12/22-the_ultimate_usb_stick_setup . I had to make a few changes to grub.cfg. I will attach a zip file containing the contents of the usb drive with empty files in stead of complete iso files. I have not tested the drive with various hardware configurations or BIOS settings, but it should have enough information to be able to build an application to easily create a tool to build the USB drive. The partition is FAT32 and contains an (msftdata) flag - which might be left over from using Rufus on Windows (partion name is "Microsoft Basic Data"). However, I think performing a grub install should work as well. ** Attachment added: "Contents required on USB drive that allows booting ISO images" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798251/+attachment/5202059/+files/usb-boot-iso.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798251 Title: Cannot boot from USB pen drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798251] Re: Cannot boot from USB pen drive
I just tried booting the USB drive of ubuntu-18.04-desktop-amd64.iso on a different workstation. The drive was picked up for the boot menu and the grub boot menu was displayed. I selected "Try Ubuntu without installing" and it seemed to start booting (flash screen appeared). Then after a while it dropped down to BusyBox. The message it gave might be of some help: "(initramfs) Unable to find medium containing a live file system". I then switched off the PC and booted again. This time I selected "Install Ubuntu" from the grub boot menu, but it dropped down to BusyBox again with the same message. If there is any way I can get more information from BusyBox, please let me know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798251 Title: Cannot boot from USB pen drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798251] [NEW] Cannot boot from USB pen drive
Public bug reported: I have not been able to successfully create a bootable USB flash drive for about two years using modern desktop versions of Ubuntu. This weekend I tried again by booting from an Ubuntu Desktop 18.04 amd64 workstation and using ubuntu-18.04-desktop-amd64.iso. The qemu test run seemed to boot, but after a while the boot splash screen just remained open. The PC I intended to do a clean install on simply dropped down to BusyBox. I tried various BIOS settings such as booting from UEFI, booting from legacy etc with no success. In the past I got different results on different workstations, but never got a USB stick booting (I forgot which version of Ubuntu this started becoming an issue, because I have created USB boot disks for older versions of Ubuntu many times). I have tried UNetbootin, MultiWriter, usb-creator-gtk and even tried Rufus on a Windows VM on KVM. None of the options worked (actually, UNetbootin did not even start up correctly). Up to now the workstations I built up had DVD drives, so I simply made a bootable CD - which has never let me down. However this last workstation did not have a DVD drive so in the end I booted Ubuntu 16.04 which it had installed on a different drive and used grml-rescueboot to boot the ISO and perform the installation. If you google "Ubuntu does not boot from usb" you will find that it seems there this is an existing issue for many people. I would seriously consider having a standard USB image with grml preinstalled and allowing users to put whichever ISO they want to boot in a specific folder on the USB drive. There are a number of web sites explaining how to create a USB drive which is bootable in both UEFI and Legacy modes, and since Windows 10 ships on a single USB pen drive it should be totally possible to have a solution for Linux as well. ** Affects: linux (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/1798251 Title: Cannot boot from USB pen drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781891] Re: PCI USB card passthrough does not work any more
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1781891 Title: PCI USB card passthrough does not work any more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781891] Re: PCI USB card passthrough does not work any more
Thanks. Some very good news: In a previous message I asked how I could get back to having USB card controlled by Linux USB driver. I still cannot tell whether a recent kernel upgrade bought about the change, but Linux is still handing over the device to vfio (without me changing anything in etc) and I figured out the driver problem. I tried to get a VIA driver, because I looked at the output of lspci where in I should have looked at the card manufacturer. Got the correct driver and all is good now - all attached USB drivers works as they did before the upgrade to Ubuntu 18.04. I did a complete shut down of the server and even removed the power supply as well to ensure that all hardware do a complete reset and after booting up again everything still worked as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781891] Re: PCI USB card passthrough does not work any more
First let me thank you for your quick and informative and very helpful responses. Installing the mainline kernel is not really an option for the following reason: The server is at a client and was built about a month before Ubuntu 18.04 was released, so I opted to install Ubuntu Server 17.10 to get the latest updates in KVM and then upgrade to 18.04 as soon as it became available. This upgrade lead to PCI graphics adapter not forwarded (needed for 3D graphics used on VM) as well as the USB PCI card and it caused. Fortunately Christian got my heart rate back to normal after pointing out how I could fix the Graphics pass-through (which was at the time crucial to get the office firing on all cylinders). In the mean time I used other solutions to get round a number of USB issues (including falling back to a old VirtualBox VM for one application and using Dosbox for interfacing with a USB to Serial device). So at this point I am reluctant to try a kernel that is not released via the Ubuntu repositories as I think you can understand. How long do you think it will take for this current mainline kernel release you meniuned to make its way into Ubuntu repositories? There is one side effect of the USB pass-through that I don't think I have mentioned to now, but I am not very clear on its relevance and even if this is a real issue. Every time I have ever worked with USB devices, I always relied on the USB device ID (e.g. 1d6b:0002). For some peculiar reason in the Windows 10 pro VM this ID is nowhere to be found when going through the device properties in the device manager. I only saw this after trying to identify the correct USB device for updating a driver and it might be that Windows just never show the ID, or it could be because of changes to the way USB devices connected to a USB controller card is now shared to a VM when only the card is passed to the VM using pass-through. The most likely explanation is that I try to steer clear of Windows wherever possible and therefore does not know too much on what to expect when I am faced with a situation where I have to look deeper. In any event, you would know best what to make of this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781891] Re: PCI USB card passthrough does not work any more
I followed the instructions to unbind the device from xhci and bind it to vfio and afterwords I was able to boot the VM with the PCI card set up as pass-through. However, the Windows VM only listed it as an unknown PCI device and could not find the device drivers (VIA VL805) and I could not find any driver on the internet, so I tried to roll back the changes so that the one USB device that did work could still work. This is where I am stuck now since a reboot does not load the xhci device as before. I was under the impression unloading the device using the given instructions would only change it until I reboot since I have not changed anything in etc. I tried binding it to xhci again, but could not. I would really appreciate some help getting it back to how it was since I can only do these tests after hours. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781891] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1781891/+attachment/5164573/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781891] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1781891/+attachment/5164575/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781891] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1781891/+attachment/5164578/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781891] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1781891/+attachment/5164574/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781891] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1781891/+attachment/5164572/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781891] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1781891/+attachment/5164576/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781891] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1781891/+attachment/5164577/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781891] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1781891/+attachment/5164568/+files/Card0.Codecs.codec.0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781891] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1781891/+attachment/5164567/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781891] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1781891/+attachment/5164571/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781891] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1781891/+attachment/5164570/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781891] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1781891/+attachment/5164569/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781891] Re: PCI USB card passthrough does not work any more
apport information ** Tags added: apport-collected ** Description changed: System information: Ubuntu 18.04 LTS (server edition) with kernel 4.15.0-24-generic x86_64 Upgraded from Ubuntu server 17.10 Software: qemu-kvm: Installed: 1:2.11+dfsg-1ubuntu7.4 Candidate: 1:2.11+dfsg-1ubuntu7.4 Version table: *** 1:2.11+dfsg-1ubuntu7.4 500 500 http://za.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:2.11+dfsg-1ubuntu7.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:2.11+dfsg-1ubuntu7 500 500 http://za.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Hardware: Motherboard: X370 Killer SLI CPU: AMD Ryzen 7 1800X PCI device: 27:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) IOMMU Group 15 27:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483] (rev 01) USB controller of PCI card: Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Loaded device drivers: Before upgrading to Ubuntu 18.04, this PCI device was added to pci-stub.ids which allowed the device to be passed to a Windows 10 VM. In turn, all USB devices connected to this card worked in the VM and drivers could successfully be installed. Since the upgrade from Ubuntu 17.10 to Ubuntu 18.04, I have tried several approaches to have this device not bound to the xhci driver but all in vain. (In every test I did, I always performed update-initramfs -u as well as update-grub) pci-stub.ids does not stop xhci from grabbing device. So passing PCI card to VM does not work Adding the device ID to /etc/modprobe.d/vfio.conf (options) does seem to load the connect the vfio driver to it, but xhci still binds to it as well, so passing PCI device to VM does not work. Adding ":27:00.0,xhci" to /etc/unbindpci also did not work. By adding the USB controller to the VM, USB devices connected to it does seem to be USB devices on the VM, but some of the drivers does not load correctly in Windows 10. For example, I need to install a device driver for a ROCKEY4 USB dongle and even though the driver installs (which must be done with device disconnected), the driver does not seem to ever bind correctly to the device because the software that uses the dongle does not recognise it. I have successfully bound a PCI graphics adapter to the VM, so in principle PCI passthrough works, bit in the case of the USB PCI card there seems to be no way to pass the device to a VM. Expected result: - PCI passthrough should be available to all types of PCI devices and - instructions should be available from qemu or kvm documentation even - though it involves different parts of the OS (such as making use of - /etc/modprobe/vfio.conf, /etc/unbindpci etc) + PCI passthrough should be available to all types of PCI devices and instructions should be available from qemu or kvm documentation even though it involves different parts of the OS (such as making use of /etc/modprobe/vfio.conf, /etc/unbindpci etc) + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-24-generic. + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7.1 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' + Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=087ca1e6-4fd0-4a4b-a323-8b8ce733b3c7 + InstallationDate: Installed on 2018-03-14 (124 days ago) + InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + Lsusb: + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + MachineType: QEMU Standard PC (i440FX + PIIX, 1996) + Package: linux (not installed) + ProcFB: 0 qxldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=0286b7bc-6ce2-494c-89aa-6c4402876bad ro + ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-24-generic N/A + linux-backports-modules-4.15.0-24-generic N/A + linux-firmware 1.173 + RfKill: Error: [Errno 2]
[Bug 1781891] [NEW] PCI USB card passthrough does not work any more
Public bug reported: System information: Ubuntu 18.04 LTS (server edition) with kernel 4.15.0-24-generic x86_64 Upgraded from Ubuntu server 17.10 Software: qemu-kvm: Installed: 1:2.11+dfsg-1ubuntu7.4 Candidate: 1:2.11+dfsg-1ubuntu7.4 Version table: *** 1:2.11+dfsg-1ubuntu7.4 500 500 http://za.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:2.11+dfsg-1ubuntu7.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:2.11+dfsg-1ubuntu7 500 500 http://za.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Hardware: Motherboard: X370 Killer SLI CPU: AMD Ryzen 7 1800X PCI device: 27:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) IOMMU Group 15 27:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483] (rev 01) USB controller of PCI card: Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Loaded device drivers: Before upgrading to Ubuntu 18.04, this PCI device was added to pci-stub.ids which allowed the device to be passed to a Windows 10 VM. In turn, all USB devices connected to this card worked in the VM and drivers could successfully be installed. Since the upgrade from Ubuntu 17.10 to Ubuntu 18.04, I have tried several approaches to have this device not bound to the xhci driver but all in vain. (In every test I did, I always performed update-initramfs -u as well as update-grub) pci-stub.ids does not stop xhci from grabbing device. So passing PCI card to VM does not work Adding the device ID to /etc/modprobe.d/vfio.conf (options) does seem to load the connect the vfio driver to it, but xhci still binds to it as well, so passing PCI device to VM does not work. Adding ":27:00.0,xhci" to /etc/unbindpci also did not work. By adding the USB controller to the VM, USB devices connected to it does seem to be USB devices on the VM, but some of the drivers does not load correctly in Windows 10. For example, I need to install a device driver for a ROCKEY4 USB dongle and even though the driver installs (which must be done with device disconnected), the driver does not seem to ever bind correctly to the device because the software that uses the dongle does not recognise it. I have successfully bound a PCI graphics adapter to the VM, so in principle PCI passthrough works, bit in the case of the USB PCI card there seems to be no way to pass the device to a VM. Expected result: PCI passthrough should be available to all types of PCI devices and instructions should be available from qemu or kvm documentation even though it involves different parts of the OS (such as making use of /etc/modprobe/vfio.conf, /etc/unbindpci etc) ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Attachment added: "loaded drivers" https://bugs.launchpad.net/bugs/1781891/+attachment/5164106/+files/pci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781891 Title: PCI USB card passthrough does not work any more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1781891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776269] Re: Installer causes VM to be paused
Thanks. This put me on the right track and I was able to solve the problem. I will summarise the steps I took. (The PCI address in my case is 26:00.0 - take that into account when reading further) On the KVM host, execute the following: dmesg | grep -i 'vfio.*26[:]00' This produced the following: vfio-pci :26:00.0: BAR 0: can't reserve [mem 0xe000-0xefff 64bit pref] These entries indicates that the VM cannot access all IO memory of the PCI device. To find out which module grabbed the IO memory, do the following in the KVM host: grep -B 5 -A 5 "26[:]00" /proc/iomem This had the following entry: e000-e01e : efifb This address block is inside the block that could not be reserved for the VM and efifb (EFI Frame Buffer) grabbed this memory. In my case, the PCI device was also the primary device configured for the PC in EFI. It could also be be vesafb (VESA Frame Buffer). The vesafb or efifb uses this address block for virtual consoles. (See /sys/class/vtconsole/vtcon0 and vtcon1). I tried the following options from the given references: echo 0 > /sys/class/vtconsole/vtcon0/bind echo 0 > /sys/class/vtconsole/vtcon1/bind reboot - this did not solve the problem I also tried a solution which requires that edit /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT=" video=vesa:off,efifb:off" update-initramfs -u update-grub reboot - this did not solve the problem either Then I some more options: GRUB_CMDLINE_LINUX_DEFAULT=" vga=normal nofb nomodeset video=efifb:off" update-initramfs -u update-grub reboot - this solved the problem and after reboot efifb did not lock that address range any more. Reference: https://support.digium.com/community/s/article/How-to- disable-the-Linux-frame-buffer-if-it-s-causing-problems -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776269 Title: Installer causes VM to be paused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1776269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776269] Re: Installer causes VM to be paused
How difficult would it be to have a PPA repository with the qemu / libvirt version that was distributed with 17.10? I know that 18.04 is an LTS and therefore big software changes will not happen. I have to rebuild a server and install 17.10 if I do not get a solution to this process quickly. Any help would be greatly appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776269 Title: Installer causes VM to be paused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1776269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776269] Re: Installer causes VM to be paused
Sorry about the attachment. The POST timed out and I had to go back on browser and submit again. I think the attachment got lost in the process. ** Attachment added: "Logs" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1776269/+attachment/5151593/+files/bug-detail.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776269 Title: Installer causes VM to be paused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1776269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776269] [NEW] Installer causes VM to be paused
Public bug reported: Ubuntu 4.15.0-23.25-generic 4.15.18 Linux sbri19 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I have an Ubuntu 18.04 Server with a Windows 10 VM with AMD Graphics card passthrough. The driver happily installed and worked like a charm in Ubuntu Server 17.10. The server was built just before Ubuntu 18.04 was released and Ubuntu Server 17.10 was installed as a temporary measure. After upgrading to Ubuntu Server 18.04, I had to reinstall the AMD driver. Unfortunately, the VM goes into PAUSE mode during the driver installation (hardware detected without a problem). To resume the VM, it needs to be reset. The attachments show the log of the VM as well as the error when trying to resume the VM after it has been paused. Ubuntu 18.04 has libvirt 4.0.0, and Ubuntu 17.10 had libvirt 3.6, so this seems to be a bug that slipped in. Since Libvirt is already on version 4.4, is there a ppa repository with a later version which I can test so see if the bug has been resolved? ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => qemu (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776269 Title: Installer causes VM to be paused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1776269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769309] Re: Ubuntu 18.04 boot extremely slow
Although I did not get the same entry in dmesg as Tonio, it did point me towards dmesg. So I have attached my dmesg ouput. I have listed the parts where significant time is somehow lost (please note that I am not an expert and therefore I am not able to tell where exactly the gdm login screen appeared). #1 [2.780216] clocksource: Switched to clocksource tsc [ 34.422902] random: crng init done #2 [ 40.242284] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null) [ 128.816712] audit: type=1400 audit(1525590690.456:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/snap/core/4486/usr/lib /snapd/snap-confine" pid=1126 comm="apparmor_parser" #3 [ 135.805543] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready [ 166.755990] ata4: exception Emask 0x10 SAct 0x0 SErr 0x409 action 0xe frozen #4 [ 171.739128] rfkill: input handler disabled [ 193.135040] FS-Cache: Loaded #5 & 6 [ 193.148640] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [ 261.690048] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [ 467.025578] kauditd_printk_skb: 48 callbacks suppressed ** Attachment added: "dmesg output" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1769309/+attachment/5134700/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769309 Title: Ubuntu 18.04 boot extremely slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1769309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769309] [NEW] Ubuntu 18.04 boot extremely slow
Public bug reported: I have upgraded Ubuntu 16.04 (amd64) using Gnome as desktop to Ubuntu 18.04. Ubuntu 16.04 took just over 20 seconds from the time a selection on the Grub boot menu was made until the login screen was displayed. On Ubuntu 18.04 it takes about 20 seconds (from Grub menu) to display the boot splash screen and in total it takes about 2min 30sec until the login menu (gdm) is displayed. Expected behaviour: I would expect a new LTS release to have a similar boot time than the previous release. At this time I am experiencing boot times slower that those I had a few years ago from a traditional hard drive (which used to be just under 2min) Additional information: I have recently built two Ubuntu servers (17.10 in expectation of upgrading to 18.04 upon release). I found that the boot process went fairly smooth right until the end where it seems to wait for about a minute for what seems to be a network connection. After that wait period the text login prompt is displayed. So I am guessing that there might be a service start timeout which blocks the process. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic $ uname -a Linux popeye 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Boot log" https://bugs.launchpad.net/bugs/1769309/+attachment/5134222/+files/boot.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769309 Title: Ubuntu 18.04 boot extremely slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1769309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751230] Re: libc_bin package broken
** Attachment added: "Run this after installing the rebuilt package" https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1751230/+attachment/5060991/+files/postinst -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751230 Title: libc_bin package broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1751230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751230] [NEW] libc_bin package broken
Public bug reported: After an upgrade, I got this problem: dpkg: error processing package libc-bin (--configure): subprocess installed post-installation script returned error exit status 139 During several retries and trying several possible solutions I found on the internet, I have seen this as well: Segmentation fault This bug was reported in earlier versions of Ubuntu (as far back as 2011). None of the suggestions worked - they included: apt -f install dpkg --configure -a apt autoremove apt autoclean apt clean One solution suggested to remove the broken package, but that would have meant breaking Ubuntu. I created the following a workaround: Download the deb file (libc-bin_2.23-0ubuntu10_amd64.deb) from ubuntu package web site (https://packages.ubuntu.com) and save it in /tmp. Trying to install this deb will not work. Extract the contents into an empty folder (e.g. /tmp/fix). With mc (midnight commander) this is pretty easy, but here are some commands that might help. mkdir -p /tmp/fix/DEBIAN cd /tmp/fix ar x ../libc-bin_2.23-0ubuntu10_amd64.deb tar -xf data.tar.gz cd /tmp/fix/DEBIAN tar -xf ../control.tar.gz cd /tmp rm control.tar.gz rm data.tar.gx In the end, you need to have etc, sbin, usr and DEBIAN folders in /tmp/fix. If you used mc, you might have INFO and INSTALL - you can delete them. Move DEBIAN/postinst to some other place (e.g. /tmp) Now rebuild the package without the postinst script. cd /tmp dpkg --build /tmp/fix You should now have package called build.deb in /tmp. You need to rename it, so use this command: mv /tmp/build.deb /tmp/fix/libc-bin_2.23-0ubuntu10_amd64.deb Now install this file: dpkg -i tmp/fix/libc-bin_2.23-0ubuntu10_amd64.deb (it should not cause any problems) Now run the script that was supposed to be run by the installer: bash /tmp/postinst Ok, so now you can continue working until the problem has been sorted out. I attached the repackaged deb - please verify your architecture and version before using it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libc-bin 2.23-0ubuntu10 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Feb 23 10:54:34 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 SourcePackage: glibc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glibc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Patch added: "dep package rebuilt without postinst" https://bugs.launchpad.net/bugs/1751230/+attachment/5060987/+files/libc-bin_2.23-0ubuntu10_amd64.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751230 Title: libc_bin package broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1751230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 900384] Re: usbipd requires usbip_common_mod.ko and usbip.ko kernel modules, which are not available in any package
Finally got it! linux-tools-generic needs to commands to be executed after install: ln -s /usr/lib/linux-tools/$(uname -r)/usbip /usr/sbin/usbip ln -s /usr/lib/linux-tools/$(uname -r)/usbipd /usr/sbin/usbipd By doing this, root will have usbip and usbipd in its executable path -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/900384 Title: usbipd requires usbip_common_mod.ko and usbip.ko kernel modules, which are not available in any package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/900384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 900384] Re: usbipd requires usbip_common_mod.ko and usbip.ko kernel modules, which are not available in any package
Just tried it on Ubuntu 16.04 with kernel 4.4.0-112 and the problem persists. It is now more than 6 years - yes 6 YEARS - since this problem has been logged. And no, linux-tools-generic does not solve the problem. It does not contain libusb, libusbd, usbip_common_mod.ko or usbip.ko. According to ubuntu package search linux-tools-generic only contains a changelog.gz and copyright. I think it is safe to say this project is dead in the water, since nobody seems interested in solving the actual problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/900384 Title: usbipd requires usbip_common_mod.ko and usbip.ko kernel modules, which are not available in any package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/900384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1698806] [NEW] Apache dbd auth configuration error
Public bug reported: OS: Ubuntu 1604 Apache2: 2.4.18-2ubuntu Using DBD authentication using a Postgresql database for specific files seems impossible. The following configuration entries seems only to be allowed in global area (VirtualHost element) of a host definition. Putting it in a element causes Apache not to start up: DBDriver pgsql DBDParams "host=127.0.0.1 port=5432 dbname=userdb user=www password=www" DBDMin 2 DBDKeep 4 DBDMax 10 DBDExptime 300 The AuthDBDUserPWQuery parameter is not allowed in VirtualHost element. It causes "AuthDBDUserPWQuery not allowed here" on apache startup. Putting it in a element is allowed, but if I then try to activate this authentication via a .htaccess file, It produces "AH01654: No AuthDBDUserPWQuery has been specified" in error log. I AuthDBDUserPWQuery is defined in either the global section or in a element causes ".htaccess: AuthDBDUserPWQuery not allowed here" in error log. Adding any of DB... parameters listed earlier in .htaccess also does not work. So it seems there is no way to configure DBD authentication. ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New ** Tags: apache2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698806 Title: Apache dbd auth configuration error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1698806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1698758] [NEW] Encrypted password causes segmentation fault
Public bug reported:
I have configured a .htaccess to use libapache2-mod-auth-pgsql to
authenticate a user against a postgres database. The settings are as
follows:
AuthType basic
AuthName "My Auth"
Require valid-user
AuthBasicProvider pgsql
Auth_PG_authoritative On
Auth_PG_host 127.0.0.1
Auth_PG_port 5432
Auth_PG_user www
Auth_PG_pwd password
Auth_PG_database userdb
Auth_PG_encrypted off
Auth_PG_pwd_table UserLogin
Auth_PG_uid_field Username
Auth_PG_pwd_field ApachePassword
If I set Auth_PG_encrypted to off, then authentication works but the
downside is that I have to save plain unencrypted password on the
database. If I set Auth_PG_encrypted to on, a segmentation fault occurs.
A typical password to be contained in ApachePassword field is the
following (for password "password"): "{SHA}W6ph5Mm5Pz8GgiULbPgzG37mj9g="
- This matches exactly to what would be generated by htpasswd -s.
Here is the error log entry I get:
[pid 9662] AH00052: child pid 9670 exit signal Segmentation fault (11)
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apache2 2.4.18-2ubuntu3.2
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
Apache2ConfdDirListing: False
Apache2Modules:
Error: command ['/usr/sbin/apachectl', '-D DUMP_MODULES'] failed with exit
code 1: [Mon Jun 19 09:48:04.146971 2017] [so:warn] [pid 8403] AH01574: module
dav_module is already loaded, skipping
apache2: Syntax error on line 140 of /etc/apache2/apache2.conf: Syntax error
on line 2 of /etc/apache2/mods-enabled/session_dbd.load: Cannot load
/usr/lib/apache2/modules/mod_session_dbd.so into server:
/usr/lib/apache2/modules/mod_session_dbd.so: undefined symbol:
ap_hook_session_save
Action '-D DUMP_MODULES' failed.
The Apache error log may have more information.
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Mon Jun 19 09:47:34 2017
SourcePackage: apache2
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apache2.apache2.conf: [modified]
modified.conffile..etc.apache2.mods-available.dav.load: [modified]
modified.conffile..etc.apache2.sites-available.000-default.conf: [modified]
mtime.conffile..etc.apache2.apache2.conf: 2017-06-03T16:27:12.439856
mtime.conffile..etc.apache2.mods-available.dav.load: 2017-06-03T16:31:51.028040
mtime.conffile..etc.apache2.sites-available.000-default.conf:
2016-11-11T14:57:50
** Affects: apache2 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698758
Title:
Encrypted password causes segmentation fault
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1698758/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642598] [NEW] Nemo memory leak
Public bug reported: Nemo either has a memory leak or very bad memory management. Ubuntu 16.04 comes to a grinding halt on a PC with Nemo installed. This happened a number of times the last week (since nemo was installed because of its ability to have dual panes). The PC is switched off every night and some time during the day it becomes slower and slower until it comes to a grinding halt. This last time I was informed and was able to SSH in before the system completely died. Memory consumption was 100% and I had to kill some other app in order to open top. Nemo used 3.2GB at the time and after killing it, the system became responsive again. Additional information that may be helpful: A smb share is used to access all company data from a central server. I have read about memory issues in Nemo and one person seems to think it is a thumbnail issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nemo 2.8.6-2 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 17 15:24:30 2016 InstallationDate: Installed on 2015-11-10 (373 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140807.1) SourcePackage: nemo UpgradeStatus: Upgraded to xenial on 2016-10-15 (32 days ago) ** Affects: nemo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 xenial ** Attachment added: "Grep nemo on both syslog and kern.log" https://bugs.launchpad.net/bugs/1642598/+attachment/4778627/+files/nemo-logs.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642598 Title: Nemo memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nemo/+bug/1642598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 794415] Re: Seg fault on launch
*** This bug is a duplicate of bug 753520 *** https://bugs.launchpad.net/bugs/753520 I have seen Remmina causing a segmentation fault on startup many times. I always had to fix it by changing the default locale to en_US. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/794415 Title: Seg fault on launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/794415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577341] [NEW] 180, 000 _XSERVTrans error log lines on single boot
Public bug reported: lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 uname -a Linux popeye 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux My PC booted in 18 seconds before upgrading to Ubuntu Gnome 16.04 - now it takes 2 minutes. I tried to find the culprit in the logs. There is a set of 4 lines that repeats abount 50,000 times (to be exact, a total of 179628 log lines containing "gdm-x-session[2329]: _XSERVTrans".) Although these entries are logged over a timespan of 4 seconds, I cannot but wonder how long syslog takes to acually log the individual entries to the /var/log/syslog file. In total, this adds 22MB of logging output to syslog. (By the way, my Gnome 3 session starts just fine, the log is just outrageous) What I expect to happen: Logging the same error as may times in such a short period indicates one of two problems: 1) If something fails (maybe some service is not ready yet), then allow more time before trying again - there is no point in taking away processing power if some service is trying to start up. 2) If it is an absolute necessity for the number of failures (there might be 50,000 small components all trying the same thing), then limit log output. Logging the 4 lines once, then adjust a counter which you then log once the process is complete. Here follows this first and last lines of just such a block of errors: May 2 10:10:55 popeye /usr/lib/gdm3/gdm-x-session[2329]: _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created. May 2 10:10:55 popeye /usr/lib/gdm3/gdm-x-session[2329]: _XSERVTransmkdir: ERROR: Cannot create /tmp/.X11-unix May 2 10:10:55 popeye /usr/lib/gdm3/gdm-x-session[2329]: _XSERVTransSocketUNIXCreateListener: mkdir(/tmp/.X11-unix) failed, errno = 13 May 2 10:10:55 popeye /usr/lib/gdm3/gdm-x-session[2329]: _XSERVTransMakeAllCOTSServerListeners: failed to create listener for unix May 2 10:10:55 popeye /usr/lib/gdm3/gdm-x-session[2329]: _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created. May 2 10:10:55 popeye /usr/lib/gdm3/gdm-x-session[2329]: _XSERVTransmkdir: ERROR: Cannot create /tmp/.X11-unix May 2 10:10:55 popeye /usr/lib/gdm3/gdm-x-session[2329]: _XSERVTransSocketUNIXCreateListener: mkdir(/tmp/.X11-unix) failed, errno = 13 May 2 10:10:55 popeye /usr/lib/gdm3/gdm-x-session[2329]: _XSERVTransMakeAllCOTSServerListeners: failed to create listener for unix ... ... ... May 2 10:10:58 popeye /usr/lib/gdm3/gdm-x-session[2329]: _XSERVTransOpen: transport open failed for unix/popeye:59533 May 2 10:10:58 popeye /usr/lib/gdm3/gdm-x-session[2329]: _XSERVTransMakeAllCOTSServerListeners: failed to open listener for unix May 2 10:10:58 popeye /usr/lib/gdm3/gdm-x-session[2329]: _XSERVTransSocketOpenCOTSServer: Unable to open socket for unix May 2 10:10:58 popeye /usr/lib/gdm3/gdm-x-session[2329]: _XSERVTransOpen: transport open failed for unix/popeye:59534 May 2 10:10:58 popeye /usr/lib/gdm3/gdm-x-session[2329]: _XSERVTransMakeAllCOTSServerListeners: failed to open listener for unix May 2 10:10:58 popeye /usr/lib/gdm3/gdm-x-session[2329]: _XSERVTransSocketOpenCOTSServer: Unable to open socket for unix May 2 10:10:58 popeye /usr/lib/gdm3/gdm-x-session[2329]: _XSERVTransOpen: transport open failed for unix/popeye:59535 May 2 10:10:58 popeye /usr/lib/gdm3/gdm-x-session[2329]: _XSERVTransMakeAllCOTSServerListeners: failed to open listener for unix ** Affects: gnome-session (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/1577341 Title: 180,000 _XSERVTrans error log lines on single boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1577341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1404779] Re: Hp Designjet 130 prints part of page then freezes
We have a HP-DesignJet 130 connected to Ubuntu 14.04 (upgraded from 12.04 in order to get plotter to work). The HP-DesignJet_130-cdnj500.ppd seems to be very close to a working solution. It seems as if all that is needed is for the buffer to be flushed and the paper ejected (manual load). All prints (from Ubuntu test page to BricsCAD printing to printing a PDF) prints almost the complete page and then stalls right at the end. My gut tells me that the printer needs a command at the end of a printout to flush whatever is in the buffer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1404779 Title: Hp Designjet 130 prints part of page then freezes To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1404779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1010349] Re: Evolution address book inaccessible without killing one time e-addressbook-factory
I have had this problem for some time using Thunderbird. I have a Google addressbook that I cannot remember creating. After reading these posts (especially killing e-addressbook-factory) I seemed to have solved it for me (a Thunderbird user). The Google address book dates back to the time I used evolution. So here is what I understand of the problem: The Google address book would always be empty (after opening Thunderbird and getting the message). But I could not delete it. After killing e-addressbook-factory and re-opening Thunderbird, the message was gone and the Google address book was filled. I could still not delete it though, because Thunderbird does not allow deleting a gnome- contacts folder (short version of message after trying to delete it). Even though I am not using evolution any more and have uninstalled it, evolution-data-server (package) was still installed and the gnome- contacts depends on it. However, I have always used Thunderbird for my contacts, so uninstalling evolution-data-server together with gnome- contacts would not seem to affect me. So how do I sync contacts with Google? Simple - I use Zindus Thunderbird plugin (and have been since I installed Thunderbird). This allows you to pick an addressbook to sync - in my case Personal Address Book. So I really do not need to have a Google address book in any case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1010349 Title: Evolution address book inaccessible without killing one time e -addressbook-factory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1010349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005766] [NEW] System boot hangs
Public bug reported: Since I installed 12.04 on my system, I have had the following problem consistently. I first tried to upgrade an installation on a mda raid1 partition, which simply would not boot. I then did a clean install of 12.04 on a normal ext4 partition, but I still have a mda raid1 with ext4 mounted as /home. I regularly install updates. Every evening I do a shutdown, since the area I live in has many power failures and the UPS would not sustain the machine for longer than 5 minutes. In the morning when I start up the pc, I get an all purple screen and the hard drive light is inactive. Then I press CTRL+AL+DEL to reboot the pc. Once it reboots, the GRUB menu appears and it starts to boot, but it informs me that the raid is not consistent, so I have the choice to continue booting with a degraded raid. I then select yes. By the time I am logged in, the raid drive is ok as you can see in the following output: $ cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md2 : active raid1 sdb4[1] sda4[0] 466366848 blocks [2/2] [UU] unused devices: none I then continue working the whole day without a single problem and shut down at night, simply to go through the same routine the next morning. On one or two occasions it booted up without the grub menu (as if it was in sleep or hibernate mode). This leads me to believe that a normal shutdown (either by gnome shutdown or the command line utility), does not do a proper shutdown, but in stead indicates that a sleep or hibernate state should be booted. Also, the fact that the raid drive consistently starts up in degraded mode only to be ready when I do an mdastat, leaves me to believe the raid drive is not shut down properly. From reports on the internet about mda problems in 12.04 in standard raid tests, I held back on this bug report, but now it is a month later and the problem still has not been resolved. ** Affects: upstart (Ubuntu) Importance: Undecided Status: New ** Tags: boot mda raid shutdown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005766 Title: System boot hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1005766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 429044] Re: USB barcode scanner (emulating keyboard) crashes with current kernel
According to comment on 2011-01-24 the bug fix was released. I am currently running and Linux 2.6.32-33 (Ubuntu 10.04) and the bug still seems to be present. I have tried 2 different Zebex scanners and some digits are consistently dropped. For instance a barcode 14010 yields 140. I have commented out the line blacklist usbkbd as mentioned earlier, but I still get FATAL: Module usbkbd not found. Seemingly the best description of the problem, I found here: http://web.archiveorange.com/archive/v/LLXmLhi1jH9FherdyRBK - according to this page, the author recognized that all key events were present, but because of the sequence (or maybe speed) some of the events are not translated into characters. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/429044 Title: USB barcode scanner (emulating keyboard) crashes with current kernel To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/429044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 429044] Re: USB barcode scanner (emulating keyboard) crashes with current kernel
I did another test on Ubuntu 11.04 (which I booted from an Ubuntu installation CD). I loaded the usbkbd module, unplugged the scanner and plugged it in again. No change whatsoever - still got 140 in stead of 14014. The exact same scanner works in a Windows XP POS system, but on 3 different computers with Linux installations it consistently misses characters. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/429044 Title: USB barcode scanner (emulating keyboard) crashes with current kernel To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/429044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400485] Re: Empathy sounds not in default ubuntu theme
It is a pity, really, to think that programmers have time to waste like this. Had it been me, I would have simply added an Ubuntu with sound scheme in 2009 when this bug was first reported. Yes, here we are in 2011 and the only time spent on the bug was posting 50 replies to this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/400485 Title: Empathy sounds not in default ubuntu theme -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 343421] Re: antspotlight crashed with SIGSEGV in exit()
I think the bug I experienced over the last month or two is linked to this. Often I would get back to the login screen in stead of the unlock screen after screen saver was activated (screen would be switched off at already at that time). This means all the programs in my session is closed. At first I thought the PC rebooted for some reason, but after checking process times (TIME+ in top), I determined the computer could not have rebooted. I then tried to find the screensaver that caused this (because I was using random screen saver). I would use a specific screensaver for a day or two and after using the first 6, the problem occurred on 50% of them. I don't know whether this would help, but it seems to me that the user session is terminated if there is an invalid exit condition on the screen saver. Would it not be possible to catch and log screen saver errors without loosing the user session? -- antspotlight crashed with SIGSEGV in exit() https://bugs.launchpad.net/bugs/343421 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 531027] Re: spurious warning at boot time that is unrelated to your actual problem
*** This bug is a duplicate of bug 532984 *** https://bugs.launchpad.net/bugs/532984 After getting GLib WARNING **: getpwuid_r(): failed due to unknown user id (0) on fresh install of Lubuntu 10.4 and reading lots of posts, I looked and /var/log/lxdm.log and found a message stating that no screens could be detected. I then found there was a rahter empty xorg.conf in /etc/X11. I renamed it to xorg.conf.bak and rebooted and whala - problem solved (for me at least). -- spurious warning at boot time that is unrelated to your actual problem https://bugs.launchpad.net/bugs/531027 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
