[Bug 1792247] [NEW] Setting the current directory to a subdirectory of $HOME
Public bug reported: I'm using Ubuntu 18.10 dev with mame 0.188+dfsg.1-0ubuntu2 and I noticed that MAME defines several directories in its ui.ini to be located in the current directory (which is the users home) and some of them like history are also automatically created if MAME is running. To not bloat up the users home directory it might make sense if mame.desktop would set the current directory to $HOME/.mame or $HOME/mame to avoid this issue. ** Affects: mame (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/1792247 Title: Setting the current directory to a subdirectory of $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mame/+bug/1792247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772975] Re: /lib/udev/ifupdown-hotplug is not executable
On checking this again with ifupdown 0.8.34ubuntu2 the file is now executable. ** Changed in: ifupdown (Ubuntu) Status: Confirmed => 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/1772975 Title: /lib/udev/ifupdown-hotplug is not executable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1772975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1489360] Re: đ Spaces after some unicode characters are looking like unicode placeholder characters
On testing this with Ubuntu 18.10 dev with unifont 1:11.0.01-1 I do not see this issue anymore on the flag at this site (the browser document, the tab title, the window title and the taskbar title are all fine). I also did test this on other sites with other characters where I did usually see this issue and I couldn't reproduce it there too. ** Changed in: unifont (Ubuntu) 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/1489360 Title: đ Spaces after some unicode characters are looking like unicode placeholder characters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unifont/+bug/1489360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780466] Re: Kernel panic at boot
I have tested all those 4 kernels (amd64; generic) but none of them causes a kernel panic at boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780466 Title: Kernel panic at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780466] Re: Kernel panic at boot
That all those kernels are working now was a bit suspicious to me. I did upgrade yesterday my system which also involved an issue: The vboxdrv (VirtualBox) kernel module couldn't be loaded anymore because of a format error or such. Since a downgrade from version 5.2.14 to version 5.2.12 of VirtualBox did not solve the issue and it looked like that the upgrade also made GCC 8 a default my guess was that the compilation of the vboxdrv kernel module with GCC 8 caused this incompatibility either due to a GCC bug or my kernel being too old. I also noticed that my boot time was some seconds faster due to vboxdrv not being loaded at boot. To make sure this issue is not related to the kernel panic at boot I tested the mainline kernel 4.18 RC5 again but it didn't panic now on boot. On testing then linux-image-4.17.0-5-generic from the Ubuntu repository it did also boot without a kernel panic and after 8 months of being haunted by kernel panics at boot I have finally an up-to-date working kernel again (also vboxdrv is being loaded successfully and VirtualBox works). My guess is that kernel versions after linux-image-4.13.0-15-generic with virtualbox-dkms being installed and its vboxdrv compiled via GCC 7.3.0 caused this issue. I'm not sure which of the 3 candidates is to blame here but the combination of linux-image-4.17.0-5-generic with virtualbox-dkms with its vboxdrv compiled via GCC 8.1.0 works fine so it appears there is no remaining issue (at least for cosmic except somebody compiles vboxdrv with GCC 7 as I guess the kernel does panic then again). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780466 Title: Kernel panic at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782436] [NEW] libnvidia-gl-390:i386 does not depend on libgl1:i386
Public bug reported: I'm using Ubuntu 18.10 dev with libnvidia-gl-390:i386 390.67-0ubuntu1 and I noticed that libnvidia-gl-390:i386 does not depend on libgl1:i386 (the same probably applies to the amd64 arch). For example this results 32 bit games with Wine to not being able to initialize OpenGL until libgl1:i386 gets installed manually. ** Affects: nvidia-graphics-drivers-390 (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/1782436 Title: libnvidia-gl-390:i386 does not depend on libgl1:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1782436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782582] [NEW] linux-image-generic depends on the proprietary amd64-microcode and intel-microcode
Public bug reported: I'm using Ubuntu 18.10 dev with linux-image-generic 4.17.0.5.8 and the package depends on amd64-microcode and intel-microcode which are proprietary if I'm not wrong. Normally the kernel should run without any microcode updates so it might make sense to move amd64-microcode and intel-microcode from Depends to Recommends to allow users staying on the linux-image-generic metapackage without being required to install proprietary software. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Summary changed: - * + linux-image-generic depends on the proprietary amd64-microcode and intel-microcode ** Description changed: - * + I'm using Ubuntu 18.10 dev with linux-image-generic 4.17.0.5.8 and the + package depends on amd64-microcode and intel-microcode which are + proprietary if I'm not wrong. Normally the kernel should run without any + microcode updates so it might make sense to move amd64-microcode and + intel-microcode from Depends to Recommends to allow users staying on the + linux-image-generic metapackage without being required to install + proprietary software. ** Package changed: ubuntu => linux-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782582 Title: linux-image-generic depends on the proprietary amd64-microcode and intel-microcode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1782582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782582] Re: linux-image-generic depends on the proprietary amd64-microcode and intel-microcode
** 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/1782582 Title: linux-image-generic depends on the proprietary amd64-microcode and intel-microcode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1401318] Re: GRUB menu doesn't appear after showing "GRUB loading."
On testing this again on Ubuntu 18.10 dev with grub-pc 2.02-2ubuntu13 and this time by not setting GRUB_HIDDEN_TIMEOUT at all, setting GRUB_TIMEOUT to 0.0 and then testing with GRUB_TIMEOUT_STYLE being set to menu (while keeping shift pressed at booting), hidden (while keeping ESC pressed at booting) and coutdown (while keeping ESC pressed at booting) I'm still seing the behavior from the startpost. But according to the documentation at https://www.gnu.org/software/grub/manual/grub/html_node/Simple- configuration.html it should work: > âGRUB_TIMEOUT_STYLEâ > > If this option is unset or set to âmenuâ, then GRUB will display the menu > and then wait for the timeout set by âGRUB_TIMEOUTâ to expire before booting > the default entry. Pressing a key interrupts the timeout. > > If this option is set to âcountdownâ or âhiddenâ, then, before displaying > the menu, GRUB will wait for the timeout set by âGRUB_TIMEOUTâ to expire. If > ESC is pressed during that time, it will display the menu and wait for input. > If a hotkey associated with a menu entry is pressed, it will boot the > associated menu entry immediately. If the timeout expires before either of > these happens, it will boot the default entry. In the âcountdownâ case, it > will show a one-line indication of the remaining time. One could argue if a timeout of 0 can be interrupted by a button press or not but there are a few reason why it should: - Otherwise I see not how the wanted behavior from the startpost could be possible (booting to the default operating system at default without waiting and only displaying the selection if a related key is pressed). - The reporter from the upstream report claims that this has worked in the past. - I think the documentation for GRUB_HIDDEN_TIMEOUT also implies that a timeout of 0 should be interruptable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1401318 Title: GRUB menu doesn't appear after showing "GRUB loading." To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1401318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780466] Re: Kernel panic at boot
At the current time kernel.ubuntu.com has no https availability (it times out) and downloading those packages over http is very insecure. I hope https becomes available soon so I can test this kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780466 Title: Kernel panic at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780466] Re: Kernel panic at boot
Edit: I checked the uncompromisedness via GPG - as I do not want to risk waiting a very long time until the https issue is solved. The kernel still panics at boot and claims this time about a tick-broadcast.c:652. ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu Cosmic) Status: Triaged => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780466 Title: Kernel panic at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
