[Bug 1699844] Re: Onboard settings and scanning problem
The error message you're encountering indicates a problem with the settings.ui file of Onboard, specifically related to an attribute "id" that seems to be missing or incorrectly defined on line 2126. This issue typically arises from mismatches or errors in the XML definition of the UI file. Here are steps you can take to address this problem: Check the settings.ui file: Navigate to /usr/share/onboard/ and locate the settings.ui file. Open it using a text editor or an XML editor that supports UI definition files. Inspect line 2126: Go to line 2126 in settings.ui and examine the XML code around that line. Look for any elements and ensure they have an id attribute specified correctly. Correct the XML syntax: If the id attribute is missing or incorrectly defined, correct it according to the correct syntax for GTK UI files. An example of a properly defined object in GTK XML might look like this: xml Label Text Ensure your id attribute follows similar conventions and is unique within the scope of the UI file. Validate the XML: After making corrections, validate the XML file to ensure there are no syntax errors. This can be done using an XML validator or simply by checking for any obvious syntax mistakes (unclosed tags, incorrect attribute values, https://nbiclearancesonline.com/ etc.). Restart Onboard: Once you've saved the corrected settings.ui file, restart the Onboard application to see if the issue is resolved. Sometimes, changes to UI files may require a restart to take effect. Update or reinstall Onboard: If the problem persists and you suspect a more fundamental issue with the application installation or configuration, consider updating Onboard to the latest version available for your system. Alternatively, reinstalling Onboard can sometimes resolve persistent UI-related issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699844 Title: Onboard settings and scanning problem To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1699844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967951] Re: hotplug external monitor logs me out
I have been using Ubuntu 22.04 for several months, initially Ubuntu on wayland was working but at some point Ubuntu on wayland stopped working (It doesn't even show up as an option on the gdm3 login screen). I am mentioning this to preemptively say that: - Ubuntu on wayland is not working - Sway on wayland is working - I don't know why Ubuntu-wayland is not working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967951 Title: hotplug external monitor logs me out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1967951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967951] [NEW] hotplug external monitor logs me out
Public bug reported: Summary: When hotplugging an external monitor, I am sent immediately to the login screen. Actions: Boot my laptop either with or without the external plugged in and then log in to my user account. If the monitor is not plugged in, plug it in. Expected result: The monitor is detected and the previous monitor configurations are loaded. Actual result: When the monitor is detected, I am immediately sent to the login screen. On X, with either HDMI or usb c port: I need to log in again. The monitor is detected and functions as expected once I have logged in. On sway with HDMI: I can change to tty2 (where my sway session was started) and the monitor is detected and functions as expected. On sway with usb c: I cannot log in again. It is stuck in a log-in loop. Other info: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 xserver-xorg-video-nouveau: Installed: 1:1.0.17-2build1 Candidate: 1:1.0.17-2build1 Version table: *** 1:1.0.17-2build1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Sway version 1.5.1 I have uninstalled all the propriety drivers. From the 'About Ubuntu' page, it seems that my Nvidia GPU is not in use. Laptop ASUS TUF A15 FA506IH ** Affects: xserver-xorg-video-nouveau (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/1967951 Title: hotplug external monitor logs me out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1967951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724732] Re: Wayland login options are missing when a radeon card is installed
I am having a similar issue on Ubuntu 22.04 with Asus Tuf A15 FA605IH -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724732 Title: Wayland login options are missing when a radeon card is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955918] [NEW] Triyng to update to 22.04 fails due to missing 'ubuntu-minimal' package.
Public bug reported: "Invalid package information After updating your package information, the essential package 'ubuntu-minimal' could not be located. This may be because you have no official mirrors listed in your software sources, or because of excessive load on the mirror you are using. See /etc/apt/sources.list for the current list of configured software sources. In the case of an overloaded mirror, you may want to try the upgrade again later. " ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.6 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu Date: Tue Dec 28 11:58:21 2021 InstallationDate: Installed on 2021-01-28 (334 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to impish on 2021-12-28 (0 days ago) VarLogDistupgradeAptlog: Log time: 2021-12-28 11:57:54.958839 Log time: 2021-12-28 11:57:57.884172 Log time: 2021-12-28 11:58:20.773992 Log time: 2021-12-28 11:58:22.493872 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955918 Title: Triyng to update to 22.04 fails due to missing 'ubuntu-minimal' package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1955918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779289] Re: [regression] bluetooth mouse not reconnected on reboot
BTLE persition mouse. There were problems with pair and repeated connection.( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779413 ) All decided this way: https://gist.github.com/Mygod/f390aabf53cf1406fc71166a47236ebf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779289 Title: [regression] bluetooth mouse not reconnected on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1779289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779413] Re: Bluetooth bug
The mouse is connected only after its removal and reboot of the bluetooth. But as soon as the mouse turns off falling into a dream, you have to remove it again and restart the bluetooth. Pair does not happen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779413 Title: Bluetooth bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1779413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779413] Re: Bluetooth bug
This problem was always. Kernel 4.18 did not solve the problem. Pair does not happen. ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779413 Title: Bluetooth bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779413] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1779413/+attachment/5157933/+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/1779413 Title: Bluetooth bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779413] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1779413/+attachment/5157935/+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/1779413 Title: Bluetooth bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779413] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1779413/+attachment/5157938/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779413 Title: Bluetooth bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779413] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1779413/+attachment/5157934/+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/1779413 Title: Bluetooth bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779413] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1779413/+attachment/5157937/+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/1779413 Title: Bluetooth bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779413] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1779413/+attachment/5157936/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779413 Title: Bluetooth bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779413] Re: Bluetooth bug
apport information ** Tags added: apport-collected ** Description changed: Good afternoon! I have a small problem. It is connected with the mouse from Microsoft (BTLE Precision Mouse). She does not want to connect on bluetooth. The version of my bluetooth 4.1. Ubuntu 4.15.0-22.24-generic 4.15.17 ``` lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 ``` Here's the output when trying to pair: ``` pair E0:52:31:92:AB:5B Attempting to pair with E0:52:31:92:AB:5B [CHG] Device E0:52:31:92:AB:5B Connected: yes [NEW] Primary Service /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0008 1801--1000-8000-00805f9b34fb Generic Attribute Profile [NEW] Primary Service /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009 180a--1000-8000-00805f9b34fb Device Information [NEW] Characteristic /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000a 2a29--1000-8000-00805f9b34fb Manufacturer Name String [NEW] Characteristic /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000c 2a24--1000-8000-00805f9b34fb Model Number String [NEW] Characteristic /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000e 2a26--1000-8000-00805f9b34fb Firmware Revision String [NEW] Characteristic /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0010 2a28--1000-8000-00805f9b34fb Software Revision String [NEW] Characteristic /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0012 2a50--1000-8000-00805f9b34fb PnP ID [NEW] Characteristic /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0014 6ff6f99d-536c-4ea6-88a3-c3aabb718b68 Vendor specific [CHG] Device E0:52:31:92:AB:5B UUIDs: 1800--1000-8000-00805f9b34fb [CHG] Device E0:52:31:92:AB:5B UUIDs: 1801--1000-8000-00805f9b34fb [CHG] Device E0:52:31:92:AB:5B UUIDs: 180a--1000-8000-00805f9b34fb [CHG] Device E0:52:31:92:AB:5B UUIDs: 180f--1000-8000-00805f9b34fb [CHG] Device E0:52:31:92:AB:5B UUIDs: 1812--1000-8000-00805f9b34fb [CHG] Device E0:52:31:92:AB:5B UUIDs: 1813--1000-8000-00805f9b34fb [CHG] Device E0:52:31:92:AB:5B ServicesResolved: yes [CHG] Device E0:52:31:92:AB:5B Modalias: usb:v045Ep0821d0105 Failed to pair: org.freedesktop.DBus.Error.NoReply ``` journalctl -u bluetooth ``` июн 29 23:42:34 mi bluetoothd[5983]: No cache for E0:52:31:92:AB:5B июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for E0:52:31:92:AB:5B июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for E0:52:31:92:AB:5B июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for E0:52:31:92:AB:5B июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for E0:52:31:92:AB:5B июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for E0:52:31:92:AB:5B июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for E0:52:31:92:AB:5B июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for E0:52:31:92:AB:5B июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for E0:52:31:92:AB:5B июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for E0:52:31:92:AB:5B июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for E0:52:31:92:AB:5B июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22) июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22) июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22) июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22) июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22) июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22) июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22) июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22) июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22) июн 29 23:42:45 mi bluetoothd[5983]: Unable to register device interface for E0:52:31:92:AB:5B июн 29 23:42:45 mi bluetoothd[5983]: Unable to get device object for E0:52:31:92:AB:5B ``` + --- + ApportVersion: 2.20.9-0ubuntu7.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/pcmC0D0p: pocoz 2614 F...m pulseaudio + /dev/snd/controlC0: pocoz 2614 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-05-23 (37 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + MachineType: Timi TM1701 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 inteldrmfb +
[Bug 1779413] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1779413/+attachment/5157930/+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/1779413 Title: Bluetooth bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779413] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1779413/+attachment/5157928/+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/1779413 Title: Bluetooth bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779413] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1779413/+attachment/5157926/+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/1779413 Title: Bluetooth bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779413] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1779413/+attachment/5157929/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779413 Title: Bluetooth bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779413] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1779413/+attachment/5157932/+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/1779413 Title: Bluetooth bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779413] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1779413/+attachment/5157931/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779413 Title: Bluetooth bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779413] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1779413/+attachment/5157927/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779413 Title: Bluetooth bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779413] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1779413/+attachment/5157925/+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/1779413 Title: Bluetooth bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779413] [NEW] Bluetooth bug
Public bug reported: Good afternoon! I have a small problem. It is connected with the mouse from Microsoft (BTLE Precision Mouse). She does not want to connect on bluetooth. The version of my bluetooth 4.1. Ubuntu 4.15.0-22.24-generic 4.15.17 ``` lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 ``` Here's the output when trying to pair: ``` pair E0:52:31:92:AB:5B Attempting to pair with E0:52:31:92:AB:5B [CHG] Device E0:52:31:92:AB:5B Connected: yes [NEW] Primary Service /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0008 1801--1000-8000-00805f9b34fb Generic Attribute Profile [NEW] Primary Service /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009 180a--1000-8000-00805f9b34fb Device Information [NEW] Characteristic /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000a 2a29--1000-8000-00805f9b34fb Manufacturer Name String [NEW] Characteristic /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000c 2a24--1000-8000-00805f9b34fb Model Number String [NEW] Characteristic /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000e 2a26--1000-8000-00805f9b34fb Firmware Revision String [NEW] Characteristic /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0010 2a28--1000-8000-00805f9b34fb Software Revision String [NEW] Characteristic /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0012 2a50--1000-8000-00805f9b34fb PnP ID [NEW] Characteristic /org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0014 6ff6f99d-536c-4ea6-88a3-c3aabb718b68 Vendor specific [CHG] Device E0:52:31:92:AB:5B UUIDs: 1800--1000-8000-00805f9b34fb [CHG] Device E0:52:31:92:AB:5B UUIDs: 1801--1000-8000-00805f9b34fb [CHG] Device E0:52:31:92:AB:5B UUIDs: 180a--1000-8000-00805f9b34fb [CHG] Device E0:52:31:92:AB:5B UUIDs: 180f--1000-8000-00805f9b34fb [CHG] Device E0:52:31:92:AB:5B UUIDs: 1812--1000-8000-00805f9b34fb [CHG] Device E0:52:31:92:AB:5B UUIDs: 1813--1000-8000-00805f9b34fb [CHG] Device E0:52:31:92:AB:5B ServicesResolved: yes [CHG] Device E0:52:31:92:AB:5B Modalias: usb:v045Ep0821d0105 Failed to pair: org.freedesktop.DBus.Error.NoReply ``` journalctl -u bluetooth ``` июн 29 23:42:34 mi bluetoothd[5983]: No cache for E0:52:31:92:AB:5B июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for E0:52:31:92:AB:5B июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for E0:52:31:92:AB:5B июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for E0:52:31:92:AB:5B июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for E0:52:31:92:AB:5B июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for E0:52:31:92:AB:5B июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for E0:52:31:92:AB:5B июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for E0:52:31:92:AB:5B июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for E0:52:31:92:AB:5B июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for E0:52:31:92:AB:5B июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for E0:52:31:92:AB:5B июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22) июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22) июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22) июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22) июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22) июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22) июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22) июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22) июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22) июн 29 23:42:45 mi bluetoothd[5983]: Unable to register device interface for E0:52:31:92:AB:5B июн 29 23:42:45 mi bluetoothd[5983]: Unable to get device object for E0:52:31:92:AB:5B ``` ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1779413/+attachment/5157923/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779413 Title: Bluetooth bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682682] Re: Upgrade from 16.10 to 17.04 failed due to rabbitmq-server
Guys, I have same issue. https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1714992 Could you please advise ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682682 Title: Upgrade from 16.10 to 17.04 failed due to rabbitmq-server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1682682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714992] [NEW] do-release-upgrade fails due to "An unresolvable problem occurred while calculating the upgrade."
Public bug reported: My problem is similar to one described at https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/1682682 But I don't have rabbitmq-server ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubuntu-release-upgrader-core 1:16.10.10 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.7 Architecture: amd64 CrashDB: ubuntu Date: Mon Sep 4 19:06:50 2017 InstallationDate: Installed on 2015-12-06 (638 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to yakkety on 2017-09-04 (0 days ago) VarLogDistupgradeAptlog: Log time: 2017-09-04 19:02:43.964458 Log time: 2017-09-04 19:02:47.505667 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade yakkety yakkety2zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714992 Title: do-release-upgrade fails due to "An unresolvable problem occurred while calculating the upgrade." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1714992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1510570] Re: BLE pairing fail
I don't know guys. None of the above helped me. I initially had Killer 1535 card on my DELL XPS 13. Today I replaced it with Intel 8260 ant it still doesn't see Mobile Bluetooth 3600 mouse. Oddly it worked on another laptop with Intel 7260 card. Go figure :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1510570 Title: BLE pairing fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665589] [NEW] Killer 1535 802.11 2×2 Wi-Fi + BT 4.1 controller can't discover MS Mobile Mouse 3600
Public bug reported: I saw number of posts here about Mobile Mouse 3600 but sadly none of them helped me to debug the issue. I have Killer 1535 card on my Dell XPS 13. According to specs it's Bluetooth 4.1 device. Mobile Mouse 3600 is Bluetooth Low Energy device of version 4.0. In theory these two devices should be able to communicate. Unfortunately they don't :( I'm on Ubuntu MATE 16.10 but I also tested it on Linux Mint 18 and Element OS. I have bluez 5.41 installed. Here is what info I have abut my devices usb-devices | awk '/e301/' RS= T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=03 Dev#= 4 Spd=12 MxCh= 0 D: Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0cf3 ProdID=e301 Rev=00.01 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb hciconfig -a | grep HCI HCI Version: 4.1 (0x7) Revision: 0x0 lsusb | grep Ath Bus 001 Device 004: ID 0cf3:e301 Atheros Communications, Inc. `sudo hcitool lescan` finds nothing. After clean installation `dmesg | grep ath10` gives [ 14.979939] ath10k_pci :3a:00.0: enabling device ( -> 0002) [ 14.981966] ath10k_pci :3a:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [ 15.263691] ath10k_pci :3a:00.0: Direct firmware load for ath10k/pre-cal-pci-:3a:00.0.bin failed with error -2 [ 15.263709] ath10k_pci :3a:00.0: Direct firmware load for ath10k/cal-pci-:3a:00.0.bin failed with error -2 [ 15.263734] ath10k_pci :3a:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 [ 15.263736] ath10k_pci :3a:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 [ 15.440154] ath10k_pci :3a:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [ 15.440156] ath10k_pci :3a:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [ 15.440582] ath10k_pci :3a:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5 [ 15.532098] ath10k_pci :3a:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7 [ 17.658135] ath10k_pci :3a:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [ 17.770412] ath10k_pci :3a:00.0 wlp58s0: renamed from wlan0 My WiFi works. I can also pair Bluetooth keyboard. Since I don't really know how device drivers work in Linux I noticed line with error about `firmware-5.bin` in output of dmesg. So I took missing file from https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4. It turned out to be bad idea because it botched wifi/bluetooth completely. Here is what I had in log [3.519354] ath10k_pci :3a:00.0: enabling device ( -> 0002) [3.521259] ath10k_pci :3a:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0 [3.765880] ath10k_pci :3a:00.0: Direct firmware load for ath10k/cal-pci-:3a:00.0.bin failed with error -2 [3.831220] ath10k_pci :3a:00.0: failed to fetch board data for ath10k/QCA6174/hw3.0 from bus=pci,bmi-chip-id=0,bmi-board-id=0/board-2.bin [5.887772] ath10k_pci :3a:00.0: Unknown eventid: 90118 [5.887786] ath10k_pci :3a:00.0: qca6174 hw3.2 (0x0503, 0x00340aff bmi 0:0) fw WLAN.RM.4.4-00022-QCARMSWPZ-2 fwapi 5 bdapi 1 htt-ver 3.32 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 features wowlan,ignore-otp [5.887789] ath10k_pci :3a:00.0: debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [8.884160] ath10k_pci :3a:00.0: could not suspend target (-11) [8.966789] ath10k_pci :3a:00.0 wlp58s0: renamed from wlan0 [ 11.178547] ath10k_pci :3a:00.0: Unknown eventid: 90118 [ 14.176459] ath10k_pci :3a:00.0: failed to enable dynamic BW: -11 [ 20.176417] ath10k_pci :3a:00.0: could not suspend target (-11) [ 22.435758] ath10k_pci :3a:00.0: Unknown eventid: 90118 [ 25.432569] ath10k_pci :3a:00.0: failed to enable dynamic BW: -11 [ 31.432925] ath10k_pci :3a:00.0: could not suspend target (-11) [ 33.687090] ath10k_pci :3a:00.0: Unknown eventid: 90118 [ 36.684683] ath10k_pci :3a:00.0: failed to enable dynamic BW: -11 [ 42.685119] ath10k_pci :3a:00.0: could not suspend target (-11) [ 55.191367] ath10k_pci :3a:00.0: Unknown eventid: 90118 [ 58.189447] ath10k_pci :3a:00.0: failed to enable dynamic BW: -11 [ 64.189569] ath10k_pci :3a:00.0: could not suspend target (-11) [ 66.442090] ath10k_pci :3a:00.0: Unknown eventid: 90118 [ 69.441647] ath10k_pci :3a:00.0: failed to enable dynamic BW: -11 [ 75.441641] ath10k_pci :3a:00.0: could not suspend target (-11) [ 88.191952] ath10k_pci :3a:00.0: Unknown eventid: 90118 [
[Bug 1470014] Re: systemd-udevd: Process '/lib/udev/hdparm' failed with exit code 5.
The other bug suggested this could be repeated by running (where sdX is the name of your block device, e.g. sda from /dev/sda): sudo udevadm trigger --action=add /sys/block/sdX --verbose Another way debug this without a reboot for a drive that's not mounted, you can disconnect the device and re-scan to add it. # #Comment: First, figure out which logical port the drive is connected to: # #Comment: In the output, make note of the host0 part. Other output may have host1 etc. # #Comment: you may need to put a sudo in front of readlink. # readlink /sys/block/sdX #e.g. for /dev/sda it would be readlink /sys/block/sda ../devices/pci:00/:00:1f.1/ata1/host0/target0:0:1/0:0:1:0/block/sda # #Comment: Force disconnect the device (you may have to "sudo su -" first, or use sudo with tee): # echo 1 > /sys/block/sdX/device/delete # #Comment: Trigger rescan (you may have to "sudo su -" first, or use sudo with tee). # #Comment: Note host0 matches from the readlink call above: # echo "- - -" > /sys/class/scsi_host/host0/scan If you want to apply the workaround for xenial, you need to comment out both "hdparm_set_option -B254" and the "else" above it in /lib/hdparm/hdparm-functions. If you don't properly comment out the else section, then you'll get something like: systemd-udevd[XXX]: Process '/lib/udev/hdparm' failed with exit code 2. A workaround that didn't work for me was to add "hdparm_set_option -q" on the line before "hdparm_set_option -B254" /lib/hdparm/hdparm- functions . Just changing it to "hdparm_set_options -q -B254" results in the -B254 not getting set as a parameter, which may be good enough for some people. To add some debugging code, add the following to line 2 of /lib/udev/hdparm like suggested in bug 1568474. set -x; exec 2>>/tmp/hdparm.txt When incorrectly commenting out the "-B254" part, you may see something in /tmp/hdparm.txt like: /lib/udev/hdparm: 89: /lib/hdparm/hdparm-functions: Synax error: "fi" unexpected https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795025 says "the -B254 option status is written to the unavailable output and generates the IO error." The correct solution seems to be, as suggested test if the -B option is accepted before using it, having hdparm ignore the error (with a -q on line 88?), or changing the hdparm code's handling of the -B option failing. It would be nice to know when it fails with a warning in syslog instead of this error. It may also be useful to somehow get the output of hdparm going directly to the syslog when there is a non-0 error code, or even adding some information about what the command line was for the statement that failed if /lib/udev/hdparm is allowed to write to syslog. For me this may be a problem that comes and goes as I need to look at older drives where the APM_level is not supported. For the one drive I'm currently looking at I see: user@host:~$ sudo /sbin/hdparm -B254 /dev/sda /dev/sda: Setting Advanced Power Management level to 0xfe (254) HDIO_DRIVE_CMD failed: Input/output error APM_level = not supported user@host:~$ sudo /sbin/hdparm /dev/sda /dev/sda: multcount = 16 (on) IO_support= 1 (32-bit) readonly = 0 (off) readahead = 256 (on) geometry = 25694/255/63, sectors = 234441658, start = 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470014 Title: systemd-udevd: Process '/lib/udev/hdparm' failed with exit code 5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/1470014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1552551] Re: Dell CERC Adapter hangs temporarily until reset. REGRESSION
I've had the same issues after applying patches for 14.10. Had to use recovery to boot and decided to upgrade to fix. This did not help as 16.04 has same issue with "Host adapter" errors on Dell PowerEdge 2800 and CERC controller. OS will not boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1552551 Title: Dell CERC Adapter hangs temporarily until reset. REGRESSION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533631] Re: dhclient killed when DHCPv6 lease is out-of date
I'm getting DOS'd about 20 times a day as a result of this issue. Could a "band-aid" shell script be whipped up by anyone in the know, to physically purge the expired lease files periodically, and posted here? I would gladly set such a script to run as a "cleanup service" or even run it manually, while the proper fix is implemented. Thanks, Jason -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533631 Title: dhclient killed when DHCPv6 lease is out-of date To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1533631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576833] [NEW] cleanly installed win8, left half drive unformatted for mate
Public bug reported: Completely formatted the drive, put windows on half of it and now wanted to dual-boot install mate on the unformatted half of the drive, but the installer crashed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 Date: Fri Apr 29 22:30:43 2016 InstallCmdLine: file=/cdrom/preseed/ubuntu-mate.seed boot=casper initrd=/casper/initrd.lz quiet splash --- LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63 ubuntu-mate xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576833 Title: cleanly installed win8, left half drive unformatted for mate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1576833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430156] [NEW] Boot errors
Public bug reported: After installing ubuntu14.04.1 onto a separate drive in my home built tower which I already had windows 8.1 pro install on another drive. Before the installation of ubuntu the windows 8.1 was working properly. This is not to say or imply that ubuntu is at fault in this process but instead, my lack of complete understanding of what was involved in the process. Subsequently, I've read lots of tutorials and question/answers on Ubuntu One. The most important of which I read only this morning at 3 AM. It said simply that you can't simply re-install ubuntu on an drive one problems have been encountered. At this point I'm using the drive that I originally installed the ubuntu onto with ubuntu installed and running somewhat errantly. To the point. At first I could still boot into windows 8.1, but there were problems with booting ubuntu. The boot menu then began to display with the windows bios boot option missing. However, I could still enter into the bios and select windows from there by selecting its drive. After trying to figure out what happened to the windows option then, I was no longer able to choose windows from the bios boot. I was at least able to boot into ubuntu with great difficulty. As it began to boot there were lots of fails and quit items displayed on the screen. Things have gone from bad to worse, as I attempted to fix the problem. Of course, I assumed the windows was still there on the original drive. I tried deleting the ubuntu OS and re-installing it and then things really went to hell in a hand basket. I am now at the point where, I've been able to re-install ubuntu, but can see the windows 8.1 on either of the other drives that I have installing in the tower. I've used various of the linux sites to seek ways to recover from this disaster, but have not achieve good results. The xorg information that was sent from the latest boot is beyond my level of knowledge at this point. I would appreciate it very much if someone could walk me through the process of recovery. One of the errors messages Found GPt, add bios-boot partition. Another was Comreset failed error-16. These among many. Please excuse, my lack of detail in this matter I've grasping for straws believing that I could retrieve the system on my own. Given enough time I ultimately could, but at this point I'm putting up the white flag. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Mar 9 22:33:56 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7921] InstallationDate: Installed on 2015-02-25 (12 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: MSI MS-7921 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic root=UUID=cb670b6e-0135-4803-9d60-5c1c64cabc36 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-G55 SLI (MS-7921) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.0:bd04/21/2014:svnMSI:pnMS-7921:pvr1.0:rvnMSI:rnZ97-G55SLI(MS-7921):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7921 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Mar 9 22:22:45 2015
[Bug 1420589] [NEW] Wacom Intuos2 stops working at boot after installing Nvidia drivers.
Public bug reported: My Wacom Intuos2 6x8 tablet works out the box on an Ubuntu 14.04 install. After installing the Nvidia drivers and running updates, the tablet stops responding/moving. The only way to get the stylus working again is to add blacklist wacom to the /etc/modprobe.d/blacklist file. And after reboot re-enable the wacom module with: sudo modprobe wacom This is a problem in Ubuntu 14.04 64bit, as well as, Debian Jessie. It seems something is getting confused with udev. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-input-wacom 1:0.23.0-0ubuntu2 [modified: usr/share/X11/xorg.conf.d/50-wacom.conf] ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Tue Feb 10 21:25:51 2015 InstallationDate: Installed on 2015-01-05 (36 days ago) InstallationMedia: Ubuntu MATE 14.04.1 Trusty Tahr - final amd64 (2014) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xf86-input-wacom UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xf86-input-wacom (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1420589 Title: Wacom Intuos2 stops working at boot after installing Nvidia drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1420589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1408149] [NEW] nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build
Public bug reported: I am running Ubuntu 14.04 LTS 64bit release. When I logged in today I got an apport bug notification about the nvidia driver. nvidia-331 kernel module failed to build Everything appears to be working fine though. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.113-0ubuntu0.0.4 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 DKMSKernelVersion: 3.13.0-43-generic Date: Mon Jan 5 18:16:05 2015 InstallationDate: Installed on 2015-01-05 (1 days ago) InstallationMedia: Ubuntu MATE 14.04.1 Trusty Tahr - final amd64 (2014) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package nvidia third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1408149 Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1408149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 912320] Re: DVD CSS decoder
What are you talking about ? On 16/08/14 03:14, Reinhard Tartler wrote: AFAIUI, there is nothing to do for the libdvdread package ** Changed in: libdvdread (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/912320 Title: DVD CSS decoder To manage notifications about this bug go to: https://bugs.launchpad.net/medibuntu/+bug/912320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1207812] Re: [Sony VGN-SR29XN_S] Iphone with iOS 7 does not work on Ubuntu
Hello Iuri Diniz, I'm currently running Linux Mint 13, which is based on 12.04.3 LTS, Precise Pangolin. I've tried sudo apt-get install libgnutls26, and it gives me this message in the terminal (It's pretty long, so I posted it on pastebin) Link: http://pastebin.com/rs2w6kXW Anything else you can do to help? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1207812 Title: [Sony VGN-SR29XN_S] Iphone with iOS 7 does not work on Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1207812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1207812] Re: [Sony VGN-SR29XN_S] Iphone with iOS 7 does not work on Ubuntu
Hi Iuri Diniz, I've tried to install the updated version of libimobiledevice that you posted via the .deb file, and it gives me the following error: Error: Dependency is not satisfiable: libgnutls26 (= 2.12.17-0) Is there any fix that you would know of? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1207812 Title: [Sony VGN-SR29XN_S] Iphone with iOS 7 does not work on Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1207812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184691] Re: nvidia kernel module fails to build with kernel 3.10 or later [In function ‘nv_i2c_del_adapter’:... error: void value not ignored as it ought to be]
After i upgraded and got the black screen and all that...i discovered a way to get my system working again. I just hit Ctrl+Alt+F1 to get to a text console, and used apt-get from there to remove the nvidia drivers (*all* of them), then installed `nvidia-current`. After rebooting, everything was back to normal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184691 Title: nvidia kernel module fails to build with kernel 3.10 or later [In function ‘nv_i2c_del_adapter’:... error: void value not ignored as it ought to be] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1184691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 764912] [NEW] compiz crashed with SIGSEGV in i915UpdateTextureState()
I have sold that computer so I can no longer test it. Since no one else had problems, let's just close it out and assume the new distro fixed it. Don On Saturday, February 16, 2013, Chris Wilson wrote: ** Summary changed: - compiz crashed with SIGSEGV in i915UpdateTextureState() + [mesa] compiz crashed with SIGSEGV in i915UpdateTextureState() -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/764912 Title: [mesa] compiz crashed with SIGSEGV in i915UpdateTextureState() Status in “xserver-xorg-video-intel” package in Ubuntu: Incomplete Bug description: Just booted laptop and plugged in HP Photosmart D7360 printer to try and get drivers. Ubuntu 11.04 Beta 2 32 bit on Toshiba M45-S359 laptop with 1.5G memory and dual boot with Win XP ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: libnux-0.9-0 0.9.44-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Date: Sun Apr 17 21:39:28 2011 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta i386 (20110413) ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xec2ed6: mov0x20c(%eax),%eax PC (0x00ec2ed6) ok source 0x20c(%eax) (0x020c) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nux StacktraceTop: ?? () from /usr/lib/dri/i915_dri.so i915UpdateTextureState () from /usr/lib/dri/i915_dri.so ?? () from /usr/lib/dri/i915_dri.so _tnl_draw_prims () from /usr/lib/dri/libdricore.so _tnl_vbo_draw_prims () from /usr/lib/dri/libdricore.so Title: compiz crashed with SIGSEGV in i915UpdateTextureState() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/764912/+subscriptions -- Don Daniels -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/764912 Title: [mesa] compiz crashed with SIGSEGV in i915UpdateTextureState() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/764912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1062735] Re: ethercodes.dat in arpwatch is out of date
man (section 8) massagevendor contains some notes about how to update it. http://manpages.ubuntu.com/massagevendor In the changelog Steve Langasek vor...@debian.org said: * Revert change in previous NMU that makes /usr/share/arpwatch/ethercodes.dat a conffile; users who need to modify this can use dpkg-divert instead. Closes: #552792, #550233. This seems like it should be handled similarly to the whois database or other periodically updated data (tzdata's probably one of the most visable and most common to get updates). Maybe the freshclam of clamav approach could be taken. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1062735 Title: ethercodes.dat in arpwatch is out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arpwatch/+bug/1062735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 855348] Re: Powertop wont work, it says every time I start it
** Bug watch added: Red Hat Bugzilla #698020 https://bugzilla.redhat.com/show_bug.cgi?id=698020 ** Also affects: powertop (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=698020 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/855348 Title: Powertop wont work, it says every time I start it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powertop/+bug/855348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 855348] Re: Powertop wont work, it says every time I start it
A patch was proposed at: http://comments.gmane.org/gmane.linux.power-management.powertop/2170 It says that if the file exists then it will write to it. It seems that a powertop --calibrate may be required after an empty file is created to get benifit from it. E.g. sudo touch /var/cache/powertop/saved_parameters.powertop as suggested. Note, you want to make sure of the permissions of this file, especially on multi- user systems. powertop --calibrate turns things on and off to test power usage. One suggestion said to let it run for an hour or so after and it will show estimates in a new column. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/855348 Title: Powertop wont work, it says every time I start it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powertop/+bug/855348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 525784] Re: APT should support scanning .iso for packages, as it scans CD-ROMs
Loopback isn't as easy as it used to be. In lucid, apt-cdrom, synaptic, and update-manager are expecting to mount real hardware. I worked around this by something like: sudo mkdir /mnt/image #append mount point information to fstab echo '/ext/precise-dvd-amd64.iso /mnt/image iso9660 user,loop,ro 0 0'/etc/fstab #requires root and plain sudo doesn't work, sudo gedit could be used instead #test: mount /mnt/image ls /mnt/image echo 'Acquire::cdrom::mount /mnt/image; APT::CDROM::NoMount;'/etc/apt/apt.conf.d/30local-cdimage #requires root and plain sudo doesn't work, sudo gedit could be used instead Then I could use the software to mount a cdrom image, though apt-cdrom still didn't work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/525784 Title: APT should support scanning .iso for packages, as it scans CD-ROMs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/525784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452848] Re: u1sdtool crashes when run remotely through ssh
@Timo Thanks for the wrapper script, although I think you need to export DBUS_SESSION_BUS_ADDRESS? This is still an issue in 12.10, would somebody with permissions please consider nominating this for some series? I don't think it is such an unlikely/uncommon use case that you get to work, go to open your document then realise that you forgot to copy it to your U1 sync folder... so you SSH in to your home desktop and copy it to U1... naturally, you might want to check the status of the transfer etc. This is going to keep happening to people, so would be nice if U1 devs would commit to fixing it _eventually_ which does not seem to be the case at present. Just worried that this feature request has gotten lost is all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/452848 Title: u1sdtool crashes when run remotely through ssh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntuone-client/+bug/452848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1015388] [NEW] applet.py crashed with KeyError in refresh()
*** This bug is a duplicate of bug 768237 *** https://bugs.launchpad.net/bugs/768237 Public bug reported: I don't know what happened except for the crash message. This happened a while after a resume from hibernate. The printer is on, but I'm not sure about he state of cups or the printer. There's a job stuck in the queue that I can see with the printer applet on the taskbar even after this crash. ProblemType: Crash DistroRelease: Ubuntu 10.04 Package: system-config-printer-gnome 1.2.0+20100408-0ubuntu5.2 ProcVersionSignature: Ubuntu 2.6.32-41.90-generic 2.6.32.59+drm33.24 Uname: Linux 2.6.32-41-generic x86_64 Architecture: amd64 CupsErrorLog: Date: Tue Jun 19 21:44:06 2012 ExecutablePath: /usr/share/system-config-printer/applet.py InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) InterpreterPath: /usr/bin/python2.6 Lpstat: device for Brother-MFC-7840W: lpd://BRN001BA930D2EC/BINARY_P1 MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC PackageArchitecture: all Papersize: letter PpdFiles: Brother-MFC-7840W: Brother MFC-7840W BR-Script3 , Postscript-Brother 20101122 (OpenPrinting LSB 3.2) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-41-generic root=UUID=c1d3ef97-e09e-4499-8fdf-f55f8c7f51cd ro ProcCmdline: python /usr/share/system-config-printer/applet.py ProcEnviron: LANG=en_CA.utf8 SHELL=/bin/bash PythonArgs: ['/usr/share/system-config-printer/applet.py'] SourcePackage: system-config-printer Title: applet.py crashed with KeyError in refresh() UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare dmi.bios.date: 08/31/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.33 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3627 dmi.board.vendor: Quanta dmi.board.version: 18.42 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnQuanta:rn3627:rvr18.42:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard ** Affects: system-config-printer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1015388 Title: applet.py crashed with KeyError in refresh() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1015388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1015388] Re: applet.py crashed with KeyError in refresh()
*** This bug is a duplicate of bug 768237 *** https://bugs.launchpad.net/bugs/768237 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1015388 Title: applet.py crashed with KeyError in refresh() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1015388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 768237] Re: applet.py crashed with KeyError in refresh()
Hi,
Seems straight forward in where the problem is (though maybe not the root
cause):
...
File /usr/share/system-config-printer/monitor.py, line 553, in refresh
if job['job-state'] cups.IPP_JOB_CANCELED:
KeyError: 'job-state'
...
Relevant code:
545 debugprint (Created subscription %d % self.sub_id)
546
547 if self.monitor_jobs:
548 jobs = self.jobs.copy ()
549 if self.which_jobs not in ['all', 'completed']:
550 # Filter out completed jobs.
551 filtered = {}
552 for jobid, job in jobs.iteritems ():
553 if job['job-state'] cups.IPP_JOB_CANCELED:
554 filtered[jobid] = job
555 jobs = filtered
So job exists but doesn't have a state. I guess a check for job having
that key could be done, but I don't know whether filtered is needed.
If you need debugging turned on, I may be able to help. I'd prefer
instructions as I don't want to look it up. As it's python I could even
add some code, but again I don't want to spend much time looking things
up right now so some direction would speed things up for us.
Thanks,
Drew Daniels
Blog: http://www.boxheap.net/ddaniels/blog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/768237
Title:
applet.py crashed with KeyError in refresh()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/768237/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 206303] Re: needs upgrade from version 0.3.1
I contacted the Debian maintainer (Igor Stroh) a couple of times and had a reply from him on 8th Apr, 2011 then latest reply on 20th Dec 2011. He said I'm willing to RFA the ldap2dns package, no problems here but still no further action. So I've been using my own updated package (https://github.com/wdaniels/ldap2dns/tree/ubuntu), which I just rebuilt for precise and separated in a PPA here: https://launchpad.net/~wdaniels/+archive/ldap2dns I got in touch with Ben Klang (upstream maintainer) who was very amenable to helping get this updated in Debian (he quickly fixed a license issue that I raised) and I contacted Björn Boschman who first tried to get a NMU done via Debian mentors, he was still willing to help maintain the package at that time (Apr 2011). I would gladly help maintain it via the mentors process also, but not 100% sure the best way to move things forward either via Debian or Ubuntu. If an old version of the package is still in Debian, is it OK to try to update it via REVU, MOTU? Probably the updated package still needs work but the original is far from perfect and I can't invest more time in this until somebody is willing to mentor and maybe NMU. Hope the PPA version helps someone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/206303 Title: needs upgrade from version 0.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ldap2dns/+bug/206303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004938] [NEW] This is the same as Activity log for bug #891968
Public bug reported: Basically, I am having exactly the same issue. I've just bought an Acer Aspire AX3470 Desktop PC (AMD A6 3420 2.2GHz, 6GB RAM, 500GB HDD] which has an AMD Radeon HD6530D integrated graphics. I've downloaded a fresh 21.04 Ununtu. created a boot usb and the screen goes blank pretty much straight away. Any help / fixes would be appreciated. Thanks ** 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/1004938 Title: This is the same as Activity log for bug #891968 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1004938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 963615] [NEW] clementine crashed with SIGABRT in raise()
Private bug reported: I had clementine playing music from my samba server, with the visualizations on. Clementine eventually froze then crashed. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: clementine 1.0.1+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Fri Mar 23 21:40:01 2012 ExecutablePath: /usr/bin/clementine InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) ProcCmdline: clementine ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: clementine Title: clementine crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: clementine (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963615 Title: clementine crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clementine/+bug/963615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924739] Re: after upgrade from oneiric to precise, previous squid config unused, cannot be used when relocated
Some options could be translated. http://www.squid-cache.org/Doc/config/ shows what's compatible and what's not. The release notes list which tags have been added, changed and removed. E.g. header_access was replaced by request_header_access and reply_header_access so the one tag becomes two for more fine grained control. A pointer to the Squid release notes is what Red Hat did for RHEL 6.0's notes: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Migration_Planning_Guide/ch04s12.html And I think it was referenced elsewhere too. Drew Daniels Blog: http://www.boxheap.net/ddaniels/blog/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/924739 Title: after upgrade from oneiric to precise, previous squid config unused, cannot be used when relocated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/924739/+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 924739] Re: after upgrade from oneiric to precise, previous squid config unused, cannot be used when relocated
Some options could be translated. http://www.squid-cache.org/Doc/config/ shows what's compatible and what's not. The release notes list which tags have been added, changed and removed. E.g. header_access was replaced by request_header_access and reply_header_access so the one tag becomes two for more fine grained control. A pointer to the Squid release notes is what Red Hat did for RHEL 6.0's notes: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Migration_Planning_Guide/ch04s12.html And I think it was referenced elsewhere too. Drew Daniels Blog: http://www.boxheap.net/ddaniels/blog/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924739 Title: after upgrade from oneiric to precise, previous squid config unused, cannot be used when relocated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/924739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 912320] Re: DVD CSS decoder
Hi, Gauvain, has not gone well, messed up my computer, can still open my important things and can view DVD that predates the most recent CSS encoding. As soon as I request anything, the no entry symbol appears, screentop right. I guess I misread something and typed in a bad command, a sort out job for Sunday or Monday. Thanks, sorry I messed up, I have to clean up before I can do anything else. Regards, Michael. On 07/01/12 15:53, Gauvain Pocentek wrote: Hi, There's been a new libdvdcss release, which is available in the medibuntu -staging repositories (lucid-staging seems to be the one you need). Could you upgrade your package to see if it fixes the problem? Thanks. ** Changed in: medibuntu Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/912320 Title: DVD CSS decoder To manage notifications about this bug go to: https://bugs.launchpad.net/medibuntu/+bug/912320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 912320] [NEW] DVD CSS decoder
Public bug reported: sudo apt-get install libdvd read4 sudo/user/share/doc/libdvdread4/install-css.sh Source, RestrictedFormats/PlayingDVD - Community Ubuntu The instruction does not decode the latest Warner DVD's, they changed their CSS around 2-3 years ago. Recent copy software which removes CSS will remove the Warner CSS but an alternative to creating a new Region 0 disc would be better. ( O/S is Ubuntu 10.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/912320 Title: DVD CSS decoder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/912320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 912320]
Application used was Movie Player. Regards, Michael On 05/01/12 16:15, Ubuntu Foundation's Bug Bot wrote: Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/912320/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/912320 Title: DVD CSS decoder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/912320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 568090] Re: ath5k should be loaded with nohwcrypt parameter
My card is indeed an Askey. 02:04.0 Ethernet controller: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01) Subsystem: Askey Computer Corp. Device 7094 Flags: bus master, medium devsel, latency 168, IRQ 20 Memory at c020 (32-bit, non-prefetchable) [size=64K] Capabilities: access denied Kernel driver in use: ath5k -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/568090 Title: ath5k should be loaded with nohwcrypt parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/568090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857810] [NEW] Snapped Windows Detach when accessing from them from the Unity launcher.
Public bug reported: If you edge snap a window in Unity, go to another workspace, then attempt to go back to the initial window by clicking the icon in the unity launcher, compiz will not switch workspaces but will instead detach the application resulting in the window crossing over into other workspaces because of the wrapping. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: compiz 1:0.9.5.94+bzr20110919-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.agp.gpu: Fast Writes:Supported SBA:Supported AGP Rates: 8x 4x Registers: 0xff000e1b:0x1f000302 .proc.driver.nvidia.agp.host.bridge: Host Bridge:PCI device 1106:3188 Fast Writes:Supported SBA:Supported AGP Rates: 8x Registers: 0x1f000a1a:0x0b02 .proc.driver.nvidia.agp.status: Status: Enabled Driver: AGPGART AGP Rate: 8x Fast Writes:Disabled SBA:Enabled .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 280.13 Wed Jul 27 16:55:43 PDT 2011 GCC version: gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Fri Sep 23 17:39:10 2011 DistUpgraded: Fresh install DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: nvidia-current, 280.13, 3.0.0-11-generic, i686: installed nvidia-current, 280.13, 3.0.0-9-generic, i686: installed GraphicsCard: nVidia Corporation NV44A [GeForce 6200] [10de:0221] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:a401] InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110901) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic root=UUID=1610695b-d0a5-4d0a-8d53-39b8c4284b44 ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 06/17/2005 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1007.003 dmi.board.name: K8VSEDX dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: Rev 2.00 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1007.003:bd06/17/2005:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnK8VSEDX:rvrRev2.00:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.5.94+bzr20110919-0ubuntu1 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 oneiric ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857810 Title: Snapped Windows Detach when accessing from them from the Unity launcher. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/857810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857810] Re: Snapped Windows Detach when accessing from them from the Unity launcher.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857810 Title: Snapped Windows Detach when accessing from them from the Unity launcher. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/857810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 828684] Re: [i965gm] False GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000100
Update - tested Suspend which works correctly and backlight comes back on. However then get errors with gnome-power-manager showing 2 battery icons (one empty one in red) and the System cog shows Restart to complete updates in red also. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/828684 Title: [i965gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver/+bug/828684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 828684] Re: [i965gm] False GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000100
Unfortunately the brightness keys on my laptop won't bring the screen back so still waiting for a solution! As you can imagine, this is getting very annoying now -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/828684 Title: [i965gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/828684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 844633] [NEW] Screen dim unreadable on resume from lock screen [i915gm] GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000100 render.IPEHR: 0x01000000
*** This bug is a duplicate of bug 828684 *** https://bugs.launchpad.net/bugs/828684 Public bug reported: After timeout for lock screen, the display is barely visible and the backlight does not appear to be on. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic i686 .tmp.unity.support.test.0: Architecture: i386 Chipset: i915gm CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Thu Sep 8 09:20:16 2011 DistUpgraded: Log time: 2011-09-07 11:49:48.636957 DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: vboxhost, 4.0.12, 2.6.38-11-generic, i686: installed vboxhost, 4.0.12, 3.0.0-10-generic, i686: installed DuplicateSignature: [i915gm] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100 render.IPEHR: 0x0100 Ubuntu 11.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: I just need an easy workaround GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company NX6110/NC6120 [103c:099c] Subsystem: Hewlett-Packard Company NX6110/NC6120 [103c:099c] InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) InterpreterPath: /usr/bin/python2.7 MachineType: Hewlett-Packard HP COMPAQ NC6120 (PT597AA#ABN) PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic root=UUID=9f12fc6a-8194-4ab1-9e94-52e0bdb4fd7d ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.6+7ubuntu6 libdrm2 2.4.26-1ubuntu1 xserver-xorg-video-intel 2:2.15.901-1ubuntu2 SourcePackage: xserver-xorg-video-intel Title: [i915gm] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100 render.IPEHR: 0x0100 UpgradeStatus: Upgraded to oneiric on 2011-09-07 (0 days ago) UserGroups: dmi.bios.date: 07/27/2006 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68DTD Ver. F.14 dmi.board.name: 099C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 39.2A dmi.chassis.asset.tag: CNU5241R9G dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68DTDVer.F.14:bd07/27/2006:svnHewlett-Packard:pnHPCOMPAQNC6120(PT597AA#ABN):pvrF.14:rvnHewlett-Packard:rn099C:rvrKBCVersion39.2A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP COMPAQ NC6120 (PT597AA#ABN) dmi.product.version: F.14 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.5.92+bzr2791-0ubuntu2 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash compiz-0.9 freeze i386 oneiric reproducible single-occurrence ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/844633 Title: Screen dim unreadable on resume from lock screen [i915gm] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100 render.IPEHR: 0x0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/844633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 844633] Re: Screen dim unreadable on resume from lock screen [i915gm] GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000100 render.IPEHR: 0x01000000
*** This bug is a duplicate of bug 828684 *** https://bugs.launchpad.net/bugs/828684 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/844633 Title: Screen dim unreadable on resume from lock screen [i915gm] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100 render.IPEHR: 0x0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/844633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 828684] Re: [i965gm] False GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000100
I have the same issue with a HP NC6120 laptop - all fine with 11.04 and earlier. It happens every time the system sleeps - the screen goes blank but I know it is still working as I have a pixel fault on the LCD screen showing a solid vertical line which has been there for years. After a few minutes the screen goes almost completely dead - i.e. the backlight has been turned off and the dead pixel line is not visible. When the system resumes the password unlock screen appears but I cannot really see it. I then enter my password then go blindly to the System menu top right, cursor down 10 times to the Shutdown menu and select Shutdown by pressing enter or left cursor across twice for Restart. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/828684 Title: [i965gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/828684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 828684] Re: [i965gm] False GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000100
Forgot to add that this is NOT a single occurrence as it happens every time! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/828684 Title: [i965gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/828684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 828684] Re: [i965gm] False GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000100
After a few more tests it happens exactly 10 minutes after the lock screen so looks like a suspend issue on the GPU. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/828684 Title: [i965gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/828684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543183] Re: Updating system certificates requires rebuild
** Bug watch added: Mozilla Bugzilla #449498 https://bugzilla.mozilla.org/show_bug.cgi?id=449498 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=449498 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/543183 Title: Updating system certificates requires rebuild To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/543183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543183] Re: Updating system certificates requires rebuild
** Bug watch added: Red Hat Bugzilla #546221 https://bugzilla.redhat.com/show_bug.cgi?id=546221 ** Also affects: firefox (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=546221 Importance: Unknown Status: Unknown ** Tags added: patch ** Patch added: F14 1.9.2 patch to allow use of system certificate store https://bugs.launchpad.net/fedora/+source/firefox/+bug/543183/+attachment/2374493/+files/fc14-mozilla-1.9.2-use_certificate_store.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/543183 Title: Updating system certificates requires rebuild To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/543183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543183] Re: Updating system certificates requires rebuild
The attached patch is not a full solution. Removing the compiled in certificates would be needed, but this might be good enough for basic enterprise needs to add root certificates to FireFox. Drew Daniels http://www.boxheap.net/ddaniels/blog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/543183 Title: Updating system certificates requires rebuild To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/543183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543183] Re: Updating system certificates requires rebuild
To remove fraudulent certificates like this recent one: https://blog.mozilla.com/security/2011/08/29/fraudulent-google-com-certificate/ a rebuild is required. See the discussion at lwn.net at: http://lwn.net/Articles/456798/#Comments Note the comment about how Internet Explorer doesn't have to be rebuilt and the Microsoft Advisory at: https://www.microsoft.com/technet/security/advisory/2607712.mspx Maybe better Certificate Revocation List (CRL) support is needed. I haven't yet submitted a bug upstream as Ubuntu may just want to fork for better enterprise support. Drew Daniels http://www.boxheap.net/ddaniels/blog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/543183 Title: Updating system certificates requires rebuild To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/543183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 835818] Re: Can't boot qemu w/o kvm (no boot=on param, upstream patch)
Hi,
I'm willing to rebuild and test the fix myself when I get some time, but I
thought it might be faster and easier for a maintainer to do.
I apologise if this comment seems negative, it's not intended as such.
1) lucid's qemu does not seem to support boot=on, but maybe my testing
is wrong? Certainly libvirt's upstream says that not all versions of
qemu do even though the documentation may say that it does. I can get
ReactOS to boot without this parameter, but I can't get it to boot with
this parameter. I isolated the commands to that one difference.
2) qemu-kvm does not require kvm. Many peices of hardware, including
mine don't support kvm. Perhaps this is what's misleading you.
3) I did attach a patch from upstream. I figured attaching a patch would
make it easier to spot rather than having to see that there's a link to
a patch in the git repository. It looks like the patch doesn't effect
qemu when in kvm mode, and it looks like lucid's qemu without kvm
doesn't support boot=on (but perhaps my testing is flawed? See point 1).
4) I'm using lucid. Is maverick's libvirt already in a supported
backported archive? I don't see it, but I do see a bug that says it's
not there: https://bugs.launchpad.net/lucid-backports/+bug/724026
5) I've added the tags patch and patch-accepted-upstream. I hope
that's appropriate.
Here's the metadata about the patch:
- cut -
author Daniel Veillard veill...@redhat.com
Fri, 30 Jul 2010 14:38:48 + (16:38 +0200)
committer Daniel Veillard veill...@redhat.com
Fri, 30 Jul 2010 14:38:48 + (16:38 +0200)
Basically the 'boot=on' boot selection device is something present in
KVM but not in upstream QEmu, as a result if we boot a QEmu domain
without KVM acceleration we must disable boot=on ... even if the front
end kvm binary expose that capability in the help page.
* src/qemu/qemu_conf.c: in qemudBuildCommandLine if -no-kvm is passed, then
deactivate QEMUD_CMD_FLAG_DRIVE_BOOT
--
Here's the patch inline:
-
--- a/src/qemu/qemu_conf.c
+++ b/src/qemu/qemu_conf.c
@@ -3707,9 +3707,17 @@ int qemudBuildCommandLine(virConnectPtr conn,
* 2. The qemu binary has the -no-kvm flag
*/
if ((qemuCmdFlags QEMUD_CMD_FLAG_KVM)
-def-virtType == VIR_DOMAIN_VIRT_QEMU)
+def-virtType == VIR_DOMAIN_VIRT_QEMU) {
disableKVM = 1;
+/*
+ * do not use boot=on for drives when not using KVM since this
+ * is not supported at all in upstream QEmu.
+ */
+if (qemuCmdFlags QEMUD_CMD_FLAG_DRIVE_BOOT)
+qemuCmdFlags -= QEMUD_CMD_FLAG_DRIVE_BOOT;
+}
+
/* Should explicitly enable KVM if
* 1. Guest domain is 'kvm'
* 2. The qemu binary has the -enable-kvm flag
-
Drew Daniels
** Tags added: patch patch-accepted-upstream
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/835818
Title:
Can't boot qemu w/o kvm (no boot=on param, upstream patch)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/835818/+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 835818] Re: Can't boot qemu w/o kvm (no boot=on param, upstream patch)
** Tags added: lucid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/835818 Title: Can't boot qemu w/o kvm (no boot=on param, upstream patch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/835818/+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 835818] Re: Can't boot qemu w/o kvm (no boot=on param, upstream patch)
Hi,
I'm willing to rebuild and test the fix myself when I get some time, but I
thought it might be faster and easier for a maintainer to do.
I apologise if this comment seems negative, it's not intended as such.
1) lucid's qemu does not seem to support boot=on, but maybe my testing
is wrong? Certainly libvirt's upstream says that not all versions of
qemu do even though the documentation may say that it does. I can get
ReactOS to boot without this parameter, but I can't get it to boot with
this parameter. I isolated the commands to that one difference.
2) qemu-kvm does not require kvm. Many peices of hardware, including
mine don't support kvm. Perhaps this is what's misleading you.
3) I did attach a patch from upstream. I figured attaching a patch would
make it easier to spot rather than having to see that there's a link to
a patch in the git repository. It looks like the patch doesn't effect
qemu when in kvm mode, and it looks like lucid's qemu without kvm
doesn't support boot=on (but perhaps my testing is flawed? See point 1).
4) I'm using lucid. Is maverick's libvirt already in a supported
backported archive? I don't see it, but I do see a bug that says it's
not there: https://bugs.launchpad.net/lucid-backports/+bug/724026
5) I've added the tags patch and patch-accepted-upstream. I hope
that's appropriate.
Here's the metadata about the patch:
- cut -
author Daniel Veillard veill...@redhat.com
Fri, 30 Jul 2010 14:38:48 + (16:38 +0200)
committer Daniel Veillard veill...@redhat.com
Fri, 30 Jul 2010 14:38:48 + (16:38 +0200)
Basically the 'boot=on' boot selection device is something present in
KVM but not in upstream QEmu, as a result if we boot a QEmu domain
without KVM acceleration we must disable boot=on ... even if the front
end kvm binary expose that capability in the help page.
* src/qemu/qemu_conf.c: in qemudBuildCommandLine if -no-kvm is passed, then
deactivate QEMUD_CMD_FLAG_DRIVE_BOOT
--
Here's the patch inline:
-
--- a/src/qemu/qemu_conf.c
+++ b/src/qemu/qemu_conf.c
@@ -3707,9 +3707,17 @@ int qemudBuildCommandLine(virConnectPtr conn,
* 2. The qemu binary has the -no-kvm flag
*/
if ((qemuCmdFlags QEMUD_CMD_FLAG_KVM)
-def-virtType == VIR_DOMAIN_VIRT_QEMU)
+def-virtType == VIR_DOMAIN_VIRT_QEMU) {
disableKVM = 1;
+/*
+ * do not use boot=on for drives when not using KVM since this
+ * is not supported at all in upstream QEmu.
+ */
+if (qemuCmdFlags QEMUD_CMD_FLAG_DRIVE_BOOT)
+qemuCmdFlags -= QEMUD_CMD_FLAG_DRIVE_BOOT;
+}
+
/* Should explicitly enable KVM if
* 1. Guest domain is 'kvm'
* 2. The qemu binary has the -enable-kvm flag
-
Drew Daniels
** Tags added: patch patch-accepted-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/835818
Title:
Can't boot qemu w/o kvm (no boot=on param, upstream patch)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/835818/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 512964] Re: gtkpod crashes with SIGSEGV in gdk_window_set_geometry_hints
** Tags added: patch-accepted-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/512964 Title: gtkpod crashes with SIGSEGV in gdk_window_set_geometry_hints To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtkpod/+bug/512964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 455461] Re: Sound Juicer depends on deprecated libmusicbrainz4
Re: comment #26 Just to be clear to others: Upstream's libmusicbrainz version 4 is not libmusicbrainz4c2a in Debian or Ubuntu. lucid's (and Debian's) package libmusicbrainz4c2a (2.1.5-4)'s short description is Second generation incarnation of the CD Index - library. Drew Daniels Blog: http://www.boxheap.net/ddaniels/blog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/455461 Title: Sound Juicer depends on deprecated libmusicbrainz4 To manage notifications about this bug go to: https://bugs.launchpad.net/sound-juicer/+bug/455461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 516928] Re: Disabled wireless is shown, but doesn't work
Fixed in lucid. I hope Fix Committed is the right status to set. Karmic is likely still affected, but might not be supported anymore. ** Changed in: network-manager (Ubuntu) Status: New = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/516928 Title: Disabled wireless is shown, but doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/516928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 504547] Re: Wrong Reboot Required for kmod:wl on livecd
This may not be directly related to others, but: https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx#b43%20-%20Internet%20access says: LiveCD/LiveUSB Step 3. For temporary use with the LiveCD and LiveUSB environments, instead of a computer restart, in a terminal issue the following commands: ~$ sudo modprobe -r b43 ssb ~$ sudo modprobe b43 Note: Allow several seconds for the network manager to scan for available networks before attempting a connection. Drew Daniels http://www.boxheap.net/ddaniels/blog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/504547 Title: Wrong Reboot Required for kmod:wl on livecd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/504547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 835818] Re: Can't boot qemu w/o kvm (no boot=on param, upstream patch)
** Tags added: lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/835818 Title: Can't boot qemu w/o kvm (no boot=on param, upstream patch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/835818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 835818] [NEW] Can't boot qemu w/o kvm (no boot=on param, upstream patch)
Public bug reported: I can't boot ReactOS's qemu when using libvirt, but I can from the command line when I remove the -drive parameter's boot=on, text (along with vnc and -S to get it to show a window and start outside of libvirt). http://sourceforge.net/projects/reactos/files/ReactOS/0.3.13/ReactOS-0.3.13-REL-qemu.zip/download The problem *seems* to be patched upstream at: http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=e7da872294bd1cfaa9733e1292476221659ab47b The git tree shows version 0.8.2 for this patch so Lucid is affected, maverick and later likely aren't affected. Drew Daniels Blog: http://www.boxheap.net/ddaniels/blog ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/835818 Title: Can't boot qemu w/o kvm (no boot=on param, upstream patch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/835818/+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 835818] Re: Can't boot qemu w/o kvm (no boot=on param, upstream patch)
** Patch added: Do not activate boot=on on devices when not using KVM (by Daniel Veillard) https://bugs.launchpad.net/bugs/835818/+attachment/2324811/+files/qemu-no-kvm-do-not-use-drive-boot-on-parameter.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/835818 Title: Can't boot qemu w/o kvm (no boot=on param, upstream patch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/835818/+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 835818] [NEW] Can't boot qemu w/o kvm (no boot=on param, upstream patch)
Public bug reported: I can't boot ReactOS's qemu when using libvirt, but I can from the command line when I remove the -drive parameter's boot=on, text (along with vnc and -S to get it to show a window and start outside of libvirt). http://sourceforge.net/projects/reactos/files/ReactOS/0.3.13/ReactOS-0.3.13-REL-qemu.zip/download The problem *seems* to be patched upstream at: http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=e7da872294bd1cfaa9733e1292476221659ab47b The git tree shows version 0.8.2 for this patch so Lucid is affected, maverick and later likely aren't affected. Drew Daniels Blog: http://www.boxheap.net/ddaniels/blog ** Affects: libvirt (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/835818 Title: Can't boot qemu w/o kvm (no boot=on param, upstream patch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/835818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 835818] Re: Can't boot qemu w/o kvm (no boot=on param, upstream patch)
** Patch added: Do not activate boot=on on devices when not using KVM (by Daniel Veillard) https://bugs.launchpad.net/bugs/835818/+attachment/2324811/+files/qemu-no-kvm-do-not-use-drive-boot-on-parameter.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/835818 Title: Can't boot qemu w/o kvm (no boot=on param, upstream patch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/835818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787475] Re: Rhythmbox [0.12.8] [0.12.5] Not Fetching Album Information From MusicBrainz
** Bug watch added: GNOME Bug Tracker #650848 https://bugzilla.gnome.org/show_bug.cgi?id=650848 ** Also affects: rhythmbox via https://bugzilla.gnome.org/show_bug.cgi?id=650848 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/787475 Title: Rhythmbox [0.12.8] [0.12.5] Not Fetching Album Information From MusicBrainz To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/787475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 820703] [NEW] safe_eval() incompatible with python2.7's bytecode
Public bug reported: Package needs updating to incorporate the patch from Bug #644267. Essential functionality of the application is broken without it (e.g. validate an invoice). ** Affects: openerp-server (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/820703 Title: safe_eval() incompatible with python2.7's bytecode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openerp-server/+bug/820703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787475] Re: Rhythmbox [0.12.8] [0.12.5] Not Fetching Album Information From MusicBrainz
The patch for sound-juicer adds three new direct build dependencies which includes two packages from universe. This means some sort of request to pull these packages into lucid's main may be required. libmusicbrainz4-dev is in main, libmusicbrainz3-dev is in universe for lucid. libmusicbrainz3-dev is in main as of natty. libdiscid0-dev is in universe for lucid, but in main for natty. I don't know if this was a sound-juicer specific dependency. libneon27-dev is in main, but is it required to fix rhythmbox? Drew Daniels Blog: http://www.boxheap.net/ddaniels/blog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787475 Title: Rhythmbox [0.12.8] [0.12.5] Not Fetching Album Information From MusicBrainz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/787475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 455461] Re: Sound Juicer depends on deprecated libmusicbrainz4
As mentioned in bug #732892 and #788921, this bug can trigger a crash bug in sound-juicer. Though that's a separate bug, it's worth mentioning here as well. Basically the crash seems to be caused by no tag information being entered or pulled, and the user trying to Read in the CD. I can't seem to see that anyone has nominated this for a stable release update (sru) nor how to in Launchpad. Drew Daniels Blog: http://www.boxheap.net/~ddaniels/blog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/455461 Title: Sound Juicer depends on deprecated libmusicbrainz4 To manage notifications about this bug go to: https://bugs.launchpad.net/sound-juicer/+bug/455461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 752215] Re: plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
It's hard to tell if this bug affects me but it seems to. On Lucid, I get a different offset (line number): Segfault happened at: 0x7f08b9e1109c ply_event_loop_process_pending_events+508: test %r12d,0x8(%r13) PC (0x7f08b9e1109c) ok source %r12d ok destination 0x8(%r13) (0x0008) not located in a known VMA region (needed writable region)! libplymouth2 0.8.2-2ubuntu2.2 plymouth 0.8.2-2ubuntu2.2 I may also just be hitting the bug that apport takes me to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745 I don't want to ignore this crash as it happens quite regularly after boot now wheras it didn't before. Thanks, Drew Daniels Resume: http://www.boxheap.net/ddaniels/resume.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/752215 Title: plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/752215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 717166] Re: Broken with v4 isc-dhcp-server in Natty
The error message was like this:
dhcpd.c(473): trace_begin: //var/run/eucalyptus/net/euca-dhcp.trace:
Permission denied
I had that copied somewhere, but unfortunately I deleted all the logs
yesterday and I don't even recall exactly which log that came from now
(sorry).
In any case, I can no longer reproduce that particular problem, even
after removing dac_override from the profile :S
But the other problem (and the original subject of this bug) still
remains (for me, using MANAGED mode):
---
root@whirlpool:~/debs# /usr/sbin/dhcpd -cf
//var/run/eucalyptus/net/euca-dhcp.conf -lf
//var/run/eucalyptus/net/euca-dhcp.leases -pf
//var/run/eucalyptus/net/euca-dhcp.pid -tf
//var/run/eucalyptus/net/euca-dhcp.trace eucabr10 eth0.2187
Internet Systems Consortium DHCP Server 4.1.1-P1
Copyright 2004-2010 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
WARNING: Overwriting trace file //var/run/eucalyptus/net/euca-dhcp.trace
WARNING: Host declarations are global. They are not limited to the scope you
declared them in.
Wrote 0 deleted host decls to leases file.
Wrote 0 new dynamic host decls to leases file.
Wrote 0 leases to leases file.
No subnet declaration for eth0.2187 (169.254.169.254).
** Ignoring requests on eth0.2187. If this is not what
you want, please write a subnet declaration
in your dhcpd.conf file for the network segment
to which interface eth0.2187 is attached. **
No subnet declaration for eucabr10 (no IPv4 addresses).
** Ignoring requests on eucabr10. If this is not what
you want, please write a subnet declaration
in your dhcpd.conf file for the network segment
to which interface eucabr10 is attached. **
Not configured to listen on any interfaces!
---
root@whirlpool:~/debs# cat /var/run/eucalyptus/net/euca-dhcp.conf
# automatically generated config file for DHCP server
default-lease-time 1200;
max-lease-time 1200;
ddns-update-style none;
shared-network euca {
subnet 10.32.8.0 netmask 255.255.255.0 {
option subnet-mask 255.255.255.0;
option broadcast-address 10.32.8.255;
option domain-name-servers 127.0.0.1, 10.32.8.1;
option routers 10.32.8.1;
option interface-mtu 1496;
}
host node-10.32.8.2 {
hardware ethernet D0:0D:4E:02:07:90;
fixed-address 10.32.8.2;
}
}
---
I have tried using isc-dhcp version 4.1.1-P1-15ubuntu9 (latest) as well as
specifically 15ubuntu6 where the patch was first applied. I also tried building
it myself to make extra sure that the patch is applied...I still get the same
problem.
---
root@whirlpool:~/src/getifaddrs# dpkg -l 'isc-dhcp*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++---
rc isc-dhcp-client 4.1.1-P1-15ubuntu5 ISC DHCP client
ii isc-dhcp-common 4.1.1-P1-15ubuntu9 common files used by all
the isc-dhcp* packages
ii isc-dhcp-server 4.1.1-P1-15ubuntu9 ISC DHCP server for
automatic IP address assignment
un isc-dhcp-server-ldap none (no description available)
---
Yet Dan's code, which _should_ be in dhcpd, looks to work OK on this
system:
---
root@whirlpool:~/src/getifaddrs# ./a.out
INTERFACE=lo INTERFACE_BEFORE_getnameinfo=lo INTERFACE_AFTER_getnameinfo=lo
SCRUBBEDINTERFACE=lo ADDR=127.0.0.1
INTERFACE=eth0 INTERFACE_BEFORE_getnameinfo=eth0
INTERFACE_AFTER_getnameinfo=eth0 SCRUBBEDINTERFACE=eth0 ADDR=a.b.c.211
INTERFACE=eth0 INTERFACE_BEFORE_getnameinfo=eth0
INTERFACE_AFTER_getnameinfo=eth0 SCRUBBEDINTERFACE=eth0 ADDR=x.y.z.220
INTERFACE=eth0 INTERFACE_BEFORE_getnameinfo=eth0
INTERFACE_AFTER_getnameinfo=eth0 SCRUBBEDINTERFACE=eth0 ADDR=x.y.z.221
INTERFACE=eth0 INTERFACE_BEFORE_getnameinfo=eth0
INTERFACE_AFTER_getnameinfo=eth0 SCRUBBEDINTERFACE=eth0 ADDR=x.y.z.223
INTERFACE=eth0:pub INTERFACE_BEFORE_getnameinfo=eth0
INTERFACE_AFTER_getnameinfo=eth0 SCRUBBEDINTERFACE=eth0
ADDR=instance.public.ip.address
INTERFACE=eth0.2187 INTERFACE_BEFORE_getnameinfo=eth0.2187
INTERFACE_AFTER_getnameinfo=eth0.2187 SCRUBBEDINTERFACE=eth0.2187
ADDR=169.254.169.254
INTERFACE=eth0.2187 INTERFACE_BEFORE_getnameinfo=eth0.2187
INTERFACE_AFTER_getnameinfo=eth0.2187 SCRUBBEDINTERFACE=eth0.2187 ADDR=10.0.0.1
INTERFACE=eucabr10:priv INTERFACE_BEFORE_getnameinfo=eucabr10
INTERFACE_AFTER_getnameinfo=eucabr10 SCRUBBEDINTERFACE=eucabr10 ADDR=10.32.8.1
---
[NB: public IPs censored]
So it _should_ match the eucabr10 ADDR=10.32.8.1 correctly to the
config subnet 10.32.8.0 netmask 255.255.255.0, but it instead it says
No subnet declaration for eucabr10 (no IPv4 addresses). as it did
before. I don't recall now whether I actually tested the patch
previously, or just Dan's getifaddrs snippet, but I was
[Bug 717166] Re: Broken with v4 isc-dhcp-server in Natty
Additional info: -- root@whirlpool:~# ip addr show 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:25:90:13:44:a4 brd ff:ff:ff:ff:ff:ff inet a.b.c.211/24 brd 188.165.231.255 scope global eth0 inet x.y.z.220/32 scope global eth0 inet x.y.z.221/32 scope global eth0 inet x.y.z.223/32 scope global eth0 inet instance.public.ip.address/32 scope global eth0:pub inet6 fe80::225:90ff:fe13:44a4/64 scope link valid_lft forever preferred_lft forever 3: eth1: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 00:25:90:13:44:a5 brd ff:ff:ff:ff:ff:ff 4: eth0.2187@eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UP link/ether 00:25:90:13:44:a4 brd ff:ff:ff:ff:ff:ff inet 169.254.169.254/32 scope link eth0.2187 inet 10.0.0.1/8 scope global eth0.2187 inet6 fe80::225:90ff:fe13:44a4/64 scope link valid_lft forever preferred_lft forever 7: eucabr10: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/ether 00:25:90:13:44:a4 brd ff:ff:ff:ff:ff:ff inet 10.32.8.1/24 brd 10.32.8.255 scope global eucabr10:priv 8: eth0.2187.10@eth0.2187: BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP mtu 1500 qdisc noqueue state UP link/ether 00:25:90:13:44:a4 brd ff:ff:ff:ff:ff:ff inet6 fe80::225:90ff:fe13:44a4/64 scope link valid_lft forever preferred_lft forever --- root@whirlpool:~# cat /etc/eucalyptus/eucalyptus.conf # /etc/eucalyptus/eucalyptus.conf # # These are the Ubuntu Enterprise Cloud's default Eucalyptus parameters. # Affects: All # See: **NOTE** below EUCALYPTUS=/ EUCA_USER=eucalyptus # Affects: CLC, Walrus, SC DISABLE_DNS=N CLOUD_OPTS=-Xmx512m # Affects: SC DISABLE_EBS=N DISABLE_ISCSI=N # Affects: CC, NC # See: **NOTE** below ENABLE_WS_SECURITY=Y LOGLEVEL=DEBUG VNET_PUBINTERFACE=eth0 VNET_CLOUDIP=x.y.z.220 VNET_PRIVINTERFACE=eth0.2187 VNET_MODE=MANAGED VNET_DHCPOPTS=option interface-mtu 1496; # Affects: CC # See: **NOTE** below CC_PORT=8774 SCHEDPOLICY=ROUNDROBIN POWER_IDLETHRESH=300 POWER_WAKETHRESH=300 NC_SERVICE=axis2/services/EucalyptusNC VNET_DHCPDAEMON=/usr/sbin/dhcpd VNET_DHCPUSER=dhcpd DISABLE_TUNNELLING=N NODES= VNET_ADDRSPERNET=256 VNET_SUBNET=10.32.0.0 VNET_NETMASK=255.240.0.0 #VNET_DNS= VNET_PUBLICIPS=instance.public.ips.208-instance.public.ips.223 -- NB: You may notice that VNET_PRIVINTERFACE already is a VLAN, but this seems to work OK so long as I reduce the MTU on instances by 4 bytes for the VLAN tag. And it still works fine with dhcpd3. Perhaps dhcpd goes through a different code path for discovery on VLAN interfaces? I'm just too tired to work any more on this today...I'll debug everything properly some time over the next week, but this system is far from clean and probably not entirely typical, so I wouldn't want to assert that things are still not fixed if it appears OK for people doing more formal testing here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/717166 Title: Broken with v4 isc-dhcp-server in Natty -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 717166] Re: Broken with v4 isc-dhcp-server in Natty
@Carlos The upgrade was from maverick (10.10), but this is a server that I have been using for development and has been on natty devel branch since early days in the cycle. I have had to do a bit of jiggery-pokery with eucalyptus and other packages at points, as tends to be the way during development (instance IFACE problem in the upstart scripts IIRC). Why this would have needed dac_override I do not know - me neither, and that seemed to be a temporary problem. I cannot make that happen now...I'm happy to forget that one ;) Currently, the only problem I have is that dhcpd won't identify and listen on eucabr10. After that, everything works (or at least as well as it did on maverick...I have the issue with 32-bit images and also that restarting eucalyptus seems to lose the public IP, but that was the case before anyway). Not sure what other info I can provide, other than what I expect to see instead; switching back to dhcp3, things immediately work as expected: == /var/log/eucalyptus/httpd-cc_error_log == No subnet declaration for eth0.2187 (169.254.169.254). ** Ignoring requests on eth0.2187. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface eth0.2187 is attached. ** Listening on LPF/eucabr10/00:25:90:13:44:a4/euca Sending on LPF/eucabr10/00:25:90:13:44:a4/euca Sending on Socket/fallback/fallback-net ...I then have both public and private connectivity to the started instance! A slight aside, I don't know why Eucalyptus passes the VNET_PRIVINTERFACE as last parameter in it's command line to dhcpd[3] as this causes (as it should, since there is no subnet in the config for that interface) the notice seen above in httpd-cc_error_log...which is not unexpected, so cluttering the error log could be avoided here? I would feel better about this bug if somebody has tested it successfully using VLANs in MANAGED mode? There must be something that happens differently because I'm as certain as I can be that Dan's patch is compiled into the dhcpd bin that is still failing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/717166 Title: Broken with v4 isc-dhcp-server in Natty -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 769568] [NEW] Ability to set ad-hoc DHCP options
Public bug reported: I would like to see some way to set ad-hoc DHCP options with Eucalyptus. For example, I need my instances to have MTU =1496 otherwise packets will get lost, but rather than try to modify images and enforce by documented policy for new images, it would be much simpler to be able to set this option via the DHCP server. Attaching my branch which has a rudimentary implementation using a VNET_DHCPOPTS config setting. I'm not exactly proposing to merge this as-is, but I didn't want to invest more time in it unless this is something that might be accepted into the project. I think that a generally more flexible DHCP config would be appreciated by a number of people for different purposes, but would need to go beyond a simple config addition such as is made here. ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: Opinion ** Changed in: eucalyptus (Ubuntu) Status: New = Opinion -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in Ubuntu. https://bugs.launchpad.net/bugs/769568 Title: Ability to set ad-hoc DHCP options -- 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 769568] Re: Ability to set ad-hoc DHCP options
PS: I intended to put this as a Wishlist item but don't see how to do that...maybe I have done things the wrong way. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in Ubuntu. https://bugs.launchpad.net/bugs/769568 Title: Ability to set ad-hoc DHCP options -- 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 717166] Re: Broken with v4 isc-dhcp-server in Natty
I'm not too sure that this is fixed guys :( Finally got back to this project yesterday and experiencing the same problem, although the code snippet Dan provided (which is the same as I can see in the isc-dhcp patch) does pick up the correct IPs for each interface...when actually running dhcpd it doesn't appear to work. The error is the same as before. Strangely, I'm also finding that now I have to add the capability dac_override to dhcpd apparmor profile otherwise it fails even earlier with permission denied trying to create the trace file. I can see that permissions for the trace file should be granted explicitly already in the profile, yet still have to add the more general dac_override for some reason :S Has this been successfully tested by others? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/717166 Title: Broken with v4 isc-dhcp-server in Natty -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 769568] [NEW] Ability to set ad-hoc DHCP options
Public bug reported: I would like to see some way to set ad-hoc DHCP options with Eucalyptus. For example, I need my instances to have MTU =1496 otherwise packets will get lost, but rather than try to modify images and enforce by documented policy for new images, it would be much simpler to be able to set this option via the DHCP server. Attaching my branch which has a rudimentary implementation using a VNET_DHCPOPTS config setting. I'm not exactly proposing to merge this as-is, but I didn't want to invest more time in it unless this is something that might be accepted into the project. I think that a generally more flexible DHCP config would be appreciated by a number of people for different purposes, but would need to go beyond a simple config addition such as is made here. ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: Opinion ** Changed in: eucalyptus (Ubuntu) Status: New = Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/769568 Title: Ability to set ad-hoc DHCP options -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 769568] Re: Ability to set ad-hoc DHCP options
PS: I intended to put this as a Wishlist item but don't see how to do that...maybe I have done things the wrong way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/769568 Title: Ability to set ad-hoc DHCP options -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 761632] Re: crash on startup before any activities
When I first installed Natty I got this error message on every boot up, however the machine did not totally lock up. When I installed the updates the next day, it booted normally without error messages and has had no problems since. It looks like something in the updates fixed the problem. Also, this laptop has had a hardware problem with the video card, probably thermally related as it seems to work fine until you load up the video card with say a full screen movie. When the video card works hard and heats up I will get a video tear or vertical strips and a HARD lock up requiring a hard shutdown and reboot. This problem on boot did not cause a hard lockup and occurred on the boot when the video card had not yet been doing much, so I did not think it a high probability it was the same problem. Working fine after the daily Update Manager run. Did not have similar error messages with Maverick, but did have the occasional video lockup in both Maverick and Windows XP, which is what led me to believe I have a thermal problem with the video card and not a software driver issue. Those never threw an error code because they hard locked the computer. Interestingly have not had a hard video lockup since installing Natty, even when trying to push it with full screen videos. May have to try Passmark or some similar video test in Linux. Thanks, Don On 4/20/2011 8:44 PM, Bryce Harrington wrote: Have you encountered other system freezes like this one since upgrading to natty? Did you experience freezes like this on maverick? Are you able to reproduce this freeze reliably? ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Confirmed = Incomplete ** Summary changed: - crash on startup before any activities + [i915gm] GPU lockup (ESR: 0x0001 IPEHR: 0x7d8e0001) ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/761632 Title: [i915gm] GPU lockup (ESR: 0x0001 IPEHR: 0x7d8e0001) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 727679] Re: Unity Launcher does not switch to running app on another workspace if aero snap left or right has been used
This bug is still affecting me, and I am fully updated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727679 Title: Unity Launcher does not switch to running app on another workspace if aero snap left or right has been used -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 764924] [NEW] [i915gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x7d8e0001)
*** This bug is a duplicate of bug 761632 *** https://bugs.launchpad.net/bugs/761632 Public bug reported: Binary package hint: xserver-xorg-video-intel Had just booted up and got these error messages before any activity other than plugging in HP Photosmart D7360 printer in order to try to install drivers. Looks like a duplicate of the bug I just sent, but sending again just in case there is extra info for you in the dump. ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: xserver-xorg-video-intel 2:2.14.0-4ubuntu7 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Chipset: i915gm CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1280x800 edid-base64: AP///wBMo0UyAAAPAQOAIRV4Cof1lFdPjCcnUFQBAQEBAQEBAQEBAQEBAQEB7hoAgFAgEDAQMBMAS88QAAAZDwAAACOHAmQC/gBTQU1TVU5HCiAgICAg/gBMVE4xNTRYMy1MMDcKAGE= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: Date: Sun Apr 17 21:39:26 2011 DistUpgraded: Fresh install DistroCodename: natty DistroVariant: ubuntu DuplicateSignature: (ESR: 0x0001 IPEHR: 0x7d8e0001) ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:ff10] Subsystem: Toshiba America Info Systems Device [1179:ff10] InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta i386 (20110413) InterpreterPath: /usr/bin/python2.7 MachineType: TOSHIBA Satellite M45 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=e8043cde-6057-4e96-9752-33528e9d131a ro quiet splash vt.handoff=7 ProcKernelCmdLine_: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=e8043cde-6057-4e96-9752-33528e9d131a ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.6+4ubuntu3 libdrm2 2.4.23-1ubuntu6 xserver-xorg-video-intel 2:2.14.0-4ubuntu7 Renderer: Unknown SourcePackage: xserver-xorg-video-intel Title: [i915gm] GPU lockup (ESR: 0x0001 IPEHR: 0x7d8e0001) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 02/07/2006 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.20 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 8 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.20:bd02/07/2006:svnTOSHIBA:pnSatelliteM45:pvrPSM42U-017006:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct8:cvrVersion1.0: dmi.product.name: Satellite M45 dmi.product.version: PSM42U-017006 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu1 version.libdrm2: libdrm2 2.4.23-1ubuntu6 version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu1 version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash compiz-0.9 freeze i386 natty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/764924 Title: [i915gm] GPU lockup (ESR: 0x0001 IPEHR: 0x7d8e0001) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 764924] Re: [i915gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x7d8e0001)
*** This bug is a duplicate of bug 761632 *** https://bugs.launchpad.net/bugs/761632 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/764924 Title: [i915gm] GPU lockup (ESR: 0x0001 IPEHR: 0x7d8e0001) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 764919] [NEW] [i915gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x7d8e0001)
*** This bug is a duplicate of bug 761632 *** https://bugs.launchpad.net/bugs/761632 Public bug reported: Binary package hint: xserver-xorg-video-intel Had just booted up and got these error messages before any activity other than plugging in HP Photosmart D7360 printer in order to try to install drivers. ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: xserver-xorg-video-intel 2:2.14.0-4ubuntu7 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Chipset: i915gm CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1280x800 edid-base64: AP///wBMo0UyAAAPAQOAIRV4Cof1lFdPjCcnUFQBAQEBAQEBAQEBAQEBAQEB7hoAgFAgEDAQMBMAS88QAAAZDwAAACOHAmQC/gBTQU1TVU5HCiAgICAg/gBMVE4xNTRYMy1MMDcKAGE= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: Date: Sun Apr 17 21:39:31 2011 DistUpgraded: Fresh install DistroCodename: natty DistroVariant: ubuntu DuplicateSignature: (ESR: 0x0001 IPEHR: 0x7d8e0001) ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:ff10] Subsystem: Toshiba America Info Systems Device [1179:ff10] InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta i386 (20110413) InterpreterPath: /usr/bin/python2.7 MachineType: TOSHIBA Satellite M45 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=e8043cde-6057-4e96-9752-33528e9d131a ro quiet splash vt.handoff=7 ProcKernelCmdLine_: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=e8043cde-6057-4e96-9752-33528e9d131a ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.6+4ubuntu3 libdrm2 2.4.23-1ubuntu6 xserver-xorg-video-intel 2:2.14.0-4ubuntu7 Renderer: Unknown SourcePackage: xserver-xorg-video-intel Title: [i915gm] GPU lockup (ESR: 0x0001 IPEHR: 0x7d8e0001) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 02/07/2006 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.20 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 8 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.20:bd02/07/2006:svnTOSHIBA:pnSatelliteM45:pvrPSM42U-017006:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct8:cvrVersion1.0: dmi.product.name: Satellite M45 dmi.product.version: PSM42U-017006 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu1 version.libdrm2: libdrm2 2.4.23-1ubuntu6 version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu1 version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash compiz-0.9 freeze i386 natty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/764919 Title: [i915gm] GPU lockup (ESR: 0x0001 IPEHR: 0x7d8e0001) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
