[Bug 2058152] Re: running the daily cron job is VERY slow
I added the new index on 2024-03-12. The cronjob kicks off at 01:00 and you can see that it greatly reduced the time. On 2024-03-09 you can see that the cronjob started at 01:00 completed at 21:00 ... this is the 20 hour run. ** Attachment added: "Screenshot 2024-03-17 12.38.32.png" https://bugs.launchpad.net/ubuntu/+source/opendmarc/+bug/2058152/+attachment/5756585/+files/Screenshot%202024-03-17%2012.38.32.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058152 Title: running the daily cron job is VERY slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opendmarc/+bug/2058152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058152] [NEW] running the daily cron job is VERY slow
Public bug reported: I found that the daily cron job was taking many hours. Once it took 20 hours to complete! In mysql, I added a new index on the `messages` table, on the from_domain column. Now the cronjob takes four minutes, every time it runs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: opendmarc 1.3.2-7ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-1055.60~20.04.1-aws 5.15.136 Uname: Linux 5.15.0-1055-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Mar 17 12:42:19 2024 Ec2AMI: ami-063aa838bd7631e0b Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-1b Ec2InstanceType: t3a.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: opendmarc UpgradeStatus: Upgraded to focal on 2021-07-10 (981 days ago) mtime.conffile..etc.default.opendmarc: 2022-08-05T08:39:10.606732 mtime.conffile..etc.opendmarc.conf: 2022-12-13T20:42:56.531125 ** Affects: opendmarc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058152 Title: running the daily cron job is VERY slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opendmarc/+bug/2058152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056713] Re: eog opens with incorrect upper left xy window coordinates cannot change in dconf or in any of the xml settings files, observed in wayland, and confirmed it is opening in wayland. Whe
Keep in mind the nvidia card is setup as computer only, and is not used for graphics. I have an AMD Card on open driver for my video and nvidia card does not have the opengl drivers installed. AMD is set in settings for to be default for DisplayManager and for Gnome. No X threads are running on the NVIDIA-SMI and just want to be clear that card is not the one in use and runs workloads only. Has python threads once in a while, but wayland works good no issue otherwise has for a long time and this app has seeming always displayed wrong size and x,y coordinates upon open at least in Wayland. I do not recall, it might not have had this issue in X11. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056713 Title: eog opens with incorrect upper left xy window coordinates cannot change in dconf or in any of the xml settings files, observed in wayland, and confirmed it is opening in wayland. When attempt to confirm I ran xprop and tried to launch eog again by clicking on a file that opens it by default and it froze the whole gui session, and locked up my ability to press ctrl-alt-f2, for about a halfhour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/2056713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056713] [NEW] eog opens with incorrect upper left xy window coordinates cannot change in dconf or in any of the xml settings files, observed in wayland, and confirmed it is opening in wayland. W
Public bug reported: logs an error when opening : Mar 10 21:45:07 meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed eog opens with incorrect upper left xy window coordinates cannot change in dconf or in any of the xml settings files, observed in wayland, and confirmed it is opening in wayland. When attempt to confirm I ran xprop and tried to launch eog again by clicking on a file that opens it by default and it froze the whole gui session, and locked up my ability to press ctrl-alt-f2, for about a halfhour. I cannot get the crash to happen again, but keeps opening with incorrect size, looks like maybe is using display one for relative positioning but my primary scree is display 2 and is in the middle, so my screens go display 1,2,3 in order and pretty sure somewhere it pulls the relative size of the larger monitor which is monitor 1, and then tries to apply the size and display it on monitor 2 which is smaller and the relative x,y, position of the window is incorrect and oddly the height of the and when I alt-space, move to monitor left, appears exactly at top of monitor on the display 1. Looks like cannot be corrected in wayland compositor, and cannot be corrected in dconf, or in enum.xml settings file, or any of the other .xml files that are with the package. not able to make it give any other errors that I see the logs for, just: Mar 10 21:46:54 meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: eog 42.0-1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Mar 10 21:26:13 2024 InstallationDate: Installed on 2022-06-18 (631 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056713 Title: eog opens with incorrect upper left xy window coordinates cannot change in dconf or in any of the xml settings files, observed in wayland, and confirmed it is opening in wayland. When attempt to confirm I ran xprop and tried to launch eog again by clicking on a file that opens it by default and it froze the whole gui session, and locked up my ability to press ctrl-alt-f2, for about a halfhour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/2056713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed
I recently was able to work around this issue using the nvidia 510 drivers and following this suggestion: https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150/3 Thus far no issues with resuming. Not sure if it helps with 460 but thought I'd share. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911055 Title: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1911055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940131] Re: sudo ua attach is not working
** Changed in: ubuntu-advantage-tools (Ubuntu) Assignee: (unassigned) => shawn audet (thabeast1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940131 Title: sudo ua attach is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1940131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935727] [NEW] package xymon-client 4.3.30 failed to install/upgrade: conflicting packages - not installing xymon-client
Public bug reported: I was doing an upgrade from 18.04 to 20.04 and this bug was automatically built by the system. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: xymon-client 4.3.30 ProcVersionSignature: Ubuntu 5.4.0-1051.53~18.04.1-aws 5.4.119 Uname: Linux 5.4.0-1051-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jul 9 22:03:21 2021 Ec2AMI: ami-063aa838bd7631e0b Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-1b Ec2InstanceType: t3a.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: conflicting packages - not installing xymon-client Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: xymon Title: package xymon-client 4.3.30 failed to install/upgrade: conflicting packages - not installing xymon-client UpgradeStatus: Upgraded to focal on 2021-07-10 (0 days ago) ** Affects: xymon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package ec2-images focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935727 Title: package xymon-client 4.3.30 failed to install/upgrade: conflicting packages - not installing xymon-client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1935727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed
I was also having a suspend/resume with 460.56+. Rolling back to 460.39 fixed it. Older packages can be found at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-460/+publishinghistory List of packages I have installed: libnvidia-cfg1-460:amd64 libnvidia-common-460 libnvidia-compute-460:amd64 libnvidia-compute-460:i386 libnvidia-decode-460:amd64 libnvidia-decode-460:i386 libnvidia-encode-460:amd64 libnvidia-encode-460:i386 libnvidia-extra-460:amd64 libnvidia-extra-460:i386 libnvidia-fbc1-460:amd64 libnvidia-fbc1-460:i386 libnvidia-gl-460:amd64 libnvidia-gl-460:i386 libnvidia-ifr1-460:amd64 libnvidia-ifr1-460:i386 nvidia-compute-utils-460 nvidia-dkms-460 nvidia-driver-460 nvidia-kernel-common-460 nvidia-kernel-source-460 nvidia-prime nvidia-prime-applet nvidia-settings nvidia-utils-460 xserver-xorg-video-nvidia-460 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911055 Title: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1911055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919431] [NEW] Installtion crashed on grub - Dual boot option
Public bug reported: While setting up grub the installer crashed ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 17 11:09:11 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=en_ZA.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: linux-image-5.8.0-25-generic linux-base SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.13 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919431 Title: Installtion crashed on grub - Dual boot option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1919431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 170049] Re: Inverted ruler co-ordinate system
The fix is barely adequate for only a few people IMO. Some 1990s-era programs for graphical work had the ability to drag the corner where the rulers meet, out into the document somewhere, to set a new origin. I would expect to _at least_ have a document-specific setting to set the origin anywhere on the page, numerically. If I'm drawing a room (furniture layout etc.), I don't want the corner of the room to need to be at the corner of the page. It should be whichever corner I decided to start measuring from. (And that in fact is what I'm trying to do at this very moment.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/170049 Title: Inverted ruler co-ordinate system To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/170049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842886] Re: Yaru-dark shell menus and dialogs are not dark
I followed this guide and it sorted me out: https://allthings.how/how- to-fully-enable-dark-mode-in-ubuntu-20-04-including-calendar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842886 Title: Yaru-dark shell menus and dialogs are not dark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902139] [NEW] Can not upgrade from Ubuntu 18 to 20
Public bug reported: Can not upgrade to version 20 from 18. Seems to be a broken issue with mutter?? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.34 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 29 13:49:37 2020 InstallationDate: Installed on 2019-07-04 (483 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-29 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902139 Title: Can not upgrade from Ubuntu 18 to 20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1902139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895212] Re: Strange ui and dock icon behavior
Fixing the .desktop file seems to have resolved the issues I was seeing. ** Attachment added: "higan.desktop" https://bugs.launchpad.net/ubuntu/+source/higan/+bug/1895212/+attachment/5422187/+files/higan.desktop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895212 Title: Strange ui and dock icon behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/higan/+bug/1895212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895424] Re: duplicate rc local service
Seems to only happen on systems that upgrade from 16LTS to 18LTS to 20TLS (using do-release-upgrade -d) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895424 Title: duplicate rc local service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895424] Re: duplicate rc local service
** Changed in: systemd (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895424 Title: duplicate rc local service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895424] Re: duplicate rc local service
journalctl -b | grep local shows: Sep 17 19:48:34 ubuntu systemd[1]: Starting LSB: Run /etc/rc.local if it exist... Sep 17 19:48:35 ubuntu smartd[696]: smartd 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-47-generic] (local build) Sep 17 19:48:35 ubuntu polkitd[771]: started daemon version 0.105 using authority implementation `local' version `0.105' Sep 17 19:48:35 ubuntu systemd[1]: Started LSB: Run /etc/rc.local if it exist. Sep 17 19:48:41 ubuntu systemd-resolved[868]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test Sep 17 19:48:42 ubuntu systemd[1]: Starting /etc/rc.local Compatibility... Sep 17 19:48:42 ubuntu systemd[1]: Started /etc/rc.local Compatibility. root@ubuntu:~# systemctl | grep local rc-local.service loaded active exited/etc/rc.local Compatibility rc.local.service loaded active exitedLSB: Run /etc/rc.local if it exist If I add something like: echo Running rc.local `date` >> /root/rc.local.log to /etc/rc.local delete the /root/rc.log and reboot I definitely get 2 entries: root@ubuntu:~# cat /root/rc.local.log Running rc.local Thu 17 Sep 2020 07:55:10 PM PDT Running rc.local Thu 17 Sep 2020 07:55:12 PM PDT ** Attachment added: "journalctl -b outpout attached." https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895424/+attachment/5411996/+files/journal.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895424 Title: duplicate rc local service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895424] [NEW] duplicate rc local service
Public bug reported: Upgrading from Ubuntu 18.04 to 20.04 using "do-release-upgrade -d" Creates two systemd services: rc.local and rc-local This has the unfortunate event of running /etc/rc.local multiple times during bootup ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Package changed: grub2 (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895424 Title: duplicate rc local service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895212] [NEW] Strange ui and dock icon behavior
Public bug reported: Upon launch, it can be seen that the main ui screen has a transparent background and the app icon in the dock is blank. Otherwise functions as expected. See attached screencap. ** Affects: higan (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2020-09-10 15-37-37.png" https://bugs.launchpad.net/bugs/1895212/+attachment/5409525/+files/Screenshot%20from%202020-09-10%2015-37-37.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895212 Title: Strange ui and dock icon behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/higan/+bug/1895212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second
I am experiencing this also on 20.04 running on Skylake (Intel 520). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842886] Re: Yaru-dark shell menus and dialogs are not dark
Thanks Lyubomir, this is a good workaround. I installed the user themes extension with 'apt-get install gnome-shell-extensions', then enabled it in gnome tweaks and set the shell theme to yaru-dark. After a few gnome restarts, things look great. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842886 Title: Yaru-dark shell menus and dialogs are not dark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1842886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842886] Re: Yaru-dark shell menus and dialogs are not dark
Please fix this. It looks bad and defeats the purpose of using a dark theme. Previous versions just used dark menus as the default and that was better. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842886 Title: Yaru-dark shell menus and dialogs are not dark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1842886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875085] Re: curtin install hook fails with No closing quotation on new 20.04 install
Using ioreg on MacOS also shows that SanDisk used a quote in the USB Vendor Name. I have around 30 of these drives and everyone I've checked has that quote in the vendor name. Cruzer Fit@1462 https://bugs.launchpad.net/bugs/1875085 Title: curtin install hook fails with No closing quotation on new 20.04 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1875085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875085] Re: curtin install hook fails with No closing quotation on new 20.04 install
** Package changed: ubuntu => curtin (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875085 Title: curtin install hook fails with No closing quotation on new 20.04 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1875085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875085] Re: curtin install hook fails with No closing quotation on new 20.04 install
https://stackoverflow.com/questions/57483794/python-shlex-no-closing- quotations-error-how-to-deal-with -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875085 Title: curtin install hook fails with No closing quotation on new 20.04 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1875085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875085] Re: curtin install hook fails with No closing quotation on new 20.04 install
It looks like the issue is SanDisk is including quotes in their device names. Not sure who's problem this actually is. udevadm? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875085 Title: curtin install hook fails with No closing quotation on new 20.04 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1875085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875085] Re: curtin install hook fails with No closing quotation on new 20.04 install
This failure doesn't happen on the same usb drive for 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/1875085 Title: curtin install hook fails with No closing quotation on new 20.04 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1875085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875085] Re: curtin install hook fails with No closing quotation on new 20.04 install
Here is the output from udevadm info --query=property --export /dev/sdc1. Note /dev/sdc1 is the USB Drive being used to install ubuntu. ** Attachment added: "output.txt" https://bugs.launchpad.net/ubuntu/+bug/1875085/+attachment/5360532/+files/output.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875085 Title: curtin install hook fails with No closing quotation on new 20.04 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1875085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875085] [NEW] curtin install hook fails with No closing quotation on new 20.04 install
Public bug reported: While doing a new install of 20.04 Server to Software Raid 1 the installation fails while running one of the curtin hooks related to udevadm_info. I'm including the complete crash log. ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "1587844054.616324902.install_fail.crash" https://bugs.launchpad.net/bugs/1875085/+attachment/5360531/+files/1587844054.616324902.install_fail.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875085 Title: curtin install hook fails with No closing quotation on new 20.04 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1875085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785157] Re: external (letsencrypt) certs failing to parse due to pyasn1
FreeIPA fixed this issue in https://pagure.io/freeipa/issue/7685. Will this be back-ported to 18.04 because FreeIPA doesn't work without it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785157 Title: external (letsencrypt) certs failing to parse due to pyasn1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyasn1/+bug/1785157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861440] Re: [upstream regression] wget does not honor dot-prefixed domains in no_proxy env variable
** Bug watch added: Red Hat Bugzilla #1763702 https://bugzilla.redhat.com/show_bug.cgi?id=1763702 ** Also affects: wget (CentOS) via https://bugzilla.redhat.com/show_bug.cgi?id=1763702 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/1861440 Title: [upstream regression] wget does not honor dot-prefixed domains in no_proxy env variable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1861440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861440] Re: wget does not honor dot-prefixed domains in no_proxy env variable
Just another data point. I searched Debian packages and there is not an associated release impacted by this issue. Debian oldstable (stretch) ships wget 1.18 (pre-regression release). See https://packages.debian.org/stretch/wget Debian stable (buster) ships wget 1.20 (regression fixed release). See https://packages.debian.org/buster/wget ** Summary changed: - wget does not honor dot-prefixed domains in no_proxy env variable + [upstream regression] wget does not honor dot-prefixed domains in no_proxy env variable -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861440 Title: [upstream regression] wget does not honor dot-prefixed domains in no_proxy env variable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1861440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861440] [NEW] wget does not honor dot-prefixed domains in no_proxy env variable
Public bug reported: Traditionally (AFAIK for at least the last decade), tools that support the no_proxy environment variable support specifying an entire subdomain by prefixing it with a "dot". For example, to exclude any website under example.com from using the proxy, you would set no_proxy to .example.com (export no_proxy=.example.com). A regression in wget 1.19 changed this behavior to expect non-prefixed domains (example.com vs .example.com). This regression was ultimately fixed and released with the 1.20 release of wget. bionic includes the regressed behavior version of wget. The regression was apparently introduced in wget 1.19.3. This bug should not effect other Ubuntu releases (xenial contains 1.17.1 and both disco and eoan contain 1.20.x versions that have the upstream fix). For more details, see references below and my additional comments on the RHEL8 bug filed for this issue (RH bug 1763702 linked below). What happens: no_proxy=.example.com in bionic sends requests to the proxy server for URLs like http://www.example.com/ despite requesting proxy exception via no_proxy. What should happen: Request should bypass the proxy and go directly to the web server. (works in xenial, disco and eoan as expected). System/software information: $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 $ apt-cache policy wget wget: Installed: 1.19.4-1ubuntu2.2 Candidate: 1.19.4-1ubuntu2.2 Version table: *** 1.19.4-1ubuntu2.2 500 500 http://div6mirrors.llan.ll.mit.edu:80/ubuntu bionic-updates/main amd64 Packages 500 http://div6mirrors.llan.ll.mit.edu:80/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 1.19.4-1ubuntu2 500 500 http://div6mirrors.llan.ll.mit.edu:80/ubuntu bionic/main amd64 Packages References: * Upstream wget bug report: GNU Wget - Bugs: bug #53622 wget no_proxy leading dot on (sub)domains not working contradicting man page https://savannah.gnu.org/bugs/?53622 * Upstream commit reference that introduces the regression http://git.savannah.gnu.org/cgit/wget.git/commit/?id=fd85ac9cc623847e9d94d9f9241ab34e2c146cbf * Upstream commit reference that introduces the fix http://git.savannah.gnu.org/cgit/wget.git/commit/?id=fd85ac9cc623847e9d94d9f9241ab34e2c146cbf * Expected behavior of no_proxy as documented in the GNU Emacs manual: https://www.gnu.org/software/emacs/manual/html_node/url/Proxies.html * Red Hat Bugzilla entry for this issue (Reported against RHEL8.1) Bug 1763702 - wget is ignoring no_proxy environment variable https://bugzilla.redhat.com/show_bug.cgi?id=1763702 * Red Hat Bugzilla entry tracking the (now released) errata package for RHEL8.1 Bug 1772821 - wget is ignoring no_proxy environment variable [rhel-8.1.0.z] https://bugzilla.redhat.com/show_bug.cgi?id=1772821 ** Affects: wget (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/1861440 Title: wget does not honor dot-prefixed domains in no_proxy env variable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1861440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817537] Re: libsoup should support ntlmv2
Awesome! I revert back to stable and it's continuing to work for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817537 Title: libsoup should support ntlmv2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1817537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817537] Re: libsoup should support ntlmv2
Quick question. Will this be added to the regular updates? I'm still using proposed for this update in bionic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817537 Title: libsoup should support ntlmv2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1817537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841119] [NEW] please sync version from unstable
Public bug reported: GnuCash is really quite a bit better, for example it can create reports when multiple currencies are involved (correctly). I managed to build it on disco (I am asking for Ermine) without any backports. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnucash 1:3.4-1 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 22 18:03:42 2019 InstallationDate: Installed on 2019-02-23 (180 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: gnucash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnucash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session ** Summary changed: - please package new version + please sync version from unstable -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841119 Title: please sync version from unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1841119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817537] Re: libsoup should support ntlmv2
To clarify, it resolved the issue for me. I was previously unable to connect because NTLMv1 was turned off where I work. Now I can connect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817537 Title: libsoup should support ntlmv2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1817537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817537] Re: libsoup should support ntlmv2
I tested the proposed package and it worked for me. I connected via NTLM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817537 Title: libsoup should support ntlmv2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1817537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833440] [NEW] My University disabled NTLMv1 and Evolution won't let me authenticate to Exchange
Public bug reported: There is a newer version of libsoup that allows NTLMv2 authentication that resolves this issue. Here is a bug from the Gnome libsoup bug report: https://gitlab.gnome.org/GNOME/libsoup/issues/114 In this bug report for Evolution: https://gitlab.gnome.org/GNOME/evolution-ews/issues/38 someone mentions "the change landed after 2.64.0 and before 2.65.1 and seems to be part of 2.65.1+ only" ** Affects: libsoup2.4 (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/1833440 Title: My University disabled NTLMv1 and Evolution won't let me authenticate to Exchange To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1833440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832964] Re: Suggested fix/enhancement for wireless-tools.if-pre-up script
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930585 ** Bug watch added: Debian Bug tracker #930585 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930585 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832964 Title: Suggested fix/enhancement for wireless-tools.if-pre-up script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-tools/+bug/1832964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832964] [NEW] Suggested fix/enhancement for wireless-tools.if-pre-up script
Public bug reported:
I've been experiencing an issue with my wireless card and ifup relating
to this script. I have a fix for it and thought the devs here might be
interested.
This is the issue: If a setting fails to be applied, the script brings
the card up and then tries to apply the setting again. This is fine, but
it leaves the card up. Later on in the ifup process other scripts try to
access the card and if the card is up it will respond that it's busy and
ifup fails.
My solution has been to alter the wireless-tools if-pre-up script so
that it ends by running ifconfig down in this case. Here is the patch:
--- ./wireless-tools.if-pre-up 2017-04-22 10:15:05.0 -0400
+++ ./wireless-tools2019-06-03 22:39:24.314725863 -0400
@@ -6,7 +6,7 @@
exit 0
fi
-# check if this is a 802.11 device we're supposed to be effecting
+# check if this is a 802.11 device we're supposed to be affecting
case "${IF_WIRELESS:-enable}" in
wireless-tools|iwconfig)
# *we* and not some other 802.11 tool should be used
@@ -140,4 +140,5 @@
FAIL=
ifconfig "$IFACE" up
apply_settings
+ ifconfig "$IFACE" down
fi
** Affects: wireless-tools (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/1832964
Title:
Suggested fix/enhancement for wireless-tools.if-pre-up script
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-tools/+bug/1832964/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827523] [NEW] logf -lm ppc64el broken under qemu
Public bug reported:
This program does not work as expected:
#include
#include
#include
int main(int argc) {
vector float o = {4, 3, 2, 0};
printf("%f %f %f %f\n", o[0], logf(argc), logf(4.0), logf(o[0]));
}
logf always returns -inf when it is run (gcc is analyzing the constant,
logf(4.0)).
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: libc6:ppc64el 2.29-0ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri May 3 09:20:00 2019
Dependencies:
gcc-9-base 9-20190402-1ubuntu1
libc6 2.29-0ubuntu2
libgcc1 1:9-20190402-1ubuntu1
libidn2-0 2.0.5-1
libunistring2 0.9.10-1ubuntu2
InstallationDate: Installed on 2019-02-23 (69 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
PackageArchitecture: ppc64el
SourcePackage: glibc
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: glibc (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug disco ppc64el wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827523
Title:
logf -lm ppc64el broken under qemu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1827523/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725779] Re: Gnome network manager cannot find authentication binary
Confirming that the bug still happens on 19.04. I'm using network- manager-vpnc-gnome which has this issue. However, nm-applet does work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725779 Title: Gnome network manager cannot find authentication binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/1725779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823562] [NEW] failed to copy all files
Public bug reported: upon installing ubuntu I was creating a name for my pc. I went to type an apostrophe and it crashed and said it was unable to transfer all files. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 14:43:22 2019 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823562 Title: failed to copy all files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1823562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822496] [NEW] dpkg-buildpackage build-dep list should be easier to install
Public bug reported: When building from source dpkg-buildpackage very kindly tells you what build-dep packages are not installed. Usually, I just want install all these packages. However this list, because of the version requirements, cannot be copied and pasted with "apt install" in front. There are three way to fix this 1. teach apt to understand these version requirements 2. have dpkg output another line without the versions 3. add a flag to dpkg-buildpackage that makes it call into apt to install these (not recommended) $ dpkg-buildpackage -b dpkg-buildpackage: info: source package network-manager dpkg-buildpackage: info: source version 1.16.0-1 dpkg-buildpackage: info: source distribution experimental dpkg-buildpackage: info: source changed by Michael Biebl dpkg-buildpackage: info: host architecture amd64 dpkg-source --before-build . dpkg-checkbuilddeps: error: Unmet build dependencies: intltool ppp-dev (>= 2.4.7-1+1) libpolkit-gobject-1-dev libpolkit-agent-1-dev (>= 0.97) libaudit-dev libsystemd-dev (>= 209) libgirepository1.0-dev (>= 0.10.7-1~) gobject-introspection (>= 0.9.12-4~) python-gi libpsl-dev (>= 0.1) libcurl4-gnutls-dev (>= 7.24.0) gtk-doc-tools libyaml-perl libglib2.0-doc libmm-glib-dev (>= 0.7.991) libndp-dev libreadline-dev libnewt-dev (>= 0.52.15) libteam-dev (>= 1.9) libjansson-dev libbluetooth-dev (>= 5) valac (>= 0.17.1.24) python-dbus ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: dpkg 1.19.5ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 31 14:12:05 2019 InstallationDate: Installed on 2019-02-23 (36 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: dpkg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822496 Title: dpkg-buildpackage build-dep list should be easier to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1822496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806754] [NEW] Ubuntu Mate won't install grub2, I noticed that during install that gnome keyring failed so maybe that is the reason grub couldn't be installed
Public bug reported: Grub2 wouldn't install ubuntu and mint both with Mate. I noticed during the install that the gnome keyring failed. I'm thinking that may be needed to install the bootloader. If so either you guys or mate failed to check what changes gnome made to the keyring. I'm seeing them sending the information out to Gnome3 install teams but failing to inform others of the key ring changes and the gnome team loves changes, now if we could get them to reduce their code for a few revisions everything might be more stable. Hope this helps and sorry about the rant at the end. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 Date: Tue Dec 4 13:48:27 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806754 Title: Ubuntu Mate won't install grub2, I noticed that during install that gnome keyring failed so maybe that is the reason grub couldn't be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1806754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778984] Re: Parse error of /etc/apparmor.d/tunables/home.d/ubuntu after unattended-upgrades
Clarification: I followed the hint in /etc/apparmor.d/tunables/home.d/ubuntu and ran root@ubuntu:~# sudo dpkg-reconfigure apparmor In the window that popped up, I added "/home/" (which is the location of my home directories) and clicked OK. This solved the problem -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778984 Title: Parse error of /etc/apparmor.d/tunables/home.d/ubuntu after unattended-upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1778984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778984] Re: Parse error of /etc/apparmor.d/tunables/home.d/ubuntu after unattended-upgrades
I have just hit this problem on Ubuntu 18.04, and I was able to solve it by
running
root@ubuntu:~# sudo dpkg-reconfigure apparmor
Unlike the previous poster, I am not aware of any sudden powercycles. I
simply attempted to run a docker container. The docker command and
output are below, with PII redacted.
docker run --rm -v /home/[REDACTED]/projects/snap/out/log:/log -v
/home/[REDACTED]/projects/snap/django:/tmslogs -v
/home/[REDACTED]/projects/snap/out/db:/db -v
/home/[REDACTED]/projects/snap/out/media:/media -v
/home/[REDACTED]/projects/snap/out/dumps:/dumps -v
/home/[REDACTED]/projects/snap/config:/config -t -i
[REDACTED].com/tmslogs:latest /bin/bash
docker: Error response from daemon: AppArmor enabled on system but the
docker-default profile could not be loaded: running
`/sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-
default964375229` failed with output: AppArmor parser error for
/var/lib/docker/tmp/docker-default964375229 in
/etc/apparmor.d/tunables/home.d/ubuntu at line 7: Found unexpected
character: ''
root@ubuntu:~# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS"
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
root@ubuntu:~# docker --version
Docker version 17.12.1-ce, build 7390fc6
root@ubuntu:~# cat /etc/apparmor.d/tunables/home.d/ubuntu
# This file is auto-generated. It is recommended you update it using:
# $ sudo dpkg-reconfigure apparmor
#
# The following is a space-separated list of where additional user home
# directories are stored, each must have a trailing '/'. Directories added
# here are appended to @{HOMEDIRS}. See tunables/home for details.
root@ubuntu:~#
I followed the hint in /etc/apparmor.d/tunables/home.d/ubuntu and ran
root@ubuntu:~# sudo dpkg-reconfigure apparmor
This solved the problem.
After this solved the problem, this reminded me that I have modified my
/home directories. After installing Ubuntu 18.04 and creating my
default user account, I logged in and mounted a second drive into
'/home'. Perhaps anyone looking into this issue, or experiencing this
issue could take this clue and run with it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778984
Title:
Parse error of /etc/apparmor.d/tunables/home.d/ubuntu after
unattended-upgrades
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1778984/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754084] Re: Freecad crashes at start
Works for me too -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754084 Title: Freecad crashes at start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freecad/+bug/1754084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791455] [NEW] error do-release-upgrade 16.04->18.04
Public bug reported: Error log grep Broken /var/log/dist-upgrade/apt.log Broken libegl1:amd64 Depends on libegl-mesa0 [ amd64 ] < none -> 18.0.5-0ubuntu0~18.04.1 > ( libs ) Broken libwebkit2gtk-4.0-37:amd64 Depends on libegl1 [ amd64 ] < none -> 1.0.0-2ubuntu2.1 > ( libs ) Broken libdouble-conversion1:amd64 Breaks on libdouble-conversion1v5 [ amd64 ] < 2.0.1-3ubuntu2 > ( libs ) Broken yelp:amd64 Depends on libwebkit2gtk-4.0-37 [ amd64 ] < 2.20.5-0ubuntu0.16.04.1 -> 2.20.5-0ubuntu0.18.04.1 > ( libs ) (>= 2.5.3) Broken libpeas-1.0-0:amd64 Conflicts on libpeas-1.0-0-python3loader [ amd64 ] < 1.16.0-1ubuntu2 > ( libs ) Broken gnome-session-bin:amd64 Depends on libegl1 [ amd64 ] < none -> 1.0.0-2ubuntu2.1 > ( libs ) Broken libgoa-backend-1.0-1:amd64 Depends on libwebkit2gtk-4.0-37 [ amd64 ] < 2.20.5-0ubuntu0.16.04.1 -> 2.20.5-0ubuntu0.18.04.1 > ( libs ) (>= 2.15.1) Broken libgstreamer-gl1.0-0:amd64 Depends on libegl1 [ amd64 ] < none -> 1.0.0-2ubuntu2.1 > ( libs ) Broken unity-control-center:amd64 Depends on libgoa-backend-1.0-1 [ amd64 ] < 3.18.3-1ubuntu2 -> 3.28.0-0ubuntu2.1 > ( libs ) (>= 3.18.0) Broken libyelp0:amd64 Depends on libwebkit2gtk-4.0-37 [ amd64 ] < 2.20.5-0ubuntu0.16.04.1 -> 2.20.5-0ubuntu0.18.04.1 > ( libs ) (>= 2.15.1) Broken gstreamer1.0-gl:amd64 Depends on libgstreamer-gl1.0-0 [ amd64 ] < none -> 1.14.1-1ubuntu1~ubuntu18.04.1 > ( libs ) (>= 1.14.1) Broken gnome-online-accounts:amd64 Depends on libgoa-backend-1.0-1 [ amd64 ] < 3.18.3-1ubuntu2 -> 3.28.0-0ubuntu2.1 > ( libs ) (= 3.28.0-0ubuntu2.1) Broken gnome-user-docs:amd64 Depends on yelp [ amd64 ] < 3.18.1-1ubuntu4 -> 3.26.0-1ubuntu2 > ( gnome ) (>= 3) Broken gnome-control-center-faces:amd64 Conflicts on unity-control-center-faces [ amd64 ] < 15.04.0+16.04.20171130-0ubuntu1 > ( gnome ) Broken libevolution:amd64 Depends on libwebkit2gtk-4.0-37 [ amd64 ] < 2.20.5-0ubuntu0.16.04.1 -> 2.20.5-0ubuntu0.18.04.1 > ( libs ) (>= 2.15.1) Broken libsane1:amd64 Conflicts on libsane [ amd64 ] < 1.0.25+git20150528-1ubuntu2.16.04.1 > ( libs ) (< 1.0.27-1~) Broken libgjs0g:amd64 Conflicts on libgjs0e [ amd64 ] < 1.44.0-1ubuntu1 > ( libs ) Broken libpng-dev:amd64 Conflicts on libpng12-0-dev [ amd64 ] < none -> > ( none ) Broken libpng-dev:amd64 Conflicts on libpng12-dev [ amd64 ] < 1.2.54-1ubuntu1.1 > ( libdevel ) Broken libpng-dev:amd64 Conflicts on libpng3-dev [ amd64 ] < none -> > ( none ) Broken gir1.2-webkit2-4.0:amd64 Depends on libwebkit2gtk-4.0-37 [ amd64 ] < 2.20.5-0ubuntu0.16.04.1 -> 2.20.5-0ubuntu0.18.04.1 > ( libs ) (>= 2.19.4) Broken libedataserverui-1.2-2:amd64 Depends on libwebkit2gtk-4.0-37 [ amd64 ] < 2.20.5-0ubuntu0.16.04.1 -> 2.20.5-0ubuntu0.18.04.1 > ( libs ) (>= 2.15.1) Broken gnome-startup-applications:amd64 Depends on gnome-session-bin [ amd64 ] < 3.18.1.2-1ubuntu1.16.04.2 -> 3.28.1-0ubuntu3 > ( gnome ) (>= 3.28.1-0ubuntu3) Broken gnome-session:amd64 Depends on gnome-session-bin [ amd64 ] < 3.18.1.2-1ubuntu1.16.04.2 -> 3.28.1-0ubuntu3 > ( gnome ) (>= 3.28.1-0ubuntu3) Broken apparmor:amd64 Breaks on webbrowser-app [ amd64 ] < 0.23+16.04.20161028-0ubuntu2 > ( x11 ) Broken zenity:amd64 Depends on libwebkit2gtk-4.0-37 [ amd64 ] < 2.20.5-0ubuntu0.16.04.1 -> 2.20.5-0ubuntu0.18.04.1 > ( libs ) (>= 2.15.1) Broken ubuntu-release-upgrader-gtk:amd64 Depends on gir1.2-webkit2-4.0 [ amd64 ] < 2.20.5-0ubuntu0.16.04.1 -> 2.20.5-0ubuntu0.18.04.1 > ( introspection ) Broken libmutter-2-0:amd64 Depends on libegl1 [ amd64 ] < none -> 1.0.0-2ubuntu2.1 > ( libs ) Broken aptdaemon:amd64 Breaks on python3-aptdaemon.pkcompat [ amd64 ] < 1.1.1+bzr982-0ubuntu14 > ( python ) Broken update-manager:amd64 Depends on ubuntu-release-upgrader-gtk [ amd64 ] < 1:16.04.25 -> 1:18.04.25 > ( admin ) Broken gnome-user-guide:amd64 Depends on gnome-user-docs [ amd64 ] < none -> 3.28.2+git20180715-0ubuntu0.1 > ( doc ) Broken ubuntu-docs:amd64 Depends on yelp [ amd64 ] < 3.18.1-1ubuntu4 -> 3.26.0-1ubuntu2 > ( gnome ) Broken update-notifier:amd64 Depends on update-manager-gnome [ amd64 ] < none -> > ( none ) Broken update-notifier:amd64 Depends on update-manager [ amd64 ] < 1:16.04.13 -> 1:18.04.11.4 > ( gnome ) (>= 1:17.04.3) Broken update-notifier:amd64 Depends on ubuntu-release-upgrader-gtk [ amd64 ] < 1:16.04.25 -> 1:18.04.25 > ( admin ) Broken rhythmbox-plugins:amd64 Depends on gir1.2-webkit2-4.0 [ amd64 ] < 2.20.5-0ubuntu0.16.04.1 -> 2.20.5-0ubuntu0.18.04.1 > ( introspection ) Broken ubuntu-session:amd64 Depends on gnome-session-bin [ amd64 ] < 3.18.1.2-1ubuntu1.16.04.2 -> 3.28.1-0ubuntu3 > ( gnome ) (>= 3.28.1-0ubuntu3) Broken evolution:amd64 Depends on libevolution [ amd64 ] < 3.18.5.2-0ubuntu3.2 -> 3.28.1-2 > ( universe/gnome ) (>= 3.28.1) Broken gir1.2-mutter-2:amd64 Depends on libmutter-2-0 [ amd64 ] < none -> 3.28.3-2~ubuntu18.04.1 > ( libs ) (= 3.28.3-2~ubuntu18.04.1) Broken mutter:amd64 Depends on libmutter-2-0 [ amd64 ] < none -> 3.28.3-2~ubuntu18.04.1 > ( libs ) (>= 3.28.2) Broken gir1.2-gst-plugins-base-1.0:amd64
[Bug 1786823] [NEW] installation crash
Public bug reported: installation crash is all it said ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 Date: Mon Aug 13 13:07:52 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 only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786823 Title: installation crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1786823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778649] [NEW] clang headers aren't installed or linked in /usr/include/clang-c
Public bug reported: This causes a problem building qdoc on Ubuntu 18.04: https://bugreports.qt.io/browse/QTBUG-69044 In summary, #include doesn't work unless one adds an extra -I include path. On some other Linux OSes, that's not necessary. So I wonder if this is a matter of policy to have these headers only in /usr/lib/llvm-6.0/include/clang-c, or an oversight? It will be an issue for any software that attempts to reuse parts of clang to build other tools. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libclang-6.0-dev 1:6.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jun 26 08:52:55 2018 SourcePackage: llvm-toolchain-6.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: llvm-toolchain-6.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778649 Title: clang headers aren't installed or linked in /usr/include/clang-c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-6.0/+bug/1778649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777994] [NEW] the header xcb/xinput.h is missing
Public bug reported: I suspect this means there should be another package, libxcb-xinput-dev perhaps? I already did sudo apt install "libxcb*dev" to get all related dev packages, but none of them provide xcb/xinput.h. The result is that when building Qt from source, it's necessary to use a copy of this file which Qt provides (qtbase/src/3rdparty/xcb/include/xcb/xinput.h), because it's missing from the system. So if you don't give the option -qt-xcb to configure, then Qt will be built without multi-touch support. https://bugreports.qt.io/browse/QTBUG-69045 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libxcb1-dev 1.13-1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 21 08:32:12 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3802] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 04f2:b5da Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80Y7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro SourcePackage: libxcb UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5NCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 920-13IKB dmi.modalias: dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB: dmi.product.family: YOGA 920-13IKB dmi.product.name: 80Y7 dmi.product.version: Lenovo YOGA 920-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A 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 ** Affects: libxcb (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777994 Title: the header xcb/xinput.h is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/1777994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ["no screens found"]
Just to close the loop on this, it seems that my problem was a corrupted dist-upgrade and reinstalling a fresh Xubuntu 18.04 fixed it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543192 Title: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ["no screens found"] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ["no screens found"]
That file (/etc/gdm3/custom.conf) doesn't exist on my system. I haven't been getting the popup for an error occurring today though. (The details in that dialog said it was a duplicate of this issue, which is how I found this) I still have an issue where if I lock the screen it goes black with a blinking _ in the upper left. I can ssh in and reboot, but the UI is unresponsive no matter how long I wait (even Ctrl+Shift+F1-6 key combos do nothing). I'm not sure that is related, but the 'system error has occurred' dialog with this crash only happened after I did a reboot to get out of this. I'm going to do more debugging on this later this afternoon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543192 Title: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ["no screens found"] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ["no screens found"]
I just updated to Xubuntu 18.04 (from 17.10) and I have started getting this when I log in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543192 Title: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ["no screens found"] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774242] Re: Wacom touchscreens should use libinput, not wacom driver
I verified that the stylus does still work OK (using the Qt tablet example which demonstrates pressure-sensitivity etc.) So I think it's probably OK to remove that stanza completely: there's probably no reason to use wacom.drv for the touchscreen, just let it fall back to libinput or evdev, whichever is installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774242 Title: Wacom touchscreens should use libinput, not wacom driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774242] [NEW] Wacom touchscreens should use libinput, not wacom driver
Public bug reported: /usr/share/X11/xorg.conf.d/70-wacom.conf as shipped, has this: Section "InputClass" Identifier "Wacom touchscreen class" MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4" MatchDevicePath "/dev/input/event*" MatchIsTouchscreen "true" Driver "wacom" EndSection The result is that on my Yoga 920, in a plain X11 session (running openbox in my case), the touchscreen acts like a broken mouse: there is no multi-touch capability in Qt Quick applications, and clicking isn't quite right either. I also verified it with Peter Hutterer's old cairo- based mt-touch test program. I suspect we will get some users mistakenly writing up Qt bugs about this if you don't ship a fix. (Seems to me that already happened at least once, actually.) Yes, the touchscreen is made by Wacom, but wacom_drv.so has historically been only for Wacom tablets and in-screen stylus digitizers, and IMO that continues to be the case. libinput is a much better choice of driver for this hardware (so is evdev for that matter), so I changed it to Driver "libinput" and got it working. (Wayland uses libinput, so in a wayland session, touch already works fine in Qt apps on this hardware.) I'm one of the Qt Quick maintainers, most concerned with touch handling, and I've also written some of the Qt xcb code for dealing with XInput touch and tablet devices. So if you think that there's something wrong with Qt, such that it should still work anyway to use a wacom driver for a Wacom touchscreen, let me know. These AES devices are still new to me (that's why I got a Yoga, to try it out). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-input-wacom 1:0.36.1-0ubuntu1 [modified: usr/share/X11/xorg.conf.d/70-wacom.conf] ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 30 19:40:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu MachineType: LENOVO 80Y7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=ZFS=rpool/ROOT/ubuntu ro SourcePackage: xf86-input-wacom UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5NCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 920-13IKB dmi.modalias: dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB: dmi.product.family: YOGA 920-13IKB dmi.product.name: 80Y7 dmi.product.version: Lenovo YOGA 920-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A 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 ** Affects: xf86-input-wacom (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/1774242 Title: Wacom touchscreens should use libinput, not wacom driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773032] [NEW] does not mark support for obda:a811
Public bug reported: This driver supports a usb dongle that it doesn't advertise that it support. All it needs is the new device ID. https://lzone.de/blog/Solving+rtl8812au+installation+on+Ubuntu+17.10 May 23 15:47:09 jordon-desktop kernel: usb 2-4: new high-speed USB device number 12 using ehci-pci May 23 15:47:09 jordon-desktop kernel: usb 2-4: New USB device found, idVendor=0bda, idProduct=a811 May 23 15:47:09 jordon-desktop kernel: usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 May 23 15:47:09 jordon-desktop kernel: usb 2-4: Product: 802.11ac WLAN Adapter May 23 15:47:09 jordon-desktop kernel: usb 2-4: Manufacturer: Realtek May 23 15:47:09 jordon-desktop kernel: usb 2-4: SerialNumber: 00e04c01 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rtl8812au-dkms 4.3.8.12175.20140902+dfsg-0ubuntu8 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 23 15:48:08 2018 InstallationDate: Installed on 2017-10-29 (206 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtl8812au UpgradeStatus: Upgraded to bionic on 2018-04-09 (44 days ago) ** Affects: rtl8812au (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773032 Title: does not mark support for obda:a811 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8812au/+bug/1773032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772132] [NEW] no 8822bu support
Public bug reported: some realtek usb devices require the rtl8822bu driver, which i have patched to support Linux 4.15 https://github.com/shawnl/rtl8822bu ** Affects: rtl8812au (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/1772132 Title: no 8822bu support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8812au/+bug/1772132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768923] [NEW] crash during install
Public bug reported: crash during install ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.4 [modified: usr/share/ubiquity/apt-setup] ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 Date: Thu May 3 11:50:49 2018 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. LiveMediaBuild: Black-Lab-Linux 16.04 - Release amd64 ProcEnviron: LANGUAGE=en_CA.UTF-8 PATH=(username, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SourcePackage: ubiquity UbiquitySyslog: UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug custom xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768923 Title: crash during install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1768923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768112] Re: 7.47.0-1ubuntu2.2 is much slower than 7.22.0-3ubuntu4.17 for https
strace output of curl 7.47.0 ** Attachment added: "curl_7.47.0_strace.txt" https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1768112/+attachment/5130959/+files/curl_7.47.0_strace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768112 Title: 7.47.0-1ubuntu2.2 is much slower than 7.22.0-3ubuntu4.17 for https To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1768112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768112] Re: 7.47.0-1ubuntu2.2 is much slower than 7.22.0-3ubuntu4.17 for https
strace output of curl 7.22.0 ** Attachment added: "curl_7.22.0_strace.txt" https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1768112/+attachment/5130960/+files/curl_7.22.0_strace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768112 Title: 7.47.0-1ubuntu2.2 is much slower than 7.22.0-3ubuntu4.17 for https To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1768112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768112] [NEW] 7.47.0-1ubuntu2.2 is much slower than 7.22.0-3ubuntu4.17 for https
Public bug reported: curl-7.47.0-1ubuntu2.2 spent lots of time reading CA certs before sending "client hello"; on the other hand, curl 7.22.0 didn't spend time reading CA certs before a "client hello" and after "server hello" was received and it only read few CA certs. This made significant difference in term of response time between 7.22.0 and 7.47.0. $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=12.04 DISTRIB_CODENAME=precise DISTRIB_DESCRIPTION="Ubuntu 12.04.5 LTS" $ dpkg -l curl Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii curl 7.47.0-1ubuntu2.2 amd64command line tool for transferring data with URL syntax $ curl -w "@curl-format.txt" https://170.199.194.0:4443/@p1/heartbeat/ -k -s -o /dev/null time_namelookup: 0.000 time_connect: 0.001 time_appconnect: 0.009 time_pretransfer: 0.009 time_redirect: 0.000 time_starttransfer: 0.011 -- time_total: 0.011 $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.3 LTS" $ dpkg -l curl Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Description +++-==-==- ii curl 7.22.0-3ubuntu4.17 Get a file from an HTTP, HTTPS or FTP server $ curl -w "@curl-format.txt" https://170.199.194.0:4443/@p1/heartbeat/ -k -s -o /dev/null time_namelookup: 0.000 time_connect: 0.001 time_appconnect: 0.256 time_pretransfer: 0.256 time_redirect: 0.000 time_starttransfer: 0.257 -- time_total: 0.257 The problem was that when cul-7.47.0 compiled with gnutls and with --with-ca-path=/etc/ssl/certs, it would read all certificates from the path before sending client hello; on the other hand, when it's compiled libssl and it's fine. I checked the build option for 7.22.0-3ubuntu4.17, only --with-ca-bundle=/etc/ssl/certs/ca-certificates.crt was used. curl built with gnutls with --with-ca-bundle and without --with-ca-path was still slower than the built with libssl. What needs to be done to build 7.47.0 with similar response time for https as 7.22.0? ** Affects: curl (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/1768112 Title: 7.47.0-1ubuntu2.2 is much slower than 7.22.0-3ubuntu4.17 for https To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1768112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737375] [NEW] package linux-image-extra-4.10.0-42-generic 4.10.0-42.46~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Don't know caused this - the dialog just popped up. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.10.0-42-generic 4.10.0-42.46~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Sat Dec 9 21:12:15 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-12-05 (4 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: linux-hwe Title: package linux-image-extra-4.10.0-42-generic 4.10.0-42.46~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737375 Title: package linux-image-extra-4.10.0-42-generic 4.10.0-42.46~16.04.1 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/linux-hwe/+bug/1737375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730508] [NEW] please build with openssl for sha1
Public bug reported: Openssl's sha1 implementation is much faster, as it has asm optimized versions for many architectures including cpu sha1 acceleration for x86 and arm. ** Affects: git (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/1730508 Title: please build with openssl for sha1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/git/+bug/1730508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724955] Re: unable to drag monitors in Display Arrangement
I just wanted to add that I experience this same problem. I do not receive an error of any kind the mini displays simply will not rearrange when I attempt to drag them. Let me know if I can supply any additional information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724955 Title: unable to drag monitors in Display Arrangement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1724955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 497904] Re: Support Application Indicators
the tray is now in package connman-ui (which I maintain in Debian), and has been rewritten. ** Changed in: connman (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/497904 Title: Support Application Indicators To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/connman/+bug/497904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 613793] Re: o2cb stopping Failed
** Description changed:
Binary package hint: ocfs2-tools
Ubuntu release:
Description:Ubuntu 10.04.1 LTS
Release:10.04
Package version:
ocfs2-tools 1.4.3-1
The script /etc/init.d/o2cb exits with an error when stopped and the services
do not stop.
Here the error message:
/etc/init.d/o2cb stop
Stopping O2CB cluster ocfs2: Failed
Unable to stop cluster as heartbeat region still active
I have identified a first error in the script. In the function
clean_heartbeat the following if:
if [ ! -f "$(configfs_path)/cluster/${CLUSTER}/heartbeat/*" ]
- then
- return
+ then
+ return
fi
is always true and the function returns. If the intention was to check
the existence of the directory code must be:
if [ ! -d "$(configfs_path)/cluster/${CLUSTER}/heartbeat/" ]
- then
- echo "OK"
- return
+ then
+ echo "OK"
+ return
fi
An error persist even after these changes.
/etc/init.d/o2cb stop
Cleaning heartbeat on ocfs2: Failed
At least one heartbeat region still active
I added some lines for debugging by changing the function so:
#
# clean_heartbeat()
# Removes the inactive heartbeat regions
#
clean_heartbeat()
{
- if [ "$#" -lt "1" -o -z "$1" ]
- then
- echo "clean_heartbeat(): Requires an argument" >&2
- return 1
- fi
- CLUSTER="$1"
+ if [ "$#" -lt "1" -o -z "$1" ]
+ then
+ echo "clean_heartbeat(): Requires an argument" >&2
+ return 1
+ fi
+ CLUSTER="$1"
- if [ ! -d "$(configfs_path)/cluster/${CLUSTER}/heartbeat/" ]
- then
- echo "OK"
- return
- fi
+ if [ ! -d "$(configfs_path)/cluster/${CLUSTER}/heartbeat/" ]
+ then
+ echo "OK"
+ return
+ fi
- echo -n "Cleaning heartbeat on ${CLUSTER}: "
+ echo -n "Cleaning heartbeat on ${CLUSTER}: "
- ls -1 "$(configfs_path)/cluster/${CLUSTER}/heartbeat/" | while read HBUUID
- do
- if [ ! -d "$(configfs_path)/cluster/${CLUSTER}/heartbeat/${HBUUID}" ]
- then
- continue
- fi
+ ls -1 "$(configfs_path)/cluster/${CLUSTER}/heartbeat/" | while read HBUUID
+ do
+ if [ ! -d "$(configfs_path)/cluster/${CLUSTER}/heartbeat/${HBUUID}" ]
+ then
+ continue
+ fi
echo
echo "DEBUG ocfs2_hb_ctl -I -u ${HBUUID} 2>&1"
- OUTPUT="`ocfs2_hb_ctl -I -u ${HBUUID} 2>&1`"
- if [ $? != 0 ]
- then
- echo "Failed"
- echo "${OUTPUT}" >&2
- exit 1
- fi
+ OUTPUT="`ocfs2_hb_ctl -I -u ${HBUUID} 2>&1`"
+ if [ $? != 0 ]
+ then
+ echo "Failed"
+ echo "${OUTPUT}" >&2
+ exit 1
+ fi
echo "DEBUG ${OUTPUT}"
- REF="`echo ${OUTPUT} | awk '/refs/ {print $2; exit;}' 2>&1`"
+ REF="`echo ${OUTPUT} | awk '/refs/ {print $2; exit;}' 2>&1`"
echo "DEBUG REF=$REF"
- if [ $REF != 0 ]
- then
-echo "Failed"
-echo "At least one heartbeat region still active" >&2
-exit 1
- else
-OUTPUT="`ocfs2_hb_ctl -K -u ${HBUUID} 2>&1`"
- fi
- done
- if [ $? = 1 ]
- then
- exit 1
- fi
- echo "OK"
+ if [ $REF != 0 ]
+ then
+ echo "Failed"
+ echo "At least one heartbeat region still active" >&2
+ exit 1
+ else
+ OUTPUT="`ocfs2_hb_ctl -K -u ${HBUUID} 2>&1`"
+ fi
+ done
+ if [ $? = 1 ]
+ then
+ exit 1
+ fi
+ echo "OK"
}
The new output is:
/etc/init.d/o2cb stop
- Cleaning heartbeat on ocfs2:
+ Cleaning heartbeat on ocfs2:
DEBUG ocfs2_hb_ctl -I -u FC046AD7B2584E7EB12A7293993C81B0 2>&1
DEBUG FC046AD7B2584E7EB12A7293993C81B0: 2 refs
DEBUG REF=2
Failed
At least one heartbeat region still active
At this point I checked the source code ocfs2_hb_ctl. The command
ocfs2_hb_ctl-I-u ${HBUUID} returns the number of references in a semaphore used
by programs that manage ocfs filesystem. In the source file libo2cb/o2cb_api.c:
- the function o2cb_mutex_down increases the second semaphore;
- the function o2cb_mutex_up decreases the first semaphore;
- the function __o2cb_get_ref increases the first semaphore;
- the function __o2cb_drop_ref decreases the first semaphore.
I have not found the point where the second semaphore is decreased. This
could be the cause of the error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/613793
Title:
o2cb stopping Failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/613793/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
[Bug 1584629] Re: Failed to start LSB: Load O2CB cluster services at system boot.
** Description changed: Ubuntu 16.04. Sometimes (not every boot) o2cb failed to start: systemctl status o2cb ● o2cb.service - LSB: Load O2CB cluster services at system boot. -Loaded: loaded (/etc/init.d/o2cb; bad; vendor preset: enabled) -Active: failed (Result: exit-code) since Пн 2016-05-23 11:46:43 SAMT; 2min 12s ago - Docs: man:systemd-sysv-generator(8) - Process: 1526 ExecStart=/etc/init.d/o2cb start (code=exited, status=1/FAILURE) + Loaded: loaded (/etc/init.d/o2cb; bad; vendor preset: enabled) + Active: failed (Result: exit-code) since Пн 2016-05-23 11:46:43 SAMT; 2min 12s ago + Docs: man:systemd-sysv-generator(8) + Process: 1526 ExecStart=/etc/init.d/o2cb start (code=exited, status=1/FAILURE) май 23 11:46:43 inetgw1 systemd[1]: Starting LSB: Load O2CB cluster services at system boot май 23 11:46:43 inetgw1 o2cb[1526]: Loading filesystem "configfs": OK - май 23 11:46:43 inetgw1 o2cb[1526]: Mounting configfs filesystem at /sys/kernel/config: mount: configfs is already + май 23 11:46:43 inetgw1 o2cb[1526]: Mounting configfs filesystem at /sys/kernel/config: mount: configfs is already май 23 11:46:43 inetgw1 o2cb[1526]:configfs is already mounted on /sys/kernel/config май 23 11:46:43 inetgw1 o2cb[1526]: Unable to mount configfs filesystem май 23 11:46:43 inetgw1 o2cb[1526]: Failed май 23 11:46:43 inetgw1 systemd[1]: o2cb.service: Control process exited, code=exited status=1 май 23 11:46:43 inetgw1 systemd[1]: Failed to start LSB: Load O2CB cluster services at system boot.. май 23 11:46:43 inetgw1 systemd[1]: o2cb.service: Unit entered failed state. май 23 11:46:43 inetgw1 systemd[1]: o2cb.service: Failed with result 'exit-code'. - next try is successful: systemctl status o2cb ● o2cb.service - LSB: Load O2CB cluster services at system boot. -Loaded: loaded (/etc/init.d/o2cb; bad; vendor preset: enabled) -Active: active (exited) since Пн 2016-05-23 11:49:07 SAMT; 1s ago - Docs: man:systemd-sysv-generator(8) - Process: 2101 ExecStart=/etc/init.d/o2cb start (code=exited, status=0/SUCCESS) + Loaded: loaded (/etc/init.d/o2cb; bad; vendor preset: enabled) + Active: active (exited) since Пн 2016-05-23 11:49:07 SAMT; 1s ago + Docs: man:systemd-sysv-generator(8) + Process: 2101 ExecStart=/etc/init.d/o2cb start (code=exited, status=0/SUCCESS) май 23 11:49:07 inetgw1 systemd[1]: Starting LSB: Load O2CB cluster services at system boot май 23 11:49:07 inetgw1 o2cb[2101]: Loading stack plugin "o2cb": OK май 23 11:49:07 inetgw1 o2cb[2101]: Loading filesystem "ocfs2_dlmfs": OK май 23 11:49:07 inetgw1 o2cb[2101]: Mounting ocfs2_dlmfs filesystem at /dlm: OK май 23 11:49:07 inetgw1 o2cb[2101]: Setting cluster stack "o2cb": OK май 23 11:49:07 inetgw1 o2cb[2101]: Starting O2CB cluster inetgw: OK май 23 11:49:07 inetgw1 systemd[1]: Started LSB: Load O2CB cluster services at system boot.. - I guess this is startup dependency problem. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584629 Title: Failed to start LSB: Load O2CB cluster services at system boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/1584629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
shawn@budgie:~$ dmesg [0.00] microcode: microcode updated early to revision 0x62, date = 2017-04-27 [0.00] random: get_random_bytes called from start_kernel+0x42/0x4e1 with crng_init=0 [0.00] Linux version 4.13.0-041300-generic (kernel@gloin) (gcc version 7.2.0 (Ubuntu 7.2.0-2ubuntu1)) #201709031731 SMP Sun Sep 3 21:33:09 UTC 2017 [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.13.0-041300-generic root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' [0.00] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 [0.00] x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 [0.00] x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format. [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x00057fff] usable [0.00] BIOS-e820: [mem 0x00058000-0x00058fff] reserved [0.00] BIOS-e820: [mem 0x00059000-0x0009dfff] usable [0.00] BIOS-e820: [mem 0x0009e000-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x75807fff] usable [0.00] BIOS-e820: [mem 0x75808000-0x75808fff] ACPI NVS [0.00] BIOS-e820: [mem 0x75809000-0x75809fff] reserved [0.00] BIOS-e820: [mem 0x7580a000-0x7a844fff] usable [0.00] BIOS-e820: [mem 0x7a845000-0x7abc] reserved [0.00] BIOS-e820: [mem 0x7abd-0x7ac10fff] ACPI data [0.00] BIOS-e820: [mem 0x7ac11000-0x7aef5fff] ACPI NVS [0.00] BIOS-e820: [mem 0x7aef6000-0x7b51] reserved [0.00] BIOS-e820: [mem 0x7b52-0x7b5fefff] type 20 [0.00] BIOS-e820: [mem 0x7b5ff000-0x7b5f] usable [0.00] BIOS-e820: [mem 0x7b60-0x7f7f] reserved [0.00] BIOS-e820: [mem 0xe000-0xefff] reserved [0.00] BIOS-e820: [mem 0xfe00-0xfe010fff] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xff00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00027e7f] usable [0.00] NX (Execute Disable) protection: active [0.00] efi: EFI v2.40 by American Megatrends [0.00] efi: ACPI=0x7abdd000 ACPI 2.0=0x7abdd000 SMBIOS=0xf SMBIOS 3.0=0xf0020 ESRT=0x7b29f118 MEMATTR=0x78220018 [0.00] random: fast init done [0.00] SMBIOS 3.0.0 present. [0.00] DMI: Dell Inc. XPS 13 9360/05JK94, BIOS 2.1.0 08/02/2017 [0.00] e820: update [mem 0x-0x0fff] usable ==> reserved [0.00] e820: remove [mem 0x000a-0x000f] usable [0.00] e820: last_pfn = 0x27e800 max_arch_pfn = 0x4 [0.00] MTRR default type: write-back [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 base 008000 mask 7F8000 uncachable [0.00] 1 base 007E00 mask 7FFE00 uncachable [0.00] 2 base 007D00 mask 7FFF00 uncachable [0.00] 3 disabled [0.00] 4 disabled [0.00] 5 disabled [0.00] 6 disabled [0.00] 7 disabled [0.00] 8 disabled [0.00] 9 disabled [0.00] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WC UC- WT [0.00] e820: last_pfn = 0x7b600 max_arch_pfn = 0x4 [0.00] esrt: Reserving ESRT space from 0x7b29f118 to 0x7b29f150. [0.00] Scanning 1 areas for low memory corruption [0.00] Base memory trampoline at [8e2bc0098000] 98000 size 24576 [0.00] Using GB pages for direct mapping [0.00] BRK [0x23eb23000, 0x23eb23fff] PGTABLE [0.00] BRK [0x23eb24000, 0x23eb24fff] PGTABLE [0.00] BRK [0x23eb25000, 0x23eb25fff] PGTABLE [0.00] BRK [0x23eb26000, 0x23eb26fff] PGTABLE [0.00] BRK [0x23eb27000, 0x23eb27fff] PGTABLE [0.00]
[Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
Will it not load by default? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
Also, the log file. Sorry for all the posts. ** Attachment added: "log.on.suspend" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+attachment/4946659/+files/log.on.suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
I installed the kernel and clicked suspend on the taskbar at the top. Then did "journalctl" and shift+g. Sep 08 14:13:50 budgie gsd-sharing[1527]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not Sep 08 14:13:50 budgie gsd-sharing[1527]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-server.servic Sep 08 14:13:50 budgie systemd-resolved[941]: Switching to DNS server 130.85.1.23 for interface wlp58s0. Sep 08 14:13:50 budgie dbus[729]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Sep 08 14:13:50 budgie systemd[1]: Started Network Manager Script Dispatcher Service. Sep 08 14:13:50 budgie nm-dispatcher[3239]: req:1 'connectivity-change': new request (2 scripts) Sep 08 14:13:50 budgie nm-dispatcher[3239]: req:1 'connectivity-change': start running ordered scripts... Sep 08 14:13:50 budgie nm-dispatcher[3239]: req:2 'up' [wlp58s0]: new request (2 scripts) Sep 08 14:13:50 budgie whoopsie[1084]: [14:13:50] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/1 Sep 08 14:13:50 budgie nm-dispatcher[3239]: req:2 'up' [wlp58s0]: start running ordered scripts... Sep 08 14:13:50 budgie whoopsie[1084]: [14:13:50] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/1 Sep 08 14:13:50 budgie whoopsie[1084]: [14:13:50] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/1 Sep 08 14:13:50 budgie whoopsie[1084]: [14:13:50] online Sep 08 14:13:51 budgie dbus-daemon[1333]: Activating service name='com.gexperts.Terminix' Sep 08 14:13:51 budgie dbus-daemon[1333]: Successfully activated service 'com.gexperts.Terminix' Sep 08 14:13:51 budgie terminix[3275]: ../../../../gobject/gsignal.c:2523: signal 'notification-received' is invalid for instance '0x55b31b050 Sep 08 14:13:52 budgie avahi-daemon[723]: Joining mDNS multicast group on interface wlp58s0.IPv6 with address fe80::f50a:cc1e:f4f1:12cc. Sep 08 14:13:52 budgie avahi-daemon[723]: New relevant interface wlp58s0.IPv6 for mDNS. Sep 08 14:13:52 budgie avahi-daemon[723]: Registering new address record for fe80::f50a:cc1e:f4f1:12cc on wlp58s0.*. ~ ~ ~ ~ ~ ~ lines 1974-1996/1996 (END) Sep 08 14:13:50 budgie NetworkManager[736]: [1504894430.5641] manager: NetworkManager state is now CONNECTED_GLOBAL Sep 08 14:13:50 budgie NetworkManager[736]: [1504894430.5647] policy: set 'UMBC Visitor' (wlp58s0) as default for IPv4 routing and DNS Sep 08 14:13:50 budgie NetworkManager[736]: [1504894430.5667] device (wlp58s0): Activation: successful, device activated. Sep 08 14:13:50 budgie systemd[1]: Starting Network Manager Script Dispatcher Service... Sep 08 14:13:50 budgie gsd-sharing[1527]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not l Sep 08 14:13:50 budgie gsd-sharing[1527]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-server.service Sep 08 14:13:50 budgie systemd-resolved[941]: Switching to DNS server 130.85.1.23 for interface wlp58s0. Sep 08 14:13:50 budgie dbus[729]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Sep 08 14:13:50 budgie systemd[1]: Started Network Manager Script Dispatcher Service. Sep 08 14:13:50 budgie nm-dispatcher[3239]: req:1 'connectivity-change': new request (2 scripts) Sep 08 14:13:50 budgie nm-dispatcher[3239]: req:1 'connectivity-change': start running ordered scripts... Sep 08 14:13:50 budgie nm-dispatcher[3239]: req:2 'up' [wlp58s0]: new request (2 scripts) Sep 08 14:13:50 budgie whoopsie[1084]: [14:13:50] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/1 Sep 08 14:13:50 budgie nm-dispatcher[3239]: req:2 'up' [wlp58s0]: start running ordered scripts... Sep 08 14:13:50 budgie whoopsie[1084]: [14:13:50] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/1 Sep 08 14:13:50 budgie whoopsie[1084]: [14:13:50] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/1 Sep 08 14:13:50 budgie whoopsie[1084]: [14:13:50] online Sep 08 14:13:51 budgie dbus-daemon[1333]: Activating service name='com.gexperts.Terminix' Sep 08 14:13:51 budgie dbus-daemon[1333]: Successfully activated service 'com.gexperts.Terminix' Sep 08 14:13:51 budgie terminix[3275]: ../../../../gobject/gsignal.c:2523: signal 'notification-received' is invalid for instance '0x55b31b050a Sep 08 14:13:52 budgie avahi-daemon[723]: Joining mDNS multicast group on interface wlp58s0.IPv6 with address fe80::f50a:cc1e:f4f1:12cc. Sep 08 14:13:52 budgie avahi-daemon[723]: New relevant interface wlp58s0.IPv6 for mDNS. Sep 08 14:13:52 budgie avahi-daemon[723]: Registering new address record for fe80::f50a:cc1e:f4f1:12cc on wlp58s0.*. ~ ~ ~ ~ ~ ~ lines 1974-1996/1996 (END) Sep 08 14:13:50 budgie NetworkManager[736]: [1504894430.5641] manager: NetworkManager state is now CONNECTED_GLOBAL Sep 08 14:13:50
[Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
shawn@budgie:~/Downloads$ sudo dpkg -i linux-image-4.13.0-041300-generic_4.13.0-041300.201709031731_amd64.deb [sudo] password for shawn: Selecting previously unselected package linux-image-4.13.0-041300-generic. (Reading database ... 258306 files and directories currently installed.) Preparing to unpack linux-image-4.13.0-041300-generic_4.13.0-041300.201709031731_amd64.deb ... Examining /etc/kernel/preinst.d/ run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.13.0-041300-generic /boot/vmlinuz-4.13.0-041300-generic Done. Unpacking linux-image-4.13.0-041300-generic (4.13.0-041300.201709031731) ... Setting up linux-image-4.13.0-041300-generic (4.13.0-041300.201709031731) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.13.0-041300-generic /boot/vmlinuz-4.13.0-041300-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.13.0-041300-generic /boot/vmlinuz-4.13.0-041300-generic update-initramfs: Generating /boot/initrd.img-4.13.0-041300-generic W: Possible missing firmware /lib/firmware/i915/kbl_huc_ver02_00_1810.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_huc_ver01_07_1398.bin for module i915 W: Possible missing firmware /lib/firmware/i915/skl_huc_ver01_07_1398.bin for module i915 run-parts: executing /etc/kernel/postinst.d/pm-utils 4.13.0-041300-generic /boot/vmlinuz-4.13.0-041300-generic run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.13.0-041300-generic /boot/vmlinuz-4.13.0-041300-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 4.13.0-041300-generic /boot/vmlinuz-4.13.0-041300-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.13.0-041300-generic /boot/vmlinuz-4.13.0-041300-generic Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.13.0-041300-generic Found initrd image: /boot/initrd.img-4.13.0-041300-generic Found linux image: /boot/vmlinuz-4.10.0-33-generic Found initrd image: /boot/initrd.img-4.10.0-33-generic Found linux image: /boot/vmlinuz-4.10.0-19-generic Found initrd image: /boot/initrd.img-4.10.0-19-generic Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi Adding boot menu entry for EFI firmware configuration done shawn@budgie:~/Downloads$ Will report back.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
I do not have anything plugged into the USB type-c port. I will try that kernel out and report back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
[21453]: Allocating size to GtkScrollbar 0x55ad36983880 without calling gtk_widget_get_preferred_width/height(). How does the c Sep 08 13:11:35 budgie terminix[21453]: Allocating size to GtkScrollbar 0x55ad36983880 without calling gtk_widget_get_preferred_width/height(). How does the c Sep 08 13:11:35 budgie terminix[21453]: Allocating size to GtkScrollbar 0x55ad36983880 without calling gtk_widget_get_preferred_width/height(). How does the c Sep 08 13:11:35 budgie terminix[21453]: Allocating size to GtkScrollbar 0x55ad36983880 without calling gtk_widget_get_preferred_width/height(). How does the c ~ ~ ~ ~ ~ ~ ~ shawn@budgie:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
shawn@budgie:~$ lspci 00:00.0 Host bridge: Intel Corporation Device 5904 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation Device 5916 (rev 02) 00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 02) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1) 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Device 9d58 (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 01:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015] (rev ff) 02:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015] (rev ff) 02:01.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015] (rev ff) 02:02.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015] (rev ff) 03:00.0 System peripheral: Intel Corporation DSL6340 Thunderbolt 3 NHI [Alpine Ridge 2C 2015] (rev ff) 39:00.0 USB controller: Intel Corporation DSL6340 USB 3.1 Controller [Alpine Ridge] (rev ff) 3a:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 3b:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 3c:00.0 Non-Volatile memory controller: Device 1c5c:1283 shawn@budgie:~$ ^C shawn@budgie:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
Sep 8 11:37:12 budgie NetworkManager[746]: [1504885032.6272] dhcp4 (wlp58s0): domain name 'umbc.edu' Sep 8 11:37:12 budgie NetworkManager[746]: [1504885032.6273] dhcp4 (wlp58s0): wins '130.85.11.19' Sep 8 11:37:12 budgie NetworkManager[746]: [1504885032.6273] dhcp4 (wlp58s0): wins '130.85.11.30' Sep 8 11:37:12 budgie avahi-daemon[715]: Joining mDNS multicast group on interface wlp58s0.IPv4 with address 10.200.154.116. Sep 8 11:37:12 budgie NetworkManager[746]: [1504885032.6273] dhcp4 (wlp58s0): wins '130.85.11.7' Sep 8 11:37:12 budgie avahi-daemon[715]: New relevant interface wlp58s0.IPv4 for mDNS. Sep 8 11:37:12 budgie NetworkManager[746]: [1504885032.6273] dhcp4 (wlp58s0): state changed unknown -> bound Sep 8 11:37:12 budgie avahi-daemon[715]: Registering new address record for 10.200.154.116 on wlp58s0.IPv4. Sep 8 11:37:12 budgie NetworkManager[746]: [1504885032.6344] device (wlp58s0): state change: ip-config -> ip-check (reason 'none') [70 80 0] Sep 8 11:37:12 budgie NetworkManager[746]: [1504885032.6354] device (wlp58s0): state change: ip-check -> secondaries (reason 'none') [80 90 0] Sep 8 11:37:12 budgie NetworkManager[746]: [1504885032.6389] device (wlp58s0): state change: secondaries -> activated (reason 'none') [90 100 0] Sep 8 11:37:12 budgie NetworkManager[746]: [1504885032.6427] manager: NetworkManager state is now CONNECTED_LOCAL Sep 8 11:37:12 budgie dhclient[13776]: bound to 10.200.154.116 -- renewal in 1755 seconds. Sep 8 11:37:12 budgie kernel: [ 4546.263489] wlp58s0: Limiting TX power to 17 (17 - 0) dBm as advertised by 64:a0:e7:ff:45:cf Sep 8 11:37:12 budgie nm-dispatcher: req:295 'connectivity-change': new request (2 scripts) Sep 8 11:37:12 budgie nm-dispatcher: req:295 'connectivity-change': start running ordered scripts... Sep 8 11:37:12 budgie NetworkManager[746]: [1504885032.6510] manager: NetworkManager state is now CONNECTED_GLOBAL Sep 8 11:37:12 budgie NetworkManager[746]: [1504885032.6513] policy: set 'UMBC Visitor' (wlp58s0) as default for IPv4 routing and DNS Sep 8 11:37:12 budgie NetworkManager[746]: [1504885032.6520] device (wlp58s0): Activation: successful, device activated. Sep 8 11:37:12 budgie nm-dispatcher: req:296 'up' [wlp58s0]: new request (2 scripts) Sep 8 11:37:12 budgie nm-dispatcher: req:296 'up' [wlp58s0]: start running ordered scripts... Sep 8 11:37:12 budgie gsd-sharing[1473]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded. Sep 8 11:37:12 budgie whoopsie[1020]: [11:37:12] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/113 Sep 8 11:37:12 budgie gsd-sharing[1473]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-server.service not loaded. Sep 8 11:37:12 budgie whoopsie[1020]: [11:37:12] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/113 Sep 8 11:37:12 budgie whoopsie[1020]: [11:37:12] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/113 Sep 8 11:37:12 budgie whoopsie[1020]: [11:37:12] online Sep 8 11:37:12 budgie systemd-resolved[948]: Switching to DNS server 130.85.1.23 for interface wlp58s0. Sep 8 11:37:13 budgie avahi-daemon[715]: Joining mDNS multicast group on interface wlp58s0.IPv6 with address fe80::f50a:cc1e:f4f1:12cc. Sep 8 11:37:13 budgie avahi-daemon[715]: New relevant interface wlp58s0.IPv6 for mDNS. Sep 8 11:37:13 budgie avahi-daemon[715]: Registering new address record for fe80::f50a:cc1e:f4f1:12cc on wlp58s0.*. Sep 8 11:37:22 budgie systemd[1]: Reloading. Sep 8 11:37:32 budgie NetworkManager[746]: [1504885052.2047] manager: sleep requested (sleeping: no enabled: yes) Sep 8 11:37:32 budgie NetworkManager[746]: [1504885052.2048] manager: sleeping... Sep 8 11:37:32 budgie NetworkManager[746]: [1504885052.2050] manager: NetworkManager state is now ASLEEP Sep 8 11:37:32 budgie NetworkManager[746]: [1504885052.2063] device (wlp58s0): state change: activated -> deactivating (reason 'sleeping') [100 110 37] Sep 8 11:37:32 budgie whoopsie[1020]: [11:37:32] offline Sep 8 11:37:32 budgie nm-dispatcher: req:297 'connectivity-change': new request (2 scripts) Sep 8 11:37:32 budgie NetworkManager[746]: [1504885052.2187] device (wlp58s0): state change: deactivating -> disconnected (reason 'sleeping') [110 30 37] Sep 8 11:37:32 budgie avahi-daemon[715]: Withdrawing address record for fe80::f50a:cc1e:f4f1:12cc on wlp58s0. Sep 8 11:37:32 budgie avahi-daemon[715]: Leaving mDNS multicast group on interface wlp58s0.IPv6 with address fe80::f50a:cc1e:f4f1:12cc. Sep 8 11:37:32 budgie avahi-daemon[715]: Interface wlp58s0.IPv6 no longer relevant for mDNS. Sep 8 11:37:32 budgie NetworkManager[746]: [1504885052.2546] dhcp4 (wlp58s0): canceled DHCP transaction, DHCP client pid 13776 Sep 8 11:37:32 budgie NetworkManager[746]: [1504885052.2547] dhcp4 (wlp58s0): state
[Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
This is still an issue. Not suspending. Please assist. ** Attachment added: "Screenshot from 2017-09-08 12-10-01.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+attachment/4946602/+files/Screenshot%20from%202017-09-08%2012-10-01.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
Just downgrade network-manager to 1.2.2-0ubuntu0.16.04.4 until the issue is resolved. Pretty simple. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944742/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944739/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944737/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944743/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944736/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944738/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944735/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944740/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944741/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944732/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944734/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944733/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
apport information ** Tags added: apport-collected zesty ** Description changed: I installed Ubuntu Budgie 17.04 64-bit. I installed the operating system and then when booted, I apt-get update and apt-get upgrade. I went to the coffee shop and used the system for a while. When I came home I left my laptop Dell XPS 9360 in its leather case and inside my laptop bag. I left to do some errands and came back to a really hot laptop and case. The system had not gone to sleep when I closed the lid and the computer was very hot. I have attached a copy of the log files. I then: sudo vi /etc/systemd/logind.conf Changed: HandleLidSwitchDocked=suspend - when I close the lid now it gives me a password to login when I open the - lid, but I am not sure if it is sleeping properly. Please assist, as I - do not want my laptop battery damaged by this heat again. + when I close the lid now it gives me a password to login when I open the lid, but I am not sure if it is sleeping properly. Please assist, as I do not want my laptop battery damaged by this heat again. + --- + ApportVersion: 2.20.4-0ubuntu4.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: shawn 1786 F pulseaudio + DistroRelease: Ubuntu 17.04 + InstallationDate: Installed on 2017-09-04 (1 days ago) + InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0c45:670c Microdia + Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Dell Inc. XPS 13 9360 + Package: linux (not installed) + ProcEnviron: + LANGUAGE=en_US + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 + PulseList: + Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied + No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-4.10.0-33-generic N/A + linux-backports-modules-4.10.0-33-generic N/A + linux-firmware 1.164.1 + Tags: zesty + Uname: Linux 4.10.0-33-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 08/02/2017 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 2.1.0 + dmi.board.name: 05JK94 + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr: + dmi.product.name: XPS 13 9360 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1715146/+attachment/4944731/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694182] [NEW] changrd to gentoo
Public bug reported: system is all messed up, dvd inop, just totally lost on this system and it seem like I can't even remove it ! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-53-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun May 28 22:42:20 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:81eb] InstallationDate: Installed on 2017-05-09 (19 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-53-generic.efi.signed root=UUID=5cba8a50-d750-4c6f-8fe1-84ddc229f60e ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.17 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EB dmi.board.vendor: HP dmi.board.version: 61.35 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.17:bd09/01/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EB:rvr61.35:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A 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 N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1694182 Title: changrd to gentoo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1694182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
I experience the same issue on 16.04 but it ends up breaking DNS responses entirely because traffic is forced through the OpenVPN tunnel where the DNS resides and the local DNS is no longer accessible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1627117] Re: After systemd integration enabled, Postfix will no longer send mail on startup
I'm seeing the same issue on 17.04 with postfix. The patch described here is implemented in postfix-3.1.4-4, but I still have to update the resolve.conf in the postfix chroot every time I reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1627117 Title: After systemd integration enabled, Postfix will no longer send mail on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1627117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface
Ah yes. This is indeed referenced in the changelog on the system. Not sure what I should do next though. Open a new bugid or continue here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639776 Title: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface
@Paul dnsmasq is 2.75-1ubuntu0.16.04.2 and I don't see anything newer within my repo. Has the pkg been updated for 16.04? pkg info: https://pastebin.com/aximAJxc Mint 18.1 (Ubuntu 16.04.2) x64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639776 Title: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface
I also have the same issue as Lukas. Occurs: VPN Connects using redirect gateway VPN DNS is not used Local DNS unavailable No DNS queries work Expected: VPN Connects using redirect gateway VPN DNS is used Local DNS unavailable Temporary workaround: sudo pkill dnsmasq -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639776 Title: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680924] [NEW] package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1679784 ***
https://bugs.launchpad.net/bugs/1679784
Public bug reported:
I have no idea what to type here...
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Fri Apr 7 13:53:59 2017
DistributionChannelDescriptor:
# This is a distribution channel descriptor
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-xenial-amd64-20160624-2
DuplicateSignature:
package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
Processing triggers for shim-signed
(1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ...
Running in non-interactive mode, doing nothing.
dpkg: error processing package shim-signed (--configure):
subprocess installed post-installation script returned error exit status 1
EFIBootMgr:
BootCurrent: 0001
Timeout: 2 seconds
BootOrder: 0001,
Boot* Windows Boot Manager
HD(1,GPT,58ef9cc6-f63d-4d53-9e96-5bfcce94fcbf,0x800,0x64000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....
Boot0001* ubuntu
HD(1,GPT,58ef9cc6-f63d-4d53-9e96-5bfcce94fcbf,0x800,0x64000)/File(\EFI\ubuntu\shimx64.efi)
ErrorMessage: subprocess installed post-installation script returned error exit
status 1
InstallationDate: Installed on 2017-04-06 (1 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary
20160624-10:47
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.1
apt 1.2.19
SourcePackage: shim-signed
Title: package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed
to install/upgrade: subprocess installed post-installation script returned
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: shim-signed (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-package third-party-packages xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680924
Title:
package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
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/shim-signed/+bug/1680924/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
