[Bug 1950461] Re: Installing vino does not expose the screen sharing slider in Gnome Control Center
In that case, it's certainly the case that it's not installed in a minimal install. I've come across this more than once. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950461 Title: Installing vino does not expose the screen sharing slider in Gnome Control Center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1950461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950461] Re: Installing vino does not expose the screen sharing slider in Gnome Control Center
Thanks for getting back to me. I have never heard of gnome-remote- desktop before. Installing it cures the issue that I've been having. Yes, I meant the minimal install from ubiquity. I would consider this lack of knowledge on my part but I will update the threads on askubuntu and reddit with the solution as I'm sure others will encounter the same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950461 Title: Installing vino does not expose the screen sharing slider in Gnome Control Center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1950461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950461] [NEW] Installing vino does not expose the screen sharing slider in Gnome Control Center
Public bug reported: Ubuntu 21.10 - minimal install on a fresh machine apt install vino Open the gnome settings dialog and go to the Sharing tab. I would expect to see the screen sharing slider but it is not there. Searching around I found a suggestion to use Ubunutu with Xorg but this makes no difference. This behaviour is also present in 21.04. I have put gnome-control-center as the package at fault as this is ultimately where I observe the issue but it may be that during the install of vino makes the gnome configuration change and this step is missed. I have enquired on askubuntu and reddit but have not received a response so decided to report this gnome-control-center 1:40.0-1ubuntu5 is installed vino 3.22.0-6ubuntu3 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: minimal screen sharing vino -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950461 Title: Installing vino does not expose the screen sharing slider in Gnome Control Center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1950461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940993] [NEW] package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1
Public bug reported: I was just upgrading from 16 LTS to 18 LTS to 20 LTS and this popped up. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: tex-common 6.09 ProcVersionSignature: Ubuntu 4.15.0-154.161-generic 4.15.18 Uname: Linux 4.15.0-154-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 Date: Tue Aug 24 12:49:22 2021 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-02-13 (2749 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.14 SourcePackage: tex-common Title: package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2021-08-24 (0 days ago) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic 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/1940993 Title: package tex-common 6.09 failed to install/upgrade: installed tex- common package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1940993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895301] Re: XrandR does not propose 3440x1440 21:9 resolution
Same issue with my Ultrawide. Workaround: xrandr --newmode "2560x999_60.00" 211.75 2560 2720 2984 3408 999 1002 1012 1037 -hsync +vsync xrandr --addmode Virtual1 2560x999_60.00 xrandr --output Virtual1 --mode 2560x999_60.00 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895301 Title: XrandR does not propose 3440x1440 21:9 resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1895301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890514] [NEW] The "find entries" search function does not find matching username
Public bug reported: When looking for a password to which one knows only the username, entering the correct and full username in the "fund entries" does not find the entry. It appears the "username" field in the records is not looked for when searching entries. -- also the about box where I can find the version (version is 0.56 - from January 2020) the copyright is 2011-2013, may require an update ** Affects: pasaffe (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/1890514 Title: The "find entries" search function does not find matching username To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pasaffe/+bug/1890514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1374825] Re: VDPAU does not work in libav on Utopic
Can confirm that this is affecting VLC as well. ** Changed in: vlc (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1374825 Title: VDPAU does not work in libav on Utopic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1374825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1885414] Re: on flavours ubiquity: bootloader failed on /dev/vda
I just tested Kubuntu 20200710 linked from qtracker and it works now. Bug appears fixed. On Fri, Jul 10, 2020 at 4:06 AM Rik Mills <1885...@bugs.launchpad.net> wrote: > For Kubuntu ISOs: > > At least in testing in a VM, adjusting the live and ship-live seeds to > make sure both include 'shim-signed' and 'grub-pc' packages, seems to > have worked around the issue in legacy bios installs. i.e. in 20200709.2 > images onwards. > > If people could test and confirm that BOTH legacy and efi install now > seem fine for Kubuntu ISOs, that would be great. :) > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1886085). > https://bugs.launchpad.net/bugs/1885414 > > Title: > on flavours ubiquity: bootloader failed on /dev/vda > > Status in ubiquity package in Ubuntu: > Triaged > Status in ubiquity source package in Groovy: > Triaged > > Bug description: > Testing the 2020-06-28 ubuntu-mate iso on QEMU (QuickEMU) > Selected Normal and 3rd party installation. > Installation looked to be going fine until it got to grub2 installation > part > Came up with the following error: > > https://i.imgur.com/IanRMYk.jpg > > Had to do screenshot as apport is crashing and unable to submit bug > via ubuntu-bug: > > https://i.imgur.com/dqYcKqb.png > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1885414/+subscriptions > -- *Truck driver, Linux Tech, Webmaster, and Web Admin.Volunteer Kubuntu Linux Development Tester* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885414 Title: on flavours ubiquity: bootloader failed on /dev/vda To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1885414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1885414] Re: on flavours ubiquity: bootloader failed on /dev/vda
Kubuntu from qtracker is still on 08 I got the 09 version from here: http://cdimage.ubuntu.com/kubuntu/daily-live/current/ It says last updated 2020-07-09 05:48 Bug is still there. Will watch for the next point update to hit. On Thu, Jul 9, 2020 at 1:50 PM Dimitri John Ledkov < 1885...@bugs.launchpad.net> wrote: > We have landed a fix for one of the booting/install issues in 20200709 > build stamp images and higher. > > If you are experiencing boot issues of install media, please try > 20200709 media and please report back if it is still fails or is > imporved. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1886085). > https://bugs.launchpad.net/bugs/1885414 > > Title: > on flavours ubiquity: bootloader failed on /dev/vda > > Status in ubiquity package in Ubuntu: > Triaged > Status in ubiquity source package in Groovy: > Triaged > > Bug description: > Testing the 2020-06-28 ubuntu-mate iso on QEMU (QuickEMU) > Selected Normal and 3rd party installation. > Installation looked to be going fine until it got to grub2 installation > part > Came up with the following error: > > https://i.imgur.com/IanRMYk.jpg > > Had to do screenshot as apport is crashing and unable to submit bug > via ubuntu-bug: > > https://i.imgur.com/dqYcKqb.png > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1885414/+subscriptions > -- *Truck driver, Linux Tech, Webmaster, and Web Admin.Volunteer Kubuntu Linux Development Tester* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885414 Title: on flavours ubiquity: bootloader failed on /dev/vda To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1885414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886085] [NEW] ubiquity crashes during install
Public bug reported: Tried 3 times on VBox and once on real metal laptop. Crashing just after "creating user" is displayed on the progress bar (as best I can tell) Kubuntu 20.04, daily build dl'd 7/2/2020 VBox settings 6 G ram, 40 G HD Laptop Compaq 2 ghz, 2 G ram, 60 G HD intel graphics ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.7 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu42 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: KDE Date: Thu Jul 2 14:19:51 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200702) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy kubuntu ubiquity-20.10.7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886085 Title: ubiquity crashes during install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1886085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878567] [NEW] gnome-software crashes with segmentation fault error
Public bug reported: Uning Ubuntu 18.04, recently gnome software started crashing on startup. When running via terminal I see segmentation fault error. System is up to date after running apt upgrade etc. I have attached the output of gnome-software --verbose --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-07 (280 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InstalledPlugins: gnome-software-plugin-flatpak 3.28.1-0ubuntu4.18.04.15 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.15 Package: gnome-software 3.28.1-0ubuntu4.18.04.15 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm lpadmin plugdev sambashare sudo _MarkForUpload: True ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected bionic ** Attachment added: "gnome-software-verbose.txt" https://bugs.launchpad.net/bugs/1878567/+attachment/5371378/+files/gnome-software-verbose.txt ** Tags added: apport-collected bionic ** Description changed: Uning Ubuntu 18.04, recently gnome software started crashing on startup. When running via terminal I see segmentation fault error. System is up to date after running apt upgrade etc. I have attached the output of gnome-software --verbose + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.14 + Architecture: amd64 + CurrentDesktop: GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-08-07 (280 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + InstalledPlugins: + gnome-software-plugin-flatpak 3.28.1-0ubuntu4.18.04.15 + gnome-software-plugin-limba N/A + gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.15 + Package: gnome-software 3.28.1-0ubuntu4.18.04.15 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_GB.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-99-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker kvm lpadmin plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878567 Title: gnome-software crashes with segmentation fault error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1878567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878567] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1878567/+attachment/5371380/+files/ProcCpuinfoMinimal.txt ** Description changed: Uning Ubuntu 18.04, recently gnome software started crashing on startup. When running via terminal I see segmentation fault error. System is up to date after running apt upgrade etc. I have attached the output of gnome-software --verbose - --- + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-07 (280 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InstalledPlugins: - gnome-software-plugin-flatpak 3.28.1-0ubuntu4.18.04.15 - gnome-software-plugin-limba N/A - gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.15 + gnome-software-plugin-flatpak 3.28.1-0ubuntu4.18.04.15 + gnome-software-plugin-limba N/A + gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.15 Package: gnome-software 3.28.1-0ubuntu4.18.04.15 PackageArchitecture: amd64 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_GB.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_GB.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm lpadmin plugdev sambashare sudo _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878567 Title: gnome-software crashes with segmentation fault error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1878567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878567] Re: gnome-software crashes with segmentation fault error
Please let me know if there is additional information I can provide, not used to reporting bugs. Many thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878567 Title: gnome-software crashes with segmentation fault error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1878567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878567] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1878567/+attachment/5371379/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878567 Title: gnome-software crashes with segmentation fault error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1878567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1735986] Re: Unable to set different scale correctly on different monitors
This is affecting me on Ubuntu 20.04. My first monitor is 1080p, and my second monitor is 2K. Everything is small on the 2K monitor, and I'm trying to fractionally scale the display to 125%. This results in the display automatically going to 200% instead of 125%. The display crashes when I subsequently turn off fractional scaling. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1735986 Title: Unable to set different scale correctly on different monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1735986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855186] Re: Trackpad scrolling and taps not working on resume
apport information ** Tags added: apport-collected ** Description changed: Lenovo Thinkpad T480 Ubuntu 18.04.03 On resume (e.g. after closing and then opening lid), the track pad will no longer allow me to scroll, tap or drag. The problem can be temporarily resolved by entering the following commands into the terminal... sudo modprobe -r psmouse && sudo modprobe psmouse + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: daledavies 3138 F pulseaudio + CurrentDesktop: GNOME + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=f3a5b044-6dc1-4ca0-a3aa-357b4f6344b6 + InstallationDate: Installed on 2019-08-07 (121 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + MachineType: LENOVO 20L50004UK + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_GB.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-70-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-70-generic N/A + linux-backports-modules-4.15.0-70-generic N/A + linux-firmware 1.173.12 + Tags: bionic + Uname: Linux 4.15.0-70-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker kvm lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 10/17/2019 + dmi.bios.vendor: LENOVO + dmi.bios.version: N24ET53W (1.28 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20L50004UK + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40697 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrN24ET53W(1.28):bd10/17/2019:svnLENOVO:pn20L50004UK:pvrThinkPadT480:rvnLENOVO:rn20L50004UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad T480 + dmi.product.name: 20L50004UK + dmi.product.version: ThinkPad T480 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1855186/+attachment/5310375/+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/1855186 Title: Trackpad scrolling and taps not working on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855186] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1855186/+attachment/5310386/+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/1855186 Title: Trackpad scrolling and taps not working on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855186] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1855186/+attachment/5310380/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855186 Title: Trackpad scrolling and taps not working on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855186] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1855186/+attachment/5310382/+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/1855186 Title: Trackpad scrolling and taps not working on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855186] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1855186/+attachment/5310387/+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/1855186 Title: Trackpad scrolling and taps not working on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855186] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1855186/+attachment/5310384/+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/1855186 Title: Trackpad scrolling and taps not working on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855186] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1855186/+attachment/5310383/+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/1855186 Title: Trackpad scrolling and taps not working on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855186] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1855186/+attachment/5310378/+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/1855186 Title: Trackpad scrolling and taps not working on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855186] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1855186/+attachment/5310388/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855186 Title: Trackpad scrolling and taps not working on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855186] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1855186/+attachment/5310379/+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/1855186 Title: Trackpad scrolling and taps not working on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855186] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1855186/+attachment/5310376/+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/1855186 Title: Trackpad scrolling and taps not working on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855186] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1855186/+attachment/5310385/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855186 Title: Trackpad scrolling and taps not working on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855186] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1855186/+attachment/5310381/+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/1855186 Title: Trackpad scrolling and taps not working on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855186] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1855186/+attachment/5310377/+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/1855186 Title: Trackpad scrolling and taps not working on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855186] [NEW] Trackpad scrolling and taps not working on resume
Public bug reported: Lenovo Thinkpad T480 Ubuntu 18.04.03 On resume (e.g. after closing and then opening lid), the track pad will no longer allow me to scroll, tap or drag. The problem can be temporarily resolved by entering the following commands into the terminal... sudo modprobe -r psmouse && sudo modprobe psmouse ** Affects: ubuntu Importance: Undecided Status: New ** Package changed: xubuntu-meta (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855186 Title: Trackpad scrolling and taps not working on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1855186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853837] [NEW] package libsane-hpaio 3.19.6+dfsg0-1ubuntu1 [modified: usr/share/hplip/data/models/models.dat] failed to install/upgrade: trying to overwrite shared '/usr/share/hplip/data/models/m
Public bug reported: Printer Not Found ProblemType: Package DistroRelease: Ubuntu 19.10 Package: libsane-hpaio 3.19.6+dfsg0-1ubuntu1 [modified: usr/share/hplip/data/models/models.dat] ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CupsErrorLog: Date: Mon Nov 25 12:50:00 2019 DuplicateSignature: package:libsane-hpaio:3.19.6+dfsg0-1ubuntu1 [modified: usr/share/hplip/data/models/models.dat] Unpacking libsane-hpaio:i386 (3.19.6+dfsg0-1ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-uY0A9Z/36-libsane-hpaio_3.19.6+dfsg0-1ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other instances of package libsane-hpaio:i386 ErrorMessage: trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other instances of package libsane-hpaio:i386 InstallationDate: Installed on 2019-10-29 (26 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for DeskJet-3630-series: hp:/usb/DeskJet_3630_series?serial=CN73J4N1DQ067P device for HP_DeskJet_3630_series_ADB89F_: implicitclass://HP_DeskJet_3630_series_ADB89F_/ MachineType: Acer Aspire XC-885 Papersize: a4 PpdFiles: DeskJet-3630-series: HP Deskjet 3630 Series, hpcups 3.19.6 HP_DeskJet_3630_series_ADB89F_: DeskJet 3630 series - IPP Everywhere ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=b52db822-2ce2-4628-8952-db3d3e0f8dcb ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: hplip Title: package libsane-hpaio 3.19.6+dfsg0-1ubuntu1 [modified: usr/share/hplip/data/models/models.dat] failed to install/upgrade: trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other instances of package libsane-hpaio:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-B3 dmi.board.name: Aspire XC-885(DCH) dmi.board.vendor: Acer dmi.board.version: V:1.1 dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-B3:bd01/16/2019:svnAcer:pnAspireXC-885:pvr:rvnAcer:rnAspireXC-885(DCH):rvrV1.1:cvnAcer:ct3:cvr: dmi.product.family: Aspire X dmi.product.name: Aspire XC-885 dmi.product.sku: dmi.sys.vendor: Acer mtime.conffile..etc.hp.hplip.conf: 2019-11-11T11:22:18.102400 ** Affects: hplip (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan package-conflict -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853837 Title: package libsane-hpaio 3.19.6+dfsg0-1ubuntu1 [modified: usr/share/hplip/data/models/models.dat] failed to install/upgrade: trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other instances of package libsane-hpaio:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1853837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1413665] Re: Bad Request - Bad bot, go away! Request aborted.
It seems any password auto filler gets fooled by the honeypot on the page and results in the error. The irony is that in order to comment or mark "it affects me", you have to get past the very form that's causing the problem. I suspect this affects a lot more people than is indicated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1413665 Title: Bad Request - Bad bot, go away! Request aborted. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-identity-provider/+bug/1413665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1681830] Re: No Label for LVM Encryption Passwords
Still here in eoan (19.10 Beta). No label for LVM Encryption passwords. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1681830 Title: No Label for LVM Encryption Passwords To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1681830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847602] [NEW] Package libglib2.0-0:armhf fails to install: Exec format error
Public bug reported: Description:Ubuntu 18.04.3 LTS Release:18.04 uname -a: Linux dtsmith-vallum 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux All updates available to date have been applied. Command is "sudo apt-get install libglib2.0-0:armhf" Debian team supposed to fix this bug with package version 2.54.2-5 see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885019 I am doing cross-compile work with the following compilers arm-linux-gnueabihf-gcc-8 from package gcc-8-arm-linux-gnueabihf The schemas from the native gcc-7 package are in /usr/share/glib-2.0/schemas. "sudo apt-get install libglib2.0-dev:armhf" has the same error. Work-around is to install libglib2.0-dev for the host. The schema files are in /usr/share/glib-2.0. I have cross-compiled syslog-ng as armhf and it works. Here is the output of the apt install command: Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/2,186 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 172895 files and directories currently installed.) Preparing to unpack .../libglib2.0-0_2.56.4-0ubuntu0.18.04.4_amd64.deb ... Unpacking libglib2.0-0:amd64 (2.56.4-0ubuntu0.18.04.4) over (2.56.4-0ubuntu0.18.04.4) ... Preparing to unpack .../libglib2.0-0_2.56.4-0ubuntu0.18.04.4_armhf.deb ... Unpacking libglib2.0-0:armhf (2.56.4-0ubuntu0.18.04.4) over (2.56.4-0ubuntu0.18.04.4) ... Setting up libglib2.0-0:amd64 (2.56.4-0ubuntu0.18.04.4) ... Setting up libglib2.0-0:armhf (2.56.4-0ubuntu0.18.04.4) ... /var/lib/dpkg/info/libglib2.0-0:armhf.postinst: 39: /var/lib/dpkg/info/libglib2.0-0:armhf.postinst: /usr/lib/arm-linux-gnueabihf/glib-2.0/glib-compile-schemas: Exec format error Processing triggers for libc-bin (2.27-3ubuntu1) ... dtsmith@dtsmith-vallum:[~]$ /usr/lib/arm-linux-gnueabihf/glib-2.0/glib-compile-schemas bash: /usr/lib/arm-linux-gnueabihf/glib-2.0/glib-compile-schemas: cannot execute binary file: Exec format error ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libglib2.0-0:armhf 2.56.4-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 10 07:47:58 2019 InstallationDate: Installed on 2019-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: armhf ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847602 Title: Package libglib2.0-0:armhf fails to install: Exec format error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1847602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845733] [NEW] Kubuntu beta 19.10 ubiquity oem crash on reboot
Public bug reported: Ubiquity oem-config crashes upon first reboot after applying "prepare for shipping to end user" resulting in not being able to create a first user and not able to login with oem user. Metal install on Compaq Presario CQ60 I was not able to recreate this crash in a VM on another machine. crash log: Ubiquity 19.10.12 (oem-config) Ubiquity 19.10.12 (oem-config) Exception in KDE frontend (invoking crash handler): Traceback (most recent call last): File "/usr/sbin/oem-config", line 655, in main(oem_config) File "/usr/sbin/oem-config", line 641, in main install(query=options.query) File "/usr/sbin/oem-config", line 270, in install wizard = ui.Wizard(distro) File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 250, in __init__ mod.ui = mod.ui_class(mod.controller) File "/usr/lib/ubiquity/plugins/ubi-wireless.py", line 212, in __init__ self._setup_page() File "/usr/lib/ubiquity/plugins/ubi-wireless.py", line 218, in _setup_page self.nmwidget = nmwidgets.NetworkManagerWidget() File "/usr/lib/ubiquity/ubiquity/frontend/kde_components/nmwidgets.py", line 373, in __init__ self.view = NetworkManagerTreeView(self._on_state_changed) File "/usr/lib/ubiquity/ubiquity/frontend/kde_components/nmwidgets.py", line 232, in __init__ self.wifi_model = NetworkManager(model, QtQueuedCaller, state_changed) File "/usr/lib/ubiquity/ubiquity/nm.py", line 120, in __init__ self.start(state_changed) File "/usr/lib/ubiquity/ubiquity/nm.py", line 140, in start self.build_cache() File "/usr/lib/ubiquity/ubiquity/nm.py", line 237, in build_cache vendor, model = get_vendor_and_model(udi) File "/usr/lib/ubiquity/ubiquity/nm.py", line 43, in get_vendor_and_model universal_newlines=True) File "/usr/lib/python3.7/subprocess.py", line 775, in __init__ restore_signals, start_new_session) File "/usr/lib/python3.7/subprocess.py", line 1522, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: '/sbin/udevadm': '/sbin/udevadm' ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: iso-testing kubuntu oem oem-config ubiquity ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1845733/+attachment/5291992/+files/syslog ** Summary changed: - ubiquity-oem crash on reboot + Kubuntu beta 19.10 ubiquity oem crash on reboot -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to ubiquity in Ubuntu. https://bugs.launchpad.net/bugs/1845733 Title: Kubuntu beta 19.10 ubiquity oem crash on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1845733/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1831896] [NEW] Videos are playing very fast same thing with streaming
Public bug reported: Videos are playing very fast same thing with streaming and cant download and install anything. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-docs 16.04.4 ProcVersionSignature: Ubuntu 4.4.0-150.176-generic 4.4.179 Uname: Linux 4.4.0-150-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 6 08:08:51 2019 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-docs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-docs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1831896 Title: Videos are playing very fast same thing with streaming To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1831896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821822] Re: Temporary failure in name resolution in Python 3.7.2
** Description changed: - My Python application works in 18.10 fine, but when upgrading to 19.10 - for development reasons the same script produces the errors reported - below. I have checked on the Python bug tracker and there are no related - bug reports. - - Traceback (most recent call last): - File "/usr/lib/python3.7/urllib/request.py", line 1317, in do_open - encode_chunked=req.has_header('Transfer-encoding')) - File "/usr/lib/python3.7/http/client.py", line 1229, in request - self._send_request(method, url, body, headers, encode_chunked) - File "/usr/lib/python3.7/http/client.py", line 1275, in _send_request - self.endheaders(body, encode_chunked=encode_chunked) - File "/usr/lib/python3.7/http/client.py", line 1224, in endheaders - self._send_output(message_body, encode_chunked=encode_chunked) - File "/usr/lib/python3.7/http/client.py", line 1016, in _send_output - self.send(msg) - File "/usr/lib/python3.7/http/client.py", line 956, in send - self.connect() - File "/usr/lib/python3.7/http/client.py", line 1384, in connect - super().connect() - File "/usr/lib/python3.7/http/client.py", line 928, in connect - (self.host,self.port), self.timeout, self.source_address) - File "/usr/lib/python3.7/socket.py", line 707, in create_connection - for res in getaddrinfo(host, port, 0, SOCK_STREAM): - File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo - for res in _socket.getaddrinfo(host, port, family, type, proto, flags): - socket.gaierror: [Errno -3] Temporary failure in name resolution - - During handling of the above exception, another exception occurred: - - Traceback (most recent call last): - File "/usr/lib/myapp/main.py", line 312, in - win = GridWindow() - File "/usr/lib/myapp/main.py", line 37, in __init__ - self.updates_frame = self.draw_updates_frame() - File "/usr/lib/myapp/main.py", line 132, in draw_updates_frame - if self.version_check() == True: - File "/usr/lib/myapp/main.py", line 53, in version_check - get_version = urlopen('https://urlchanged.com').read() - File "/usr/lib/python3.7/urllib/request.py", line 222, in urlopen - return opener.open(url, data, timeout) - File "/usr/lib/python3.7/urllib/request.py", line 525, in open - response = self._open(req, data) - File "/usr/lib/python3.7/urllib/request.py", line 543, in _open - '_open', req) - File "/usr/lib/python3.7/urllib/request.py", line 503, in _call_chain - result = func(*args) - File "/usr/lib/python3.7/urllib/request.py", line 1360, in https_open - context=self._context, check_hostname=self._check_hostname) - File "/usr/lib/python3.7/urllib/request.py", line 1319, in do_open - raise URLError(err) - urllib.error.URLError: + Fixed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821822 Title: Temporary failure in name resolution in Python 3.7.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1821822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821822] Re: Temporary failure in name resolution in Python 3.7.2
** Description changed: My Python application works in 18.10 fine, but when upgrading to 19.10 for development reasons the same script produces the errors reported below. I have checked on the Python bug tracker and there are no related bug reports. Traceback (most recent call last): - File "/usr/lib/python3.7/urllib/request.py", line 1317, in do_open - encode_chunked=req.has_header('Transfer-encoding')) - File "/usr/lib/python3.7/http/client.py", line 1229, in request - self._send_request(method, url, body, headers, encode_chunked) - File "/usr/lib/python3.7/http/client.py", line 1275, in _send_request - self.endheaders(body, encode_chunked=encode_chunked) - File "/usr/lib/python3.7/http/client.py", line 1224, in endheaders - self._send_output(message_body, encode_chunked=encode_chunked) - File "/usr/lib/python3.7/http/client.py", line 1016, in _send_output - self.send(msg) - File "/usr/lib/python3.7/http/client.py", line 956, in send - self.connect() - File "/usr/lib/python3.7/http/client.py", line 1384, in connect - super().connect() - File "/usr/lib/python3.7/http/client.py", line 928, in connect - (self.host,self.port), self.timeout, self.source_address) - File "/usr/lib/python3.7/socket.py", line 707, in create_connection - for res in getaddrinfo(host, port, 0, SOCK_STREAM): - File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo - for res in _socket.getaddrinfo(host, port, family, type, proto, flags): + File "/usr/lib/python3.7/urllib/request.py", line 1317, in do_open + encode_chunked=req.has_header('Transfer-encoding')) + File "/usr/lib/python3.7/http/client.py", line 1229, in request + self._send_request(method, url, body, headers, encode_chunked) + File "/usr/lib/python3.7/http/client.py", line 1275, in _send_request + self.endheaders(body, encode_chunked=encode_chunked) + File "/usr/lib/python3.7/http/client.py", line 1224, in endheaders + self._send_output(message_body, encode_chunked=encode_chunked) + File "/usr/lib/python3.7/http/client.py", line 1016, in _send_output + self.send(msg) + File "/usr/lib/python3.7/http/client.py", line 956, in send + self.connect() + File "/usr/lib/python3.7/http/client.py", line 1384, in connect + super().connect() + File "/usr/lib/python3.7/http/client.py", line 928, in connect + (self.host,self.port), self.timeout, self.source_address) + File "/usr/lib/python3.7/socket.py", line 707, in create_connection + for res in getaddrinfo(host, port, 0, SOCK_STREAM): + File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo + for res in _socket.getaddrinfo(host, port, family, type, proto, flags): socket.gaierror: [Errno -3] Temporary failure in name resolution During handling of the above exception, another exception occurred: Traceback (most recent call last): - File "/usr/lib/pihole-panel/main.py", line 312, in - win = GridWindow() - File "/usr/lib/pihole-panel/main.py", line 37, in __init__ - self.updates_frame = self.draw_updates_frame() - File "/usr/lib/pihole-panel/main.py", line 132, in draw_updates_frame - if self.version_check() == True: - File "/usr/lib/pihole-panel/main.py", line 53, in version_check - get_version = urlopen('https://urlchanged.com').read() - File "/usr/lib/python3.7/urllib/request.py", line 222, in urlopen - return opener.open(url, data, timeout) - File "/usr/lib/python3.7/urllib/request.py", line 525, in open - response = self._open(req, data) - File "/usr/lib/python3.7/urllib/request.py", line 543, in _open - '_open', req) - File "/usr/lib/python3.7/urllib/request.py", line 503, in _call_chain - result = func(*args) - File "/usr/lib/python3.7/urllib/request.py", line 1360, in https_open - context=self._context, check_hostname=self._check_hostname) - File "/usr/lib/python3.7/urllib/request.py", line 1319, in do_open - raise URLError(err) + File "/usr/lib/myapp/main.py", line 312, in + win = GridWindow() + File "/usr/lib/myapp/main.py", line 37, in __init__ + self.updates_frame = self.draw_updates_frame() + File "/usr/lib/myapp/main.py", line 132, in draw_updates_frame + if self.version_check() == True: + File "/usr/lib/myapp/main.py", line 53, in version_check + get_version = urlopen('https://urlchanged.com').read() + File "/usr/lib/python3.7/urllib/request.py", line 222, in urlopen + return opener.open(url, data, timeout) + File "/usr/lib/python3.7/urllib/request.py", line 525, in open + response = self._open(req, data) + File "/usr/lib/python3.7/urllib/request.py", line 543, in _open + '_open', req) + File "/usr/lib/python3.7/urllib/request.py", line 503, in _call_chain + result = func(*args) + File "/usr/lib/python3.7/urllib/request.py", line 1360, in https_open + context=self._context, check_hostname=self._check_hostname) + File
[Bug 1821822] Re: Temporary failure in name resolution in Python 3.7.2
** Tags added: disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821822 Title: Temporary failure in name resolution in Python 3.7.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1821822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821822] [NEW] Temporary failure in name resolution in Python 3.7.2
Public bug reported: My Python application works in 18.10 fine, but when upgrading to 19.10 for development reasons the same script produces the errors reported below. I have checked on the Python bug tracker and there are no related bug reports. Traceback (most recent call last): File "/usr/lib/python3.7/urllib/request.py", line 1317, in do_open encode_chunked=req.has_header('Transfer-encoding')) File "/usr/lib/python3.7/http/client.py", line 1229, in request self._send_request(method, url, body, headers, encode_chunked) File "/usr/lib/python3.7/http/client.py", line 1275, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/usr/lib/python3.7/http/client.py", line 1224, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/usr/lib/python3.7/http/client.py", line 1016, in _send_output self.send(msg) File "/usr/lib/python3.7/http/client.py", line 956, in send self.connect() File "/usr/lib/python3.7/http/client.py", line 1384, in connect super().connect() File "/usr/lib/python3.7/http/client.py", line 928, in connect (self.host,self.port), self.timeout, self.source_address) File "/usr/lib/python3.7/socket.py", line 707, in create_connection for res in getaddrinfo(host, port, 0, SOCK_STREAM): File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags): socket.gaierror: [Errno -3] Temporary failure in name resolution During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/pihole-panel/main.py", line 312, in win = GridWindow() File "/usr/lib/pihole-panel/main.py", line 37, in __init__ self.updates_frame = self.draw_updates_frame() File "/usr/lib/pihole-panel/main.py", line 132, in draw_updates_frame if self.version_check() == True: File "/usr/lib/pihole-panel/main.py", line 53, in version_check get_version = urlopen('https://urlchanged.com').read() File "/usr/lib/python3.7/urllib/request.py", line 222, in urlopen return opener.open(url, data, timeout) File "/usr/lib/python3.7/urllib/request.py", line 525, in open response = self._open(req, data) File "/usr/lib/python3.7/urllib/request.py", line 543, in _open '_open', req) File "/usr/lib/python3.7/urllib/request.py", line 503, in _call_chain result = func(*args) File "/usr/lib/python3.7/urllib/request.py", line 1360, in https_open context=self._context, check_hostname=self._check_hostname) File "/usr/lib/python3.7/urllib/request.py", line 1319, in do_open raise URLError(err) urllib.error.URLError: ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Description changed: My Python application works in 18.10 fine, but when upgrading to 19.10 for development reasons the same script produces the errors reported below. I have checked on the Python bug tracker and there are no related bug reports. Traceback (most recent call last): - File "/usr/lib/python3.7/urllib/request.py", line 1317, in do_open - encode_chunked=req.has_header('Transfer-encoding')) - File "/usr/lib/python3.7/http/client.py", line 1229, in request - self._send_request(method, url, body, headers, encode_chunked) - File "/usr/lib/python3.7/http/client.py", line 1275, in _send_request - self.endheaders(body, encode_chunked=encode_chunked) - File "/usr/lib/python3.7/http/client.py", line 1224, in endheaders - self._send_output(message_body, encode_chunked=encode_chunked) - File "/usr/lib/python3.7/http/client.py", line 1016, in _send_output - self.send(msg) - File "/usr/lib/python3.7/http/client.py", line 956, in send - self.connect() - File "/usr/lib/python3.7/http/client.py", line 1384, in connect - super().connect() - File "/usr/lib/python3.7/http/client.py", line 928, in connect - (self.host,self.port), self.timeout, self.source_address) - File "/usr/lib/python3.7/socket.py", line 707, in create_connection - for res in getaddrinfo(host, port, 0, SOCK_STREAM): - File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo - for res in _socket.getaddrinfo(host, port, family, type, proto, flags): + File "/usr/lib/python3.7/urllib/request.py", line 1317, in do_open + encode_chunked=req.has_header('Transfer-encoding')) + File "/usr/lib/python3.7/http/client.py", line 1229, in request + self._send_request(method, url, body, headers, encode_chunked) + File "/usr/lib/python3.7/http/client.py", line 1275, in _send_request + self.endheaders(body, encode_chunked=encode_chunked) + File "/usr/lib/python3.7/http/client.py", line 1224, in endheaders + self._send_output(message_body, encode_chunked=encode_chunked) + File "/usr/lib/python3.7/http/client.py", line 1016, in _send_output + self.send(msg) + File "/usr/lib/python3.7/http/client.py", line 956, in send
[Bug 1809173] [NEW] package nvidia-kernel-common-390 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-340 340.107-0ub
Public bug reported: Synaptic flagged this error when trying to upgrade and install package ProblemType: Package DistroRelease: Ubuntu 18.10 Package: nvidia-kernel-common-390 (not installed) ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Wed Dec 19 15:15:22 2018 DuplicateSignature: package:nvidia-kernel-common-390:(not installed) Unpacking nvidia-kernel-common-390 (390.87-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-wWlLFn/643-nvidia-kernel-common-390_390.87-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-340 340.107-0ubuntu2 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-340 340.107-0ubuntu2 InstallationDate: Installed on 2014-01-21 (1793 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-kernel-common-390 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-340 340.107-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic package-conflict -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809173 Title: package nvidia-kernel-common-390 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-340 340.107-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1809173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794312] Re: Doesn't honor reversed scroll direction
Xubuntu 18.04 downloaded and installed within a week of making this BR. It's on a laptop I have given to a friend so don't have direct access to pull details off it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794312 Title: Doesn't honor reversed scroll direction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-appfinder/+bug/1794312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794312] [NEW] Doesn't honor reversed scroll direction
Public bug reported: Setting up an old laptop for a person used to using OSX so set touchpad scroll direction to be Reversed. It works in nearly all applications and windows but the Application Finder still scrolls in the standard direction, rather than change with this setting. ** Affects: xfce4-appfinder (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/1794312 Title: Doesn't honor reversed scroll direction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-appfinder/+bug/1794312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787127] Re: java Corrupted page table
@ggrandes: I experienced that reboot loop on one my aws machines (with 3.13.0-155-generic) today too. Stopping the machine from the web UI and bringing it back up stopped the loop, and the machine stayed up, if that helps at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787127 Title: java Corrupted page table To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778908] Re: 16.04 libtag dependancy issues
Why does Launchpad not recognise Launchpad's bug tracker when you try and associate another package as being affected? I wanted to correctly link this bug on the Mixxx tracker but it throws up an error of unrecognise bug tracker!! https://bugs.launchpad.net/mixxx/+bug/1778950 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778908 Title: 16.04 libtag dependancy issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/taglib/+bug/1778908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778908] Re: 16.04 libtag dependancy issues
Ahhh obviously fully Mixxx's fault, just realised the libtag version it fails to downgrade to is in their ppa and not the Ubuntu repo looking at the apt-cache policy output. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778908 Title: 16.04 libtag dependancy issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/taglib/+bug/1778908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778908] [NEW] 16.04 libtag dependancy issues
Public bug reported: This issue has come up from trying to install Mixxx from their official LaunchPad host ppa and it appears to reference libtag1-vanilla, which does appear to exist in 16.04 but I believe should be superseded by libtag1v5-vanilla, yet it doesn't seem to recognise as such. As it then can't be manually installed or the other removed I think there is a deeper issue with this package than just Mixxx having the wrong one down as a dependency. This has been reported to the Mixxx developers on their forum about a week ago but no official response as yet... I've run this in a virtual box but there are multiple users who have reported this on their main systems (at least four I've seen.) osboxes@osboxes:~$ sudo apt-get update [sudo] password for osboxes: Hit:1 http://security.ubuntu.com/ubuntu xenial-security InRelease Hit:2 http://ppa.launchpad.net/mixxx/mixxx/ubuntu xenial InRelease Hit:3 http://us.archive.ubuntu.com/ubuntu xenial InRelease Hit:4 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:5 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease Reading package lists... Done osboxes@osboxes:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. osboxes@osboxes:~$ sudo apt-get install mixxx Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mixxx : Depends: libtag1-vanilla (>= 1.10-0ubuntu1~xenial0) but it is not going to be installed E: Unable to correct problems, you have held broken packages. osboxes@osboxes:~$ sudo apt-get install libtag1-vanilla Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libcheese8 : Depends: gstreamer1.0-plugins-good (>= 0.11.0) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. osboxes@osboxes:~$ sudo apt-get install gstreamer1.0-plugins-good Reading package lists... Done Building dependency tree Reading state information... Done gstreamer1.0-plugins-good is already the newest version (1.8.3-1ubuntu0.4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. osboxes@osboxes:~$ sudo apt-get remove libtag1v5-vanilla Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: indicator-bluetooth : Depends: unity-control-center but it is not going to be installed or gnome-control-center but it is not going to be installed or ubuntu-system-settings but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. osboxes@osboxes:~$ sudo apt-get remove libtag1v5 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libcheese8 : Depends: gstreamer1.0-plugins-good (>= 0.11.0) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. osboxes@osboxes:~$ sudo apt-cache policy libtag1-vanilla libtag1-vanilla: Installed: (none) Candidate: 1.10-0ubuntu1~xenial0 Version table: 1.10-0ubuntu1~xenial0 500 500 http://ppa.launchpad.net/mixxx/mixxx/ubuntu xenial/main amd64 Packages ** Affects: taglib (Ubuntu) Importance: Undecided
[Bug 1448254] Re: openvswitch systemd unit file ordering wrong
I ran across this today, apparently still not fixed. I was also surprised and shocked that netplan.io doesn't support it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448254 Title: openvswitch systemd unit file ordering wrong To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773515] Re: apparmor fails after removal of snapd
@Jamie Thanks, I hadn't thought of purging to try and clean up from issues like this when there's a left over file but on hearing you say it then it seems so obvious! As I said above I manually removed the file to get apparmor loading (actually three of them in the /etc/apparmor folders) and not seen any errors since. In fact it was only by chance I saw the one that triggered by above report, I doubt the effect would have been serious enough to cause me issues from the little I understand of this package... But again thanks, purging still seems to have removed a few bits and I will definitely remember to try it in any similar situations in the future. ~$ sudo dpkg --purge snapd [sudo] password for dale: (Reading database ... 402920 files and directories currently installed.) Purging configuration files for snapd (2.32.8+18.04) ... Final directory cleanup Discarding preserved snap namespaces Removing extra snap-confine apparmor rules Removing snapd cache Removing snapd state -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773515 Title: apparmor fails after removal of snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1773515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773515] Re: apparmor fails after removal of snapd
"Does anything happen if you run: sudo dpkg --configure -a" Absolutely nothing. As I said I have manually removed the files, if that may affect it. Worth noting I run Ubuntu Studio, not vanilla Ubuntu or even Xubuntu, and sometimes configuration steps may get missed by that team (eg Xubuntu is apparently back with the Synaptics pointer driver due to issues but coming from Studio I had to manually do the change to get the touchpad working properly again.) So it's possible everything is fine in the main Ubuntu version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773515 Title: apparmor fails after removal of snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1773515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774196] [NEW] 18.04 Hidden files in Tree view visibility only changes from last open window
Public bug reported: Just come across this bus in Ubuntu Studio 18.04, seems there is no way to report the bug to the Xubuntu team on Launchpad directly. Thunar version in question is 1.6.15 according to the Help page. Bug is pretty simple to recreate: Open Thunar Make sure Tree sidepane is selected. Expand Home in Tree so you can see the folder list. Press Ctrl+H to show and hide the hidden folders. Open a second instance of Thunar and expand the Home folder in Tree as above. Press Ctrl+H - It will show/hide the hidden folders from the Tree in both (all) open Thunar windows! Go back to the original window. Press Ctrl+H - It will only change visibility of the hidden folders in the main pane, not the tree pane. Obviously Ctrl+H should only affect the window which had focus when it was pressed. And it should always affect all parts of that window. Currently Ctrl+H always affects the main section of the current window but the Tree pane is affected globally by the last opened Thunar window. ** Affects: thunar Importance: Unknown Status: Unknown ** Affects: thunar (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Xfce Bugzilla #14423 https://bugzilla.xfce.org/show_bug.cgi?id=14423 ** Also affects: thunar via https://bugzilla.xfce.org/show_bug.cgi?id=14423 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/1774196 Title: 18.04 Hidden files in Tree view visibility only changes from last open window To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1774196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773515] Re: apparmor fails after removal of snapd
I do 99% of my package management with apt-get so it was removed via the command "sudo apt-get remove snapd" >From dkpg.log from just either side of the last mentions of snapd 2018-05-16 13:29:33 startup packages remove 2018-05-16 13:29:33 status installed snapd:amd64 2.32.8+18.04 2018-05-16 13:29:33 remove snapd:amd64 2.32.8+18.04 2018-05-16 13:29:33 status half-configured snapd:amd64 2.32.8+18.04 2018-05-16 13:29:33 status half-installed snapd:amd64 2.32.8+18.04 2018-05-16 13:29:33 status triggers-pending man-db:amd64 2.8.3-2 2018-05-16 13:29:36 status config-files snapd:amd64 2.32.8+18.04 2018-05-16 13:29:36 status config-files snapd:amd64 2.32.8+18.04 2018-05-16 13:29:36 startup packages configure 2018-05-16 13:29:36 trigproc man-db:amd64 2.8.3-2 2018-05-16 13:29:36 status half-configured man-db:amd64 2.8.3-2 2018-05-16 13:29:37 status installed man-db:amd64 2.8.3-2 apt/history.log gives this date (which time seems to coincide with the finish of the process, not the issue of the command, comparing to the above.) Start-Date: 2018-05-16 13:29:33 Commandline: apt-get remove snapd Requested-By: me (1000) Remove: snapd:amd64 (2.32.8+18.04) End-Date: 2018-05-16 13:29:37 apt/term.log from the system upgrade and then remove snapd. Log started: 2018-05-16 13:29:07 (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 352517 files and directories currently installed.) Preparing to unpack .../libpoppler-qt5-1_0.62.0-2ubuntu2.1_amd64.deb ... Unpacking libpoppler-qt5-1:amd64 (0.62.0-2ubuntu2.1) over (0.62.0-2ubuntu2) ... Preparing to unpack .../poppler-utils_0.62.0-2ubuntu2.1_amd64.deb ... Unpacking poppler-utils (0.62.0-2ubuntu2.1) over (0.62.0-2ubuntu2) ... Preparing to unpack .../libpoppler-glib8_0.62.0-2ubuntu2.1_amd64.deb ... Unpacking libpoppler-glib8:amd64 (0.62.0-2ubuntu2.1) over (0.62.0-2ubuntu2) ... Preparing to unpack .../libpoppler73_0.62.0-2ubuntu2.1_amd64.deb ... Unpacking libpoppler73:amd64 (0.62.0-2ubuntu2.1) over (0.62.0-2ubuntu2) ... Preparing to unpack .../snapd_2.32.8+18.04_amd64.deb ... Unpacking snapd (2.32.8+18.04) over (2.32.5+18.04) ... Setting up libpoppler73:amd64 (0.62.0-2ubuntu2.1) ... Setting up snapd (2.32.8+18.04) ... Created symlink /etc/systemd/system/multi-user.target.wants/snapd.seeded.service → /lib/systemd/system/snapd.seeded.service. Created symlink /etc/systemd/system/cloud-final.service.wants/snapd.seeded.service → /lib/systemd/system/snapd.seeded.service. snapd.snap-repair.service is a disabled or a static unit, not starting it. Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for man-db (2.8.3-2) ... Setting up libpoppler-glib8:amd64 (0.62.0-2ubuntu2.1) ... Setting up poppler-utils (0.62.0-2ubuntu2.1) ... Setting up libpoppler-qt5-1:amd64 (0.62.0-2ubuntu2.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Log ended: 2018-05-16 13:29:17 Log started: 2018-05-16 13:29:33 (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 352516 files and directories currently installed.) Removing snapd (2.32.8+18.04) ... Processing triggers for man-db (2.8.3-2) ... Log ended: 2018-05-16 13:29:37 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773515 Title: apparmor fails after removal of snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1773515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773515] Re: apparmor fails after removal of snapd
BTW as I don't plan to reinstall snapd the next day I did a find find /etc/apparmor.d/ -iname "*snap*" /etc/apparmor.d/usr.lib.snapd.snap-confine.real /etc/apparmor.d/cache/usr.lib.snapd.snap-confine.real /etc/apparmor.d/local/usr.lib.snapd.snap-confine.real and then manually deleted those files myself. This has obviously stopped apparmor complaining but it doesn't seem right I should have to do this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773515 Title: apparmor fails after removal of snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1773515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773515] [NEW] apparmour fails after removal of snapd
Public bug reported: $ sudo systemctl status apparmor ● apparmor.service - AppArmor initialization Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-05-26 10:36:35 BST; 38s ago Docs: man:apparmor(7) http://wiki.apparmor.net/ Process: 2850 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Main PID: 2850 (code=exited, status=123) May 26 10:36:35 ThisOne apparmor[2850]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox May 26 10:36:35 ThisOne apparmor[2850]: AppArmor parser error for /etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/apparmor.d/usr.lib.snapd.snap-confine.real at line 11: Could not open '/var/lib/snapd/apparmor/snap-confine' May 26 10:36:35 ThisOne apparmor[2850]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd May 26 10:36:35 ThisOne apparmor[2850]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox May 26 10:36:35 ThisOne apparmor[2850]: AppArmor parser error for /etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/apparmor.d/usr.lib.snapd.snap-confine.real at line 11: Could not open '/var/lib/snapd/apparmor/snap-confine' May 26 10:36:35 ThisOne apparmor[2850]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd May 26 10:36:35 ThisOne apparmor[2850]:...fail! May 26 10:36:35 ThisOne systemd[1]: apparmor.service: Main process exited, code=exited, status=123/n/a May 26 10:36:35 ThisOne systemd[1]: apparmor.service: Failed with result 'exit-code'. May 26 10:36:35 ThisOne systemd[1]: Failed to start AppArmor initialization. $ sudo apt-get install apparmor-easyprof Reading package lists... Done Building dependency tree Reading state information... Done apparmor-easyprof is already the newest version (2.12-4ubuntu5). 0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. $ sudo systemctl start apparmor.service Job for apparmor.service failed because the control process exited with error code. See "systemctl status apparmor.service" and "journalctl -xe" for details. ** Affects: apparmor (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/1773515 Title: apparmour fails after removal of snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1773515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773346] [NEW] Selected track nto always advanced on deletion
Public bug reported: Something has changed between the Audacious used in Ubuntu 16.04 and 18.04. When deleting a track, with the "Advance when current song deleted" option set to true, the track selected by the cursor always used to advance to the next (now playing) track. It no longer does this, or rather does it only intermittently. This is rather annoying when sorting through large lists of music submitted to me or trying to make a short list of samples to then work on later! ** Affects: audacious (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/1773346 Title: Selected track nto always advanced on deletion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/1773346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464913] Re: portaudio19-dev can't be installed without conflicts
I'm afraid my terminal scrollback history isn't long enough for me to see the original error. Reinstalling libjack-jackd2-dev afterwards was not a possible solution due to the vast quantity of software it wished to remove! I wish I knew exactly what I did but after installing all the other dependencies, apart from the jack libraries and it would remove half my system, running the build-dep command just worked without complaining about dependacies that aren't going to be installed and without trying to remove any other packages. Looking around I did notice this, which seems to be a library for Port Audio using Jack2, which is what seems to be installed on most systems as far as I can tell. x$ apt-cache show libportaudio2 Package: libportaudio2 Architecture: amd64 Version: 19.6.0-1 Multi-Arch: same Priority: optional Section: universe/libs Source: portaudio19 Origin: Ubuntu Maintainer: Ubuntu DevelopersOriginal-Maintainer: Debian VoIP Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 210 Depends: libasound2 (>= 1.0.16), libc6 (>= 2.15), libjack-jackd2-0 (>= 1.9.10+20150825) | libjack-0.125 Filename: pool/universe/p/portaudio19/libportaudio2_19.6.0-1_amd64.deb Size: 64556 MD5sum: 34190a46175b757eac9bec5884b347f7 SHA1: 9e33d7302ca0e2a280c8c936e69a33b5d5db12b0 SHA256: e192f31b52833eb17881ae81c9ff0eb3469da6195d1fa30bdd3873a23bf058ee Homepage: http://www.portaudio.com/ Description-en_GB: Portable audio I/O - shared library PortAudio is a portable audio I/O library designed for cross-platform support of audio. It uses a callback mechanism to request audio processing. Audio can be generated in various formats, including 32 bit floating point, and will be converted to the native format internally. . This package contains the shared library. Description-md5: a71bbbd00a98fe093b85cc97ff79e9ae Task: xubuntu-desktop, lubuntu-gtk-desktop, lubuntu-desktop, ubuntustudio-desktop Supported: 3y -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464913 Title: portaudio19-dev can't be installed without conflicts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portaudio19/+bug/1464913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
Yes, I was using -backports. I dumped a list of everything I had installed before I reinstalled, and I had cgmanager/trusty-updates 0.24-0ubuntu7.5 installed right before the I wiped my system. I was still experiencing 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/1303649 Title: systemd-logind spins in cgmanager_ping_sync() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
Serge, I am not seeing anything like this with 16.04.4. Since I did a full wipe and reinstall, I didn't expect to. Yes, I definitely saw it with 14.04.5 with "proposed" enabled. And the packages Marcelo indicated were among the most recently installed. I think you can treat his system as representative of the problem I saw. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303649 Title: systemd-logind spins in cgmanager_ping_sync() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
Marcelo, Thanks for the information. My system was unresponsive enough that diagnosing the problem was a huge pain. I decided to back up /home and do an install of 16.04 from scratch since I'd been intending to do an upgrade soon anyway. I was also using the "proposed" repo, so I should have been running the same versions you were of those packages. I installed them Thursday evening, but didn't reboot then. When I booted on Friday morning, the problem started. I remembered them because they don't get frequent updates so it was a bit of a surprise to see them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303649 Title: systemd-logind spins in cgmanager_ping_sync() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
I don't know whether we've had a regression here, but I started seeing what looks like this exact same problem this morning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303649 Title: systemd-logind spins in cgmanager_ping_sync() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729893] [NEW] lspci and lshw causing total system freeze
Public bug reported: Hi, not sure if this is the best place to file this bug report and I couldn't find any other similar. System: Dell XPS 15 laptop late 2017, 32GB ram, 1TB SSD, 7th Gen i7 quad-core 8-thread, etc OS: Fresh install Ubuntu 17.10; dual boot with windows 10 pro on AHCI Bug: Total system freeze with certain commands Always reproduced with lspci | grep network (ie I typed it with n instead of N) also always reproduced with any other use of lspci | grep Often reproduced with lspci | grep Network (correctly spelled) and occasionally reproduced with just lspci on its own. when it doesn't freeze the system, it takes it about 2 or 3 seconds to respond (whereas on my old ASUS 8GB ram, dual core quad thread i5 3rd gen it works instantly; same on my ubuntu server running on a crappy headless HP pavillion tower) Also happens when using lshw, esp with lshw -C . It does not matter how long the system has been running. At the same time, it will let me run crunch together with aircrack-ng when pen testing my home lab without any problems even though all 8 threads are maxed out to 100% and I can still use the system as if nothing else is happening. Also, running lspci and lshw on a virtualbox install of Kali 2017.2 will work instantly as expected without any problems. Any suggestions or request of more info would be welcome. Thanks ** Affects: ubuntu-terminal-app (Ubuntu) Importance: Undecided Status: New ** Description changed: - Hi, not sure if this is the best place to file this bug report and I couldn't find any other similar. - System: Dell XPS 15 laptop late 2017, 32GB ram, 1TB SSD, 7th Gen i7 quad-core 8-thread, etc + Hi, not sure if this is the best place to file this bug report and I + couldn't find any other similar. + + System: Dell XPS 15 laptop late 2017, 32GB ram, 1TB SSD, 7th Gen i7 + quad-core 8-thread, etc + OS: Fresh install Ubuntu 17.10; dual boot with windows 10 pro on AHCI + Bug: Total system freeze with certain commands Always reproduced with lspci | grep network (ie I typed it with n instead of N) also always reproduced with any other use of lspci | grep Often reproduced with lspci | grep Network (correctly spelled) and occasionally reproduced with just lspci on its own. when it doesn't freeze the system, it takes it about 2 or 3 seconds to respond (whereas on my old ASUS 8GB ram, dual core quad thread i5 3rd gen it works instantly; same on my ubuntu server running on a crappy headless HP pavillion tower) Also happens when using lshw, esp with lshw -C . It does not matter how long the system has been running. At the same time, it will let me run crunch together with aircrack-ng when pen testing my home lab without any problems even though all 8 threads are maxed out to 100% and I can still use the system as if nothing else is happening. Also, running lspci and lshw on a virtualbox install of Kali 2017.2 will work instantly as expected without any problems. Any suggestions or request of more info would be welcome. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729893 Title: lspci and lshw causing total system freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-terminal-app/+bug/1729893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728170] [NEW] package libpython3.5-minimal:amd64 3.5.2-2ubuntu0~16.04.3 failed to install/upgrade: package libpython3.5-minimal:amd64 is already installed and configured
Public bug reported: crashed when using the Software application. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpython3.5-minimal:amd64 3.5.2-2ubuntu0~16.04.3 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 CrashReports: 640:0:117:3262953:2017-10-27 18:58:01.670561313 -0400:2017-10-27 18:58:03.782556245 -0400:/var/crash/python3.5-minimal.0.crash 644:0:117:0:2017-10-27 18:58:03.782556245 -0400:2017-10-27 18:58:03.782556245 -0400:/var/crash/python3.5-minimal.0.upload 644:0:117:0:2017-10-27 19:05:13.937657091 -0400:2017-10-27 19:05:13.937657091 -0400:/var/crash/grub-common.0.upload 640:0:117:3254155:2017-10-27 19:05:09.269656896 -0400:2017-10-27 19:05:10.269656896 -0400:/var/crash/grub-common.0.crash 600:0:117:600909:2017-10-27 18:57:39.175474166 -0400:2017-10-27 18:57:40.175474166 -0400:/var/crash/libpython3.5-minimal:amd64.0.crash Date: Fri Oct 27 18:57:39 2017 DuplicateSignature: package:libpython3.5-minimal:amd64:3.5.2-2ubuntu0~16.04.3 Processing triggers for dbus (1.10.6-1ubuntu3.3) ... dpkg: error processing package libpython3.5-minimal:amd64 (--configure): package libpython3.5-minimal:amd64 is already installed and configured ErrorMessage: package libpython3.5-minimal:amd64 is already installed and configured InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: dpkg Title: package libpython3.5-minimal:amd64 3.5.2-2ubuntu0~16.04.3 failed to install/upgrade: package libpython3.5-minimal:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed 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/1728170 Title: package libpython3.5-minimal:amd64 3.5.2-2ubuntu0~16.04.3 failed to install/upgrade: package libpython3.5-minimal:amd64 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1728170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728171] [NEW] package libpython3.5-minimal:amd64 3.5.2-2ubuntu0~16.04.3 failed to install/upgrade: package libpython3.5-minimal:amd64 is already installed and configured
Public bug reported: crash when using Software installer. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpython3.5-minimal:amd64 3.5.2-2ubuntu0~16.04.3 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 CrashReports: 640:0:117:3262953:2017-10-27 18:58:01.670561313 -0400:2017-10-27 18:58:03.782556245 -0400:/var/crash/python3.5-minimal.0.crash 644:0:117:0:2017-10-27 18:58:03.782556245 -0400:2017-10-27 18:58:03.782556245 -0400:/var/crash/python3.5-minimal.0.upload 644:0:117:0:2017-10-27 19:05:13.937657091 -0400:2017-10-27 19:05:13.937657091 -0400:/var/crash/grub-common.0.upload 640:0:117:3254155:2017-10-27 19:05:09.269656896 -0400:2017-10-27 19:05:10.269656896 -0400:/var/crash/grub-common.0.crash 600:0:117:600909:2017-10-27 18:57:39.175474166 -0400:2017-10-27 18:57:40.175474166 -0400:/var/crash/libpython3.5-minimal:amd64.0.crash Date: Fri Oct 27 18:57:39 2017 DuplicateSignature: package:libpython3.5-minimal:amd64:3.5.2-2ubuntu0~16.04.3 Processing triggers for dbus (1.10.6-1ubuntu3.3) ... dpkg: error processing package libpython3.5-minimal:amd64 (--configure): package libpython3.5-minimal:amd64 is already installed and configured ErrorMessage: package libpython3.5-minimal:amd64 is already installed and configured InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: python3.5 Title: package libpython3.5-minimal:amd64 3.5.2-2ubuntu0~16.04.3 failed to install/upgrade: package libpython3.5-minimal:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python3.5 (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728171 Title: package libpython3.5-minimal:amd64 3.5.2-2ubuntu0~16.04.3 failed to install/upgrade: package libpython3.5-minimal:amd64 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.5/+bug/1728171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705361] [NEW] job for nfs-server.service failed because the control process exited with error code.package nfs-kernel-server 1:1.2.8-9ubuntu12.1 failed to install/upgrade: subprocess installed p
Public bug reported: I was trying to set up NFS server using "SettingUpNFSHowTo" web page, on 16.04 LTS release. https://help.ubuntu.com/community/SettingUpNFSHowTo?action=fullsearch=linkto%3A%22SettingUpNFSHowTo%22=180 Not sure if this is user/setup error or system error. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nfs-kernel-server 1:1.2.8-9ubuntu12.1 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: nfs-common: Install nfs-kernel-server: Install nfs-common: Configure nfs-kernel-server: Configure NULL: ConfigurePending Architecture: amd64 Date: Wed Jul 19 19:22:38 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-02-22 (513 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: nfs-utils Title: package nfs-kernel-server 1:1.2.8-9ubuntu12.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-05-15 (65 days ago) ** Affects: nfs-utils (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/1705361 Title: job for nfs-server.service failed because the control process exited with error code.package nfs-kernel-server 1:1.2.8-9ubuntu12.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/nfs-utils/+bug/1705361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1701856] Re: Install crashes.
Thanks for your reply. I don't remember seeing a message like that but I'll try again and see what happens. I'm very new to this so I'll do some reading and try to get my knowledge level up a bit. Sorry to have wasted your time. Sent from my iPhone > On 6 Jul 2017, at 3:51 PM, Phillip Susiwrote: > > Your disk is currently partitioned to boot in bios mode, but you booted > the installer in EFI mode. A warning message prompted you that this > could be a problem and recommended performing a bios mode install > instead, but you chose not to. You either need to perform the bios mode > install, or partition the disk using GPT and set up an EFI system > partition to install in EFI mode. This will be done for you if you > choose the "use entire disk" guided install option. > > ** Changed in: grub-installer (Ubuntu) > Status: New => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1701856 > > Title: > Install crashes. > > Status in grub-installer package in Ubuntu: > Invalid > > Bug description: > 17.04 > Grub wont install. I also had to unmount my main Raid0 boot drive to get any > of my drives to show up in Ubuntu live. Ubuntu wont see the partition I > created for it on the raid. Raid consists of 2x M2 NVMe ssd's in 0. Windows > installed fine. > > ProblemType: Bug > DistroRelease: Ubuntu 17.04 > Package: ubiquity 17.04.9 [modified: > lib/partman/automatically_partition/question] > ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 > Uname: Linux 4.10.0-19-generic x86_64 > ApportVersion: 2.20.4-0ubuntu4 > Architecture: amd64 > CasperVersion: 1.380 > Date: Sat Jul 1 23:59:31 2017 > InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi > file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- > LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) > ProcEnviron: > TERM=unknown > 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) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1701856/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701856 Title: Install crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1701856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1701856] [NEW] Install crashes.
Public bug reported: 17.04 Grub wont install. I also had to unmount my main Raid0 boot drive to get any of my drives to show up in Ubuntu live. Ubuntu wont see the partition I created for it on the raid. Raid consists of 2x M2 NVMe ssd's in 0. Windows installed fine. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ubiquity 17.04.9 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CasperVersion: 1.380 Date: Sat Jul 1 23:59:31 2017 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=unknown 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 ubiquity-17.04.9 ubuntu zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701856 Title: Install crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1701856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1695557] [NEW] emacs failed during upgrade
Public bug reported: Setting up emacs24 (24.5+1-6ubuntu1) ... Install emacsen-common for emacs24 emacsen-common: Handling install of emacsen flavor emacs24 emacs24: relocation error: /usr/lib/x86_64-linux-gnu/libboost_system.so.1.58.0: symbol _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEED1Ev, version GLIBCXX_3.4.21 not defined in file libstdc++.so.6 with link time reference ERROR: install script from emacsen-common package failed dpkg: error processing package emacs24 (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of emacs: emacs depends on emacs24 | emacs24-lucid | emacs24-nox; however: Package emacs24 is not configured yet. Package emacs24-lucid is not installed. Package emacs24-nox is not installed. dpkg: error processing package emacs (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: emacs24 emacs ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Attachment added: "gzip'ed tar of /var/log/dist-upgrade/" https://bugs.launchpad.net/bugs/1695557/+attachment/4888123/+files/dist-upgrade.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1695557 Title: emacs failed during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1695557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome
If it helps, I had success configuring a Google account with GOA on Unity yesterday afternoon. Today, setting up the same with Ubuntu-Gnome no longer works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687019 Title: Cannot add a Google account using Online Accounts in Ubuntu Gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1687019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673571] [NEW] plasma-discover gives faulty information, some only temporarily
Public bug reported: may be a duplicate of #1671909 Fresh install of kubuntu, the notification area pops up an icon saying "Updates Available", when I click it, it says 4 updates available, I select update, Plasma-Discover opens, loads for a few moments, then says "The software on this computer is up to date." If I leave it on this screen for about a minute, suddenly the 4 updates appear. The updates that finally appear all show as having a size of 0 bytes, with a total for the 4 selected updates also 0 B. When I press update, a bar at the top shows up saying Updating, which jumps to about 20% progress, then down to 10% progress, then slowly works it way up to 30% progress, then jumps back to 0%, then the individual progress bars for each update complete, then restart from 0%, then complete again, then start from 0% again, then get to about 20% and the whole thing hangs for a minute, then the screen jumps back to "The software on this computer is up to date." and the icon in the notification area disappears (the updates were installed) As an updater, I guess it's working, but the user interface/experience has a large number of glaring issues. ** Affects: plasma-discover (Ubuntu) Importance: Undecided Status: New ** Description changed: - may be a duplicate of #1671909 + may be a duplicate of 1671909 Fresh install of kubuntu, the notification area pops up an icon saying "Updates Available", when I click it, it says 4 updates available, I select update, Plasma-Discover opens, loads for a few moments, then says "The software on this computer is up to date." If I leave it on this screen for about a minute, suddenly the 4 updates appear. The updates that finally appear all show as having a size of 0 bytes, with a total for the 4 selected updates also 0 B. When I press update, a bar at the top shows up saying Updating, which jumps to about 20% progress, then down to 10% progress, then slowly works it way up to 30% progress, then jumps back to 0%, then the individual progress bars for each update complete, then restart from 0%, then complete again, then start from 0% again, then get to about 20% and the whole thing hangs for a minute, then the screen jumps back to "The software on this computer is up to date." and the icon in the notification area disappears (the updates were installed) ** Description changed: - may be a duplicate of 1671909 + may be a duplicate of bug #1671909 Fresh install of kubuntu, the notification area pops up an icon saying "Updates Available", when I click it, it says 4 updates available, I select update, Plasma-Discover opens, loads for a few moments, then says "The software on this computer is up to date." If I leave it on this screen for about a minute, suddenly the 4 updates appear. The updates that finally appear all show as having a size of 0 bytes, with a total for the 4 selected updates also 0 B. When I press update, a bar at the top shows up saying Updating, which jumps to about 20% progress, then down to 10% progress, then slowly works it way up to 30% progress, then jumps back to 0%, then the individual progress bars for each update complete, then restart from 0%, then complete again, then start from 0% again, then get to about 20% and the whole thing hangs for a minute, then the screen jumps back to "The software on this computer is up to date." and the icon in the notification area disappears (the updates were installed) ** Description changed: - may be a duplicate of bug #1671909 + may be a duplicate of #1671909 Fresh install of kubuntu, the notification area pops up an icon saying "Updates Available", when I click it, it says 4 updates available, I select update, Plasma-Discover opens, loads for a few moments, then says "The software on this computer is up to date." If I leave it on this screen for about a minute, suddenly the 4 updates appear. The updates that finally appear all show as having a size of 0 bytes, with a total for the 4 selected updates also 0 B. When I press update, a bar at the top shows up saying Updating, which jumps to about 20% progress, then down to 10% progress, then slowly works it way up to 30% progress, then jumps back to 0%, then the individual progress bars for each update complete, then restart from 0%, then complete again, then start from 0% again, then get to about 20% and the whole thing hangs for a minute, then the screen jumps back to "The software on this computer is up to date." and the icon in the notification area disappears (the updates were installed) + + As an updater, I guess it's working, but the user interface/experience + has a large number of glaring issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673571 Title: plasma-discover gives faulty information, some only
[Bug 1647122] [NEW] package libsord-0-0:amd64 0.14.0~dfsg0-1 failed to install/upgrade: package libsord-0-0:amd64 is already installed and configured
Public bug reported: All I was doing was installing multiple programs, one at a time, and the system was completely updated as well. No processing or other programs running at the time. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libsord-0-0:amd64 0.14.0~dfsg0-1 ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30 Uname: Linux 4.4.0-51-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 CrashReports: 640:0:116:2445242:2016-12-03 20:46:58.586420536 -0700:2016-12-03 20:47:01.002432421 -0700:/var/crash/libserd-0-0:amd64.0.crash 644:0:116:0:2016-12-03 20:47:01.002432421 -0700:2016-12-03 20:47:01.002432421 -0700:/var/crash/libserd-0-0:amd64.0.upload 600:0:116:450327:2016-12-03 20:46:10.298010826 -0700:2016-12-03 20:46:11.298010826 -0700:/var/crash/libsord-0-0:amd64.0.crash 600:0:116:449281:2016-12-03 20:46:10.742006024 -0700:2016-12-03 20:46:10.302002228 -0700:/var/crash/libsbsms10:amd64.0.crash Date: Sat Dec 3 20:46:11 2016 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu4 libgcc1 1:6.0.1-0ubuntu1 libserd-0-0 0.22.0~dfsg0-2 DuplicateSignature: package:libsord-0-0:amd64:0.14.0~dfsg0-1 Processing triggers for libc-bin (2.23-0ubuntu4) ... dpkg: error processing package libsbsms10:amd64 (--configure): package libsbsms10:amd64 is already installed and configured ErrorMessage: package libsord-0-0:amd64 is already installed and configured InstallationDate: Installed on 2016-12-03 (0 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: dpkg Title: package libsord-0-0:amd64 0.14.0~dfsg0-1 failed to install/upgrade: package libsord-0-0:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647122 Title: package libsord-0-0:amd64 0.14.0~dfsg0-1 failed to install/upgrade: package libsord-0-0:amd64 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1647122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553150] Re: Ubuntu One account does not stay logged in or does not sign in at all
Argh... after reading the above (yeh, I know...) I went into the accounts settings and put my credentials in there, then returning to the updates page I could request the updates only to be hit by a 401 UNAUTHORIZED error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553150 Title: Ubuntu One account does not stay logged in or does not sign in at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntuone-credentials/+bug/1553150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553150] Re: Ubuntu One account does not stay logged in or does not sign in at all
This problem has hit me in the last two weeks (Meizu MX4), and I can't install *any* upgrades. HELP! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553150 Title: Ubuntu One account does not stay logged in or does not sign in at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntuone-credentials/+bug/1553150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630152] [NEW] package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 - general issues with apt-update as well
Public bug reported: Just an overall problem with apt-update from the CL after a fresh install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Oct 4 02:28:16 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-10-04 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fontconfig (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/1630152 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 - general issues with apt-update as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1630152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614533] [NEW] package account-plugin-facebook (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package kac
Public bug reported: Installing Mate desktop on Ubuntu Studio. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: account-plugin-facebook (not installed) ProcVersionSignature: Ubuntu 4.4.0-34.53-lowlatency 4.4.15 Uname: Linux 4.4.0-34-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Aug 18 09:29:36 2016 DuplicateSignature: package:account-plugin-facebook:(not installed) Unpacking account-plugin-facebook (0.12+16.04.20160126-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/account-plugin-facebook_0.12+16.04.20160126-0ubuntu1_all.deb (--unpack): trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 ErrorMessage: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 InstallationDate: Installed on 2016-05-18 (91 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: account-plugins Title: package account-plugin-facebook (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: account-plugins (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614533 Title: package account-plugin-facebook (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit- options.d/www.facebook.com.conf', which is also in package kaccounts- providers 4:15.12.3-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1614533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614534] [NEW] package account-plugin-google (not installed) failed to install/upgrade: trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in package kaccounts-pro
Public bug reported: Installing Mate desktop on Ubuntu Studio. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: account-plugin-google (not installed) ProcVersionSignature: Ubuntu 4.4.0-34.53-lowlatency 4.4.15 Uname: Linux 4.4.0-34-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Aug 18 09:29:38 2016 DuplicateSignature: package:account-plugin-google:(not installed) Unpacking account-plugin-facebook (0.12+16.04.20160126-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/account-plugin-facebook_0.12+16.04.20160126-0ubuntu1_all.deb (--unpack): trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 ErrorMessage: trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 InstallationDate: Installed on 2016-05-18 (91 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: account-plugins Title: package account-plugin-google (not installed) failed to install/upgrade: trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: account-plugins (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614534 Title: package account-plugin-google (not installed) failed to install/upgrade: trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1614534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1604587] Re: PCI/internal sound card not detected
I ran ubuntu 16.04 live from usb and it has sound. I installed it with updates and no sound. I installed it without updates and sound works. Conclusion? The updates nuked the sound. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1604587 Title: PCI/internal sound card not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1604587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1604587] [NEW] PCI/internal sound card not detected
Public bug reported: I updated 16.04 and rebooted. No sound on any applications. Checked to see if sound card was detected with aplay. None detected. Ran lspci. Shows audio device Intel Corporation Sunrise Point-H HD Audio (rev 31) Sound working prior to installing last updates. No hardware changes in the interim. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Tue Jul 19 16:01:29 2016 InstallationDate: Installed on 2016-06-07 (42 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0406 dmi.board.asset.tag: Default string dmi.board.name: H170M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/31/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1604587 Title: PCI/internal sound card not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1604587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382977] Re: [SRU] Thunar open default not respecting mimetype
It appears 14.04.4 may be affect so please patch that version for all users, not just me with my odd usercase ;) https://lists.ubuntu.com/archives/xubuntu-users/2016-April/009233.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382977 Title: [SRU] Thunar open default not respecting mimetype To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1382977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382977] Re: [SRU] Thunar open default not respecting mimetype
Any chance of getting this backported to Trusty? I have installed Thunar using the Trusty packages as there is functionality changes in 1.6.10 which cause it to be really unpleasant for me to use! As 16.04 has a newer version of libglib2.0-0 I have come across the issues that some files (for me seems to be only image files) will not follow the change of Default program. As neither Utopic or Vivid are supported any more the files from those releases are no longer available for download! Although the version does look like it should be the same in Utopic (1.6.3-1ubuntu5) I definitely have issues that sound related to this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382977 Title: [SRU] Thunar open default not respecting mimetype To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1382977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592932] [NEW] unity8 using 100% of CPU
Public bug reported: unity8 will freeze up from time to time during operation of xterm or other x11 legacy apps. This freeze up was reported by htop running in an instance on tty1. It will show two sessions of unity8 running at 100%. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: unity8 8.12+16.10.20160527-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13 Uname: Linux 4.4.0-25-generic x86_64 ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 15 14:22:04 2016 InstallationDate: Installed on 2015-05-16 (395 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150510) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) upstart.unity8-filewatcher.log: ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592932 Title: unity8 using 100% of CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1592932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1590142] Re: libertine apps work somtimes and then freeze
** Changed in: libertine (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/1590142 Title: libertine apps work somtimes and then freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libertine/+bug/1590142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1590142] Re: libertine apps work somtimes and then freeze
So when I try to open an app like gnome screenshot or gnome terminal I get: ** (process:32125): CRITICAL **: main: assertion 'bus != NULL' failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1590142 Title: libertine apps work somtimes and then freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libertine/+bug/1590142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1590142] Re: libertine apps work somtimes and then freeze
** Attachment added: "failed app" https://bugs.launchpad.net/ubuntu/+source/libertine/+bug/1590142/+attachment/4679698/+files/application-failed.log.1.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1590142 Title: libertine apps work somtimes and then freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libertine/+bug/1590142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1590142] Re: libertine apps work somtimes and then freeze
** Attachment added: "another example" https://bugs.launchpad.net/ubuntu/+source/libertine/+bug/1590142/+attachment/4679699/+files/application-failed.log.3.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1590142 Title: libertine apps work somtimes and then freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libertine/+bug/1590142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586789] [NEW] fatal error: upgrade 15.10 to 16.04 - mysql
Public bug reported: upgrading from 14.10 to 15.04 success upgrading from 15.04 to 15.10 success upgrading from 15.04 to 16.04 LTS fails = Please report this as a bug and include the files /var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in your report. The upgrade has aborted. Your original sources.list was saved in /etc/apt/sources.list.distUpgrade. SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1) Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). Please report this bug in a browser at http://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+filebug and attach the files in /var/log/dist-upgrade/ to the bug report. installArchives() failed Setting up mysql-server-5.7 (5.7.12-0ubuntu1) ... Job for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details. invoke-rc.d: initscript mysql, action "start" failed. invoke-rc.d: release upgrade in progress, error is not fatal dpkg: error processing package mysql-server-5.7 (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of mysql-server: mysql-server depends on mysql-server-5.7; however: Package mysql-server-5.7 is not configured yet. dpkg: error processing package mysql-server (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: mysql-server-5.7 mysql-server Upgrade complete The upgrade has completed but there were errors during the upgrade process. ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Attachment added: "apt-log and main-log.txt" https://bugs.launchpad.net/bugs/1586789/+attachment/4672313/+files/apt-log%20and%20main-log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586789 Title: fatal error: upgrade 15.10 to 16.04 - mysql To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1586789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578805] [NEW] mountewf on E01 file gives error
Public bug reported: Usage log. I expected the mount to succeed: $ sudo ewfmount usb1.E01 /tmp/usb1 [sudo] password for dale: ewfmount 20140608 No sub system to mount EWF format. Additional info: $ lsb_release -rd Description:Ubuntu 14.04.4 LTS Release:14.04 $ apt-cache policy ewf-tools ewf-tools: Installed: 20130416-3 Candidate: 20130416-3 Version table: *** 20130416-3 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: libewf (Ubuntu) Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578805 Title: mountewf on E01 file gives error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libewf/+bug/1578805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578805] Re: mountewf on E01 file gives error
I suspect there is some configuration step I haven't taken, since the man page for ewfmount certainly implies I should be able to do this. ** Changed in: libewf (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/libewf/+question/293343 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578805 Title: mountewf on E01 file gives error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libewf/+bug/1578805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15
Attached is lspci ** Attachment added: "lspci" https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1572630/+attachment/4640782/+files/lspci -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572630 Title: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1572630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15
Attached is dmidecode ** Attachment added: "dmidecode" https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1572630/+attachment/4640781/+files/dmidecode -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572630 Title: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1572630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572630] [NEW] boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15
Public bug reported: We discovered a pretty serious regression introduced in 4.4.0-18. At boot-time, the kernel will panic somewhere in 'blk_mq_register_disk', a snippet of the track is below, and full panic dump is attached. The panic dump was collected via serial console, as the kernel panics so early that we cannot kdump it. [2.650512] [] blk_mq_register_disk+0xa6/0x160 [2.656675] [] blk_register_queue+0xb4/0x160 [2.662661] [] add_disk+0x1ce/0x490 [2.667869] [] loop_add+0x1f0/0x270 This seems somewhat similar to https://lkml.org/lkml/2016/3/16/40, but the trace is not identical. We discovered this issue when we were experimenting with linux-generic- lts-xenial from trusty-updates on a 14.04 installation. When we installed it, 4.4.0-15 was the current package, and it worked fine and provided a large amount of improvements for us. Background security updates installed 4.4.0-18, and this updated and grub and became the default kernel. On a reboot, the node panics about 2 seconds in, resulting in a machine in a dead state. We were able to boot a rescue image and roll bac kto 4.4.0-15, which works nicely. We currently have pinning on 4.4.0-15 to prevent this problem from coming back, but would prefer to see the problem fixed. I'll attach lspci, lshw, and dmidecode for our hardware as well, but this is happening on pretty vanilla supermicro nodes. We are able to consistently reproduce it on our hardware. It is not reproducible in EC2, only on metal. ** Affects: linux-lts-xenial (Ubuntu) Importance: Undecided Status: New ** Tags: kernel kernel-bug panic xenial ** Attachment added: "loopcrash" https://bugs.launchpad.net/bugs/1572630/+attachment/4640780/+files/loopcrash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572630 Title: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1572630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15
add lshw output ** Attachment added: "lshw" https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1572630/+attachment/4640783/+files/lshw -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572630 Title: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1572630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1504724] Re: lightdm crashed with SIGSEGV in munmap()
This may be a teamviewer problem. I don't know if it is relevant, but when searching /var/log for any mention of munmap, I got the following results: dvs4@dvs4-E6540:/var/log$ sudo grep -R munmap * auth.log:Dec 7 08:31:22 dvs4-E6540 sudo: dvs4 : TTY=pts/2 ; PWD=/var/log ; USER=root ; COMMAND=/bin/grep munmap alternatives.log alternatives.log.1 alternatives.log.10.gz alternatives.log.11.gz alternatives.log.12.gz alternatives.log.2.gz alternatives.log.3.gz alternatives.log.4.gz alternatives.log.5.gz alternatives.log.6.gz alternatives.log.7.gz alternatives.log.8.gz alternatives.log.9.gz apache2 apport.log apport.log.1 apport.log.2.gz apport.log.3.gz apport.log.4.gz apport.log.5.gz apport.log.6.gz apport.log.7.gz apt auth.log auth.log.1 auth.log.2.gz auth.log.3.gz auth.log.4.gz boot.log bootstrap.log btmp btmp.1 chkrootkit ConsoleKit cups dirmngr dist-upgrade dmesg dmesg.0 dmesg.1.gz dmesg.2.gz dmesg.3.gz dmesg.4.gz dpkg.log dpkg.log.1 dpkg.log.10.gz dpkg.log.11.gz dpkg.log.12.gz dpkg.log.2.gz dpkg.log.3.gz dpkg.log.4.gz dpkg.log.5.gz dpkg.log.6.gz dpkg.log.7.gz dpkg.log.8.gz dpkg.log.9.gz faillog fontconfig.log fsck git-daemon gpu-manager.log hp installer kern.log kern.log.1 auth.log:Dec 7 08:32:45 dvs4-E6540 sudo: dvs4 : TTY=pts/2 ; PWD=/var/log ; USER=root ; COMMAND=/bin/grep -R munmap alternatives.log alternatives.log.1 alternatives.log.10.gz alternatives.log.11.gz alternatives.log.12.gz alternatives.log.2.gz alternatives.log.3.gz alternatives.log.4.gz alternatives.log.5.gz alternatives.log.6.gz alternatives.log.7.gz alternatives.log.8.gz alternatives.log.9.gz apache2 apport.log apport.log.1 apport.log.2.gz apport.log.3.gz apport.log.4.gz apport.log.5.gz apport.log.6.gz apport.log.7.gz apt auth.log auth.log.1 auth.log.2.gz auth.log.3.gz auth.log.4.gz boot.log bootstrap.log btmp btmp.1 chkrootkit ConsoleKit cups dirmngr dist-upgrade dmesg dmesg.0 dmesg.1.gz dmesg.2.gz dmesg.3.gz dmesg.4.gz dpkg.log dpkg.log.1 dpkg.log.10.gz dpkg.log.11.gz dpkg.log.12.gz dpkg.log.2.gz dpkg.log.3.gz dpkg.log.4.gz dpkg.log.5.gz dpkg.log.6.gz dpkg.log.7.gz dpkg.log.8.gz dpkg.log.9.gz faillog fontconfig.log fsck git-daemon gpu-manager.log hp installer kern.log kern.log .1 grep: teamviewer/lightdm: No such file or directory ls -al in /var/log shows the following link for teamviewer lrwxrwxrwx 1 rootroot 24 Jan 15 2015 teamviewer -> /opt/teamviewer/logfiles Checking that link includes the following lightdm link: dvs4@dvs4-E6540:/var/log$ ls -al /opt/teamviewer/logfiles/ lrwxrwxrwx 1 root root 41 Dec 10 2014 dvs4 -> /home/dvs4/.config/teamviewer10/logfiles/ lrwxrwxrwx 1 root root 47 Feb 3 2015 lightdm -> /var/lib/lightdm/.config/teamviewer10/logfiles/ Checking where that should point to shows it is not there: dvs4@dvs4-E6540:/var/log$ sudo ls -al /var/lib/lightdm/* ls: cannot access /var/lib/lightdm/*: No such file or directory Because of the similarities and because I am the only user on this machine, I changed the lightdm link to match the dvs4 user link: lrwxrwxrwx 1 root root 41 Dec 7 08:36 lightdm -> /home/dvs4/.config/teamviewer10/logfiles/ I have never seen this particular error before, but I have had some annoying glitches with the way Teamviewer starts, so I will try it this way for a while and see if it seems to make any difference... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1504724 Title: lightdm crashed with SIGSEGV in munmap() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1504724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1489119] [NEW] install crash
Public bug reported: I upgraded from 12.04, and when that did not work I tried a complete reinstall, only to have this crash ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity 2.18.8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CasperVersion: 1.340 Date: Wed Aug 26 14:33:16 2015 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash -- LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ubiquity-2.18.8 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1489119 Title: install crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1489119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1442674] Re: sysstat log corruption, time isn't changing
Oh okay, I didn't know about -L being hard coded in there, missed that. I just ended up making sure the two cron jobs won't conflict with each other, which is why I was saying it was a configuration error on my part. I did have: */5 * * * * root command -v debian-sa1 /dev/null debian-sa1 -L 1 1 59 23 * * * root command -v debian-sa1 /dev/null debian-sa1 -L 60 2 But I've gone to: 2-58/2 * * * * root command -v debian-sa1 /dev/null debian-sa1 -L 1 1 59 23 * * * root command -v debian-sa1 /dev/null debian-sa1 -L 60 2 I'm pretty sure the two were conflicting. I haven't seen any problems since making that change. On Wed, Aug 19, 2015 at 8:39 PM, Bill Cole ubuntu-20150...@billmail.scconsult.com wrote: Note that the -L flag is hardcoded in the sa1 calls of sadc, so whatever locking that does is not fixing the issue. Seems like a possible upstream bug? I've had this issue in sysstat data files generated on machines ( n=9 out of 48 sa?? files from 3 different machines) where the sysstat resolution has been changed to every 2 minutes by changing this line in /etc/cron.d/sysstat: 5-55/10 * * * * root command -v debian-sa1 /dev/null debian- sa1 1 1 To: */2 * * * * root command -v debian-sa1 /dev/null debian-sa1 1 1 I've been able to salvage the files by looking for repeating binary patterns to figure out the size and offsets of sadc records, finding the one which is a runt, and rebuilding the file by splicing together the sections before and after it, making sure the resulting file is identical in size to the other full-day files that are parseable. This is not an easily documented process, as it requires eyeballing hexdump output and making educated guesses, but there are useful tips: 1. With -S XALL in SADC_OPTIONS, each record is 8-9KB, and for some reason they seem to alternate between 2 sizes (!) 16 bytes different, e.g. 8528 bytes 8544 bytes. 2. There is a header in the file between 850-900 bytes, so a good place to start looking for patterns at the end of records (useful!) is ~9K. 3. EVERY time I've had this problem, the 2nd record has been a runt, 500-1500 bytes shorter than the normal records. Because excising the runt record yields what seems to be a perfectly good file, my guess is that the root cause is collision between the 23:59 run and the 00:00 run, with the sadc -L flag for some reason failing to do its job. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1442674 Title: sysstat log corruption, time isn't changing Status in sysstat package in Ubuntu: Invalid Bug description: I'm seeing some log file corruption in sysstat, the time stamp occasionally just stops changing. So the output I typically see is like: # sar 12:00:00 AM all 0.00 0.00 0.00 0.00 0.00 0.00 12:00:00 AM all 0.00 0.00 0.00 0.00 0.00 0.00 12:00:00 AM all 0.00 0.00 0.00 0.00 0.00 0.00 End of system activity file unexpected Typical output should be something like: 11:58:01 PM all 0.11 0.00 0.02 0.00 0.00 99.87 11:59:01 PM all 0.06 0.00 0.02 0.00 0.00 99.92 12:00:01 AM all 0.03 0.00 0.02 0.00 0.00 99.95 Average:all 0.10 0.00 0.04 0.00 0.00 99.86 I'm attaching some example logs files, sa09 is good, sa10 is corrupted. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sysstat 10.2.0-1 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 Date: Fri Apr 10 14:44:10 2015 SourcePackage: sysstat UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.cron.d.sysstat: 2015-03-25T18:44:29.274292 mtime.conffile..etc.sysstat.sysstat: 2015-03-25T18:44:29.198292 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/1442674/+subscriptions -- Dale Harris rod...@maybe.org rod...@gmail.com /.-) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to sysstat in Ubuntu. https://bugs.launchpad.net/bugs/1442674 Title: sysstat log corruption, time isn't changing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/1442674/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1442674] Re: sysstat log corruption, time isn't changing
Oh okay, I didn't know about -L being hard coded in there, missed that. I just ended up making sure the two cron jobs won't conflict with each other, which is why I was saying it was a configuration error on my part. I did have: */5 * * * * root command -v debian-sa1 /dev/null debian-sa1 -L 1 1 59 23 * * * root command -v debian-sa1 /dev/null debian-sa1 -L 60 2 But I've gone to: 2-58/2 * * * * root command -v debian-sa1 /dev/null debian-sa1 -L 1 1 59 23 * * * root command -v debian-sa1 /dev/null debian-sa1 -L 60 2 I'm pretty sure the two were conflicting. I haven't seen any problems since making that change. On Wed, Aug 19, 2015 at 8:39 PM, Bill Cole ubuntu-20150...@billmail.scconsult.com wrote: Note that the -L flag is hardcoded in the sa1 calls of sadc, so whatever locking that does is not fixing the issue. Seems like a possible upstream bug? I've had this issue in sysstat data files generated on machines ( n=9 out of 48 sa?? files from 3 different machines) where the sysstat resolution has been changed to every 2 minutes by changing this line in /etc/cron.d/sysstat: 5-55/10 * * * * root command -v debian-sa1 /dev/null debian- sa1 1 1 To: */2 * * * * root command -v debian-sa1 /dev/null debian-sa1 1 1 I've been able to salvage the files by looking for repeating binary patterns to figure out the size and offsets of sadc records, finding the one which is a runt, and rebuilding the file by splicing together the sections before and after it, making sure the resulting file is identical in size to the other full-day files that are parseable. This is not an easily documented process, as it requires eyeballing hexdump output and making educated guesses, but there are useful tips: 1. With -S XALL in SADC_OPTIONS, each record is 8-9KB, and for some reason they seem to alternate between 2 sizes (!) 16 bytes different, e.g. 8528 bytes 8544 bytes. 2. There is a header in the file between 850-900 bytes, so a good place to start looking for patterns at the end of records (useful!) is ~9K. 3. EVERY time I've had this problem, the 2nd record has been a runt, 500-1500 bytes shorter than the normal records. Because excising the runt record yields what seems to be a perfectly good file, my guess is that the root cause is collision between the 23:59 run and the 00:00 run, with the sadc -L flag for some reason failing to do its job. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1442674 Title: sysstat log corruption, time isn't changing Status in sysstat package in Ubuntu: Invalid Bug description: I'm seeing some log file corruption in sysstat, the time stamp occasionally just stops changing. So the output I typically see is like: # sar 12:00:00 AM all 0.00 0.00 0.00 0.00 0.00 0.00 12:00:00 AM all 0.00 0.00 0.00 0.00 0.00 0.00 12:00:00 AM all 0.00 0.00 0.00 0.00 0.00 0.00 End of system activity file unexpected Typical output should be something like: 11:58:01 PM all 0.11 0.00 0.02 0.00 0.00 99.87 11:59:01 PM all 0.06 0.00 0.02 0.00 0.00 99.92 12:00:01 AM all 0.03 0.00 0.02 0.00 0.00 99.95 Average:all 0.10 0.00 0.04 0.00 0.00 99.86 I'm attaching some example logs files, sa09 is good, sa10 is corrupted. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sysstat 10.2.0-1 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 Date: Fri Apr 10 14:44:10 2015 SourcePackage: sysstat UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.cron.d.sysstat: 2015-03-25T18:44:29.274292 mtime.conffile..etc.sysstat.sysstat: 2015-03-25T18:44:29.198292 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/1442674/+subscriptions -- Dale Harris rod...@maybe.org rod...@gmail.com /.-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1442674 Title: sysstat log corruption, time isn't changing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/1442674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1442674] Re: sysstat log corruption, time isn't changing
Yeah, I think is mostly a misconfiguration on my part. You can't overlap the execution of those two crontab lines without having problems, even with the -L flag. I saw some weirdness even with the file locking in place on some of my systems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1442674 Title: sysstat log corruption, time isn't changing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/1442674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1442674] Re: sysstat log corruption, time isn't changing
Yeah, I think is mostly a misconfiguration on my part. You can't overlap the execution of those two crontab lines without having problems, even with the -L flag. I saw some weirdness even with the file locking in place on some of my systems. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to sysstat in Ubuntu. https://bugs.launchpad.net/bugs/1442674 Title: sysstat log corruption, time isn't changing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/1442674/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1442674] Re: sysstat log corruption, time isn't changing
I finally noticed that sadc has optional file locking with the -L flag, so I suspect that will likely fix my problems. Just going to add -L to the debian-sa1 lines in the /etc/cron.d/sysstat. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1442674 Title: sysstat log corruption, time isn't changing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/1442674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1442674] Re: sysstat log corruption, time isn't changing
I finally noticed that sadc has optional file locking with the -L flag, so I suspect that will likely fix my problems. Just going to add -L to the debian-sa1 lines in the /etc/cron.d/sysstat. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to sysstat in Ubuntu. https://bugs.launchpad.net/bugs/1442674 Title: sysstat log corruption, time isn't changing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/1442674/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1103044] Re: outdated version of nodejs (ubuntu 12.04 / 12.10 / 13.04 / 14.04 /14.10/15.04)
Latest stable nodejs version is 0.12.4, seems like it would be better to aim for that in 14.04 LTS and later. But obviously Debian hasn't upgraded anything from upstream in a long time, either. I guess I'll just use the PPA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103044 Title: outdated version of nodejs (ubuntu 12.04 / 12.10 / 13.04 / 14.04 /14.10/15.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1103044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs