[Bug 2061740] [NEW] update to apache2_2.4.52-1ubuntu4.9_amd64 causes website to respond with 301 redirect to itself
Public bug reported: Hi, I have a wordlpress site running on Ubuntu 22.04.3 LTS (GNU/Linux 6.2.0-1017-aws x86_64). After updating apache2 the site returns a 301 redirect to itself. No other configuration was changed. ``` ~$ apache2 -v Server version: Apache/2.4.52 (Ubuntu) Server built: 2023-10-26T13:44:44 ``` ** site is working Now we update apache2 ``` ~$ sudo apt update ... ~$ sudo apt-get install --only-upgrade apache2 Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: apache2-bin apache2-data apache2-utils Suggested packages: apache2-doc apache2-suexec-pristine | apache2-suexec-custom www-browser The following packages will be upgraded: apache2 apache2-bin apache2-data apache2-utils 4 upgraded, 0 newly installed, 0 to remove and 120 not upgraded. Need to get 1698 kB of archives. After this operation, 3072 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 apache2 amd64 2.4.52-1ubuntu4.9 [97.9 kB] Get:2 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 apache2-bin amd64 2.4.52-1ubuntu4.9 [1347 kB] Get:3 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 apache2-data all 2.4.52-1ubuntu4.9 [165 kB] Get:4 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 apache2-utils amd64 2.4.52-1ubuntu4.9 [88.7 kB] Fetched 1698 kB in 0s (31.4 MB/s) (Reading database ... 78982 files and directories currently installed.) Preparing to unpack .../apache2_2.4.52-1ubuntu4.9_amd64.deb ... Unpacking apache2 (2.4.52-1ubuntu4.9) over (2.4.52-1ubuntu4.7) ... Preparing to unpack .../apache2-bin_2.4.52-1ubuntu4.9_amd64.deb ... Unpacking apache2-bin (2.4.52-1ubuntu4.9) over (2.4.52-1ubuntu4.7) ... Preparing to unpack .../apache2-data_2.4.52-1ubuntu4.9_all.deb ... Unpacking apache2-data (2.4.52-1ubuntu4.9) over (2.4.52-1ubuntu4.7) ... Preparing to unpack .../apache2-utils_2.4.52-1ubuntu4.9_amd64.deb ... Unpacking apache2-utils (2.4.52-1ubuntu4.9) over (2.4.52-1ubuntu4.7) ... Setting up apache2-bin (2.4.52-1ubuntu4.9) ... Setting up apache2-data (2.4.52-1ubuntu4.9) ... Setting up apache2-utils (2.4.52-1ubuntu4.9) ... Setting up apache2 (2.4.52-1ubuntu4.9) ... Installing new version of config file /etc/apache2/mods-available/setenvif.conf ... apache-htcacheclean.service is a disabled or a static unit not running, not starting it. Processing triggers for man-db (2.10.2-1) ... Processing triggers for ufw (0.36.1-4ubuntu0.1) ... Scanning processes... Scanning linux images... Running kernel seems to be up-to-date. No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. No VM guests are running outdated hypervisor (qemu) binaries on this host. ~$ apache2 -v Server version: Apache/2.4.52 (Ubuntu) Server built: 2024-04-10T17:45:18 ``` ** after the update the site has the 301 issue ** Affects: apache2 (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/2061740 Title: update to apache2_2.4.52-1ubuntu4.9_amd64 causes website to respond with 301 redirect to itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/2061740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1975557] Re: blank screen does not turn off display backlight
** Reply to message from Daniel van Vugt <1975...@bugs.launchpad.net> on Wed, 25 May 2022 06:15:35 - I get an error running apport-collect. I am beginning to think that the last update to this system went wrong. There are other problems comming up which I did not have before. I have now tried the display with another 22.04 install and that works OK. So I think this problem report should be closed. bob1@Juptier:~$ apport-collect 1975557 ERROR: connecting to Launchpad failed: Unable to find the server at launchpad.net You can reset the credentials by removing the file "/home/bob1/.cache/apport/launchpad.credentials" bob1@Juptier:~$ > The difference between 21.10 and 22.04 might just be that we now default > to Wayland instead of Xorg. So the display subsystems are different. > > Please run this command to gather more information: > > apport-collect 1975557 > > And to save time in future please use the 'ubuntu-bug' command to report > new bugs. > > ** Tags added: jammy > > ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) > > ** Changed in: gnome-shell (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1975557 > > Title: > blank screen does not turn off display backlight > > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > I updated a system from 21.10 to 22.04 and noticed that when the > screen is blanked by no keyboard or mouse activity that the backlight > in the VGA monitor is still on. The "settings->Displays" has "Unknown > Display" which I assume means the system does not know what commands > to send to the monitor to shut it off. I booted a live DVD of 21.10 > and the settings has the VGA display as 'AOC 22" ' which is correct > and the screen blanking works correctly. So it seems that the > definition for the AOC displays have been removed from 22.04. > > This behavior is different on Ubuntu 21.10, the VGA display is blank and the > backlight is off. A minor nit is on 21.10 the "settings->Displays" shows the > VGA display manufacture name, on 22.04 the > VGA display manufacture name is "Unknown Display". > > I have discovered that the settings have the following options > > "settings->Power->Screen Blank" with a time value to be selected and the > following text on the next line "Turns the screen off after a period of > inactivity" > > "settings->Privacy->Screen->Blank Screen Display" with a time value to be > selected and the following text on the next line "Period of inactivity after > which the screen will go blank" > > The two options have different actions but seem to be connected because > changing the time on one changes the time on the other. > > My guess is that the update changed the action for Ubuntu 22.04. I > would like the 21.10 behavior, that is to turn off the VGA display not > just blank the display when selecting the "settings->Power->Screen > Blank" for 22.04. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975557/+subscriptions -- Robert Blair Tell me and I forget. Teach me and I remember. Involve me and I learn. -- Xun Kuang (Confucian philosopher) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975557 Title: blank screen does not turn off display backlight To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975557] [NEW] blank screen does not turn off display backlight
Public bug reported: I updated a system from 21.10 to 22.04 and noticed that when the screen is blanked by no keyboard or mouse activity that the backlight in the VGA monitor is still on. The "settings->Displays" has "Unknown Display" which I assume means the system does not know what commands to send to the monitor to shut it off. I booted a live DVD of 21.10 and the settings has the VGA display as 'AOC 22" ' which is correct and the screen blanking works correctly. So it seems that the definition for the AOC displays have been removed from 22.04. This behavior is different on Ubuntu 21.10, the VGA display is blank and the backlight is off. A minor nit is on 21.10 the "settings->Displays" shows the VGA display manufacture name, on 22.04 the VGA display manufacture name is "Unknown Display". I have discovered that the settings have the following options "settings->Power->Screen Blank" with a time value to be selected and the following text on the next line "Turns the screen off after a period of inactivity" "settings->Privacy->Screen->Blank Screen Display" with a time value to be selected and the following text on the next line "Period of inactivity after which the screen will go blank" The two options have different actions but seem to be connected because changing the time on one changes the time on the other. My guess is that the update changed the action for Ubuntu 22.04. I would like the 21.10 behavior, that is to turn off the VGA display not just blank the display when selecting the "settings->Power->Screen Blank" for 22.04. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975557 Title: blank screen does not turn off display backlight To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1975557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874905] [NEW] package cqrlog-data 2.4.0-3 failed to install/upgrade: trying to overwrite '/usr/share/cqrlog/changelog.html', which is also in package cqrlog 2.4.0-1
Public bug reported: cqrlog fails becauses of mysql no connecing. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: cqrlog-data 2.4.0-3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 24 14:55:55 2020 Dependencies: DpkgTerminalLog: Preparing to unpack .../00-cqrlog-data_2.4.0-3_all.deb ... Unpacking cqrlog-data (2.4.0-3) ... [1mdpkg:[0m error processing archive /tmp/apt-dpkg-install-G6x79y/00-cqrlog-data_2.4.0-3_all.deb (--unpack): trying to overwrite '/usr/share/cqrlog/changelog.html', which is also in package cqrlog 2.4.0-1 ErrorMessage: trying to overwrite '/usr/share/cqrlog/changelog.html', which is also in package cqrlog 2.4.0-1 InstallationDate: Installed on 2020-04-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: cqrlog Title: package cqrlog-data 2.4.0-3 failed to install/upgrade: trying to overwrite '/usr/share/cqrlog/changelog.html', which is also in package cqrlog 2.4.0-1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cqrlog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874905 Title: package cqrlog-data 2.4.0-3 failed to install/upgrade: trying to overwrite '/usr/share/cqrlog/changelog.html', which is also in package cqrlog 2.4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cqrlog/+bug/1874905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824743] Re: Fonts look bad after scaling display in Kubuntu Disco
Also, the fonts do look ok at 1.0 scaling, but I can't really read them that small. They appear to be similarly broken on any factor above 1.0. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824743 Title: Fonts look bad after scaling display in Kubuntu Disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1824743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824743] [NEW] Fonts look bad after scaling display in Kubuntu Disco
Public bug reported: Hi, I'm trying out the kubuntu Disco beta. I have 4k displays, so I went into the KDE System Settings and changed my screen scaling value to 1.4. After doing this, all of the fonts in all of the LibreOffice applications looked really bad, to the point of being nearly unreadable. I eventually removed libreoffice-kde5 and libreoffice-qt5 and confirmed that the fonts were fixed, but that has obvious negative consequences. Installing libreoffice-gtk3 helped, and the fonts still look ok. This doesn't appear to happen in Kubuntu 18.10. Not sure what else to do to help diagnose this but I'm glad to have a look. Nate ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot.png" https://bugs.launchpad.net/bugs/1824743/+attachment/5255795/+files/screenshot.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824743 Title: Fonts look bad after scaling display in Kubuntu Disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1824743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823779] [NEW] package systemd 239-7ubuntu10.12 failed to install/upgrade: package systemd is already installed and configured
Public bug reported: I was updating from the software updater ProblemType: Package DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10.12 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.2 AptdaemonVersion: 1.1.1+bzr982-0ubuntu20 Architecture: amd64 Date: Mon Apr 8 14:01:33 2019 DpkgTerminalLog: dpkg: error processing package systemd (--configure): package systemd is already installed and configured ErrorMessage: package systemd is already installed and configured InstallationDate: Installed on 2019-04-04 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 003: ID 04f2:b5d9 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80X2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-17-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=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.4 SourcePackage: dpkg Title: package systemd 239-7ubuntu10.12 failed to install/upgrade: package systemd is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4QCN48WW(V2.12) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 520S-14IKB dmi.modalias: dmi:bvnLENOVO:bvr4QCN48WW(V2.12):bd11/23/2018:svnLENOVO:pn80X2:pvrLenovoideapad520S-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad520S-14IKB: dmi.product.family: ideapad 520S-14IKB dmi.product.name: 80X2 dmi.product.sku: LENOVO_MT_80X2_BU_idea_FM_ideapad 520S-14IKB dmi.product.version: Lenovo ideapad 520S-14IKB dmi.sys.vendor: LENOVO ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package cosmic 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/1823779 Title: package systemd 239-7ubuntu10.12 failed to install/upgrade: package systemd is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1823779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796499] Re: Keyboard calculator button not working
Is this fix going to be applied in 18.04? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796499 Title: Keyboard calculator button not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1796499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
I installed the packages from -proposed as per the instructions and had two issues: 1. Steam fails to launch with NVIDIA due to a "glXChooseVisual failed" error, which some cursory Googling suggests is due to a lack of 32-bit libraries—perhaps this is expected. 2. After switching from NVIDIA to Intel and logging out, the first attempt to log in again would seem to fail and just return me to the login screen. A second attempt would then succeed and take me to the desktop. This didn't happen when switching in the other direction. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1769376] Re: NMI watchdog: Watchdog detected hard LOCKUP on cpu x
The version that is currently working and has worked in the past is 16.04 LTS. Both 17.10 and 18.04 were non-functional for me. Tried multiple installs, each with the same results. Unfortunately, I can't test anything else on this machine atm as it's my work machine and I need it to be available pretty much constantly. On Mon, May 7, 2018 at 10:08 AM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having this particular problem? > > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.17 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc4 > > > ** Changed in: linux (Ubuntu) >Importance: Undecided => Medium > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1769376 > > Title: > NMI watchdog: Watchdog detected hard LOCKUP on cpu x > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Machine: > > ASUS ROG GL753VE Laptop > > Clean install of Ubuntu 18.04 LTS (I've reinstalled several times and > get same error). > > This is the error: > > NMI watchdog: Watchdog detected hard LOCKUP on cpu x (where x is some > cpu #) > > I am also seeing the following errors at random: > > watchdog: BUG: soft lockup - CPU#X stuck for 23s! [kworker/3:0:29] > watchdog: BUG: soft lockup - CPU#X stuck for 23s! [systemd-udevd:335] > watchdog: BUG: soft lockup - CPU#X stuck for 23s! [systemd-udevd:575] > > > Unfortunately due to the nature of this bug, I cannot gather any logs or > report using the Terminal. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > 1769376/+subscriptions > -- Blair -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769376 Title: NMI watchdog: Watchdog detected hard LOCKUP on cpu x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769376] [NEW] NMI watchdog: Watchdog detected hard LOCKUP on cpu x
Public bug reported: Machine: ASUS ROG GL753VE Laptop Clean install of Ubuntu 18.04 LTS (I've reinstalled several times and get same error). This is the error: NMI watchdog: Watchdog detected hard LOCKUP on cpu x (where x is some cpu #) I am also seeing the following errors at random: watchdog: BUG: soft lockup - CPU#X stuck for 23s! [kworker/3:0:29] watchdog: BUG: soft lockup - CPU#X stuck for 23s! [systemd-udevd:335] watchdog: BUG: soft lockup - CPU#X stuck for 23s! [systemd-udevd:575] Unfortunately due to the nature of this bug, I cannot gather any logs or report using the Terminal. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769376 Title: NMI watchdog: Watchdog detected hard LOCKUP on cpu x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766699] [NEW] QtCreator 3.5.1 has several bugs and should be updated to a newer version
Public bug reported: I was seeing numerous diags for bugs when running QtCreator, and reported one of them to qt.io. https://bugreports.qt.io/browse/QTCREATORBUG-20323 TL;DR: Their take is that the version 3.5.1 that is loaded by Ubuntu is way too old to be maintained (it's from like 2012). Consequently, the onus is on Ubuntu to adopt a newer version (they've released 4.6.0 and are testing up to 4.9.0) for installation with `apt install qtcreator`. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: qtcreator 3.5.1+dfsg-2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 24 12:21:44 2018 InstallationDate: Installed on 2016-04-23 (731 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qtcreator UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtcreator (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/1766699 Title: QtCreator 3.5.1 has several bugs and should be updated to a newer version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtcreator/+bug/1766699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678180] [NEW] Installing Kubuntu-desktop and package kaccounts-providers (not installed) failed to install
*** This bug is a duplicate of bug 1617564 *** https://bugs.launchpad.net/bugs/1617564 Public bug reported: I was installing Kubuntu-desktop when the error occurred. I am running Ubuntu 16.04 LTS ProblemType: Package DistroRelease: Ubuntu 16.04 Package: kaccounts-providers (not installed) ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri Mar 31 10:43:27 2017 DuplicateSignature: package:kaccounts-providers:(not installed) Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/accounts/services/google-im.service', which is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1 ErrorMessage: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 InstallationDate: Installed on 2016-09-03 (209 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: kaccounts-providers Title: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kaccounts-providers (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/1678180 Title: Installing Kubuntu-desktop and package kaccounts-providers (not installed) failed to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kaccounts-providers/+bug/1678180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659922] Re: Firefox 51.0.1 после обновления в Ubuntu 16.04 x32 не отображает содержимое сайтов
Agreed. I have the issue as well and running: sudo aa-complain /etc/apparmor.d/usr.bin.firefox fixes it. ** Description changed: Firefox 51.0.1 после обновления в Ubuntu 16.04 x32 не отображает содержимое сайтов. Т. е. сайты загружаются, но не отображаются. Отображается только стартовая страница. Придурки, чего вы там накомпилировали и слили в майнстрим? Давайте, исправляйте! + + [Firefox 51.0.1 after upgrading to Ubuntu 16.04 x32 does not display the + contents of the sites. Websites are loaded but not displayed. Displays + only the home page.] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659922 Title: Firefox 51.0.1 после обновления в Ubuntu 16.04 x32 не отображает содержимое сайтов To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1659922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656523] [NEW] LUbuntu Installer crashes on Asus TP200SA
Public bug reported: First I tried installing Lightweight Ubuntu on my new Asus Transformer TP200SA (2G RAM, 32G eMMC) with the encrypted disk + LVM option - that failed initially because I had not invoked "sudo swapoff -a" from a terminal, and then because of some other reason that I didn't understand. I then tried just LVM, but that failed. I then tried a vanilla installation, and after I'd confirmed I wanted UEFI rather than BIOS compatibility mode (I was overwriting Windows 10), the installer started copying files, so I had some lunch. When I came back I found that the installer had crashed and the bug reporter got invoked, which brought me to this page. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubiquity 16.10.14 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CasperVersion: 1.379 Date: Sat Jan 14 12:34:31 2017 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/lubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lubuntu ubiquity-16.10.14 yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656523 Title: LUbuntu Installer crashes on Asus TP200SA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1656523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610762] [NEW] ubi-partman crashed 16.04.1 install
Public bug reported: Got this error attempting to apply automatic partitioning during 16.04.1 install. System is running in legacy bios mode with a raid5 intel rapid storage technology array on a gigabyte GA-170N motherboard. Windows 10 is already installed with 3 existing partitions (boot/recovery, C:\ - system, D:\ - data). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.2 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 CasperVersion: 1.376 Date: Mon Aug 8 01:15:11 2016 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= 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 ubiquity-2.21.63.2 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610762 Title: ubi-partman crashed 16.04.1 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1610762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581890] Re: Boot registers protocol family 40, which is not in configs
(In reply to comment #2 above) I do not recall that this was seen immediately after an update. The machine has been running 14.04 (upgraded from 12.04) almost since 14.04 was released. The anomaly was noticed only by chance; I was browsing the logs for other information and simply happened to get curious about that particular line, then discovered just how curious the line was on its own. I can not run alternate configurations or test kernels on this installation without destabilizing the system configuration beyond my risk tolerance. However, what I might be able to do is set up another VM and install another instance of 14.04 and then test it with the Mainline kernel. But I don't know enough about selecting versions to know if I'm getting the 14.04 that should exhibit the problem (is there only one rev of 14.04? if not, which should I start with to best replicate what I have now? to what level of update? Is that determinable from the data I've already uploaded?). Could you take a look and post a link to the proper Ubuntu config that I can use as a baseline in a clean VM, and then I'll see if the bug is there, and if it is, then I'll use the link you have provided to check the mainline kernel also. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581890 Title: Boot registers protocol family 40, which is not in configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581890] Re: Boot registers protocol family 40, which is not in configs
apport information ** Tags added: apport-collected trusty ** Description changed: I noticed this line in the system log after boot: "May 14 14:41:08 ubuntu kernel: [8.677878] NET: Registered protocol family 40" I tried to find out what protocol that was, and eventually determined that the IANA thinks it's the IL protocol, which is deprecated and unusual in any case. Protocol number 40 doesn't appear in the expected config or alias files (for modprobe in /etc or /etc/modprobe.d/). Enabling a dead protocol without being told seems to be a thing an OS shouldn't be doing. More context for the log line is below: ... May 14 14:41:08 ubuntu vmsvc[1607]: [ warning] [GLib-GObject] Attempt to add property ToolsCoreService::tcs-app-ctx after class was initialised May 14 14:41:08 ubuntu vmsvc[1607]: [ warning] [GLib-GObject] Attempt to add property ToolsCoreService::tcs-prop-thread-pool after class was initialised May 14 14:41:08 ubuntu kernel: [8.677878] NET: Registered protocol family 40 May 14 14:48:36 ubuntu dbus[465]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper) May 14 14:48:36 ubuntu dbus[465]: [system] Successfully activated service 'org.freedesktop.UPower' ... + --- + ApportVersion: 2.14.1-0ubuntu3.19 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: blair 2640 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.04 + HibernationDevice: RESUME=UUID=38a747e6-6da8-4ab9-b2c5-d7613992fbfb + InstallationDate: Installed on 2012-05-15 (1464 days ago) + InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) + IwConfig: + eth0 no wireless extensions. + + lono wireless extensions. + Lsusb: + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub + Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + MachineType: VMware, Inc. VMware Virtual Platform + Package: linux (not installed) + ProcFB: 0 svgadrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-86-generic root=UUID=b4002a34-68be-4c40-a549-17edb4a1f7e9 ro quiet splash + ProcVersionSignature: Ubuntu 3.13.0-86.130-generic 3.13.11-ckt39 + RelatedPackageVersions: + linux-restricted-modules-3.13.0-86-generic N/A + linux-backports-modules-3.13.0-86-generic N/A + linux-firmware 1.127.22 + RfKill: + + Tags: trusty + Uname: Linux 3.13.0-86-generic x86_64 + UpgradeStatus: Upgraded to trusty on 2014-04-26 (753 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/20/2014 + dmi.bios.vendor: Phoenix Technologies LTD + dmi.bios.version: 6.00 + dmi.board.name: 440BX Desktop Reference Platform + dmi.board.vendor: Intel Corporation + dmi.board.version: None + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 1 + dmi.chassis.vendor: No Enclosure + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: + dmi.product.name: VMware Virtual Platform + dmi.product.version: None + dmi.sys.vendor: VMware, Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1581890/+attachment/4665866/+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/1581890 Title: Boot registers protocol family 40, which is not in configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581890] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1581890/+attachment/4665867/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581890 Title: Boot registers protocol family 40, which is not in configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581890] Re: Boot registers protocol family 40, which is not in configs
As requested. ** 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/1581890 Title: Boot registers protocol family 40, which is not in configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581890] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1581890/+attachment/4665875/+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/1581890 Title: Boot registers protocol family 40, which is not in configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581890] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1581890/+attachment/4665878/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581890 Title: Boot registers protocol family 40, which is not in configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581890] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1581890/+attachment/4665873/+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/1581890 Title: Boot registers protocol family 40, which is not in configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581890] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1581890/+attachment/4665869/+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/1581890 Title: Boot registers protocol family 40, which is not in configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581890] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1581890/+attachment/4665870/+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/1581890 Title: Boot registers protocol family 40, which is not in configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581890] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1581890/+attachment/4665872/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581890 Title: Boot registers protocol family 40, which is not in configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581890] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1581890/+attachment/4665877/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581890 Title: Boot registers protocol family 40, which is not in configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581890] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1581890/+attachment/4665876/+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/1581890 Title: Boot registers protocol family 40, which is not in configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581890] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1581890/+attachment/4665871/+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/1581890 Title: Boot registers protocol family 40, which is not in configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581890] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1581890/+attachment/4665868/+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/1581890 Title: Boot registers protocol family 40, which is not in configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581890] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1581890/+attachment/4665874/+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/1581890 Title: Boot registers protocol family 40, which is not in configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581890] [NEW] Boot registers protocol family 40, which is not in configs
Public bug reported: I noticed this line in the system log after boot: "May 14 14:41:08 ubuntu kernel: [8.677878] NET: Registered protocol family 40" I tried to find out what protocol that was, and eventually determined that the IANA thinks it's the IL protocol, which is deprecated and unusual in any case. Protocol number 40 doesn't appear in the expected config or alias files (for modprobe in /etc or /etc/modprobe.d/). Enabling a dead protocol without being told seems to be a thing an OS shouldn't be doing. More context for the log line is below: ... May 14 14:41:08 ubuntu vmsvc[1607]: [ warning] [GLib-GObject] Attempt to add property ToolsCoreService::tcs-app-ctx after class was initialised May 14 14:41:08 ubuntu vmsvc[1607]: [ warning] [GLib-GObject] Attempt to add property ToolsCoreService::tcs-prop-thread-pool after class was initialised May 14 14:41:08 ubuntu kernel: [8.677878] NET: Registered protocol family 40 May 14 14:48:36 ubuntu dbus[465]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper) May 14 14:48:36 ubuntu dbus[465]: [system] Successfully activated service 'org.freedesktop.UPower' ... ** Affects: gnome-system-log (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/1581890 Title: Boot registers protocol family 40, which is not in configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-log/+bug/1581890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581888] [NEW] Open command toggles between default paths
Public bug reported: Start gnome-system-log. Click on the gear button and select Open. The Open Log dialog opens, showing contents at default path /var/log. Dismiss that dialog. Again click the gear button and select Open. The same dialog opens, but the path is now ~. Closing and opening the dialog repeatedly toggles between the same two paths. The behavior changes after the dialog is used to browse to a different directory and successfully open a file (but not after simply opening a file in the default directory). Then it remembers the last path as the default between invocations of gnome-system-log, as expected. ** Affects: gnome-system-log (Ubuntu) Importance: Undecided Status: New ** Tags: ui -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581888 Title: Open command toggles between default paths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-log/+bug/1581888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579469] [NEW] package samba 2:4.3.9+dfsg-0ubuntu0.15.10.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: This fails when the system tries to do an automatic update. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: samba 2:4.3.9+dfsg-0ubuntu0.15.10.1 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic i686 ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 Date: Sat May 7 23:33:34 2016 DuplicateSignature: package:samba:2:4.3.9+dfsg-0ubuntu0.15.10.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-01-09 (1214 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) RelatedPackageVersions: nautilus 1:3.14.2-0ubuntu13 gvfs 1.24.2-0ubuntu4 SambaClientRegression: Yes SourcePackage: samba Title: package samba 2:4.3.9+dfsg-0ubuntu0.15.10.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2015-11-05 (185 days ago) ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579469 Title: package samba 2:4.3.9+dfsg-0ubuntu0.15.10.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/samba/+bug/1579469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574883] Re: libvirt not configured with numad support
Hi James, True that static NUMA placement would work (well, it would if this was fixed: https://bugs.launchpad.net/nova/+bug/1517006). But the issue with the static approach is that it requires flavor definitions and imposes stricter scheduling constraints in order to meet the pre-defined flavor NUMA topology and policy. We're doing science computing and hpc on OpenStack (using libvirt/kvm on ubuntu as hypervisor) and have done a bit of performance testing with strict NUMA policy versus numad. We've done some benchmarking of whole- node VM instances (as would be the case with most hpc workloads) and found that for the most part numad does a near enough job to static pinning (i.e., setting the guest up to mirror the host) that we would prefer to just use numad and get more performance without compromising scheduling flexibility. We'd also do this in our general purpose zones/cells where we have all sorts of mixed research workloads. Hope that helps explain it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574883 Title: libvirt not configured with numad support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1574883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574883] [NEW] libvirt not configured with numad support
Public bug reported: numad is now packaged and shipped by Ubuntu. But Ubuntu libvirt packages (which is presumably where most end-user/admins/deployers would be interested in numad support) are not configured with numad support... curl -s https://launchpadlibrarian.net/253913675/buildlog_ubuntu-xenial-amd64.libvirt_1.3.1-1ubuntu10_BUILDING.txt.gz | gunzip | nl | grep numad 3249 checking for numad... no 3454 configure: numad: no ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: numad xenial ** Summary changed: - not configured with numad support + libvirt not configured with numad support -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574883 Title: libvirt not configured with numad support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1574883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 663726] Re: pynotify.set_timeout() ignores timeout
If you set it lower than 10 seconds it still remains onscreen for 10 seconds. Except if you set it to 0 it gives you a dialog box that remains onscreen until you dismiss it instead of the momentary notification. (Currently on xenial.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/663726 Title: pynotify.set_timeout() ignores timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-python/+bug/663726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 663726] Re: pynotify.set_timeout() ignores timeout
Setting it lower than 10 seconds doesn't shorten the timeout either. But if you set it to 0 you get the info in a dialog box that persists until you dismiss it instead of a bubble that goes away in 10 seconds. (Currently running xenial.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/663726 Title: pynotify.set_timeout() ignores timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-python/+bug/663726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551430] [NEW] fix this
Public bug reported: installer fails at the very end, i have tried 3 diff computers ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubiquity 2.9.24 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6 Uname: Linux 3.2.0-17-generic-pae i686 ApportVersion: 1.94-0ubuntu1 Architecture: i386 CasperVersion: 1.305 Date: Mon Feb 29 15:30:31 2016 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301) ProcEnviron: LANGUAGE= TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise ubiquity-2.9.24 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551430 Title: fix this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1551430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551391] [NEW] unfinished install, graphics messed up
Public bug reported: install will not finish, graphics are chopped and screwed ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubiquity 2.9.24 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6 Uname: Linux 3.2.0-17-generic-pae i686 ApportVersion: 1.94-0ubuntu1 Architecture: i386 CasperVersion: 1.305 Date: Mon Feb 29 12:42:51 2016 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301) ProcEnviron: LANGUAGE= TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise ubiquity-2.9.24 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551391 Title: unfinished install, graphics messed up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1551391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1361951] Re: Ubiquity freezes while reformatting occupied partition
I was having the same issue with 15.10 install media but resolved it by booting into the live session, opening a terminal, using fdisk to create a new GPT table, making one giant partition, formatting it, then proceeding with install. Install went off without a hitch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1361951 Title: Ubiquity freezes while reformatting occupied partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-ext3/+bug/1361951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1485284] [NEW] package setserial 2.17-48ubuntu0.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
Public bug reported: i dont know exactly ProblemType: Package DistroRelease: Ubuntu 15.04 Package: setserial 2.17-48ubuntu0.1 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic i686 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: i386 Date: Sun Aug 16 00:07:03 2015 DuplicateSignature: package:setserial:2.17-48ubuntu0.1:sub-processo script post-installation instalado retornou estado de saída de erro 1 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 SourcePackage: setserial Title: package setserial 2.17-48ubuntu0.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.init.d.etc.setserial: [deleted] modified.conffile..etc.init.d.setserial: [deleted] ** Affects: setserial (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package dist-upgrade i386 need-duplicate-check vivid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to setserial in Ubuntu. https://bugs.launchpad.net/bugs/1485284 Title: package setserial 2.17-48ubuntu0.1 failed to install/upgrade: sub- processo script post-installation instalado retornou estado de saída de erro 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/setserial/+bug/1485284/+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 1485284] [NEW] package setserial 2.17-48ubuntu0.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
Public bug reported: i dont know exactly ProblemType: Package DistroRelease: Ubuntu 15.04 Package: setserial 2.17-48ubuntu0.1 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic i686 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: i386 Date: Sun Aug 16 00:07:03 2015 DuplicateSignature: package:setserial:2.17-48ubuntu0.1:sub-processo script post-installation instalado retornou estado de saída de erro 1 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 SourcePackage: setserial Title: package setserial 2.17-48ubuntu0.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.init.d.etc.setserial: [deleted] modified.conffile..etc.init.d.setserial: [deleted] ** Affects: setserial (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package dist-upgrade i386 need-duplicate-check vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1485284 Title: package setserial 2.17-48ubuntu0.1 failed to install/upgrade: sub- processo script post-installation instalado retornou estado de saída de erro 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/setserial/+bug/1485284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1459817] [NEW] Ubuntu 15.04 slow boot related to networking probably WIFI
Public bug reported: Ubuntu 15.04 boots slowly, this did not happen on version 14.10. The problem appears to be in the networking code, possibly WIFI. I have attached a bootchart file. ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: bootchart https://bugs.launchpad.net/bugs/1459817/+attachment/4406287/+files/plot4.svg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1459817 Title: Ubuntu 15.04 slow boot related to networking probably WIFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1459817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1339202] Re: vmware-view-client does not get sound when connecting to a windows host
This issue affected me but installing the three packages above fixes the problem. I attempted libgstreamer by itself and it did not resolve the problem. I installed the last two at the same time but suspect it to be the -pulseaudio package that fixes it as I have seen some other documentation that the client defaults to audio output through pulse. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1339202 Title: vmware-view-client does not get sound when connecting to a windows host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vmware-view-client/+bug/1339202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1379340] Re: qemu-kvm guest panic for AMD smp trusty guests
Not keen on providing apport info as this is a production system with multiple tenants and we have no agreement with Canonical. The info here and verification from others indicates this is a simple bug to reproduce and not specific to our systems. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1379340 Title: qemu-kvm guest panic for AMD smp trusty guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1379340/+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 1379340] Re: qemu-kvm guest panic for AMD smp trusty guests
Here's an example of an affected qemu command, as already pointed out the relevant parts are the -cpu host and -smp n where n1. qemu-system-x86_64 -enable-kvm -name instance-000173d4 -S -machine pc-1.0,accel=kvm,usb=off -cpu host -m 16384 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid e3ec1854-0b89-4384-*** -smbios type=1,manufacturer=OpenStack Foundation,product=OpenStack Nova,version=1-2013.2.2-a101-g1a048c5-1,serial=,uuid=e3ec1854-0b89-4384-*** -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-000173d4.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/nova/instances/e3ec1854-0b89-4384-9771-88c26764eef9/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/var/lib/nova/instances/e3ec1854 -0b89-4384-9771-88c26764eef9/disk.local,if=none,id=drive-virtio-disk1,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,id=virtio-disk1 -drive file=rbd:nova/volume-439f230a-12fa-4538-ab26-01c3f6617ec7:id=nova:key=***==:auth_supported=cephx\;none:mon_host=118.138***,if=none,id=drive-virtio-disk2,format=raw,serial=***,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk2,id=virtio-disk2 -netdev tap,fd=30,id=hostnet0,vhost=on,vhostfd=31 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:***,bus=pci.0,addr=0x3 -chardev file,id=charserial0,path=/var/lib/nova/instances/e3ec1854-0b89-4384-9771-88c26764eef9/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:1 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x 6 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1379340 Title: qemu-kvm guest panic for AMD smp trusty guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1379340/+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 1379340] Re: qemu-kvm guest panic for AMD smp trusty guests
Not keen on providing apport info as this is a production system with multiple tenants and we have no agreement with Canonical. The info here and verification from others indicates this is a simple bug to reproduce and not specific to our systems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1379340 Title: qemu-kvm guest panic for AMD smp trusty guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1379340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1379340] Re: qemu-kvm guest panic for AMD smp trusty guests
Here's an example of an affected qemu command, as already pointed out the relevant parts are the -cpu host and -smp n where n1. qemu-system-x86_64 -enable-kvm -name instance-000173d4 -S -machine pc-1.0,accel=kvm,usb=off -cpu host -m 16384 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid e3ec1854-0b89-4384-*** -smbios type=1,manufacturer=OpenStack Foundation,product=OpenStack Nova,version=1-2013.2.2-a101-g1a048c5-1,serial=,uuid=e3ec1854-0b89-4384-*** -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-000173d4.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/nova/instances/e3ec1854-0b89-4384-9771-88c26764eef9/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/var/lib/nova/instances/e3ec1854 -0b89-4384-9771-88c26764eef9/disk.local,if=none,id=drive-virtio-disk1,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,id=virtio-disk1 -drive file=rbd:nova/volume-439f230a-12fa-4538-ab26-01c3f6617ec7:id=nova:key=***==:auth_supported=cephx\;none:mon_host=118.138***,if=none,id=drive-virtio-disk2,format=raw,serial=***,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk2,id=virtio-disk2 -netdev tap,fd=30,id=hostnet0,vhost=on,vhostfd=31 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:***,bus=pci.0,addr=0x3 -chardev file,id=charserial0,path=/var/lib/nova/instances/e3ec1854-0b89-4384-9771-88c26764eef9/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:1 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x 6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1379340 Title: qemu-kvm guest panic for AMD smp trusty guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1379340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1387413] [NEW] Black screen after wakeup from suspending by closing the laptop lid
Public bug reported: This may be a regression of this bug: https://bugs.launchpad.net/ubuntu/+source/xubuntu-default- settings/+bug/1303736 I upgraded from 14.04 (where this also did not work) to 14.10. This is on a Thinkpad x220. When I close the lid, the laptop suspends, and when I wake it, light- locker is running. After unlocking, the screen power is off. Running xrandr --auto corrects the issue. I normally have HandleLidSwitch=ignore set in /etc/systemd/logind.conf, because otherwise, the xfce4-power-manager setting to only suspend on lid-close when on battery power is ignored. For debugging purposes, I tried changing the /xfce4-power-manager /logind-handle-lid-switch xfconf setting as well as the HandleLidSwitch=ignore setting in logind.conf. These are the results: logind.conf: HandleLidSwitch=ignore xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-lid-switch -s false lid-close: light-locker runs, screen power off after unlock lock-screen-command: light-locker runs, screen power on after unlock xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-lid-switch -s true lid-close: light-locker does not run lock-screen-command: light-locker runs, screen power on after unlock default logind.conf: xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-lid-switch -s false lid-close: suspend, light-locker runs, screen power off after unlock lock-screen-command: light-locker runs, screen power on after unlock xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-lid-switch -s true lid-close: suspend, light-locker does not run lock-screen-command: light-locker runs, screen power on after unlock ** Affects: light-locker (Ubuntu) Importance: Undecided Status: New ** Affects: xubuntu-default-settings (Ubuntu) Importance: Undecided Status: New ** Also affects: light-locker (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/1387413 Title: Black screen after wakeup from suspending by closing the laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1387413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382455] [NEW] virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build
Public bug reported: Occurred while updating through Update Manager... While Applying Changes.. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6 ProcVersionSignature: Ubuntu 3.13.0-36.63~precise1-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.7 Architecture: amd64 DKMSKernelVersion: 3.13.0-38-generic Date: Fri Oct 17 05:13:18 2014 InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) MarkForUpload: True PackageArchitecture: all PackageVersion: 4.1.12-dfsg-2ubuntu0.6 SourcePackage: virtualbox Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) VirtualBox.ModInfo: ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382455 Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1382455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1379340] [NEW] qemu-kvm guest panic for smp trusty guests
Public bug reported: Just upgraded OpenStack compute hosts in our public cloud (using qemu- kvm via libvirt) from Precise to Trusty (14.04.1), now on kernel 3.13.0-36-generic with qemu-kvm 2.0.0+dfsg-2ubuntu1.5. Following the upgrade, whenever we try to start an smp/multicore Trusty guest (existing or new), we run into this panic [1] inside the guest just towards the end of boot. This happens consistently for smp guests using the Trusty kernel (i.e., it also affects earlier Ubuntus using the HWE kernel from Trusty but not their native versions). I didn't have any other distro images to hand with 3.13.x kernels, but none of the others I tested were affected (in the 3.2 - 3.16 kernel range). There are scarce similar reports out there, but the one we did find pointed to a CPU feature as the trigger. We were running these hosts with libvirt cpu mode set to host-passthrough (so qemu starts with -cpu host), on AMD 6200 6300 Opteron hardware. Switching the guest domains to use cpu mode host-model instead works around the issue and is perfectly acceptable for most of our users. We have various other Intel compute hosts and they don't seem to be affected. (1) [ 11.256924] divide error: [#1] SMP [ 11.258133] Modules linked in: kvm_amd kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw lp parport psmouse floppy [ 11.260228] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-36-generic #63-Ubuntu [ 11.260228] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Bochs 01/01/2011 [ 11.260228] task: 81c15480 ti: 81c0 task.ti: 81c0 [ 11.260228] RIP: 0010:[8104ed58] [8104ed58] kvm_unlock_kick+0xa8/0x100 [ 11.260228] RSP: 0018:88023fc03c98 EFLAGS: 00010046 [ 11.260228] RAX: 0005 RBX: RCX: 0001 [ 11.260228] RDX: 81eaf408 RSI: RDI: [ 11.260228] RBP: 88023fc03cb8 R08: 81eaf400 R09: [ 11.260228] R10: 880037612cc0 R11: ea0002eb0a00 R12: 8800374a33c0 [ 11.260228] R13: 0020 R14: 0001 R15: 0286 [ 11.260228] FS: 7f1e8b538740() GS:88023fc0() knlGS: [ 11.260228] CS: 0010 DS: ES: CR0: 8005003b [ 11.260228] CR2: 7f1e8ae09d50 CR3: 01c0e000 CR4: 000406f0 [ 11.260228] Stack: [ 11.260228] 0286 0001 0001 00c3 [ 11.260228] 88023fc03cc8 81717ed6 88023fc03ce0 8172641a [ 11.260228] 8800374a33c0 88023fc03d18 810aaeb0 88023295e000 [ 11.260228] Call Trace: [ 11.260228] IRQ [ 11.260228] [81717ed6] __ticket_unlock_slowpath+0x24/0x34 [ 11.260228] [8172641a] _raw_spin_unlock_irqrestore+0x3a/0x40 [ 11.260228] [810aaeb0] __wake_up_sync_key+0x50/0x60 [ 11.260228] [8160ca5a] sock_def_readable+0x3a/0x70 [ 11.260228] [816fda0a] packet_rcv+0x2fa/0x430 [ 11.260228] [816228b0] __netif_receive_skb_core+0x360/0x840 [ 11.260228] [81622da8] __netif_receive_skb+0x18/0x60 [ 11.260228] [81622e13] netif_receive_skb+0x23/0x90 [ 11.260228] [815288d4] virtnet_poll+0x4d4/0x850 [ 11.260228] [81623192] net_rx_action+0x152/0x250 [ 11.260228] [8106cbac] __do_softirq+0xec/0x2c0 [ 11.260228] [8106d0f5] irq_exit+0x105/0x110 [ 11.260228] [817312d6] do_IRQ+0x56/0xc0 [ 11.260228] [81726a6d] common_interrupt+0x6d/0x6d [ 11.260228] EOI [ 11.260228] [8104f596] ? native_safe_halt+0x6/0x10 [ 11.260228] [8101c62f] default_idle+0x1f/0xc0 [ 11.260228] [8101cef6] arch_cpu_idle+0x26/0x30 [ 11.260228] [810bed95] cpu_startup_entry+0xc5/0x290 [ 11.260228] [8170ca77] rest_init+0x77/0x80 [ 11.260228] [81d35f6b] start_kernel+0x433/0x43e [ 11.260228] [81d35941] ? repair_env_string+0x5c/0x5c [ 11.260228] [81d35120] ? early_idt_handlers+0x120/0x120 [ 11.260228] [81d355ee] x86_64_start_reservations+0x2a/0x2c [ 11.260228] [81d35733] x86_64_start_kernel+0x143/0x152 [ 11.260228] Code: 66 44 39 e8 75 bd 0f b6 35 f6 06 e6 00 40 84 f6 75 2a 83 05 06 07 e6 00 01 48 c7 c0 6a b0 00 00 31 db 0f b7 0c 01 b8 05 00 00 00 0f 01 c1 0f 1f 44 00 00 5b 41 5c 41 5d 41 5e 5d c3 89 f0 31 c9 [ 11.260228] RIP [8104ed58] kvm_unlock_kick+0xa8/0x100 [ 11.260228] RSP 88023fc03c98 [ 11.260228] ---[ end trace f1c26ff24745b331 ]--- [ 11.260228] Kernel panic - not syncing: Fatal exception in interrupt [ 11.260228] Shutting down cpus with NMI ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1379340 Title: qemu-kvm
[Bug 1379340] [NEW] qemu-kvm guest panic for smp trusty guests
Public bug reported: Just upgraded OpenStack compute hosts in our public cloud (using qemu- kvm via libvirt) from Precise to Trusty (14.04.1), now on kernel 3.13.0-36-generic with qemu-kvm 2.0.0+dfsg-2ubuntu1.5. Following the upgrade, whenever we try to start an smp/multicore Trusty guest (existing or new), we run into this panic [1] inside the guest just towards the end of boot. This happens consistently for smp guests using the Trusty kernel (i.e., it also affects earlier Ubuntus using the HWE kernel from Trusty but not their native versions). I didn't have any other distro images to hand with 3.13.x kernels, but none of the others I tested were affected (in the 3.2 - 3.16 kernel range). There are scarce similar reports out there, but the one we did find pointed to a CPU feature as the trigger. We were running these hosts with libvirt cpu mode set to host-passthrough (so qemu starts with -cpu host), on AMD 6200 6300 Opteron hardware. Switching the guest domains to use cpu mode host-model instead works around the issue and is perfectly acceptable for most of our users. We have various other Intel compute hosts and they don't seem to be affected. (1) [ 11.256924] divide error: [#1] SMP [ 11.258133] Modules linked in: kvm_amd kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw lp parport psmouse floppy [ 11.260228] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-36-generic #63-Ubuntu [ 11.260228] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Bochs 01/01/2011 [ 11.260228] task: 81c15480 ti: 81c0 task.ti: 81c0 [ 11.260228] RIP: 0010:[8104ed58] [8104ed58] kvm_unlock_kick+0xa8/0x100 [ 11.260228] RSP: 0018:88023fc03c98 EFLAGS: 00010046 [ 11.260228] RAX: 0005 RBX: RCX: 0001 [ 11.260228] RDX: 81eaf408 RSI: RDI: [ 11.260228] RBP: 88023fc03cb8 R08: 81eaf400 R09: [ 11.260228] R10: 880037612cc0 R11: ea0002eb0a00 R12: 8800374a33c0 [ 11.260228] R13: 0020 R14: 0001 R15: 0286 [ 11.260228] FS: 7f1e8b538740() GS:88023fc0() knlGS: [ 11.260228] CS: 0010 DS: ES: CR0: 8005003b [ 11.260228] CR2: 7f1e8ae09d50 CR3: 01c0e000 CR4: 000406f0 [ 11.260228] Stack: [ 11.260228] 0286 0001 0001 00c3 [ 11.260228] 88023fc03cc8 81717ed6 88023fc03ce0 8172641a [ 11.260228] 8800374a33c0 88023fc03d18 810aaeb0 88023295e000 [ 11.260228] Call Trace: [ 11.260228] IRQ [ 11.260228] [81717ed6] __ticket_unlock_slowpath+0x24/0x34 [ 11.260228] [8172641a] _raw_spin_unlock_irqrestore+0x3a/0x40 [ 11.260228] [810aaeb0] __wake_up_sync_key+0x50/0x60 [ 11.260228] [8160ca5a] sock_def_readable+0x3a/0x70 [ 11.260228] [816fda0a] packet_rcv+0x2fa/0x430 [ 11.260228] [816228b0] __netif_receive_skb_core+0x360/0x840 [ 11.260228] [81622da8] __netif_receive_skb+0x18/0x60 [ 11.260228] [81622e13] netif_receive_skb+0x23/0x90 [ 11.260228] [815288d4] virtnet_poll+0x4d4/0x850 [ 11.260228] [81623192] net_rx_action+0x152/0x250 [ 11.260228] [8106cbac] __do_softirq+0xec/0x2c0 [ 11.260228] [8106d0f5] irq_exit+0x105/0x110 [ 11.260228] [817312d6] do_IRQ+0x56/0xc0 [ 11.260228] [81726a6d] common_interrupt+0x6d/0x6d [ 11.260228] EOI [ 11.260228] [8104f596] ? native_safe_halt+0x6/0x10 [ 11.260228] [8101c62f] default_idle+0x1f/0xc0 [ 11.260228] [8101cef6] arch_cpu_idle+0x26/0x30 [ 11.260228] [810bed95] cpu_startup_entry+0xc5/0x290 [ 11.260228] [8170ca77] rest_init+0x77/0x80 [ 11.260228] [81d35f6b] start_kernel+0x433/0x43e [ 11.260228] [81d35941] ? repair_env_string+0x5c/0x5c [ 11.260228] [81d35120] ? early_idt_handlers+0x120/0x120 [ 11.260228] [81d355ee] x86_64_start_reservations+0x2a/0x2c [ 11.260228] [81d35733] x86_64_start_kernel+0x143/0x152 [ 11.260228] Code: 66 44 39 e8 75 bd 0f b6 35 f6 06 e6 00 40 84 f6 75 2a 83 05 06 07 e6 00 01 48 c7 c0 6a b0 00 00 31 db 0f b7 0c 01 b8 05 00 00 00 0f 01 c1 0f 1f 44 00 00 5b 41 5c 41 5d 41 5e 5d c3 89 f0 31 c9 [ 11.260228] RIP [8104ed58] kvm_unlock_kick+0xa8/0x100 [ 11.260228] RSP 88023fc03c98 [ 11.260228] ---[ end trace f1c26ff24745b331 ]--- [ 11.260228] Kernel panic - not syncing: Fatal exception in interrupt [ 11.260228] Shutting down cpus with NMI ** Affects: qemu-kvm (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/1379340 Title: qemu-kvm guest panic for smp
[Bug 1375018] [NEW] package virtualbox 4.3.14-dfsg-1build1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Occurred while upgrading 14.04 to 14.10 using update-manager -d ProblemType: Package DistroRelease: Ubuntu 14.10 Package: virtualbox 4.3.14-dfsg-1build1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Sun Sep 28 15:11:35 2014 DuplicateSignature: package:virtualbox:4.3.14-dfsg-1build1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-04-26 (884 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) SourcePackage: virtualbox Title: package virtualbox 4.3.14-dfsg-1build1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2014-09-28 (0 days ago) VirtualBox.ModInfo: ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade need-duplicate-check utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1375018 Title: package virtualbox 4.3.14-dfsg-1build1 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/virtualbox/+bug/1375018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839588] Re: Python 2.7 unable to find it's header files in virtualenv
This is a problem in Precise with projects that have a setup_requires.
root@bare-precise-hpcloud-b1-1:~# virtualenv /usr/local/zuul-env
New python executable in /usr/local/zuul-env/bin/python
Installing setuptools, pip...done.
root@bare-precise-hpcloud-b1-1:~# /usr/local/zuul-env/bin/pip install /tmp/zuul
local-log 21
/usr/local/zuul-env/local/lib/python2.7/site-packages/pip/pep425tags.py:62:
RuntimeWarning: invalid Python installation: unable to open
/usr/zuul-env/lib/python2.7/config/Makefile (No such file or directory)
warnings.warn({0}.format(e), RuntimeWarning)
Unpacking /tmp/zuul
Running setup.py (path:/tmp/pip-cLt2Eg-build/setup.py) egg_info for package
from file:///tmp/zuul
Traceback (most recent call last):
File string, line 17, in module
File /tmp/pip-cLt2Eg-build/setup.py, line 22, in module
pbr=True)
File /usr/lib/python2.7/distutils/core.py, line 112, in setup
_setup_distribution = dist = klass(attrs)
File
/usr/local/zuul-env/local/lib/python2.7/site-packages/setuptools/dist.py,
line 260, in __init__
self.fetch_build_eggs(attrs.pop('setup_requires'))
File
/usr/local/zuul-env/local/lib/python2.7/site-packages/setuptools/dist.py,
line 285, in fetch_build_eggs
replace_conflicting=True
File
/usr/local/zuul-env/local/lib/python2.7/site-packages/pkg_resources.py, line
631, in resolve
dist = best[req.key] = env.best_match(req, ws, installer)
File
/usr/local/zuul-env/local/lib/python2.7/site-packages/pkg_resources.py, line
871, in best_match
return self.obtain(req, installer)
File
/usr/local/zuul-env/local/lib/python2.7/site-packages/pkg_resources.py, line
883, in obtain
return installer(requirement)
File
/usr/local/zuul-env/local/lib/python2.7/site-packages/setuptools/dist.py,
line 333, in fetch_build_egg
cmd.ensure_finalized()
File /usr/lib/python2.7/distutils/cmd.py, line 109, in ensure_finalized
self.finalize_options()
File
/usr/local/zuul-env/local/lib/python2.7/site-packages/setuptools/command/easy_install.py,
line 212, in finalize_options
prefix, exec_prefix = get_config_vars('prefix', 'exec_prefix')
File /usr/lib/python2.7/sysconfig.py, line 476, in get_config_vars
_init_posix(_CONFIG_VARS)
File /usr/lib/python2.7/sysconfig.py, line 344, in _init_posix
raise IOError(msg)
IOError: invalid Python installation: unable to open
/usr/zuul-env/lib/python2.7/config/Makefile (No such file or directory)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839588
Title:
Python 2.7 unable to find it's header files in virtualenv
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/839588/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1161423] Re: Removing a webapp package doesn't remove its shortcut from the dash
Corresponding entries in indicator menus also remain after webapps are uninstalled. For example, after uninstalling unity-webapps- facebookmessenger, a Facebook Messenger entry (with a broken icon) remains in the messaging menu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1161423 Title: Removing a webapp package doesn't remove its shortcut from the dash To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1161423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 988513] Re: unbound defaults break DNS resolution when upstream DNS lacks DNSSEC support
I agree with the statement in the bug report that the default should be safer. However, you can work around the problem in config management by installing the defaults file before installing the package. In our Puppet config we have the unbound package require the defaults file: https://review.openstack.org/#/c/80092/13/modules/unbound/manifests/init.pp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/988513 Title: unbound defaults break DNS resolution when upstream DNS lacks DNSSEC support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/988513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262641] Re: virsh save and virsh managedsave failed with cpu mode = host-passthrough
Serge, sorry if I've missed an obvious answer to this... but, where did you push the updated libvirt? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262641 Title: virsh save and virsh managedsave failed with cpu mode = host- passthrough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1262641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262641] Re: virsh save and virsh managedsave failed with cpu mode = host-passthrough
Oh I see: https://launchpad.net/ubuntu/+source/libvirt/1.2.1-0ubuntu4 We really need a package compatible with Precise to fix this. We may be able to test the fix if we can cherry-pick the trusty version of libvirt without conflict, however we'll still require a backport to fix this in production. Will perhaps have to build our own package if a Precise backport is unavailable... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262641 Title: virsh save and virsh managedsave failed with cpu mode = host- passthrough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1262641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262641] Re: virsh save and virsh managedsave failed with cpu mode = host-passthrough
I am now thoroughly confused... so, we should try Vlad's patch and ignore Serge's updated package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262641 Title: virsh save and virsh managedsave failed with cpu mode = host- passthrough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1262641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 812907] Re: Unallocated free space after creating parititons
This looks the same as the problem I have. I had another OS installed on the disk before I installed Ubuntu using the 12.10 live CD. There was a small primary partition, the rest of the disk was an extended partition. There were two partitions at the front of the extended space so I installed Ubuntu at the end of the extended space. It seemed that everything was normal (for a few months) until I tried to change the swap partition size. When I started gparted it listed all of the disk as free space. The last time any changes were made to the partition tables was the Ubuntu install. As I see the problem the install changed the end of the extended partition to an incorrect value. During the install I used whatever partitioning program the install uses. The first partition defined was /home then swap then root, all at the end of the free space. The following is the output of fdisk. Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0xdf5ee111 Device Boot Start End Blocks Id System /dev/sda1 * 63 160648001a OS/2 Boot Manager Partition 1 does not start on physical sector boundary. /dev/sda4 16065 703309823 351646879+ 5 Extended Partition 4 does not start on physical sector boundary. /dev/sda5 1612810265534 5124703+ 7 HPFS/NTFS/exFAT /dev/sda6102655983074840910241406b W95 FAT32 Partition 6 does not start on physical sector boundary. /dev/sda7 781461504 97677107197654784 83 Linux /dev/sda8 703324160 78144921539062528 82 Linux swap / Solaris /dev/sda9 625184768 70330982339062528 83 Linux The Ubuntu partitions are listed backwards. Notice that the end of sda4 is the same as sda9, this is wrong. Why would any program change the end of the extended partition end unless you were purposely changing the size of the extended partition? I changed the end of sda4 to 976773166 which I think is correct (if not what should it be?) and now gparted can display all the partitions on the disk and I could change the size of the swap partition. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/812907 Title: Unallocated free space after creating parititons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/812907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1196795] Re: soft lockup - CPU#0 stuck for 22s! [inotifywait:21818]
I've been running CrashPlan since January 2012 and given that I've been on raring April 12, 2013 and this bug hit on July 1st, it appears that moving to the latest upstream kernel wouldn't indicate if its been fixed there or not unless I run it for many months, given it took 1.5 months for it to crop up one time. This is also a production box, running public email and web servers. So I'm inclined not to test the latest kernel, unless you think it's going to be pretty risk free and worth the effort. Let me know your thoughts. Blair -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1196795 Title: soft lockup - CPU#0 stuck for 22s! [inotifywait:21818] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1196795] [NEW] soft lockup - CPU#0 stuck for 22s! [inotifywait:21818]
] system_call_fastpath+0x1a/0x1f Jul 1 21:36:47 orca4 kernel: [1513127.162768] Code: 24 10 49 8d 44 24 10 4c 89 e3 48 83 ea 10 49 39 c7 74 2a 49 89 d4 44 85 73 54 74 e1 f0 ff 43 04 48 89 df 4c 89 ee e8 a2 fa ff ff 48 89 df e8 da f8 ff ff eb c8 0f 1f 84 00 00 00 00 00 48 8b 7d ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-25-generic 3.8.0-25.37 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: blair 29553 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Jul 1 21:43:05 2013 HibernationDevice: RESUME=UUID=d15b6c41-e610-4f42-987e-9d99bd6e8e07 InstallationDate: Installed on 2012-01-06 (542 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64+mac (20111011) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-25-generic root=/dev/mapper/vg0-root ro quiet splash mtrr_gran_size=8M mtrr_chunk_size=512M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-25-generic N/A linux-backports-modules-3.8.0-25-generic N/A linux-firmware1.106 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to raring on 2013-04-13 (80 days ago) dmi.bios.date: 11/05/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: SWQ6710H.86A.0066.2012.1105.1504 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DQ67SW dmi.board.vendor: Intel Corporation dmi.board.version: AAG12527-310 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrSWQ6710H.86A.0066.2012.1105.1504:bd11/05/2012:svn:pn:pvr:rvnIntelCorporation:rnDQ67SW:rvrAAG12527-310:cvn:ct3:cvr: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1196795 Title: soft lockup - CPU#0 stuck for 22s! [inotifywait:21818] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1196795] Re: soft lockup - CPU#0 stuck for 22s! [inotifywait:21818]
I also increase a few limits for CrashPlan: $ cat /etc/sysctl.d/99-crashplan.conf fs.inotify.max_queued_events=131072 fs.inotify.max_user_instances=512 fs.inotify.max_user_watches=2097152 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1196795 Title: soft lockup - CPU#0 stuck for 22s! [inotifywait:21818] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1171838] Re: Last nights isc-dhcp-server update fails to start
I have had this issue off and on for a couple of weeks. After much tearing of hair and gnashing of teeth I believe I fixed it. In the upstart configuration for isc-dhcp-server there is no stanza of the form: /lib/init/apparmor-profile-load usr.sbin.dhcpd I don't know about systems running NM but if you have a dhcp server running likely you don't want NM taking your connections up and down (I remob\ved NM from this system and statically configure the network) but the apparmor profile likely needs to be there in cases where the network is statically configured. The apparmor configuration likely is loaded too late on these systems and this causes much grief. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1171838 Title: Last nights isc-dhcp-server update fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1171838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1107686] Re: dhcpd: Open a socket for LPF: Permission denied
This issue is not resolved. I too have the problem above. There are a couple of issues related. I see the same behavior as Michael. The system can run fine but a reboot seems to cause this to crop up. I notice that if you do an aa-complain you can coax the server to come back but there is a funny timing problem that you need to wait a considerable time before the last start attempt or it will fail to start even then. One possible factor is that this (and maybe many other) system is used as a dhcp server and my desktop when logged in. It has a fixed address and I have removed network manager because I don't want NM to fuss with the networking, it should remain on and up always. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1107686 Title: dhcpd: Open a socket for LPF: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1107686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1006369] Re: Flash player doesn't disable the screensaver / power management
** Also affects: hundredpapercuts 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/1006369 Title: Flash player doesn't disable the screensaver / power management To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1006369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1171056] [NEW] 2.2-3+nmu1 upgrade fails on conflict with libwagon-java
Public bug reported: Upgrading to 2.2-3+nmu1 failed with the following output: # apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: libwagon2-java 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/1,052 kB of archives. After this operation, 1,024 B of additional disk space will be used. Do you want to continue [Y/n]? Reading changelogs... Done Get:1 Changelog for libwagon2-java (http://changelogs.ubuntu.com/changelogs/pool/universe/w/wagon2/wagon2_2.2-3+nmu1/changelog) [1,068 B] wagon2 (2.2-3+nmu1) unstable; urgency=high * Non-maintainer upload by the Security Team. * Fix cve-2013-0253: doesn't check SSL certificates by default (closes: #701991). -- Michael Gilbert mgilb...@debian.org Fri, 22 Mar 2013 01:19:26 + apt-listchanges: Mailing root: apt-listchanges: changelogs for orca4.orcaware.com (Reading database ... 383224 files and directories currently installed.) Preparing to replace libwagon2-java 2.2-3 (using .../libwagon2-java_2.2-3+nmu1_all.deb) ... Unpacking replacement libwagon2-java ... dpkg: error processing /var/cache/apt/archives/libwagon2-java_2.2-3+nmu1_all.deb (--unpack): trying to overwrite '/usr/share/java/wagon-tck-http.jar', which is also in package libwagon-java 1.0.0-2ubuntu2 No apport report written because MaxReports is reached already dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libwagon2-java_2.2-3+nmu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libwagon2-java 2.2-3 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat Apr 20 20:13:54 2013 InstallationDate: Installed on 2012-01-06 (470 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64+mac (20111011) MarkForUpload: True PackageArchitecture: all ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set SourcePackage: wagon2 UpgradeStatus: Upgraded to raring on 2013-04-13 (7 days ago) ** Affects: wagon2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1171056 Title: 2.2-3+nmu1 upgrade fails on conflict with libwagon-java To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wagon2/+bug/1171056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1168757] [NEW] nova-compute missing dependency on nova-conductor
Public bug reported: I did an upgrade from quantal to raring today which upgraded OpenStack to Grizzly and saw these messages in /var/log/nova/nova-compute.log: 2013-04-13 12:42:37.104 WARNING nova.conductor.api [req-eec3e73a-3722-47a5-9a26-b831aa06e324 None None] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor? 2013-04-13 12:42:47.122 WARNING nova.conductor.api [req-eec3e73a-3722-47a5-9a26-b831aa06e324 None None] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor? 2013-04-13 12:42:57.139 WARNING nova.conductor.api [req-eec3e73a-3722-47a5-9a26-b831aa06e324 None None] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor? I manually did an 'apt-get install nova-conductor' and these messages disappeared. Also, before installing nova-conductor I was unable to launch a VM. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nova-compute 1:2013.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Uname: Linux 3.8.0-17-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat Apr 13 14:22:24 2013 InstallationDate: Installed on 2012-01-06 (462 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64+mac (20111011) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm-color SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set SourcePackage: nova UpgradeStatus: Upgraded to raring on 2013-04-13 (0 days ago) modified.conffile..etc.nova.rootwrap.d.compute.filters: [deleted] ** Affects: nova (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1168757 Title: nova-compute missing dependency on nova-conductor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1168757/+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 1168757] [NEW] nova-compute missing dependency on nova-conductor
Public bug reported: I did an upgrade from quantal to raring today which upgraded OpenStack to Grizzly and saw these messages in /var/log/nova/nova-compute.log: 2013-04-13 12:42:37.104 WARNING nova.conductor.api [req-eec3e73a-3722-47a5-9a26-b831aa06e324 None None] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor? 2013-04-13 12:42:47.122 WARNING nova.conductor.api [req-eec3e73a-3722-47a5-9a26-b831aa06e324 None None] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor? 2013-04-13 12:42:57.139 WARNING nova.conductor.api [req-eec3e73a-3722-47a5-9a26-b831aa06e324 None None] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor? I manually did an 'apt-get install nova-conductor' and these messages disappeared. Also, before installing nova-conductor I was unable to launch a VM. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nova-compute 1:2013.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Uname: Linux 3.8.0-17-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat Apr 13 14:22:24 2013 InstallationDate: Installed on 2012-01-06 (462 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64+mac (20111011) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm-color SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set SourcePackage: nova UpgradeStatus: Upgraded to raring on 2013-04-13 (0 days ago) modified.conffile..etc.nova.rootwrap.d.compute.filters: [deleted] ** Affects: nova (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1168757 Title: nova-compute missing dependency on nova-conductor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1168757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1168592] [NEW] Sound not working on tyan S7025, Alsa detects, and activates controller, but no sound
Public bug reported: It works under ubuntu 10.04, and windows. The card is detected by the system, alsa and is activated (Intel Corporation 82801JI (ICH10 Family) HD Audio Controller) I've unmuted everything. I can't test the digital port (so I don't know if that is sending anything), since I have nothing to plug into it. Here is the information dump. http://www.alsa- project.org/db/?f=7b6cd11ab958f0116538916043508c9cc05b98ce ** Affects: alsa-driver (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/1168592 Title: Sound not working on tyan S7025, Alsa detects, and activates controller, but no sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1168592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073626] Re: Constant false gpu hang system alerts
I'm running quantal and just started getting GPU hangs on 3.5.0-26 and 3.5.0-27, the last good kernel is 3.5.0-25 which doesn't cause GPU hangs. Aside from the bug in apport itself, doesn't ubuntu want to know when there are GPU hangs with newer kernels on stable releases? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073626 Title: Constant false gpu hang system alerts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1073626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157786] Re: Kernel release 3.2.0-39-generic hangs intel 64-bit X
This is an extremely serious problem for novice users, as it can cause a machine to become completely unusable (I had to spend an evening on the phone guiding my parents to get around this, which isn't something I expected from an LTS release!). I hope it can be investigated and resolved with utmost urgency. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157786 Title: Kernel release 3.2.0-39-generic hangs intel 64-bit X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1157786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1134592] [NEW] isc-dhcp 4.2.4-5's DHCPREQUEST messages no longer match ignore regex
Public bug reported: After upgrading my raring VMs to the latest isc-dhcp: isc-dhcp (4.2.4-5ubuntu1) raring; urgency=low isc-dhcp (4.2.4-5) unstable; urgency=medium logcheck's email now includes DHCPREQUEST messages. This is very annoying when deployed in a OpenStack since the client does a DHCP request every minute or so ;) Here are some messages that are correctly filtered out: $ zcat syslog.7.gz |grep DHCPRE | head -4 Feb 20 06:39:37 server-43cadf07-0162-4924-a329-f522bd6f0490 dhclient: DHCPREQUEST of 192.168.2.2 on eth0 to 192.168.2.1 port 67 Feb 20 06:40:30 server-43cadf07-0162-4924-a329-f522bd6f0490 dhclient: DHCPREQUEST of 192.168.2.2 on eth0 to 192.168.2.1 port 67 Feb 20 06:41:23 server-43cadf07-0162-4924-a329-f522bd6f0490 dhclient: DHCPREQUEST of 192.168.2.2 on eth0 to 192.168.2.1 port 67 Feb 20 06:42:15 server-43cadf07-0162-4924-a329-f522bd6f0490 dhclient: DHCPREQUEST of 192.168.2.2 on eth0 to 192.168.2.1 port 67 And here are messages now appearing in the email: This email is sent by logcheck. If you no longer wish to receive such mail, you can either deinstall the logcheck package or modify its configuration file (/etc/logcheck/logcheck.conf). System Events =-=-=-=-=-=-= Feb 27 08:02:48 server-43cadf07-0162-4924-a329-f522bd6f0490 dhclient: DHCPREQUEST of 192.168.2.2 on eth0 to 192.168.2.1 port 67 (xid=0x593f7ff6) Feb 27 08:03:36 server-43cadf07-0162-4924-a329-f522bd6f0490 dhclient: DHCPREQUEST of 192.168.2.2 on eth0 to 192.168.2.1 port 67 (xid=0x593f7ff6) Feb 27 08:04:28 server-43cadf07-0162-4924-a329-f522bd6f0490 dhclient: DHCPREQUEST of 192.168.2.2 on eth0 to 192.168.2.1 port 67 (xid=0x593f7ff6) Feb 27 08:05:14 server-43cadf07-0162-4924-a329-f522bd6f0490 dhclient: DHCPREQUEST of 192.168.2.2 on eth0 to 192.168.2.1 port 67 (xid=0x593f7ff6) It looks like the xid text is not matched. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: logcheck-database 1.3.15 ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0 Uname: Linux 3.8.0-7-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Wed Feb 27 09:21:51 2013 Dependencies: Ec2AMI: ami-000e Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: ec2-m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable MarkForUpload: True PackageArchitecture: all ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: logcheck UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: logcheck (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1134592 Title: isc-dhcp 4.2.4-5's DHCPREQUEST messages no longer match ignore regex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logcheck/+bug/1134592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1131101] Re: no icons and subtitle entries in ccsm
Have you changed your desktop theme from the default Ambiance GKT theme? ** Changed in: compiz (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1131101 Title: no icons and subtitle entries in ccsm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1131101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1130643] Re: Documentation error man sudo root
To let other users use 'sudo' open up a terminal and use 'visudo' (sudo visudo) This will allow you to add other users and groups to use the sudo command or adding them to the admin group (see /etc/sudoers) will by default allow root privlages. ** Changed in: sudo (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1130643 Title: Documentation error man sudo root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1130643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1107400] [NEW] Request upgrade to 3.4.5
Public bug reported: Hello, The latest Zookeeper is now 3.4.5 [1] which adds Kerberos authentication of clients [2], multi-updates, an improved REST API and improved operational support [3]. Cloudera considers 3.4.4 the first stable release in the 3.4.x line and as such are including it in their CDH4.2 release [4]. It would be great if the Ubuntu package was updated. I've opened a bug in Debian to request the update, which could be pulled into Ubuntu [5]. Thank you, Blair [1] http://zookeeper.apache.org/doc/r3.4.5/ [2] https://issues.apache.org/jira/browse/ZOOKEEPER-938 [3] http://blog.cloudera.com/blog/2011/11/apache-zookeeper-3-4-0-has-been-released/ [4] http://blog.cloudera.com/blog/2012/09/apache-zookeeper-3-4-4-has-been-released/ [5] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699120 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: zookeeper 3.3.6+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Sun Jan 27 18:41:08 2013 InstallationDate: Installed on 2012-01-06 (387 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64+mac (20111011) MarkForUpload: True PackageArchitecture: all ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set SourcePackage: zookeeper UpgradeStatus: Upgraded to quantal on 2013-01-01 (26 days ago) ** Affects: zookeeper (Ubuntu) Importance: Undecided Status: New ** Affects: zookeeper (Debian) Importance: Unknown Status: Unknown ** Tags: amd64 apport-bug raring upgrade-software-version ** Bug watch added: Debian Bug tracker #699120 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699120 ** Also affects: zookeeper (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699120 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to zookeeper in Ubuntu. https://bugs.launchpad.net/bugs/1107400 Title: Request upgrade to 3.4.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zookeeper/+bug/1107400/+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 1107400] [NEW] Request upgrade to 3.4.5
Public bug reported: Hello, The latest Zookeeper is now 3.4.5 [1] which adds Kerberos authentication of clients [2], multi-updates, an improved REST API and improved operational support [3]. Cloudera considers 3.4.4 the first stable release in the 3.4.x line and as such are including it in their CDH4.2 release [4]. It would be great if the Ubuntu package was updated. I've opened a bug in Debian to request the update, which could be pulled into Ubuntu [5]. Thank you, Blair [1] http://zookeeper.apache.org/doc/r3.4.5/ [2] https://issues.apache.org/jira/browse/ZOOKEEPER-938 [3] http://blog.cloudera.com/blog/2011/11/apache-zookeeper-3-4-0-has-been-released/ [4] http://blog.cloudera.com/blog/2012/09/apache-zookeeper-3-4-4-has-been-released/ [5] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699120 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: zookeeper 3.3.6+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Sun Jan 27 18:41:08 2013 InstallationDate: Installed on 2012-01-06 (387 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64+mac (20111011) MarkForUpload: True PackageArchitecture: all ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set SourcePackage: zookeeper UpgradeStatus: Upgraded to quantal on 2013-01-01 (26 days ago) ** Affects: zookeeper (Ubuntu) Importance: Undecided Status: New ** Affects: zookeeper (Debian) Importance: Unknown Status: Unknown ** Tags: amd64 apport-bug raring upgrade-software-version ** Bug watch added: Debian Bug tracker #699120 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699120 ** Also affects: zookeeper (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699120 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/1107400 Title: Request upgrade to 3.4.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zookeeper/+bug/1107400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099199] [NEW] [PATCH] support resizing btrfs filesystems
Public bug reported: I converted a cloud image from ext4 to btrfs and this warning appears when booting the image: 2013-01-13 20:03:05,057 - cc_resizefs.py[WARNING]: Could not determine filesystem type of / I put a patch to support resizing btrfs volumes up at https://code.launchpad.net/~blair/cloud-init/cloud-init It's a little tricker than I initially thought it would be, please review the commit to see details on this. The patch hasn't been tested with ext* and xfs filesystems, only btrfs filesystems. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: cloud-init 0.7.1-0ubuntu4 [modified: usr/share/pyshared/cloudinit/config/cc_resizefs.py] ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.8-0ubuntu1 Architecture: amd64 Date: Sun Jan 13 19:56:47 2013 MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=screen SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug patch raring uec-images ** Patch added: Patch to support resizing btrfs filesystems https://bugs.launchpad.net/bugs/1099199/+attachment/3482134/+files/resize-btrfs-patch.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1099199 Title: [PATCH] support resizing btrfs filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1099199/+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 1099199] [NEW] [PATCH] support resizing btrfs filesystems
Public bug reported: I converted a cloud image from ext4 to btrfs and this warning appears when booting the image: 2013-01-13 20:03:05,057 - cc_resizefs.py[WARNING]: Could not determine filesystem type of / I put a patch to support resizing btrfs volumes up at https://code.launchpad.net/~blair/cloud-init/cloud-init It's a little tricker than I initially thought it would be, please review the commit to see details on this. The patch hasn't been tested with ext* and xfs filesystems, only btrfs filesystems. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: cloud-init 0.7.1-0ubuntu4 [modified: usr/share/pyshared/cloudinit/config/cc_resizefs.py] ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.8-0ubuntu1 Architecture: amd64 Date: Sun Jan 13 19:56:47 2013 MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=screen SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug patch raring uec-images ** Patch added: Patch to support resizing btrfs filesystems https://bugs.launchpad.net/bugs/1099199/+attachment/3482134/+files/resize-btrfs-patch.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099199 Title: [PATCH] support resizing btrfs filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1099199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096531] Re: After touch /forcefsck and reboot: Assertion failed in log_clear_unflushed
The one issue with the KVM image is that it'll hang for 2 minutes upon boot and not tell you its 'ubuntu' user password. I can reproduce this using the daily server ISO: - Download rsync://cdimages.ubuntu.com/cdimage/ubuntu-server/daily/current/raring-server-amd64.iso - Start VirtualBox - Make a new VM with the raring-server-amd64.iso - Do a minimal install - Reboot into the new OS - sudo touch /forcefsck - sudo /sbin/shutdown -r now ** Attachment added: Screenshot of VirtualBox running raring which failed at boot https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1096531/+attachment/3475606/+files/Screenshot%20from%202013-01-06%2009%3A58%3A16.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096531 Title: After touch /forcefsck and reboot: Assertion failed in log_clear_unflushed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1096531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096531] [NEW] After touch /forcefsck and reboot: Assertion failed in log_clear_unflushed
Public bug reported: I made a copy of raring-server-cloudimg-amd64-disk1.img, launched in KVM on my 12.10 system, updated all the packages on it and then rebooted it after touching /forcefsck. Even though its a clean reboot, it still core dumpes. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: upstart 1.6.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0 Uname: Linux 3.7.0-7-generic x86_64 ApportVersion: 2.7-0ubuntu2 Architecture: amd64 Date: Sun Jan 6 06:39:07 2013 MarkForUpload: True ProcEnviron: TERM=screen SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: upstart (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring uec-images ** Attachment added: Stdout from kvm. https://bugs.launchpad.net/bugs/1096531/+attachment/3475322/+files/kvm-stdout.txt ** Summary changed: - After touch /forcefsck and reboot: Assertion failed in log_clear_unflushed: after + After touch /forcefsck and reboot: Assertion failed in log_clear_unflushed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096531 Title: After touch /forcefsck and reboot: Assertion failed in log_clear_unflushed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1096531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1075518] Re: Plasma Workspace (plasma-desktop), signal: Aborted [Current thread is 1 (Thread 0xb31c5720 (LWP 14726))]
yes I realize that but as my description stated bugs.kde.org was not in service that day so I went to the next best place :) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1075518 Title: Plasma Workspace (plasma-desktop), signal: Aborted [Current thread is 1 (Thread 0xb31c5720 (LWP 14726))] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1075518/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1067876] Re: [quantal] Missing Safely Remove Drive and Eject options from Quicklists. Only have Unmount.
Martin Pitt (pitti) wrote on 2012-11-13: #13 The safe remove functionality was removed from udisks2, and it's not planned to bring it back. It caused too much trouble with e. g. devices which are internally wired to an USB port, and you could never use them again until after a reboot. Also, having two options was a constant source of confusion. So I'm afraid this is wontfix from the distro side. Martin, There is myself and I am sure many others who find this justification unacceptable! I have several systems in which devices are connected internally via USB headers/ports. Yes, the option does exist, be it Ubuntu 12.04.1, Windows XP-7, etc. to safely remove these devices via a right-click, even though they are devices that would not normally require such action. Examples of these devices are a wireless N network adapter, an internal media card reader with USB port, etc. Quite frankly, it comes down to a user exercising diligence when right- clicking on any device and knowing what device it is that they are about to safely remove beforehand! Saying that it causes too much trouble for devices that would then require a reboot to use again is in my opinion, a cop-out! It is a chance that most users would be willing to take, to err on the side of caution when it comes to properly powering down a device first before removing it! If it is a choice between having the safely remove command available to remove a device properly by completely powering it down or not having the safely remove command available at all in an attempt to eliminate the confusion that exists in correlation to the eject/unmount commands while helping to prevent some users from accidentally removing the wrong device, I think the majority of users do not find it as confusing as you implicate. I and others I am sure would rather have the option to safely power down our devices using the safely remove command and thus this is a request to have it formally reinstated. This too, has prevented me from upgrading to Ubuntu 12.10! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067876 Title: [quantal] Missing Safely Remove Drive and Eject options from Quicklists. Only have Unmount. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1067876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1075518] [NEW] Plasma Workspace (plasma-desktop), signal: Aborted [Current thread is 1 (Thread 0xb31c5720 (LWP 14726))]
Public bug reported: Re arranging widgets on desktop when all the sudden I lost the side panel on analog clock widget (the panel with settings / resize / reload ). Continued to move it and desktop crashed / restarted. .. I'm not sure what the state of bugs.kde.org is but the crash assistant could not connect but I am including my system information as well as crash report here. ** Affects: kde-workspace (Ubuntu) Importance: Undecided Status: New ** Tags: kde plasma-desktop ** Attachment added: KDE crash report assistant log https://bugs.launchpad.net/bugs/1075518/+attachment/3425560/+files/plasma-desktop-20121106-052329.kcrash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075518 Title: Plasma Workspace (plasma-desktop), signal: Aborted [Current thread is 1 (Thread 0xb31c5720 (LWP 14726))] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1075518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1075518] Re: Plasma Workspace (plasma-desktop), signal: Aborted [Current thread is 1 (Thread 0xb31c5720 (LWP 14726))]
Backtrack 5 RC 3 32-bit (Most current release) distrobution.. I'm not sure if this belongs here but the distro uses ubuntu as its backbone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075518 Title: Plasma Workspace (plasma-desktop), signal: Aborted [Current thread is 1 (Thread 0xb31c5720 (LWP 14726))] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1075518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1075518] Re: Plasma Workspace (plasma-desktop), signal: Aborted [Current thread is 1 (Thread 0xb31c5720 (LWP 14726))]
** Attachment added: Full system report with releae info, hardware info and more. https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1075518/+attachment/3425561/+files/logs.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075518 Title: Plasma Workspace (plasma-desktop), signal: Aborted [Current thread is 1 (Thread 0xb31c5720 (LWP 14726))] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1075518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073914] Re: Menus background color changed, and some words have disappeared
The same affected me but I just switched themes to anything besides the ambience theme and it worked fine for a quick workaround. --- Ubuntu Bug Squad volunteer triager http://wiki.ubuntu.com/BugSquad -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073914 Title: Menus background color changed, and some words have disappeared To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1073914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073477] Re: thunderbird constantly stops by itself
Could you be more specific, what do you mean stops itself? --- Ubuntu Bug Squad volunteer triager http://wiki.ubuntu.com/BugSquad ** Changed in: thunderbird (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073477 Title: thunderbird constantly stops by itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1073477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073872] Re: Can't install Gimp on Ubuntu 12.10
** Changed in: gimp (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073872 Title: Can't install Gimp on Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1073872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606440] Re: Only the most recent episode of each podcast gets downloaded automatically
Yes, this is still an issue in 12.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606440 Title: Only the most recent episode of each podcast gets downloaded automatically To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/606440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1071994] [NEW] Compiz crashes when unmounting iPod 3G from launcher
Public bug reported: Every time I bring up the context menu to unmount my iPod from the launcher compiz crashes and extremely uses up system resource. Please watch the video attached. It will show the cause / effect and reproducing the crash. --- Ubuntu Bug Squad volunteer triager http://wiki.ubuntu.com/BugSquad ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: compiz 1:0.9.8.4+bzr3407-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 .tmp.unity.lens.academic: Error: [Errno 21] Is a directory: '/tmp/unity-lens-academic' .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Sat Oct 27 01:11:15 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices [AMD] nee ATI RV710 [Mobility Radeon HD 4500/5100 Series] [1002:9553] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:ff15] InstallationDate: Installed on 2012-08-20 (67 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120814.1) MachineType: TOSHIBA Satellite A505 MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-18-generic root=UUID=a23e0838-8975-4f64-aff6-d63264957f98 ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2009 dmi.bios.vendor: INSYDE dmi.bios.version: 1.40 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.40:bd06/08/2009:svnTOSHIBA:pnSatelliteA505:pvrPSAP3U-01G00C:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite A505 dmi.product.version: PSAP3U-01G00C dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.8.4+bzr3407-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 package-from-proposed quantal running-unity third-party-packages ubuntu ** Attachment added: Video reproduction of crash. https://bugs.launchpad.net/bugs/1071994/+attachment/3415128/+files/launcher.ogv -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1071994 Title: Compiz crashes when unmounting iPod 3G from launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1071994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1071994] Re: Compiz crashes when unmounting iPod 3G from launcher
On a side note... After the crash / restart of compiz Yakuake which is mapped to F12 does not respond to pressing the button to activate it. --- Ubuntu Bug Squad volunteer triager http://wiki.ubuntu.com/BugSquad -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1071994 Title: Compiz crashes when unmounting iPod 3G from launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1071994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1071996] [NEW] Unity/Gnome System Tray not displaying the context menu with mail symbol properly
Public bug reported: Unity/Gnome System Tray not displaying the context menu with mail symbol properly Attached is a video. Tried taking a screen capture with shutter but didn't work properly so here is a video. (The blacked out period on the video was me switching users to check see if had same results, unfortunatly RecordMyDesktop does not follow thru to another session) --- Ubuntu Bug Squad volunteer triager http://wiki.ubuntu.com/BugSquad ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 .tmp.unity.lens.academic: Error: [Errno 21] Is a directory: '/tmp/unity-lens-academic' .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Sat Oct 27 01:40:27 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices [AMD] nee ATI RV710 [Mobility Radeon HD 4500/5100 Series] [1002:9553] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:ff15] InstallationDate: Installed on 2012-08-20 (67 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120814.1) MachineType: TOSHIBA Satellite A505 MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-18-generic root=UUID=a23e0838-8975-4f64-aff6-d63264957f98 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2009 dmi.bios.vendor: INSYDE dmi.bios.version: 1.40 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.40:bd06/08/2009:svnTOSHIBA:pnSatelliteA505:pvrPSAP3U-01G00C:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite A505 dmi.product.version: PSAP3U-01G00C dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.8.4+bzr3407-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 package-from-proposed quantal running-unity third-party-packages ubuntu ** Attachment added: systray.ogv https://bugs.launchpad.net/bugs/1071996/+attachment/3415157/+files/systray.ogv -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1071996 Title: Unity/Gnome System Tray not displaying the context menu with mail symbol properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1071996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067480] [NEW] empathy crash after fresh install from source
Public bug reported: I originally set --prefix=/opt/empathy-3.4.2.3 so I can have the latest stable and proposed on same machine. It had some problems compiling but it made after I tweaked it but it wont start. To answer your question yes it keeps losing authentication. I'd love to give you that mission control log but for some reason I cant find the debug menu this time around... Gonna re-install my previous version. here are a few logs and pic tho --- Ubuntu Bug Squad volunteer triager http://wiki.ubuntu.com/BugSquad ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: empathy 3.6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Tue Oct 16 12:54:28 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120814.1) SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity third-party-packages ** Attachment added: empathy ss1.png https://bugs.launchpad.net/bugs/1067480/+attachment/3400578/+files/empathy%20ss1.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067480 Title: empathy crash after fresh install from source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1067480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067480] Re: empathy crash after fresh install from source
--- Ubuntu Bug Squad volunteer triager http://wiki.ubuntu.com/BugSquad ** Attachment added: config-compile.log https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1067480/+attachment/3400593/+files/config-compile.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067480 Title: empathy crash after fresh install from source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1067480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011019] Re: Error connecting to account manager in empathy
I have proposed enabled on 2 of my 3 test machines and I let cron handle my updates a few times a day on each so it should.. I didnt see it on my laptop only libmutter and checked my logs so maybe it hasnt hit everywhere yet so I grabbed it off of bazzar and sent it to both machines I have proposed enabled on. I already have the build dependencies for a lot of the software I use so compiling it no prob.. Now when I looked at my laptop it said darkrain@Rain:/etc/apt$ dpkg -l |grep empathy ii empathy3.6.0.3-0ubuntu1 amd64GNOME multi-protocol chat and call client ii empathy-common 3.6.0.3-0ubuntu1 all GNOME multi-protocol chat and call client (common files) ii nautilus-sendto-empathy3.6.0.3-0ubuntu1 amd64GNOME multi-protocol chat and call client (nautilus-sendto plugin) Is 3.6.0.3 a different branch? Not sure so I compiled it with --prefix=/opt/empathy-3.4.2.3 so I could have a copy of this version along side of the one already installed. Now I have a question. For some reason my debug symbols (empathy- dbgsym) I had before 3.6.0.3 was installed got removed from my system and I had to get to install empathy-dbg instead. Is that other set incompatible with the latest normal release? --- Ubuntu Bug Squad volunteer triager http://wiki.ubuntu.com/BugSquad -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1011019 Title: Error connecting to account manager in empathy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1011019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 964429] Re: Use of assignment to $[ is deprecated at /usr/sbin/fcheck line 1366.
The fix is in 12.10's 2.7.59-18 release which is working fine for me on 12.04. Download it from http://archive.ubuntu.com/ubuntu/pool/universe/f/fcheck/ . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/964429 Title: Use of assignment to $[ is deprecated at /usr/sbin/fcheck line 1366. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fcheck/+bug/964429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1041523] Re: ccsm crashed with SIGSEGV in ? [libkconfig4.so] from ccsCopyBackendInfoFromBackend() from addBackendInfo() from getBackendInfoFromDir() from ccsGetExistingBackends()
Great, I wasn't sure if it was safe to remove that file or not. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1041523 Title: ccsm crashed with SIGSEGV in ? [libkconfig4.so] from ccsCopyBackendInfoFromBackend() from addBackendInfo() from getBackendInfoFromDir() from ccsGetExistingBackends() To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1041523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063425] [NEW] installer crashed
Public bug reported: Installer crashed, it then collected information to create a bug report. The installer brought me to this site, so hopefully the debug file is being logged? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubiquity 2.10.20 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 CasperVersion: 1.315 Date: Sun Oct 7 17:04:33 2012 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity LiveMediaBuild: Xubuntu 12.04.1 LTS Precise Pangolin - Release i386 (20120817.3) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise ubiquity-2.10.20 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063425 Title: installer crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1063425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
