[Bug 1769022] Re: ubuntu 18.04 freezes after the login
Many bugs are now accumulating with this and similar issues surrounding Xorg. This is just one example https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087 There are others. Some are related to Lenovo laptops but not all. Shame that 18.04 LTS has been allowed to be released without this inherent bug being fixed. It is damaging Ubuntu reputation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769022 Title: ubuntu 18.04 freezes after the login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769022/+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 1769022] Re: ubuntu 18.04 freezes after the login
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (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/1769022 Title: ubuntu 18.04 freezes after the login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769058] Re: Xorg freeze
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (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/1769058 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768906] Re: Xorg crash
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (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/1768906 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769029] Re: Display on Dell 1440x900 is not available
Many bugs are now accumulating with this and similar issues surrounding Xorg. This is just one example https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087 There are others. Some are related to Lenovo laptops but not all. Shame that 18.04 LTS has been allowed to be released without this inherent bug being fixed. It is damaging Ubuntu reputation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769029 Title: Display on Dell 1440x900 is not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769029] Re: Display on Dell 1440x900 is not available
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (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/1769029 Title: Display on Dell 1440x900 is not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768734] Re: Restoring edge tiled windows with client-side decorations shrinks them (Wayland)
** Also affects: gtk 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/1768734 Title: Restoring edge tiled windows with client-side decorations shrinks them (Wayland) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1768734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update
Hi Donald, I am writing this e-mail using your new firefox_59.0.2+build1-0ubuntu0.14.04.4_armhf.deb version on a TinkerOS, Debian GNU/Linux 9.4 (stretch) , kernel 4.4.71+ I started firefox in Downloads folder from terminal and got the following lines: linaro@tinkerboard:~/Downloads$ firefox [fresh] [error] probe_ppp_module, can't find libppGoogleNaClPluginChrome.so [fresh] [error] probe_ppp_module, can't find libppGoogleNaClPluginChrome.so [fresh] [error] probe_ppp_module, can't find libppGoogleNaClPluginChrome.so [fresh] [error] probe_ppp_module, can't find libppGoogleNaClPluginChrome.so [fresh] [error] probe_ppp_module, can't find libppGoogleNaClPluginChrome.so [fresh] [error] probe_ppp_module, can't find libppGoogleNaClPluginChrome.so Best regards and than you again Lars Nyqvist On 5/5/18, James Donald <1711...@bugs.launchpad.net> wrote: > @herrtimson I looked in the tarball and don't even see mention of my use > of clang in mozconfig. > > Note I'm using a procedure similar to what Chituc outlined. If I kick > off dpkg-buildpackage, interrupt it, then edit the generated backend.mk > I would not expect that to appear in patch files. It's also possible > that due to use of the -b flag it skips version control comparisons, so > the C++ source diffs are not appearing either. > > For now I have documented pieces manually in this repo: > https://github.com/jdonald/firefox-armhf > > I'll update that repo as more steps come to mind. > firefox_59.0.2.build1-0ubuntu0.14.04.4.debian.tar.xz is available for > download there in the releases tab if you'd like to take a look through > it. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1733340). > https://bugs.launchpad.net/bugs/1711337 > > Title: > Firefox crashes at start on armv7L after 55.0.1 update > > Status in Mozilla Firefox: > Expired > Status in firefox package in Ubuntu: > Confirmed > > Bug description: > Firefox always crashes when launched after the 55.0.1 update on an > Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi), > even in safe mode. > > I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for > ARM single-board computer) on a similar board (Orange Pi Plus 2e), > installed Firefox and experienced the same problem--it won't load > without crashing. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: firefox 55.0.1+build2-0ubuntu0.16.04.2 > Uname: Linux 3.4.113-sun8i armv7l > AddonCompatCheckDisabled: False > AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. > ApportVersion: 2.20.1-0ubuntu2.10 > Architecture: armhf > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC1: jim1138 F pulseaudio >/dev/snd/controlC0: jim1138 F pulseaudio > BuildID: 20170814194718 > Card0.Amixer.info: >Card hw:0 'audiocodec'/'audiocodec' > Mixer name : '' > Components : '' > Controls : 12 > Simple ctrls : 12 > Card1.Amixer.info: >Card hw:1 'sndhdmi'/'sndhdmi' > Mixer name : '' > Components : '' > Controls : 1 > Simple ctrls : 1 > Card1.Amixer.values: >Simple mixer control 'hdmi audio format Function',0 > Capabilities: enum > Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' > 'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO' > Item0: 'pcm' > Channel: Unavailable > CurrentDesktop: XFCE > Date: Thu Aug 17 05:37:00 2017 > Extensions: extensions.sqlite corrupt or missing > ForcedLayersAccel: False > IncompatibleExtensions: Unavailable (corrupt or non-existant > compatibility.ini or extensions.sqlite) > IpRoute: >default via 192.168.10.1 dev eth0 >default via 192.168.10.1 dev wlan0 proto static metric 600 >169.254.0.0/16 dev eth0 scope link metric 1000 >192.168.10.0/24 dev eth0 proto kernel scope link src 192.168.10.107 >192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.108 > metric 600 > Locales: extensions.sqlite corrupt or missing > PciMultimedia: > > PciNetwork: > > Profiles: Profile0 (Default) - LastVersion=55.0.1/20170814194718 > RfKill: >0: phy0: Wireless LAN > Soft blocked: no > Hard blocked: no > RunningIncompatibleAddons: False > SourcePackage: firefox > Themes: extensions.sqlite corrupt or missing > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/firefox/+bug/1711337/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711337 Title: Firefox crashes at start on armv7L after 55.0.1 update To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1711337/+subscriptions -- ubuntu-bugs mailing list
[Bug 1769091] Re: Xorg freeze on login
Many bugs are now accumulating with this and similar issues surrounding Xorg. This is just one example https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087 There are others. Some are related to Lenovo laptops but not all. Shame that 18.04 LTS has been allowed to be released without this inherent bug being fixed. It is damaging Ubuntu reputation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769091 Title: Xorg freeze on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1767703] Re: Calling 'apt-install grub-efi-amd64-signed' failed
Thank you everyone. Actually I solved the problem using an older version of Lubuntu. I don't know what was the problem but it works perfectly now. 2018-05-04 18:57 GMT+03:00 ziya <1767...@bugs.launchpad.net>: > Thanks! > > On Fri 4 May, 2018, 1:41 AM Mohammad Hossein Shakouri, < > mhshako...@gmail.com> > wrote: > > > I was trying to install ubuntu 18.04.14 on a surface pro 4 and using all > > the disk for installation when it failed. I've tried to install it while > > formatting the whole disk and I've not yet tried to install it along > > side windows. I will see what goes on while doing that. > > > > -- > > You received this bug notification because you are subscribed to a > > duplicate bug report (1767467). > > https://bugs.launchpad.net/bugs/1767703 > > > > Title: > > Calling 'apt-install grub-efi-amd64-signed' failed > > > > Status in grub-installer package in Ubuntu: > > Confirmed > > > > Bug description: > > /plugininstall.py: Exception during installation: > > /plugininstall.py: Traceback (most recent call last): > > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line > > 1739, in > > /plugininstall.py: install.run() > > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line > > 61, in wrapper > > /plugininstall.py: func(self) > > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line > > 227, in run > > /plugininstall.py: self.configure_bootloader() > > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line > > 971, in configure_bootloader > > /plugininstall.py: "GrubInstaller failed with code %d" % ret) > > /plugininstall.py: ubiquity.install_misc.InstallStepError: > GrubInstaller > > failed with code 1 > > > > > > Manual fix: > > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/ > 1766945/comments/3 > > > > also see: https://bugs.launchpad.net/ubuntu/+source/grub- > > installer/+bug/1763441/comments/2 > > > > https://help.ubuntu.com/community/Boot-Repair > > > > > > > > ProblemType: Bug > > DistroRelease: Ubuntu 18.04 > > Package: ubiquity 18.04.14 > > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 > > Uname: Linux 4.15.0-20-generic x86_64 > > ApportVersion: 2.20.9-0ubuntu7 > > Architecture: amd64 > > CasperVersion: 1.394 > > CurrentDesktop: ubuntu:GNOME > > Date: Sat Apr 28 20:39:35 2018 > > InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz > > file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash > --- > > LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > > (20180426) > > ProcEnviron: > >LANGUAGE=de_DE.UTF-8 > >PATH=(custom, no user) > >XDG_RUNTIME_DIR= > >LANG=de_DE.UTF-8 > >LC_NUMERIC=C.UTF-8 > > SourcePackage: grub-installer > > UpgradeStatus: No upgrade log present (probably fresh install) > > > > To manage notifications about this bug go to: > > > > https://bugs.launchpad.net/ubuntu/+source/grub-installer/ > +bug/1767703/+subscriptions > > > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1768404). > https://bugs.launchpad.net/bugs/1767703 > > Title: > Calling 'apt-install grub-efi-amd64-signed' failed > > Status in grub-installer package in Ubuntu: > Confirmed > > Bug description: > /plugininstall.py: Exception during installation: > /plugininstall.py: Traceback (most recent call last): > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line > 1739, in > /plugininstall.py: install.run() > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line > 61, in wrapper > /plugininstall.py: func(self) > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line > 227, in run > /plugininstall.py: self.configure_bootloader() > /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line > 971, in configure_bootloader > /plugininstall.py: "GrubInstaller failed with code %d" % ret) > /plugininstall.py: ubiquity.install_misc.InstallStepError: > GrubInstaller failed with code 1 > > > Manual fix: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/ > 1766945/comments/3 > > also see: https://bugs.launchpad.net/ubuntu/+source/grub- > installer/+bug/1763441/comments/2 > > https://help.ubuntu.com/community/Boot-Repair > > > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: ubiquity 18.04.14 > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 > Uname: Linux 4.15.0-20-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7 > Architecture: amd64 > CasperVersion: 1.394 > CurrentDesktop: ubuntu:GNOME > Date: Sat Apr 28 20:39:35 2018 > InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed > boot=casper only-ubiquity quiet splash --- > LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver"
[Bug 1769091] Re: Xorg freeze on login
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (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/1769091 Title: Xorg freeze on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1768410] Re: grub-efi-amd64-signed
*** This bug is a duplicate of bug 1767703 *** https://bugs.launchpad.net/bugs/1767703 Thank you. Actually I solved the problem using an older version of Lubuntu. I don't know what was the problem but it works perfectly now. 2018-05-03 10:32 GMT+03:00 dino99 <1768...@bugs.launchpad.net>: > *** This bug is a duplicate of bug 1767703 *** > https://bugs.launchpad.net/bugs/1767703 > > ** This bug has been marked a duplicate of bug 1767703 >Calling 'apt-install grub-efi-amd64-signed' failed > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1768410 > > Title: > grub-efi-amd64-signed > > Status in grub-installer package in Ubuntu: > New > > Bug description: > The message says "grub-efi-amd64-signed"package failed to install into > /target/. Without the grub boot loader, the installer system will not > boot. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: ubiquity 18.04.14 > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 > Uname: Linux 4.15.0-20-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7 > Architecture: amd64 > CasperVersion: 1.394 > Date: Wed May 2 07:10:55 2018 > InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/lubuntu.seed > boot=casper quiet splash --- > LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > SourcePackage: grub-installer > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/grub-installer/ > +bug/1768410/+subscriptions > -- RAZAFITSIAROVANA Harimbola -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768410 Title: grub-efi-amd64-signed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1768410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769270] Re: Xorg freeze
Many bugs are now accumulating with this and similar issues surrounding Xorg. This is just one example https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087 There are others. Some are related to Lenovo laptops but not all. Shame that 18.04 LTS has been allowed to be released without this inherent bug being fixed. It is damaging Ubuntu reputation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769270 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769270] Re: Xorg freeze
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (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/1769270 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769308] [NEW] installer crashed out after clicking continue on setting time & date during a fresh install from a DVD, which is working fine on other machines
Public bug reported: I was installing a fresh OS from DVD, as I clicked continue after setting zone, it said installer crashed & gave me 3 options, 1.cancel,2.try again,3. continue anyway. I chose to try again and again I got another message says installer crashed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.4 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 Date: Sat May 5 12:15:21 2018 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63.4 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769308 Title: installer crashed out after clicking continue on setting time & date during a fresh install from a DVD, which is working fine on other machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1769308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1609466] Re: gnome-keyring-daemon crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1568241 *** https://bugs.launchpad.net/bugs/1568241 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-keyring (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/1609466 Title: gnome-keyring-daemon crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1609466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1611737] Re: Can't upgrade from a release if ros packages are installed from ROS servers
Thanks, I already on 18.04. After uninstalling ROS, do-release-upgrade -d starts works properly. But there is an another problem in upgrade proccess. I have zfs raid as data storage. And after rebuting new kernel was unable to load. Problem solves by by buting in old kernel and export-uninstall zfs and install-import in new kernel. Thanks for help with ROS packages! пт, 4 мая 2018 г., 22:45 Jose Luis Rivero: > Before going down into particular cases, I would like to point that > every ROS Release supports only a few subset of the Ubuntu distributions > (see REP3 http://www.ros.org/reps/rep-0003.html#platforms-by- > distribution). > > This makes some upgrades technically not possible since there could not > be packages in the ROS repositories available for the new distribution > in an upgrade process. For example, there is no a single ROS Release > that support 14.04 and 16.04. I can not see a safe/straightforward > upgrade path. > > If this is not the case, from Open Robotics we are happy help if > something can be done in ROS packages or repositories. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1768303). > https://bugs.launchpad.net/bugs/1611737 > > Title: > Can't upgrade from a release if ros packages are installed from ROS > servers > > Status in ubuntu-release-upgrader package in Ubuntu: > Confirmed > > Bug description: > This message was appear when upgrade > > ProblemType: Bug > DistroRelease: Ubuntu 14.04 > Package: ubuntu-release-upgrader-core 1:0.220.8 > ProcVersionSignature: Ubuntu 3.19.0-66.74~14.04.1-generic 3.19.8-ckt22 > Uname: Linux 3.19.0-66-generic x86_64 > NonfreeKernelModules: nvidia > ApportVersion: 2.14.1-0ubuntu3.21 > Architecture: amd64 > CrashDB: ubuntu > CurrentDesktop: Unity > Date: Wed Aug 10 18:41:24 2016 > InstallationDate: Installed on 2015-09-08 (336 days ago) > InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 > (20150805) > PackageArchitecture: all > SourcePackage: ubuntu-release-upgrader > UpgradeStatus: Upgraded to trusty on 2016-08-10 (0 days ago) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1611737/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611737 Title: Can't upgrade from a release if ros packages are installed from ROS servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1611737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769305] [NEW] Installer crashes
Public bug reported: Crashes when trying to install ubuntu from both direct and trial mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 Date: Fri May 4 23:14:48 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid boot=casper quiet splash --- LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubiquity-18.04.14 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769305 Title: Installer crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1769305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769303] [NEW] scidavis package not in bionic repository
Public bug reported: Hi, In my opinion scidavis is the best free and open source data visualization program out there. Scidavis was available in the Ubuntu repository for 16.04 and 17.10. However, it does not appear to be available in the Ubuntu 18.04LTS repository. This is odd because I did see scidavis the latest version 1.22-1 in Ubuntu launchpad (launchpad.net/ubuntu/+source/scidavis/1:1.22-1). Is there anything I can do to help make scidavis 1.22-1 available in Ubuntu 18.04 repository or is it too late? Thanks, Raad Nashmi ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769303 Title: scidavis package not in bionic repository To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1769303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769304] [NEW] Apache2 mod_remoteip+rewrite allows client to forge IP address
*** This bug is a security vulnerability *** Public security bug reported: Apache bug #60251 describes this problem: https://bz.apache.org/bugzilla/show_bug.cgi?id=60251 mod_remoteip allows us to set the client's IP address using a trusted proxy's X-Forwarded-For header. However, in a location which uses a RewriteRule, the last IP address in the chain is incorrectly stripped while redirecting to the new location, allowing a caller to forge whatever IP address they like by including it in an X-Forwarded-For header. Version 2.4.18-2ubuntu3.8 is vulnerable to this in Xenial. This is fixed upstream in 2.4.24, can the fix be backported to xenial-updates? ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New ** 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/1769304 Title: Apache2 mod_remoteip+rewrite allows client to forge IP address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1769304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769044] Re: Ubunut 18.04 d-i preseeded installer hangs at 66 % of update-grub...
We're going to probably need the logs from the affected machine, not just random photos. Once you kill the process and finish the install, tar up /var/log/installer from the installed system. Also, if this is preseeded, the preseed you're using would be helpful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769044 Title: Ubunut 18.04 d-i preseeded installer hangs at 66 % of update-grub... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1769044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768727] Re: netboot image for 18.04 out of sync
Kernel 4.15.0-13 is very much not the kernel used in the current bionic netboot images. You're using an old version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768727 Title: netboot image for 18.04 out of sync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1768727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768734] Re: Restoring edge tiled windows with client-side decorations shrinks them (Wayland)
The bug shows up only in a Wayland session. The behaviour is normal under Xorg. Quite possibly an issue with GTK+, which is improperly handling the sizing of client-side decorated windows when tiling/untiling them. ** Summary changed: - restoring edge tiled windows with client-side decorations shrinks them + Restoring edge tiled windows with client-side decorations shrinks them (Wayland) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768734 Title: Restoring edge tiled windows with client-side decorations shrinks them (Wayland) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1768734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769301] [NEW] useradd fails when selinux is set to permissive
Public bug reported: root@ubuntu:~# useradd -g 100 tst003 useradd: failure while writing changes to /etc/passwd root@ubuntu:~# sestatus SELinux status: enabled SELinuxfs mount:/sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: default Current mode: permissive Mode from config file: permissive Policy MLS status: enabled Policy deny_unknown status: allowed Memory protection checking: requested (insecure) Max kernel policy version: 31 The problem does not occur when SELinux is complete disabled. Please note that a very similar problem occurs using groupadd: root@ubuntu:~# groupadd tstgrp001 groupadd: failure while writing changes to /etc/group = journal = (Please note that there is *no* AVC!) May 05 05:11:44 ubuntu useradd[756]: new user: name=tst003, UID=1004, GID=100, home=/home/tst003, shell=/bin/sh May 05 05:11:44 ubuntu audit[756]: ADD_USER pid=756 uid=0 auid=1002 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=adding user id=1004 exe="/usr/sbin/useradd" hostname=ubuntu addr=? terminal=pts/0 res=success' May 05 05:11:44 ubuntu useradd[756]: failure while writing changes to /etc/passwd May 05 05:11:44 ubuntu audit[756]: ADD_USER pid=756 uid=0 auid=1002 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=adding user acct="tst003" exe="/usr/sbin/useradd" hostname=ubuntu addr=? terminal=pts/0 res=failed' May 05 05:11:44 ubuntu useradd[756]: failed adding user 'tst003', data deleted = ltrace = [pid 1074] SYS_write(12, "root:x:"..., 1360) = 1360 [pid 1074] <... fflush resumed> )= 0 [pid 1074] fileno(0x5595b21c6200)= 12 [pid 1074] fsync(12, 0x5595b21c62e0, 0, 0x7ff933d5c154 [pid 1074] SYS_fsync(12) = 0 [pid 1074] <... fsync resumed> ) = 0 [pid 1074] fclose(0x5595b21c6200 [pid 1074] SYS_close(12) = 0 [pid 1074] <... fclose resumed> )= 0 [pid 1074] utime(0x7ffee34207e0, 0x7ffee34206b0, 0x5595b21af010, 1 [pid 1074] SYS_utime("/etc/passwd-", 0x7ffee34206b0) = 0 [pid 1074] <... utime resumed> ) = 0 [pid 1074] fclose(0x5595b21af2a0 [pid 1074] SYS_close(5) = 0 [pid 1074] <... fclose resumed> )= 0 [pid 1074] setfscreatecon(0, 0x5595b21af118, 1, 2 [pid 1074] SYS_openat(0xff9c, 0x5595b21cebc0, 0x80002, 0) = 5 [pid 1074] SYS_write(5, nil, 0) = -22 [pid 1074] SYS_close(5) = 0 [pid 1074] <... setfscreatecon resumed> )= 0x [pid 1074] free(0x5595b21b9dc0) = [pid 1074] free(0x5595b21b8a00) = [pid 1074] strlen("x") = 1 [pid 1074] memset(0x5595b21b7560, '\0', 1) = 0x5595b21b7560 [pid 1074] free(0x5595b21b7560) = [pid 1074] free(0x5595b21b94e0) = [pid 1074] free(0x5595b21b9000) = [pid 1074] free(0x5595b21b8fc0) = = strace = write(12, "root:x:"..., 1360) = 1360 fsync(12) = 0 close(12) = 0 utime("/etc/passwd-", {actime=1525497034 /* 2018-05-05T05:10:34+ */, modtime=1525496803 /* 2018-05-05T05:06:43+ */}) = 0 close(5)= 0 openat(AT_FDCWD, "/proc/thread-self/attr/fscreate", O_RDWR|O_CLOEXEC) = 5 write(5, NULL, 0) = -1 EINVAL (Invalid argument) close(5)= 0 = Version Information = root@ubuntu:~# lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 root@ubuntu:~# dpkg -l | grep passwd | grep -v base-pa ii passwd1:4.5-1ubuntu1 amd64change and administer password and group data root@ubuntu:~# dpkg -l | grep selinux ii libselinux1:amd64 2.7-2build2 amd64SELinux runtime shared libraries ii python3-selinux 2.7-2build2 amd64Python3 bindings to SELinux shared libraries ii selinux-basics0.5.6 all SELinux basic support ii selinux-policy-default2:2.20180114-1all Strict and Targeted variants of the SELinux policy ii selinux-policy-dev2:2.20180114-1all Headers from the SELinux reference policy for building modules ii selinux-utils 2.7-2build2 amd64SELinux utility programs root@ubuntu:~# uname -a Linux ubuntu 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: shadow (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a
[Bug 1769307] [NEW] The "docky" application is started by "docky --version" input.
Public bug reported: Ubuntu 18.04 LTS (Japanese environment) Docky version: 2.2.1.1 Release Kernel version: 4.15.0.20 [Procedure to reoccur] 1. I entered the following in the "terminal" application. Install "docky" application. $ sudo apt update $ sudo apt install docky 2. I entered the following in the "terminal" application. I checked that installation was successful after installation. $ docky --version 3. There was a version indication. After that, the message was displayed for a long time. So I thought it was an error message. $ docky --version [Info 14:47:47.043] Docky version: 2.2.1.1 Release [Info 14:47:47.063] Kernel version: 4.15.0.20 [Info 14:47:47.064] CLR version: 4.0.30319.42000 [Info 14:47:47.111] [Gtk] Failed to load module "canberra-gtk-module" [Error 14:47:47.451] [SystemService] Could not initialize power manager dbus: 'Could not load type 'Docky.Services.SystemService\+IUPowerProxy' from assembly 'DBus.Proxies, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' because it is implements the inaccessible interface 'Docky.Services.SystemService+IUPower'.' [Info 14:47:47.463] [SystemService] at System.Reflection.Emit.TypeBuilder.CreateTypeInfo () [0x002dc] in <8f2c484307284b51944a1a13a14c0266>:0 at System.Reflection.Emit.TypeBuilder.CreateType () [0x0] in <8f2c484307284b51944a1a13a14c0266>:0 at DBus.TypeImplementer.GetImplementation (System.Type declType) [0x000e3] in <91cfe10d2aa049c9af550645dbbec075>:0 at DBus.BusObject.GetObject (DBus.Connection conn, System.String bus_name, DBus.ObjectPath object_path, System.Type declType) [0x1] in <91cfe10d2aa049c9af550645dbbec075>:0 at DBus.Connection.GetObject (System.Type type, System.String bus_name, DBus.ObjectPath path) [0x0002b] in <91cfe10d2aa049c9af550645dbbec075>:0 at DBus.Connection.GetObject[T] (System.String bus_name, DBus.ObjectPath path) [0x1] in <91cfe10d2aa049c9af550645dbbec075>:0 at Docky.Services.SystemService.InitializeBattery () [0x00030] in <7cbfebdf01bd437fb1e0b3e770f0dbae>:0 [Error 14:47:47.473] [SystemService] Could not initialize Network Manager dbus: 'Could not load type 'Docky.Services.SystemService\+INetworkManagerProxy' from assembly 'DBus.Proxies, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' because it is implements the inaccessible interface 'Docky.Services.SystemService+INetworkManager'.' [Info 14:47:47.474] [SystemService] at System.Reflection.Emit.TypeBuilder.CreateTypeInfo () [0x002dc] in <8f2c484307284b51944a1a13a14c0266>:0 at System.Reflection.Emit.TypeBuilder.CreateType () [0x0] in <8f2c484307284b51944a1a13a14c0266>:0 at DBus.TypeImplementer.GetImplementation (System.Type declType) [0x000e3] in <91cfe10d2aa049c9af550645dbbec075>:0 at DBus.BusObject.GetObject (DBus.Connection conn, System.String bus_name, DBus.ObjectPath object_path, System.Type declType) [0x1] in <91cfe10d2aa049c9af550645dbbec075>:0 at DBus.Connection.GetObject (System.Type type, System.String bus_name, DBus.ObjectPath path) [0x0002b] in <91cfe10d2aa049c9af550645dbbec075>:0 at DBus.Connection.GetObject[T] (System.String bus_name, DBus.ObjectPath path) [0x1] in <91cfe10d2aa049c9af550645dbbec075>:0 at Docky.Services.SystemService.InitializeNetworkManager () [0x0005c] in <7cbfebdf01bd437fb1e0b3e770f0dbae>:0 [Info 14:47:47.495] [ThemeService] Setting theme: Classic [Warn 14:47:47.523] [DesktopItemService] Could not find remap file '/home/ubn/.local/share/docky/remaps.ini'! [Info 14:47:47.667] [DockServices] Dock services initialized. [Info 14:47:48.028] [PluginManager] Loaded "Trash". Cairo.Surface is leaking, programmer is missing a call to Dispose Set MONO_CAIRO_DEBUG_DISPOSE to track allocation traces 4. After that, you can no longer enter in the "terminal" application. I thought that the "docky" application stalled. So, I thought the installation did not succeed. 5. This was a misunderstanding. I did not expect that "docky" will start when I check the version. --- [Things I think] Immediately after installing the application, I'd like to display "version" and "help" in the "terminal" application to see if the installation was successful. The problem is that the application does what the operator did not think. I think that it is desirable to terminate the application after displaying any of the following when an unsupported parameter is entered. - Display help. - "The parameter can not be used" is displayed. - Nothing is displayed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: docky 2.2.1.1-1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 15:31:55 2018 InstallationDate: Installed on 2018-05-04 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no
[Bug 1752835] Re: gbutils ARM bug (programs freezes)
This bug was fixed in the package gbutils - 5.7.1-1 --- gbutils (5.7.1-1) unstable; urgency=medium [ Tomasz Buchert ] * d/control: update vcs links to salsa * Fix insecure-copyright-format-uri [ Pietro Battiston ] * New upstream version 5.7.1 - Fix freeze on ARM (LP: #1752835) -- Pietro BattistonThu, 08 Mar 2018 08:22:01 +0100 ** Changed in: gbutils (Ubuntu) Status: Fix Committed => 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/1752835 Title: gbutils ARM bug (programs freezes) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gbutils/+bug/1752835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768968] Re: Alternate installer missing install option.
> I suspect some ISO build tools are broken at some point I would contend that if the ISO boots the way it was intended to (from BIOS or UEFI), it's working fine. Note that "grml-rescueboot", per its own definition, is for booting GRML ISOs, not just any random ISO. Maybe there's something we can do to make them get along, but it's hardly a primary goal of either project. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768968 Title: Alternate installer missing install option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1768968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769313] [NEW] Installed lxqt dependencies try to override Gnome at next start up (Ubuntu 17.10)
Public bug reported: Hello, I had installed pcmanfm-qt to try it and then I removed it*. At the next Ubuntu start up, Ubuntu got stuck at the loading screen (the one with "Ubuntu" written on a purple background and dots beneath it). The mouse pointer was not Gnome's, it was LXDE's, and there was a grey rectangle at the bottom right corner of the screen. After the third reboot instead of the rectangle there appeared a dialog reporting some lxqt error (it was something related to not being able to start the power management utility, if I recall correctly). To solve the issue I had to log in into a console and uninstall lxqt packages. I was able to get Gnome back only after uninstalling lxqt-session. * If you wish to know, I didn't keep it because I want the file manager to keep file selected after copying/cutting and pasting them around. In other words, the problem is that when I select some files, go to another directory and paste them, they get lost among the other files that are already there. ** Affects: pcmanfm-qt (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/1769313 Title: Installed lxqt dependencies try to override Gnome at next start up (Ubuntu 17.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1769313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769312] [NEW] package steam-devices (not installed) failed to install/upgrade: tentative de remplacement de « /lib/udev/rules.d/60-HTC-Vive-perms.rules », qui appartient aussi au paquet steam-la
Public bug reported: having trouble installing steam from installer straight from their website as well as ubuntu software library ProblemType: Package DistroRelease: Ubuntu 18.04 Package: steam-devices (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 AptOrdering: steam-devices:amd64: Install steam-installer:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat May 5 00:38:19 2018 ErrorMessage: tentative de remplacement de « /lib/udev/rules.d/60-HTC-Vive-perms.rules », qui appartient aussi au paquet steam-launcher 1.0.0.54 InstallationDate: Installed on 2018-05-05 (0 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-3 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.1 SourcePackage: steam Title: package steam-devices (not installed) failed to install/upgrade: tentative de remplacement de « /lib/udev/rules.d/60-HTC-Vive-perms.rules », qui appartient aussi au paquet steam-launcher 1.0.0.54 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: steam (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/1769312 Title: package steam-devices (not installed) failed to install/upgrade: tentative de remplacement de « /lib/udev/rules.d/60-HTC-Vive- perms.rules », qui appartient aussi au paquet steam-launcher 1.0.0.54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1769312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764087] Re: Wrongly boots into low graphics mode
** Bug watch added: freedesktop.org Bugzilla #106407 https://bugs.freedesktop.org/show_bug.cgi?id=106407 ** Also affects: xorg-server via https://bugs.freedesktop.org/show_bug.cgi?id=106407 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764087 Title: Wrongly boots into low graphics mode To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1764087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769316] [NEW] Notification of Live patch sign-in is inconsistent depending on how Software & Updates is started
Public bug reported: This issue has I think been partly covered in other bug reports that are currently marked incomplete but none describe my exact issue with Livepatch signing in.. I'm creating this report in the hope that it does provide enough information with regards to what I am seeing here and have been doing so since before the release of Ubuntu 18.04. Last night I enabled Livepatch by signing into the appropriate tab of Software & Updates. As a result of briefly discussing this elsewhere I decided to check whether I was still logged in or not. 1) I started synaptic and pulled up "Software & Updates" from the Settings menu. The Updates tab shows the Livepatch box as being checked but a message of "To use Livepatch you need to sign in" and a Sign-in button is displayed. If I attempt to sign in I see a "Choose an account" dialog. Clicking on "Sign in.." displays an empty panel with "Devices" in the top left corner. This is obviously the Settings application with no text being displayed. 2) I then started "Software & Updates" as a stand alone application. The Updates tab shows that I am signed in, my email address is shown along with a "Sign out" button and the message "Use Canonical Livepatch to increase security between restarts is displayed immediately above. Restarting "Software & Updates" alternately through synaptic and as a stand alone application shows either an unsuccessful login or a successful log-in as described in points 1) and 2). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sat May 5 08:38:38 2018 InstallationDate: Installed on 2017-11-07 (178 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to bionic on 2018-02-21 (72 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic livepatch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769316 Title: Notification of Live patch sign-in is inconsistent depending on how Software & Updates is started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767703] Re: Calling 'apt-install grub-efi-amd64-signed' failed
Boot repair failed for me with "grub-efi-amd04signed" package failed to install Partitioning from a Live CD to create an EFI system partition failed as there were already four partitions on the drive (dual boot with W7). Trying grub-install . error: failed to get canonical path of `/cow' Tried installing 14.04 over the top of a partial 18.04. Great - it works. Bad news - it overwrote the whole disk, now no W7 and cross SWMBO :-( After that, 18.04 overwrote 14.04 happily and other problems started. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767703 Title: Calling 'apt-install grub-efi-amd64-signed' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1767703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769301] Re: useradd fails when selinux is set to permissive
In libselinux the setfscreatecon() function is implemented - which might be the root cause of the problem. ** Package changed: shadow (Ubuntu) => libselinux (Ubuntu) ** Summary changed: - useradd fails when selinux is set to permissive + resetting /proc/thread-self/attr/fscreate results in 'Invalid Argument' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769301 Title: resetting /proc/thread-self/attr/fscreate results in 'Invalid Argument' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libselinux/+bug/1769301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769319] [NEW] Grub installation failed on fresh install
Public bug reported: Following a fresh installation using a new SSD with new partition layout (/boot, /, swap) and (/home) from old drive, installation fails when trying to install grub ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 Date: Sat May 5 15:01:54 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) 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 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769319 Title: Grub installation failed on fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1769319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769301] Re: useradd fails when selinux is set to permissive
It looks that the root cause affects multiple packages. Observations: programs like lvchange have a similar problem: # lvresize -L +1M /dev/mapper/vg-home SELinux context reset: setfscreatecon failed: Invalid argument SELinux context reset: setfscreatecon failed: Invalid argument ... It looks that the problem might be in the libselinux (procattr.c setprocattrcon_raw): ret = write(fd, NULL, 0); /* clear */ This always returns 'Invalid argument'. I was not able to reproduce this with standard system tools (echo, cat, tee, ...). Therefore I wrote some lines of C (attached): root@ubuntu:~# strace -f ./w2 ... openat(AT_FDCWD, "/proc/thread-self/attr/fscreate", O_RDWR|O_CLOEXEC) = 3 write(3, NULL, 0) = -1 EINVAL (Invalid argument) dup(2) = 4 fcntl(4, F_GETFL) = 0x2 (flags O_RDWR) brk(NULL) = 0x55af7b32a000 brk(0x55af7b34b000) = 0x55af7b34b000 fstat(4, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 0), ...}) = 0 write(4, "write: Invalid argument\n", 24write: Invalid argument ) = 24 close(4)= 0 rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0 rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1], [], 8) = 0 getpid()= 10408 gettid()= 10408 tgkill(10408, 10408, SIGABRT) = 0 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 --- SIGABRT {si_signo=SIGABRT, si_code=SI_TKILL, si_pid=10408, si_uid=0} --- +++ killed by SIGABRT +++ Aborted I have no idea if this write(fd, NULL, 0) should work to reset the attribute (then it might be a kernel /proc problem) or if the library needs to use another mechanism to reset the content. ** Attachment added: "w2.c" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1769301/+attachment/5134236/+files/w2.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769301 Title: resetting /proc/thread-self/attr/fscreate results in 'Invalid Argument' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libselinux/+bug/1769301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769321] [NEW] Clean install on partitioned drive. The grub-efi-amd64-signed package failed to install into / target // Without the GRUB boot loader, the intalled system will not start. Wut??
Public bug reported: ubuntu 18.04 LTS package. Clean install. Failed. Not sure what to do next. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 09:33:20 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANGUAGE=en_GB.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.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 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769321 Title: Clean install on partitioned drive. The grub-efi-amd64-signed package failed to install into / target // Without the GRUB boot loader, the intalled system will not start. Wut?? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1769321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769303] Re: scidavis package not in bionic repository
Thanks for reporting. >From the package publishing history it looks like it was removed because the package hadn't been ported to QT5, see https://launchpad.net/ubuntu/+source/scidavis/+publishinghistory or https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894581 for more details. (Looks like it was first removed from Debian, and then Ubuntu followed). So it looks like a QT5-version of scidavis could be readded to the current development version of Ubuntu, and perhaps from there backported to 18.04. ** Bug watch added: Debian Bug tracker #894581 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894581 ** Package changed: ubuntu => scidavis (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769303 Title: scidavis package not in bionic repository To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scidavis/+bug/1769303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769297] Re: resume from hibernation broken when resume image is autodetected
** 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/1769297 Title: resume from hibernation broken when resume image is autodetected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1308264] Re: Ubuntu 14.04 Beta 2 stuck at "Switched to clocksource tsc" when booting up, then resumes booting to the login screen, after 1 minute
Same problem with Ubuntu MATE 18.04: [2.944434] clocksource: Switched to clocksource tsc [ 34.522308] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) $ uname -r 4.15.0-20-generic My motherboard: producto: P7H55 fabricante: ASUSTeK Computer INC. Also with two SSDs (no mechanical). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1308264 Title: Ubuntu 14.04 Beta 2 stuck at "Switched to clocksource tsc" when booting up, then resumes booting to the login screen, after 1 minute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767549] Re: org.gnome.Characters.desktop untranslated
This bug was fixed in the package gnome-characters - 3.28.0-4 --- gnome-characters (3.28.0-4) unstable; urgency=medium * Recommends fonts-noto-color-emoji since it's the only color emoji font in Debian currently * Drop obsolete dh_translations overrides (LP: #1767549) -- Jeremy BichaFri, 04 May 2018 18:36:18 -0400 ** Changed in: gnome-characters (Ubuntu) Status: Fix Committed => 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/1767549 Title: org.gnome.Characters.desktop untranslated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/1767549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738400] Re: Vagrant bionic 64 with virtualbox image doesn't start network correctly
I have the same issue with 'ubuntu/bionic64' (v20180426.2.0) on MacOS 10.11 / Vagrant 1.9.8 / VirtualBox 5.1.30 --- The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed! /sbin/ifdown 'enp0s8' || true /sbin/ip addr flush dev 'enp0s8' # Remove any previous network modifications from the interfaces file sed -e '/^#VAGRANT-BEGIN/,$ d' /etc/network/interfaces > /tmp/vagrant-network-interfaces.pre sed -ne '/^#VAGRANT-END/,$ p' /etc/network/interfaces | tac | sed -e '/^#VAGRANT-END/,$ d' | tac > /tmp/vagrant-network-interfaces.post cat \ /tmp/vagrant-network-interfaces.pre \ /tmp/vagrant-network-entry \ /tmp/vagrant-network-interfaces.post \ > /etc/network/interfaces rm -f /tmp/vagrant-network-interfaces.pre rm -f /tmp/vagrant-network-entry rm -f /tmp/vagrant-network-interfaces.post /sbin/ifup 'enp0s8' Stdout from the command: Stderr from the command: bash: line 4: /sbin/ifdown: No such file or directory bash: line 20: /sbin/ifup: No such file or directory --- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738400 Title: Vagrant bionic 64 with virtualbox image doesn't start network correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1738400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714659] Re: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.)
Just purchased and installed an HP printer with software from HP web page, device. I have this same bug. Ubuntu 18.04, HPLIP 3.18.4, device manager 15.0 (Qt4) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714659 Title: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.) To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1714659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611806] Re: executable scripts missing
This bug was fixed in the package opendmarc - 1.3.2-4 --- opendmarc (1.3.2-4) unstable; urgency=medium * Add Vcs-* for salsa * Bump standards-version to 4.1.3 without further change * Drop rddmarc exmample script binary and ship examples in opendmarc (LP: #1611806) * Switch to 3.0 (quilt) source package format * Enable all hardening options (Closes: #880524), thanks to Jack Bates for the patch * Bump compat to 10 so that systemd, autoreconf, and parallel fun are handeled automatically (Closes: #878473), Thanks to Jack Bates for the patch * Change package priority to optional to match override -- Scott KittermanSun, 11 Mar 2018 15:35:42 -0400 ** Changed in: opendmarc (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/1611806 Title: executable scripts missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opendmarc/+bug/1611806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758774] Re: pytrainer doesnt start on 18.04: ImportError: No module named _backend_gdk
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pytrainer (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/1758774 Title: pytrainer doesnt start on 18.04: ImportError: No module named _backend_gdk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pytrainer/+bug/1758774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769348] [NEW] libfreerdp does not support h264
Public bug reported: am on ubuntu 18.04 upgraded from 16.04 now am seeing this bug on 18.04 only earlier i had no problem with color depth using remmina. could you please upgrade freerdp to support h264 mode. ** Affects: freerdp2 (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/1769348 Title: libfreerdp does not support h264 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1769348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769354] [NEW] it does not install the GRUB and I can not start the system. I have windows 10
Public bug reported: it does not install the GRUB and I can not start the system. I have windows 10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 Date: Sat May 5 16:10:52 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) 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 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769354 Title: it does not install the GRUB and I can not start the system. I have windows 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1769354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769311] [NEW] Usb device naming not matching the system naming
Public bug reported: My bad experience with the netboot mini.iso installation (Bionic 2018-04-25) Hardware config: oem@cc64:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 111.8G 0 disk ├─sda1 8:1016G 0 part ├─sda2 8:20 10.3G 0 part [SWAP] ├─sda3 8:30 71.8G 0 part └─sda4 8:40 13.7G 0 part / sdb 8:16 0 931.5G 0 disk ├─sdb1 8:17 030G 0 part ├─sdb2 8:18 0 29.4G 0 part ├─sdb3 8:19 0 29.5G 0 part ├─sdb4 8:20 0 1K 0 part ├─sdb5 8:21 0 10.1G 0 part └─sdb6 8:22 0 832.5G 0 part What happen when i plug an usb stick: oem@cc64:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 111.8G 0 disk ├─sda1 8:1016G 0 part ├─sda2 8:20 10.3G 0 part [SWAP] ├─sda3 8:30 71.8G 0 part └─sda4 8:40 13.7G 0 part / sdb 8:16 0 931.5G 0 disk ├─sdb1 8:17 030G 0 part ├─sdb2 8:18 0 29.4G 0 part ├─sdb3 8:19 0 29.5G 0 part ├─sdb4 8:20 0 1K 0 part ├─sdb5 8:21 0 10.1G 0 part └─sdb6 8:22 0 832.5G 0 part sdc 8:32 1 7.5G 0 disk └─sdc1 8:33 1 7.5G 0 part /media/oem/MULTISYSTEM So logically the system add the newest plugged device at the end of the existing devices list. *** Now what happen when choosing a 'manual' partitioning: - the usb stick where the mini.iso is on becomes the first device listed (aka /dev/sda) - so the permanent devices are reordered and named /dev/sdb & /dev/sdc ==> this does not match with the system logic, nor app like gparted; its confusing. *** That is disturbing and possibly the source of other problem (crappy design). Does not remember if that was also displayed like this prior Artful. But Artful have introduced a swap file use instead of a swap partition; and here is where the installation becomes crazy: - choosing manual partitioning goes well until the final validation: the listed operations does not match the choices made: a) i have repeated several times my choices: / on /dev/sdc1 (sdb1 renamed), swap on /dev/sdc5 and /home on /dev/sdc6 b) but the proposed list is: / is ok, swap is not the one chosen but the first one found into the list (/dev/sdb2, aka sda2 renamed) and /home is simply ignored. Looks like the choice previously made to now use a swap file (since Artful) have broken the 'manual' partitioning script. The result is a borked grub menu, a /etc/fstab needing a manual tweak, and at the end X cant even start (log pointing to a 'invoke.rc.d gdm3 start' that fails). That it, fully unusable. Please do a sane design matching the system one first. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sat May 5 08:45:16 2018 EcryptfsInUse: Yes InstallCmdLine: BOOT_IMAGE=(loop)/linux -- quiet ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic cosmic ** Description changed: My bad experience with the netboot mini.iso installation (Bionic 2018-04-25) Hardware config: oem@cc64:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT - sda 8:00 111.8G 0 disk - ├─sda1 8:1016G 0 part + sda 8:00 111.8G 0 disk + ├─sda1 8:1016G 0 part ├─sda2 8:20 10.3G 0 part [SWAP] - ├─sda3 8:30 71.8G 0 part + ├─sda3 8:30 71.8G 0 part └─sda4 8:40 13.7G 0 part / - sdb 8:16 0 931.5G 0 disk - ├─sdb1 8:17 030G 0 part - ├─sdb2 8:18 0 29.4G 0 part - ├─sdb3 8:19 0 29.5G 0 part - ├─sdb4 8:20 0 1K 0 part - ├─sdb5 8:21 0 10.1G 0 part - └─sdb6 8:22 0 832.5G 0 part + sdb 8:16 0 931.5G 0 disk + ├─sdb1 8:17 030G 0 part + ├─sdb2 8:18 0 29.4G 0 part + ├─sdb3 8:19 0 29.5G 0 part + ├─sdb4 8:20 0 1K 0 part + ├─sdb5 8:21 0 10.1G 0 part + └─sdb6 8:22 0 832.5G 0 part What happen when i plug an usb stick: - oem@cc64:~$ lsblk + oem@cc64:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT - sda 8:00 111.8G 0 disk - ├─sda1 8:1016G 0 part + sda 8:00 111.8G 0 disk + ├─sda1 8:1016G 0 part ├─sda2 8:20 10.3G 0 part [SWAP] - ├─sda3 8:30 71.8G 0 part + ├─sda3 8:30 71.8G 0 part └─sda4 8:40 13.7G 0 part / - sdb 8:16 0 931.5G 0 disk - ├─sdb1 8:17 030G 0 part - ├─sdb2 8:18 0 29.4G 0 part - ├─sdb3 8:19 0 29.5G 0 part - ├─sdb4 8:20 0 1K 0 part - ├─sdb5 8:21 0 10.1G 0 part - └─sdb6 8:22 0 832.5G 0 part - sdc 8:32
[Bug 1769299] Re: universal access zoom unusable
Problem reproduced on separate (virtual) machine, unmodified ubuntu live image. - Host system AMD Phenom II X6 1090T with 16GB RAM Ubuntu 14.04.4 LTS - virtualbox 14.3.36-dfsg-... - SATA 0: 8GB VMDK drive (new) - SATA 1: CD/ROM: ubuntu-18.04-desktop-amd64.iso - Base memory: 4GB (important, if you use 1GB, ubuntu will boot to desktop but nothing works) must have enough ram on host machine to permit this - Specific Virtual machine -> System -> Motherboard: Enable EFI: On otherwise it will not boot - Boot menu: TRY ubuntu without installing - Show Applications (dash)-> Terminal - Show Applications -> Settings-> Universal Access -> Always Show Universal Access Menu: On - don't dismiss settings, we will use it about 8 steps below. - Universal Access menu (round man in circle on top panel) -> Zoom: on - Move pointer to upper left corner of desktop: note left panel (launcher) icons cut in hafl, note top panel cut in half - move to top right - click on whats left of universal access menu icon to pull down menu, note it is drawn incorrectly - move mouse down and to the left and notice how these panels/pull down menus scroll independently and incorrectly. - try to turn off the zoom in the univeral access pull down menu. Try to read the word zoom, now you cant see the control, move to see the control now you can't see the word. But in this case, you can actually get there. - turn zoom back on - move mouse pointer to upper right hand corner. Make sure either the universal access or the system menu is pulled down - move mouse down and left to the words "sound keys" in the settings menu (control panel, not the pull down menu) for universal access. Leave the mouse pointer there for a few seconds. Display will pan to upper right hand corner without permission. - If you repeat this without either of the two pull down menus activated, it will jump to the highlighted "Universal Access" on the left side of the settings window. This jumping action severely interfered with issuing screenshot commands in terminal and it will interfere with many other operations as well. Behavior of program suggests that the screen is being composited of the following elements: - desktop background - application window 1 - application window 2 - application window 3 ... - top panel - left panel (launcher) - pull down menu The first four items appear to be correctly composited together before applying the zoom and pan operation but the last three appear to not be composited onto the desktop+applications before zoom and pan is applied. The size of their windows has not been enlarged, only the contents. Add to paragraph about obfuscating the identity of the programs the user is interacting with: Universal Pull down menu also doesn't have "Help" or report bug menu items. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769299 Title: universal access zoom unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769317] [NEW] implement `lua_lock()` to support multithreading
Public bug reported: liblua5.3 does not support multithreading because `lua_lock()` and `lua_unlock()` are not implemented. To implement them so that lua can support multithreading. ** Affects: lua5.3 (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/1769317 Title: implement `lua_lock()` to support multithreading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lua5.3/+bug/1769317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764087] Re: Wrongly boots into low graphics mode
** Changed in: xorg-server Status: Unknown => Won't Fix ** Changed in: xorg-server Importance: Unknown => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764087 Title: Wrongly boots into low graphics mode To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1764087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768741] Re: hplip does not wake up printer
Cudos to my wife: Here is a more detailed and accurate description of the issue: Preset: Printer is installed on Ubuntu 18.04 Turning on the printer and printing any document -> works Putting notebook into suspend, after wakeup printing a document -> not printing Mitigation: - reboot printer - reinstall printer software After printer suspended (usually after 5 mins), printing a document -> not printing After manually waking up the printer from the display and printing a document -> not printing In all cases of not printing: If the printer queue was held, resuming from the GUI (both methods, from Settings and the Additional printer settings queue view) the queue goes into printing status and reverts to held. If the printer is freshly rebooted, starting a held queue leads to printing the document. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768741 Title: hplip does not wake up printer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1768741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758512] Re: No virtual terminals (CTRL+ALT+F?) when no user logged in; erratic behaviour when user logged in.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (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/1758512 Title: No virtual terminals (CTRL+ALT+F?) when no user logged in; erratic behaviour when user logged in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1758512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720438] Re: brightness control broken nvidia
Switching to integrated graphics the Fn works perfectly on gnome. Also: ls -l /sys/class/backlight/ total 0 lrwxrwxrwx 1 root root 0 may 5 12:12 intel_backlight -> ../../devices/pci:00/:00:02.0/drm/card0/card0-eDP-1/intel_backlight -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720438 Title: brightness control broken nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/1720438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen
This is *not* fixed for Xenial. I had originally applied the workaround in the bug description to get my computer to boot again. After seeing a "fixed" status for this bug, I updated intel-microcode. After I rebooted, my computer would not boot to the kernel which had the microcode applied (4.4.0-122). It would only boot to the previous kernel without the microcode (4.4.0-119). $ tail -n 5 /var/log/apt/history.log Start-Date: 2018-05-05 06:06:43 Commandline: apt install intel-microcode Upgrade: intel-microcode:amd64 (3.20180108.0+really20170707ubuntu16.04.1, 3.20180312.0~ubuntu16.04.1) End-Date: 2018-05-05 06:06:57 $ uname -a Linux thinkpad 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -l | grep linux-image-4 | grep ^i ii linux-image-4.4.0-112-generic 4.4.0-112.135 amd64Linux kernel image for version 4.4.0 on 64 bit x86 SMP ii linux-image-4.4.0-119-generic 4.4.0-119.143 amd64Linux kernel image for version 4.4.0 on 64 bit x86 SMP ii linux-image-4.4.0-122-generic 4.4.0-122.146 amd64Linux kernel image for version 4.4.0 on 64 bit x86 SMP $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.4 LTS Release:16.04 Codename: xenial $ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 58 model name : Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz stepping: 9 microcode : 0x1c cpu MHz : 893.761 cache size : 3072 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm epb retpoline kaiser tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts bugs: cpu_meltdown spectre_v1 spectre_v2 bogomips: 3391.94 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title: intel-microcode 3.20180312.0 causes lockup at login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767603] Re: BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel
ignore comment 3, i retested it, with kernel Linux deepthought 4.17.0-041700rc3-generic #201804300800 SMP Mon Apr 30 08:03:00 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux and the bug clearly still exists. My apologies. 317 root 20 0 172284 130324 3280 R 81.2 3.3 6:30.80 systemd-udevd ** Tags removed: kernel-fixed-upstream ** Tags added: bug-exists-upstream ** Attachment removed: "Screenshot at 2018-05-05 11-19-28.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767603/+attachment/5134286/+files/Screenshot%20at%202018-05-05%2011-19-28.png ** Attachment removed: "Screenshot at 2018-05-05 11-17-38.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767603/+attachment/5134287/+files/Screenshot%20at%202018-05-05%2011-17-38.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767603 Title: BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen
Since this bug was marked as fixed I'm not sure what the best way to proceed is. I went ahead and filed a new bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1769335 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title: intel-microcode 3.20180312.0 causes lockup at login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769335] [NEW] PC won't boot with latest intel-microcode
Public bug reported: I'm experiencing the exact same symptoms as this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 However, that bug was marked as fixed. The workaround as desribed in that bug works for me. As soon as I try to update intel-microcode, my computer will not boot. I'm using the 4.4 kernel from 16.04. $ lsb_release -rd Description:Ubuntu 16.04.4 LTS Release:16.04 $ apt-cache policy intel-microcode intel-microcode: Installed: 3.20180312.0~ubuntu16.04.1 Candidate: 3.20180312.0~ubuntu16.04.1 Version table: *** 3.20180312.0~ubuntu16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 3.20151106.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/restricted amd64 Packages $ uname -a Linux thinkpad 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -l | grep linux-image-4 | grep ^i ii linux-image-4.4.0-112-generic 4.4.0-112.135 amd64 Linux kernel image for version 4.4.0 on 64 bit x86 SMP ii linux-image-4.4.0-119-generic 4.4.0-119.143 amd64 Linux kernel image for version 4.4.0 on 64 bit x86 SMP ii linux-image-4.4.0-122-generic 4.4.0-122.146 amd64 Linux kernel image for version 4.4.0 on 64 bit x86 SMP $ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 58 model name : Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz stepping: 9 microcode : 0x1c cpu MHz : 893.761 cache size : 3072 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm epb retpoline kaiser tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts bugs: cpu_meltdown spectre_v1 spectre_v2 bogomips: 3391.94 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: intel-microcode 3.20180312.0~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Sat May 5 06:44:15 2018 InstallationDate: Installed on 2014-05-08 (1457 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: intel-microcode UpgradeStatus: Upgraded to xenial on 2016-08-05 (637 days ago) ** Affects: intel-microcode (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769335 Title: PC won't boot with latest intel-microcode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1769335/+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
Ubuntu 18.04 also weirdly freezes for about 1 minute when opening the system configuration menu. That is something that didn't happen in my previous 17.10 installation and somehow prevents me from setting up a monitor in my laptop. I wonder if this issue is related, since these are the only 2 problems I've been experiencing since 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/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 1769297] Re: resume from hibernation broken when resume image is autodetected
The attachment "init.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.] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769297 Title: resume from hibernation broken when resume image is autodetected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768074] Re: Mouseover does not show folder names reliably
** Changed in: baobab Status: Unknown => Confirmed ** Changed in: baobab 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/1768074 Title: Mouseover does not show folder names reliably To manage notifications about this bug go to: https://bugs.launchpad.net/baobab/+bug/1768074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769343] Re: package util-linux 2.27.1-6ubuntu3.4 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/1769343 Title: package util-linux 2.27.1-6ubuntu3.4 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/util-linux/+bug/1769343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769322] [NEW] Trackpoint reacts jumpy and isn't precise when moved a short distance
Public bug reported: I made a fresh install of Ubuntu 18.04 on a thinkPad t450s and t480s. The trackpoint reacts, especially if i want to move it only a small distance, very jumpy and erratic. It is very difficult to hit a precise spot on the screen because if I press with very littel pressure the cursor doesn't move and with a little more it makes a big jump. Somethimes it moves backwards first and then makes a jump in the intended direction. To summ up the trackpoint is very difficult to handle and changing the speedsettings doesn't change the issue. With Ubuntu 16.04 at least on the t450s everything worked well. ** Affects: libinput (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/1769322 Title: Trackpoint reacts jumpy and isn't precise when moved a short distance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1769322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769325] Re: canonical-livepatch: unable to enable it through software-properties-gtk
*** This bug is a duplicate of bug 1769324 *** https://bugs.launchpad.net/bugs/1769324 ** This bug has been marked a duplicate of bug 1769324 canonical-livepatch: unable to enable it through software-properties-gtk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769325 Title: canonical-livepatch: unable to enable it through software-properties- gtk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725078] Re: Can't set Ctrl+Shift as a shortcut
Repository with xserver fix. Works on ubuntu 16.04, 18.04. https://launchpad.net/~nrbrtx/+archive/ubuntu/xorg-hotkeys -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725078 Title: Can't set Ctrl+Shift as a shortcut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768074] Re: Mouseover does not show folder names reliably
I have now reported the bug i Bugzilla. This is my first report there, so feel free to correct any mistakes I may have made. https://bugzilla.gnome.org/show_bug.cgi?id=795832 ** Bug watch added: GNOME Bug Tracker #795832 https://bugzilla.gnome.org/show_bug.cgi?id=795832 ** Also affects: baobab via https://bugzilla.gnome.org/show_bug.cgi?id=795832 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768074 Title: Mouseover does not show folder names reliably To manage notifications about this bug go to: https://bugs.launchpad.net/baobab/+bug/1768074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769341] [NEW] Can't find HDMI
Public bug reported: The machine cannot find the HDMI port of the computer. It was working fine in version 17.10, but not after upgrading to 18.04. When looking at the graphics part of inxi, it is reporting that modesetting has failed. command: inxi -G Graphics: Card: Intel HD Graphics 520 Display Server: x11 (X.Org 1.19.6 ) driver: FAILED: modesetting Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) version: 4.5 Mesa 18.0.0-rc5 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 5 14:27:56 2018 DistUpgraded: 2018-05-05 12:31:36,611 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] [1025:1094] InstallationDate: Installed on 2017-10-31 (186 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57f3 Realtek Semiconductor Corp. Bus 001 Device 003: ID 0489:e0a3 Foxconn / Hon Hai Bus 001 Device 002: ID 062a:4101 Creative Labs Wireless Keyboard/Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=98508690-a9ad-4456-9e28-f3d867db01e9 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago) dmi.bios.date: 04/26/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd04/26/2016:svnAcer:pnAspireE5-575:pvrV1.04:rvnAcer:rnIronman_SK:rvrV1.04:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: SKL dmi.product.name: Aspire E5-575 dmi.product.version: V1.04 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Oct 31 16:01:19 2017 xserver.configfile: default xserver.errors: Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.3 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769341 Title: Can't find HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768805] Re: package mysql-server-5.7 5.7.22-0ubuntu18.04.1 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1
I upgraded the version to solve this problem but anything changed. Some one could help me? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768805 Title: package mysql-server-5.7 5.7.22-0ubuntu18.04.1 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1768805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758384] Re: [Acer AO532h] hibernate/resume failure
Yes, 4.15.0-10 hibernates under 17.10.1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758384 Title: [Acer AO532h] hibernate/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745646] Re: Battery drains when laptop is off (shutdown)
4.15.0-20-generic #21~lp1745646v2Upstream is good. http://paste.ubuntu.com/p/CdXSMBSQB5/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745646 Title: Battery drains when laptop is off (shutdown) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1745646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769314] [NEW] parallel-ssh manpage misspells command name
Public bug reported: In every `parallel-ssh` manpage from Xenial (http://manpages.ubuntu.com/manpages/xenial/en/man1/parallel-ssh.1.html) to Bionic (http://manpages.ubuntu.com/manpages/bionic/en/man1/parallel- ssh.1.html), the command is called paralllel-ssh multiple times. The typos are introduced with the patch, see e.g. https://launchpadlibrarian.net/175197315/pssh_2.3.1-1.diff.gz – just search for “paralll”. A simple sed 's/paralllel/parallel/g' should do the trick. ** Affects: pssh (Ubuntu) Importance: Undecided Status: New ** Description changed: - In every `parallel-ssh` manpage from - [Xenial](http://manpages.ubuntu.com/manpages/xenial/en/man1/parallel- - ssh.1.html) to - [Bionic](http://manpages.ubuntu.com/manpages/bionic/en/man1/parallel- + In every `parallel-ssh` manpage from Xenial + (http://manpages.ubuntu.com/manpages/xenial/en/man1/parallel-ssh.1.html) + to Bionic (http://manpages.ubuntu.com/manpages/bionic/en/man1/parallel- ssh.1.html), the command is called para**lll**el-ssh multiple times. The typos are introduced with the patch, see e.g. https://launchpadlibrarian.net/175197315/pssh_2.3.1-1.diff.gz – just search for “paralll”. A simple `sed 's/paralllel/parallel/g'` should do the trick. ** Description changed: In every `parallel-ssh` manpage from Xenial (http://manpages.ubuntu.com/manpages/xenial/en/man1/parallel-ssh.1.html) to Bionic (http://manpages.ubuntu.com/manpages/bionic/en/man1/parallel- - ssh.1.html), the command is called para**lll**el-ssh multiple times. + ssh.1.html), the command is called paralllel-ssh multiple times. The typos are introduced with the patch, see e.g. https://launchpadlibrarian.net/175197315/pssh_2.3.1-1.diff.gz – just search for “paralll”. A simple `sed 's/paralllel/parallel/g'` should do the trick. ** Description changed: In every `parallel-ssh` manpage from Xenial (http://manpages.ubuntu.com/manpages/xenial/en/man1/parallel-ssh.1.html) to Bionic (http://manpages.ubuntu.com/manpages/bionic/en/man1/parallel- ssh.1.html), the command is called paralllel-ssh multiple times. The typos are introduced with the patch, see e.g. https://launchpadlibrarian.net/175197315/pssh_2.3.1-1.diff.gz – just search for “paralll”. - A simple `sed 's/paralllel/parallel/g'` should do the trick. + A simple sed 's/paralllel/parallel/g' should do the trick. ** Description changed: In every `parallel-ssh` manpage from Xenial (http://manpages.ubuntu.com/manpages/xenial/en/man1/parallel-ssh.1.html) to Bionic (http://manpages.ubuntu.com/manpages/bionic/en/man1/parallel- - ssh.1.html), the command is called paralllel-ssh multiple times. + ssh.1.html), the command is called para'''lll'''el-ssh multiple times. The typos are introduced with the patch, see e.g. https://launchpadlibrarian.net/175197315/pssh_2.3.1-1.diff.gz – just search for “paralll”. A simple sed 's/paralllel/parallel/g' should do the trick. ** Description changed: In every `parallel-ssh` manpage from Xenial (http://manpages.ubuntu.com/manpages/xenial/en/man1/parallel-ssh.1.html) to Bionic (http://manpages.ubuntu.com/manpages/bionic/en/man1/parallel- - ssh.1.html), the command is called para'''lll'''el-ssh multiple times. + ssh.1.html), the command is called paralllel-ssh multiple times. The typos are introduced with the patch, see e.g. https://launchpadlibrarian.net/175197315/pssh_2.3.1-1.diff.gz – just search for “paralll”. A simple sed 's/paralllel/parallel/g' should do the trick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769314 Title: parallel-ssh manpage misspells command name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pssh/+bug/1769314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
slimjet is another victim root@aio:/home/aio/Downloads# dpkg -i slimjet_amd64.deb Selecting previously unselected package slimjet. (Reading database ... 682186 files and directories currently installed.) Preparing to unpack slimjet_amd64.deb ... Unpacking slimjet (18.0.5.0) ... dpkg: dependency problems prevent configuration of slimjet: slimjet depends on libcurl3; however: Package libcurl3 is not installed. dpkg: error processing package slimjet (--install): dependency problems - leaving unconfigured Processing triggers for menu (2.1.47ubuntu2) ... Processing triggers for gnome-menus (3.13.3-11ubuntu1) ... Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.23-1ubuntu3) ... Processing triggers for mime-support (3.60ubuntu1) ... Processing triggers for man-db (2.8.3-2) ... Errors were encountered while processing: slimjet root@aio:/home/aio/Downloads# apt install -f Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages will be REMOVED: slimjet 0 to upgrade, 0 to newly install, 1 to remove and 20 not to upgrade. 1 not fully installed or removed. After this operation, 260 MB disk space will be freed. Do you want to continue? [Y/n] n Abort. root@aio:/home/aio/Downloads# apt install libcurl3 Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libcurl3 : Conflicts: libcurl4 but 7.58.0-2ubuntu3 is to be installed libcurl4 : Conflicts: libcurl3 but 7.58.0-2ubuntu2 is to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). root@aio:/home/aio/Downloads# apt --fix-broken install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages will be REMOVED: slimjet 0 to upgrade, 0 to newly install, 1 to remove and 20 not to upgrade. 1 not fully installed or removed. After this operation, 260 MB disk space will be freed. Do you want to continue? [Y/n] n Abort. root@aio:/home/aio/Downloads# uname -a Linux aio 4.15.10-041510-generic #201803152130 SMP Thu Mar 15 21:32:57 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@aio:/home/aio/Downloads# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769325] [NEW] canonical-livepatch: unable to enable it through software-properties-gtk
Public bug reported: Trying to enable canonical-livepatch through software-properties-gtk, the application itself gets stuck on access window. Nothing happens. Even when trying to enable canonical-livepatch through a terminal, running: sudo canonical-livepatch enable I receive the message: "canonical-livepatch command not found" I succeded running the command through gksu ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat May 5 11:06:30 2018 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "screenshot showing the described issue" https://bugs.launchpad.net/bugs/1769325/+attachment/5134265/+files/Istantanea_2018-05-05_11-12-42.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769325 Title: canonical-livepatch: unable to enable it through software-properties- gtk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769324] [NEW] canonical-livepatch: unable to enable it through software-properties-gtk
Public bug reported: Trying to enable canonical-livepatch through software-properties-gtk, the application itself gets stuck on access window. Nothing happens. Even when trying to enable canonical-livepatch through a terminal, running: sudo canonical-livepatch enable I receive the message: "canonical-livepatch command not found" I succeded running the command through gksu ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat May 5 11:06:30 2018 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "screenshot showing the described issue" https://bugs.launchpad.net/bugs/1769324/+attachment/5134261/+files/Istantanea_2018-05-05_11-12-42.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769324 Title: canonical-livepatch: unable to enable it through software-properties- gtk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646468] Re: GNOME Software catalog entry missing for Qt Creator
** Changed in: qtcreator (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/1646468 Title: GNOME Software catalog entry missing for Qt Creator To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtcreator/+bug/1646468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769329] [NEW] package hostapd 2:2.6-15ubuntu2 failed to install/upgrade: installed hostapd package post-installation script subprocess returned error exit status 1
Public bug reported: nothing just prompted me to do so ProblemType: Package DistroRelease: Ubuntu 18.04 Package: hostapd 2:2.6-15ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: hostapd:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat May 5 14:05:44 2018 ErrorMessage: installed hostapd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-12-18 (137 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 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.1 SourcePackage: wpa Title: package hostapd 2:2.6-15ubuntu2 failed to install/upgrade: installed hostapd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago) ** Affects: wpa (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/1769329 Title: package hostapd 2:2.6-15ubuntu2 failed to install/upgrade: installed hostapd package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1769329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769056] Re: driverless printing generates wrong language/encoding PPD
CUPS generate non-globalized PPD in this context, so I believe it should put LanguageVersion/LanguageEncoding as follows the locale of strings, not hard-code to English/ISOLatin1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769056 Title: driverless printing generates wrong language/encoding PPD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1769056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768764] Re: disable wayland by default - nvidia proprietary drivers backlight
This is a duplicate of bug #1720438 ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Confirmed ** Summary changed: - disable wayland by default - nvidia proprietary drivers backlight + nvidia proprietary drivers backlight now working on gnome but do on kde ** Summary changed: - nvidia proprietary drivers backlight now working on gnome but do on kde + Fn for nvidia backlight working on kde but not on gnome -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768764 Title: Fn for nvidia backlight working on kde but not on gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1768764/+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
This happened to me after upgrading 17.10 to 18.04. I decided to do a fresh install of 18.04 and problem persists. -- 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 1743299] Re: qualcomm atheros ar3012 bluetooth 4.0
*** This bug is a duplicate of bug 1764645 *** https://bugs.launchpad.net/bugs/1764645 ** This bug has been marked a duplicate of bug 1764645 Bluetooth not working -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743299 Title: qualcomm atheros ar3012 bluetooth 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769338] Re: software-properties-gtk gets stuck when switching from nvidia to nouveau
If I click Cancel and select nvidia and apply same problem, stays there forever. ** Summary changed: - software-properties-gtk gets stuck when switching from nvidia to nouveau + software-properties-gtk gets stuck when switching from nvidia to nouveau and vice-versa -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769338 Title: software-properties-gtk gets stuck when switching from nvidia to nouveau and vice-versa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769338] Re: software-properties-gtk gets stuck when switching from nvidia to nouveau
root@ubuntu:~# ubuntu-drivers list nvidia-driver-390 root@ubuntu:~# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769338 Title: software-properties-gtk gets stuck when switching from nvidia to nouveau and vice-versa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743299] Re: qualcomm atheros ar3012 bluetooth 4.0
*** This bug is a duplicate of bug 1764645 *** https://bugs.launchpad.net/bugs/1764645 Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1743299 Title: qualcomm atheros ar3012 bluetooth 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769338] [NEW] software-properties-gtk gets stuck when switching from nvidia to nouveau and vice-versa
Public bug reported: Switching from nvidia to nouveau makes the gui to get stuck at "Applying changes..." ** Affects: software-properties (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/1769338 Title: software-properties-gtk gets stuck when switching from nvidia to nouveau and vice-versa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769338] Re: software-properties-gtk gets stuck when switching from nvidia to nouveau
** Attachment added: "software-properties-gtk_halts-when-changing.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769338/+attachment/5134299/+files/software-properties-gtk_halts-when-changing.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769338 Title: software-properties-gtk gets stuck when switching from nvidia to nouveau and vice-versa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1769022] Re: ubuntu 18.04 freezes after the login
Thank you for your support but I was able to resolve the issue. The problem was due to the extensions that I had before upgrading. I wiped all the extensions and everything worked as a charm On 5 May 2018 at 03:00, Dave Goldsbroughwrote: > Many bugs are now accumulating with this and similar issues surrounding > Xorg. This is just one example https://bugs.launchpad.net/ > ubuntu/+source/xorg/+bug/1764087 > There are others. Some are related to Lenovo laptops but not all. > Shame that 18.04 LTS has been allowed to be released without this inherent > bug being fixed. It is damaging Ubuntu reputation. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1769022 > > Title: > ubuntu 18.04 freezes after the login > > Status in xorg package in Ubuntu: > Confirmed > > Bug description: > I am not able to log to ubuntu 18.04 after the upgrade. When I login I > get setup screen with the word "Welcome" and the system freezes > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7 > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 > Uname: Linux 4.15.0-20-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.9-0ubuntu7 > Architecture: amd64 > CompizPlugins: No value set for `/apps/compiz-1/general/ > screen0/options/active_plugins' > CompositorRunning: None > Date: Thu May 3 23:29:56 2018 > DistUpgraded: 2018-05-03 01:59:32,397 ERROR got error from > PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to > execute child process “./xorg_fix_proprietary.py” (No such file or > directory) (8)) > DistroCodename: bionic > DistroVariant: ubuntu > GraphicsCard: >Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G] > [1002:9647] (prog-if 00 [VGA controller]) > Subsystem: Lenovo BeaverCreek [Radeon HD 6520G] [17aa:3971] > InstallationDate: Installed on 2016-11-19 (530 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > MachineType: LENOVO 129925U > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic > root=UUID=91dffd26-787f-4656-94b0-9568086633ac ro radeon.dpm=1 > SourcePackage: xorg > UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) > dmi.bios.date: 07/20/2011 > dmi.bios.vendor: LENOVO > dmi.bios.version: 54CN18WW > dmi.board.asset.tag: Base Board Asset Tag Unknown > dmi.board.name: Torpedo > dmi.board.vendor: LENOVO > dmi.board.version: 109-C06210-00B > dmi.chassis.asset.tag: Chassis Asset Tag Unknown > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: Chassis Version Unknown > dmi.modalias: dmi:bvnLENOVO:bvr54CN18WW:bd07/20/2011:svnLENOVO: > pn129925U:pvrIdeapadZ575:rvnLENOVO:rnTorpedo:rvr109- > C06210-00B:cvnLENOVO:ct10:cvrChassisVersionUnknown: > dmi.product.family: IDEAPAD > dmi.product.name: 129925U > dmi.product.version: Ideapad Z575 > dmi.sys.vendor: LENOVO > version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 > version.libdrm2: libdrm2 2.4.91-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 > version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.10.5-1ubuntu1 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20171229-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau > 1:1.0.15-2 > xserver.bootTime: Thu May 3 22:52:41 2018 > xserver.configfile: default > xserver.errors: > > xserver.logfile: /var/log/Xorg.0.log > xserver.version: 2:1.19.6-1ubuntu4 > xserver.video_driver: radeon > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769022/+subscriptions > -- Ghassan Mina IT/GIS Specialist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769022 Title: ubuntu 18.04 freezes after the login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765616] Re: freeipa server install fails - RuntimeError: CA configuration failed.
dogtag-pki server now runs on bionic using 8.5.30-1ubuntu1.2 from the ppa. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765616 Title: freeipa server install fails - RuntimeError: CA configuration failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1765616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769345] [NEW] Master The Skills Of Web Development And Be Successful.
Public bug reported: Web Development: Web development extensively alludes to the errands related with creating sites for facilitating by means of intranet or web. The web development process incorporates website architecture, web content improvement, customer side/server-side scripting and system security design, among different assignments. Master The Skills Of Web Development And Be Successful: As any individual who composes code as a profession will let you know, web development is hard. The development of programs and devices to work for, nearby the dialects and structures to work with, has left engineers with all the more a test than at any other time. Given that the quantity of assets out there for figuring out how to manufacture web applications is overpowering and frequently incorporates obsolete material, here is a rundown of general standards, aptitudes and dialects. Rely on it: You'll require them. HTML and CSS: Try not to be tricked into intuition these are the simple parts. We are as yet figuring out how to ace HTML5 and CSS3 to make quick and lovely encounters in programs over our developing rundown of Devices. That is the reason numerous front-end engineers (a.k.a. client encounter (UX) creators/engineers) are acquiring higher wages than server-side designers nowadays. Furthermore, in light of current circumstances; UX building is hard. JavaScript: Full-stack JavaScript is hot right now, and it might not relax at any factor in the near destiny (if at any factor). While severa designers assume they "recognise JavaScript" in light of the truth that they are able to compose a touch of jQuery (that's crucial, glaringly), the dialect is rapidly reworking right into a pervasive and hearty device for servers, gadgets, robots and even web programs. By taking in this, you will abstain from sitting idle jumping into nonconcurrent utilitarian programming and model based programming. You'll moreover soak up a middle association of JavaScript libraries and structures. Product Management: In the wake of conversing with many contracting administrators in the course of recent months, a typical grumbling I hear is that engineers need item sensibilities. As such, there aren't sufficient individuals who know how to construct awesome items and compose incredible code. Item administration incorporates the capacity to comprehend business targets, deal with a task (as a rule), grasp spry work processes, and listen successfully to clients to change an item in like manner. Writing in a check box versus a radio catch, for instance, is a business choice. Engineers need to figure out how to precisely settle on these sorts of choices to make the activity of full-time item administrator less troublesome (or not required). Frameworks: JavaScript, Ruby, PHP, Java, C# and Python all have different structures intended to make web development more wonderful (i.e. accomplishing more in less time). Pick one and learn it extremely well. Fabricate various web applications with it and ensure you've secured whatever number distinctive highlights as could reasonably be expected on both the server and program side of things. Running inside and out with one dialect makes it less demanding to learn new structures not far off. Git: Rendition control of your code is fundamental, and Git has won the day among the web developer group as the go-to instrument for joint effort, record-keeping and consolidation with arrangement forms. In the event that you are simply beginning, I would exceptionally prescribe Try Git and taking part in "social coding" by means of GitHub. Test-Driven and Behavior-Driven Development (TDD and BDD): Not having strong experience here will get you promptly expelled from the candidate pool for work with an arrangement development group. The way toward composing tests and specs before you compose the code in your application will guarantee you have sufficient scope at small scale and full scale levels in your application. JSON APIs: This merits its very own state on the grounds that JavaScript Object Notation (JSON) is the overwhelming dialect of robotized correspondence between administrations on the web today. Developers should know both how to function with APIs and how to fabricate their own. This is critical in light of the fact that web advancement is winding up progressively modularized as administration arranged models turn into the standard, JavaScript systems turn out to be more predominant, outlining for portable begins from the very first moment, and the consolidation of outsider APIs keeps on inclining up. Background Tasks: In any case, if this is finished amid an indistinguishable demand from accepting the shape information, it can make a moderate affair for the client. In the event that the messages are sent a couple of moments after a foundation undertaking, no major ordeal. These seemingly insignificant details matter. Once more, speed is extremely vital. Web engineers ought
[Bug 1769288] Re: indicator-datetime displays the date unnaturally in Japanese
So, it seems the root is that Japan uses ISO dating typically, even handwritten, and the new default uses not ISO, and there's no GUI option to set it as such. Not so much a bug as a design choice. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769288 Title: indicator-datetime displays the date unnaturally in Japanese To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1769288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769288] Re: indicator-datetime displays the date unnaturally in Japanese
Hey, from https://askubuntu.com/questions/237941/how-to-configure-the- clock-date-format-to-iso-8601-in-unity I was able to sort this manually: There's no easy way to do it in the GUI. One can either use dconf-editor (which is GUI-ish), and edit two keys in /com/canonical/indicator/datetime (time-format to custom, and custom- time-format to the desired strftime directives, in your case %F %R (or, equivalently, %Y-%m-%d %H:%M)), or do it directly from the terminal with the following two commands (which, just to be clear, change the same keys): dconf write /com/canonical/indicator/datetime/time-format "'custom'" dconf write /com/canonical/indicator/datetime/custom-time-format "'%F %R I replaced %Y-%m-%d %H:%M with %Y年%m月%d日 %H:%M However, the default remains not sane :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769288 Title: indicator-datetime displays the date unnaturally in Japanese To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1769288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769346] Re: Unable to install 18.04 server AMD64 with targeted kernel: initramfs-tools
If I run the "install the system" process a second time immediately afterwards, it passes without errors/warnings but after installation when system restarts: error: file '/boot/grub/i386-pc/normal.mod' not found. Entering rescue mode... grub rescue> -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769346 Title: Unable to install 18.04 server AMD64 with targeted kernel: initramfs- tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539412] Re: debootstrap fails if the directory contains a space
** Changed in: debootstrap (Debian) Status: Fix Released => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/539412 Title: debootstrap fails if the directory contains a space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/539412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769310] [NEW] "bootloader install failed" dialog box broken
Public bug reported: On attempting to update to 18.04, and running into problems with my Ubuntu video card, I decided to try to reinstall the OS, booting from a USB formatted with the 18.04 ISO image. So far so good, until I got to the the "bootloader install failed" dialog box. Unfortunately, no matter which of the options I select, I cannot make the "OK" button take effect, and I'm stuck on that dialog box. ** Affects: debian-installer (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/1769310 Title: "bootloader install failed" dialog box broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1769310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768661] Re: can't make WIFI work
At a terminal screen have you tried entering the command? sudo service network-manager restart -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768661 Title: can't make WIFI work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769320] Re: Docky.exe assert failure: free(): invalid pointer
*** This bug is a duplicate of bug 1758268 *** https://bugs.launchpad.net/bugs/1758268 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1758268, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1769320/+attachment/5134244/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1769320/+attachment/5134246/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1769320/+attachment/5134249/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1769320/+attachment/5134250/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1769320/+attachment/5134251/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1769320/+attachment/5134252/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1769320/+attachment/5134253/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1758268 ** Information type changed from Private Security to Public Security ** 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/1769320 Title: Docky.exe assert failure: free(): invalid pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docky/+bug/1769320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768740] Re: virtualbox-ext-pack fails to validate or finish install properly
*** This bug is a duplicate of bug 1767402 *** https://bugs.launchpad.net/bugs/1767402 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1767402, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1767402 hash mismatch or wrong accept-license key trying to install virtualbox-ext-pack 5.2.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768740 Title: virtualbox-ext-pack fails to validate or finish install properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox-ext-pack/+bug/1768740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727842] Re: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10
Same as @dimztimz - toggling Commands plugin (doesn't matter on or off) in ccsm seems to make media keys work again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727842 Title: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1727842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764087] Re: Wrongly boots into low graphics mode
Cross reference now to a lightdm bug which has been raised as a consequence of https://bugs.freedesktop.org/show_bug.cgi?id=106407 saying it is not a xorg bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764087 Title: Wrongly boots into low graphics mode To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1764087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767376] Re: Segmentation fault in mupdf
This is a redundant vulnerability that has been reported and fixed in 1.13.0 . http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17858 2018-05-02 3:17 GMT+08:00 Seth Arnold <1767...@bugs.launchpad.net>: > Hi Fy, probably it's quickest if you request the CVE directly from MITRE > using: > > https://cveform.mitre.org/ > > Let us know how it goes. Thanks. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1767376 > > Title: > Segmentation fault in mupdf > > Status in mupdf package in Ubuntu: > Incomplete > > Bug description: > Package: mupdf > Version: Bionic (1.12.0+ds1-1) > > Hi, > We found a heap-buffer-overwrite vulnerability in mupdf. > This affects ubuntu Bionic (1.12.0+ds1-1). > > Crash happennd at ensure_solid_xref (pdf-xref.c:211): > 209 for (i =0; i < sub->len; i++) > 210 { > 211new_sub->table[i+sub->start] = sub->table[i] > 212 } > the variable "sub->start" could be a big number at run time, which > cause this crash. > > We have submit this issue to the developers, testcase can be found > at: > https://bugs.ghostscript.com/show_bug.cgi?id=699225 > > run the sample with command: > mutool draw poc.pdf > or: > mupdf poc.pdf > > We found this vulnerability is not fixed in newly ubuntu 18.04 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/mupdf/+bug/ > 1767376/+subscriptions > ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-17858 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767376 Title: Segmentation fault in mupdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mupdf/+bug/1767376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768906] Re: Xorg crash
Difference between remove & purge: - 'remove' uninstall the package, but does not remove the package settings, which can disturb the system and conflict with an other driver choice. - 'purge' remove both package & its settings; that is way recommended. About /etc/X11/xorg.conf, this is no more used since a couple releases. so your system should not finf such a path anyway. Your real problem is not about 'xorg' as you have reported but 'gdm' and/or 'gnome-session' ** May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): Failed to acquire modesetting permission. May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): Failing initialization of X screen 0 ** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768906 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs