[Bug 1975884] Re: Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04 jammy)
Just noticed the screenlock freeze again, worked fine most of yesterday (mostly only had firefox open), then later installed GSConnect extension (was essential for getting an errand done) and had sublimetext open (around 15 workspaces open). See https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976163 for associated info. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975884 Title: Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04 jammy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1975884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976163] [NEW] Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04 jammy) (continuation)
Public bug reported: See earlier discussion https://bugs.launchpad.net/ubuntu/+bug/1975884 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat May 28 13:01:17 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2021-07-15 (316 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-05-02 (26 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976163 Title: Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04 jammy) (continuation) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975884] Re: Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04 jammy)
Got it, thanks. I haven't tried to 'remove all' unsupported extensions per your instructions yet, but did disable all non-system extensions via the 'Extensions Manager' app and still noticed the issue (without logging in again). Will now try removing all per your instructions, logging in again/rebooting and see. EDIT: haven't logged out or rebooted yet, but noticing a slight (not as much) delay still. Could be associated with having a large number of apps/browser tabs open. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975884 Title: Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04 jammy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1975884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975884] Re: Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04 jammy)
** Description changed: As first mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1769981/comments/25 , I've been observing an issue when unlocking my computer (usually from a screen lock state, not hibernation/sleep) where after entering the first few characters of my password the screen freezes for 10-20 seconds before I can do any type of input (mouse, touch, keyboard). I've largely been noticing this since upgrading from Ubuntu 21.10 to 22.04. It doesn't happen all the time, but often enough to file an issue for. So far I've tried: - Disabling the 'blur my shell' extension - still encountered the issue again eventually. - Looking for anything associated with this in /var/crash - couldn't find anything. - Looking for anything associated at errors.ubuntu.com for my id. + + What I may eventually try: + - Seeing if this may depend on having too many browser tabs / apps open. Currently not in a position to do this. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 26 19:19:28 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-15 (315 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-05-02 (24 days ago) ** Description changed: As first mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1769981/comments/25 , I've been observing an issue when unlocking my computer (usually from a screen lock state, not hibernation/sleep) where after entering the first few characters of my password the screen freezes for 10-20 seconds before I can do any type of input (mouse, touch, keyboard). + + I've also seen it happen when having touch / gesture input switch + between displaying the user name and the password field - where the + screen can get stuck in the animation in an interstitial state for a + number of seconds. I've largely been noticing this since upgrading from Ubuntu 21.10 to 22.04. It doesn't happen all the time, but often enough to file an issue for. So far I've tried: - Disabling the 'blur my shell' extension - still encountered the issue again eventually. - Looking for anything associated with this in /var/crash - couldn't find anything. - Looking for anything associated at errors.ubuntu.com for my id. What I may eventually try: - Seeing if this may depend on having too many browser tabs / apps open. Currently not in a position to do this. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 26 19:19:28 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-15 (315 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-05-02 (24 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975884 Title: Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04 jammy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975884] [NEW] Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04 jammy)
Public bug reported: As first mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1769981/comments/25 , I've been observing an issue when unlocking my computer (usually from a screen lock state, not hibernation/sleep) where after entering the first few characters of my password the screen freezes for 10-20 seconds before I can do any type of input (mouse, touch, keyboard). I've largely been noticing this since upgrading from Ubuntu 21.10 to 22.04. It doesn't happen all the time, but often enough to file an issue for. So far I've tried: - Disabling the 'blur my shell' extension - still encountered the issue again eventually. - Looking for anything associated with this in /var/crash - couldn't find anything. - Looking for anything associated at errors.ubuntu.com for my id. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 26 19:19:28 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-15 (315 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-05-02 (24 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975884 Title: Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04 jammy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769981] Re: Temporary screen freeze when coming back from screen standby
I've been having an issue similar to this on 22.04 (jammy) and don't recall experiencing it on 21.10. It's actually happened not just from standby but from just being on (with display off) as well. I'm still testing, but it could be extensions like 'blur my shell' causing an issue. Couldn't find anything associated with this in /var/crash or in errors.ubuntu.com for my id. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769981 Title: Temporary screen freeze when coming back from screen standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973386] Re: 22.04 Jammy: Lockscreen (but not login) on-screen keyboard touch keys do not work
This issue is most likely related to this gnome issue fixed in gnome 42.1 - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5273 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5273 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5273 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973386 Title: 22.04 Jammy: Lockscreen (but not login) on-screen keyboard touch keys do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973386] Re: 22.04 Jammy: Lockscreen (but not login) on-screen keyboard touch keys do not work
** Description changed: Several people on reddit (many surface pro / go users, and myself as an HP tablet pc user) have been experiencing an issue on Ubuntu 22.04 (jammy jellyfish) where the gnome lockscreen on-screen keyboard is not functional, but the main ubuntu loginscreen on-screen keyboard is functional. https://www.reddit.com/r/SurfaceLinux/comments/umeiqx/onscreen_keyboard_doesnt_register_key_presses_in/ Steps to reproduce: 0) Ensure you have Screen Keyboard enabled in the accessibility menu. 1) From a logged-in state, Go to upper right corner and click Lock 2) Turn device back on so 'user lockscreen' comes back on, try to log in using touchscreen on-screen keyboard. 3) Observe key presses don't work. 4) Try to close login password prompt such that switch user login button appears. - 5) Touch switch user login button, leading to 'login screen' (black with ubuntu logo) + 5) Touch switch user login button, leading to 'login screen' (black with ubuntu logo) 6) Select user, try to log in using touchscreen on-screen keyboard and observe it works. See demo video: https://youtu.be/RjfRZOmwsgs (NOTE: In the video there's another separate issue here in regards to the 'login screen' not having awareness of tablet screen orientation) + + This was observed on 22.04, I didn't experience this issue on 21.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973386 Title: 22.04 Jammy: Lockscreen (but not login) on-screen keyboard touch keys do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973386] [NEW] 22.04 Jammy: Lockscreen (but not login) on-screen keyboard touch keys do not work
Public bug reported: Several people on reddit (many surface pro / go users, and myself as an HP tablet pc user) have been experiencing an issue on Ubuntu 22.04 (jammy jellyfish) where the gnome lockscreen on-screen keyboard is not functional, but the main ubuntu loginscreen on-screen keyboard is functional. https://www.reddit.com/r/SurfaceLinux/comments/umeiqx/onscreen_keyboard_doesnt_register_key_presses_in/ Steps to reproduce: 0) Ensure you have Screen Keyboard enabled in the accessibility menu. 1) From a logged-in state, Go to upper right corner and click Lock 2) Turn device back on so 'user lockscreen' comes back on, try to log in using touchscreen on-screen keyboard. 3) Observe key presses don't work. 4) Try to close login password prompt such that switch user login button appears. 5) Touch switch user login button, leading to 'login screen' (black with ubuntu logo) 6) Select user, try to log in using touchscreen on-screen keyboard and observe it works. See demo video: https://youtu.be/RjfRZOmwsgs (NOTE: In the video there's another separate issue here in regards to the 'login screen' not having awareness of tablet screen orientation) ** Affects: gnome-shell (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/1973386 Title: 22.04 Jammy: Lockscreen (but not login) on-screen keyboard touch keys do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962225] Re: preinst check that kernel revision < 255 now does more harm than good
Thanks for the update @Michael -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962225 Title: preinst check that kernel revision < 255 now does more harm than good To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1962225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962225] Re: preinst check that kernel revision < 255 now does more harm than good
For people working with Docker build @Itay Elgazar (elgazaritay) Copy the script above into a file(like ubuntuFix.sh) Use it in your Dockerfile like below:- FROM ubuntu:latest USER root WORKDIR /home/app COPY . /home/app #Workaround for ubuntu fix start RUN mv /bin/uname /bin/uname.orig RUN cp ./ubuntuFix.sh /bin/uname RUN chmod 755 /bin/uname; RUN cat /bin/uname #Workaround for ubuntu fix end RUN apt clean RUN apt-get update RUN apt -y install gnupg2 . . //Rest of the Dockerfile code . . @Nic thanks for the solution.. Hope this works for others using Docker image -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962225 Title: preinst check that kernel revision < 255 now does more harm than good To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1962225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946343] Re: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3
@Dimitri, thank you for looking into this issue. This is the output of apt-cache policy: $ apt-cache policy oem-release oem-release: Installed: 20.04ubuntu2 Candidate: 20.04ubuntu2 Version table: *** 20.04ubuntu2 100 100 /var/lib/dpkg/status As per synaptic package manager, the maintainer of oem-release package is: "Commercial Engineering " This package also has dependencies with 'lsb-release'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946343 Title: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/dell/+bug/1946343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946444] Re: ath11k_pci firmware crashes under regular usage on Dell XPS 13 9310 (no suspend and resume)
It has been just 1 week since I got the laptop and I am using it. So I didn't do anything out of sorts. Below is my linux kernel version (the laptop itself came with OEM Kernel and Ubuntu pre-installed) $ uname -a Linux vivek-dev-linux 5.10.0-1049-oem #51-Ubuntu SMP Mon Sep 27 11:01:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1) Release:20.04 Codename: focal $ lspci -v ... 72:00.0 Network controller: Qualcomm Device 1101 (rev 01) Subsystem: Bigfoot Networks, Inc. Device a501 Flags: bus master, fast devsel, latency 0, IRQ 178 Memory at a250 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946444 Title: ath11k_pci firmware crashes under regular usage on Dell XPS 13 9310 (no suspend and resume) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1946444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946444] [NEW] ath11k_pci firmware crashes under regular usage on Dell XPS 13 9310 (no suspend and resume)
Public bug reported: While I was normally working on my Dell XPS 13 9310 Laptop, noticed that WiFi suddenly got disconnected. Looking at dmesg, noticed that the firmware crashed. (I am also attaching the entire dmesg output as a file to this bug. ) $ dmesg | grep ath11_k [ 13.826871] ath11k_pci :72:00.0 wlp114s0: renamed from wlan0 [35908.890709] ath11k_pci :72:00.0: firmware crashed: MHI_CB_SYS_ERROR [36170.055770] ath11k_pci :72:00.0: wmi command 12290 timeout [36170.055776] ath11k_pci :72:00.0: failed to send WMI_STOP_SCAN_CMDID [36170.055783] ath11k_pci :72:00.0: failed to stop wmi scan: -11 [36170.055786] ath11k_pci :72:00.0: failed to stop scan: -11 [36170.055788] ath11k_pci :72:00.0: failed to start hw scan: -110 ... ... [36305.230431] ath11k_pci :72:00.0: wmi command 16387 timeout [36305.230436] ath11k_pci :72:00.0: failed to send WMI_PDEV_SET_PARAM cmd [36305.230445] ath11k_pci :72:00.0: failed to enable PMF QOS: (-11 I had to reboot the machine at least 2 times before WiFi started working. In the past, I had noticed WiFi would not work after boot a couple of times, but this is the first time I am seeing it breaking under normal, continuous usage. This is a major reliability issue if WiFi connection keeps breaking in the middle of work like this. Also, this is somewhat similar to the following bugs, but not exactly the same: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1944018 (here there is no message 'firmware crashed' but rather some failures from ath11k_pci. Moreover it occurred during suspend and resume. Whereas in my case, the last suspend + resume was at least 3 and half hours before the firmware crash) https://bugs.launchpad.net/ubuntu/+source/linux-signed- oem-5.10/+bug/1942060 (here there is 'firmware crashed' message, but all the error messages after that seem to be different. Moreover it seems to have occurred 56 seconds after system booted, when WiFi network was connected. Whereas I had a uptime of 9 hours and about 6 hours after the last WiFi connection). ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg_ath11k_firmware_crash.txt" https://bugs.launchpad.net/bugs/1946444/+attachment/5531464/+files/dmesg_ath11k_firmware_crash.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946444 Title: ath11k_pci firmware crashes under regular usage on Dell XPS 13 9310 (no suspend and resume) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1946444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946343] Re: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3
This is the output of my dpkg-query for os-release: $ dpkg-query --search os-release systemd: /usr/share/man/man5/os-release.5.gz diversion by oem-release from: /usr/lib/os-release diversion by oem-release to: /usr/lib/os-release.oem-release base-files: /etc/os-release diversion by oem-release from: /usr/lib/os-release diversion by oem-release to: /usr/lib/os-release.oem-release base-files: /usr/lib/os-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946343 Title: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1946343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946343] Re: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3
@Steve, thank you for looking into this. If this is not a base-files issue, where could the problem be? I have not installed any other package myself. This is just the Ubuntu installation that the laptop came with. As an end user I am unable to see whether upgrade to 20.04.3 is successful or not. Clearly lsb_release is not saying so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946343 Title: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1946343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946343] [NEW] Stale os-release file after possible upgrade from 20.04.2 to 20.04.3
Public bug reported: Refer: https://answers.launchpad.net/ubuntu/+question/698949 I recently bought a Dell laptop with Ubuntu pre-installed in it. Looks like it came with Ubuntu 20.04.2 and OEM Linux Kernel in it. After my initial login (on October 1, 2021), the 'Software Updater' GUI prompted me for updates, which I went ahead with. However at the end of it, I noticed that I was still at 20.04.2 with Linux Kernel at 5.10.0-1045-oem. lsb_release -a --- No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1) Release:20.04 Codename: focal uname -a - Linux dev-linux 5.10.0-1045-oem #47-Ubuntu SMP Wed Aug 18 10:41:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Then I manually tried sudo apt update and sudo apt upgrade / dist- upgrade from the terminal, but nothing got upgraded. When I invoked the GUI 'Software Updater' again, it showed me that my system was already up-to-date. However, as 20.04.3 was released end of Aug 2021, I was expecting that I should be at that release after my initial updates. Since that didn't happen, I asked a question regarding this in askubuntu followed by launchpad https://answers.launchpad.net/ubuntu/+question/698949, thinking my update had failed for some unknown reason. However, based on some inputs from other users, we were able to narrow down the problem to /usr/lib/os-release file not having the right contents in it. Every other file including /usr/lib/os-release.oem- release, /etc/issue, /etc/issue.net specifies that I am on 20.04.3. Whereas only /usr/lib/os-release (and its symlink /etc/release) specifies my current release as 20.04.2. Even the lsb_release -a command always displays the output of /usr/lib/os-release file only. $ cat /usr/lib/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /usr/lib/os-release.oem-release NAME="Ubuntu" VERSION="20.04.3 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.3 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /etc/issue Ubuntu 20.04.3 LTS \n \l $ cat /etc/issue.net Ubuntu 20.04.3 LTS If you look at the timestamp of these files, strangely os-release had a newer timestamp of Oct 1 compared to other files. $ ls -l /usr/lib/os-release -rw-r--r-- 1 root root 406 Oct 1 20:31 /usr/lib/os-release $ ls -l /usr/lib/os-release.oem-release -rw-r--r-- 1 root root 382 Aug 4 07:53 /usr/lib/os-release.oem-release $ ls -l /etc/issue -rw-r--r-- 1 root root 26 Aug 4 07:53 /etc/issue $ ls -l /etc/issue.net -rw-r--r-- 1 root root 19 Aug 4 07:53 /etc/issue.net Please note that, other software package updates, and linux kernel updates are happening automatically without any issues so far for me. Few days back even got a new kernel update. $ uname -a Linux vivek-dev-linux 5.10.0-1049-oem #51-Ubuntu SMP Mon Sep 27 11:01:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Workarounds Attempted - 1. Commented out all non-ubuntu external sources from /etc/apt/*.list. Then performed an apt clean + update + upgrade. But still nothing happened and the same issue remained. 2. Tried performing apt-install --reinstall base-files. But still nothing changed: $ sudo apt install --reinstall base-files Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 4 not upgraded. Need to get 60.6 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 base-files amd64 11ubuntu5.4 [60.6 kB] Fetched 60.6 kB in 1s (55.7 kB/s) (Reading database ... 191154 files and directories currently installed.) Preparing to unpack .../base-files_11ubuntu5.4_amd64.deb ... Warning: Stopping motd-news.service, but it can still be activated by: motd-news.timer Unpacking base-files (11ubuntu5.4) over (11ubuntu5.4) ... Setting up base-files (11ubuntu5.4) ... motd-news.service is a disabled or a static unit, not starting it. Processing triggers for cracklib-runtime (2.9.6-3.2) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.4git20200323-0ubuntu6.2) ... update-initramfs: deferring update (trigger activated) Processing triggers for install-info (
[Bug 1943237] [NEW] My touchpad driver - Synaptics stuck after login - Ubuntu 18.04
Public bug reported: When I login to my computer , My touchpad sometimes work and sometimes it is stuck. Also same thing happens with keyboard. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-81-generic 5.4.0-81.91~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 10 13:29:49 2021 InstallationDate: Installed on 2019-04-03 (891 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943237 Title: My touchpad driver - Synaptics stuck after login - Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1943237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938352] Re: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input
Just to summarize above, I suspect this is related to touch input event handling rather than earlier thoughts around bluetooth or screen orientation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938352 Title: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1938352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938352] Re: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input
Thanks. After experiencing this issue 2-3 times last night, I realized this may possibly be related to tablet screen rotation (not sure if the gnome-shell logs delve into this, tried looking and didn't see anything that seemed relevant) - Generally when I've noticed this bug I was using the device in portrait mode. Screen orientation done via physically rotating device + using internal sensor. My setup/experience in this last encounter was: - Had 3rd party gnome shell extensions (including wandering pixel) disabled beforehand - only "Desktop Icons NG" enabled. - Turned off bluetooth as well, to try and dispell earlier ideas of it being related to the bluetooth keyboard connection. Steps: - Rotated screen to portrait, had firefox and a gnome files window open. - Started using the device, might've rotated back to landscape once or twice quickly to see what happens. - Observed when issue happens (while in portrait mode), just beforehand active window I had open (gnome files) suddenly moved maybe 50-100px up, like it was correcting for a orientation change even though I was felt like I was just using device normally laid down in portrait mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938352 Title: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1938352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938623] Re: Audio output & input routes to usb-c hub (where audio jack is disconnected) instead of laptop speakers
Realizing this likely has more to do with the lack of driver support for usb-c hubs on linux - per pulseaudio's documentation ( https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modules/#module- switch-on-port-available ) : "# module-switch-on-connect Earlier this module was required to automatically switch to a newly plugged in USB sound card, but nowadays USB sound cards have higher priority than internal sound cards, so they automatically become the default sink (unless you have manually configured the default sink to be something else) and the need for this module is greatly reduced." "#module-switch-on-port-available (not on USB sound cards, though, since they don't support jack detection)" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938623 Title: Audio output & input routes to usb-c hub (where audio jack is disconnected) instead of laptop speakers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1938623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938623] Re: Audio output & input routes to usb-c hub (where audio jack is disconnected) instead of laptop speakers
realized this has more to do with pulseaudio settings ** Changed in: ubuntu Status: New => Opinion ** Package changed: ubuntu => pulseaudio (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938623 Title: Audio output & input routes to usb-c hub (where audio jack is disconnected) instead of laptop speakers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1938623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938623] [NEW] Audio output & input routes to usb-c hub (where audio jack is disconnected) instead of laptop speakers
Public bug reported: I'm using Ubuntu 21.04 with an intel tablet and a lenovo usb-c hub that has an audio adapter: See https://linux-hardware.org/?probe=09f8c72d80/ I never have anything hooked into the audio jack on usb-c hub, yet every time I plug my tablet into the usb-c hub the sound output switches to the usb-c hub instead of staying routed to the tablet speakers. I then have to go either into settings or use a sound output extension to switch it back to the speakers. This issue does not happen when using Windows 10 - audio stays routed through the tablet speakers - my guess is that it goes a step further and detects whether an audio jack actually has a cable plugged in or not. What package handles determining default audio routing for Ubuntu 21.04 / Gnome 3.38.5? I'd like to file a bug about this / possibly see if I can help make the defaults work better. See also OS confusion about default audio sink - pulse: https://askubuntu.com/questions/1231935/os-confusion-about-default- audio-sink-pulse ** 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/1938623 Title: Audio output & input routes to usb-c hub (where audio jack is disconnected) instead of laptop speakers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1938623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938352] Re: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input
fwiw in addition to earlier experiencing this with no extensions, I've also experienced it while running the 'wandering pixel' extension ( https://extensions.gnome.org/extension/4028/wandering-pixel/ ) intended to workaround another application hang issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938352 Title: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1938352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938435] Re: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input (2nd entry, with
** Summary changed: - gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input (2nd entry, with 3rd party extensions disabled) + [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input (2nd entry, with 3rd party extensions disabled) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938435 Title: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input (2nd entry, with 3rd party extensions disabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1938435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938352] Re: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input
** Summary changed: - gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input + [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938352 Title: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1938352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938352] Re: gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input
Done, issue observed again (without extensions) in https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1938435 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938352 Title: gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1938352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938435] [NEW] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input (2nd entry, with 3rd part
Public bug reported: filed for new attachments - see https://bugs.launchpad.net/gnome- shell/+bug/1938352 & https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/4508 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 29 06:12:21 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-15 (13 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938435 Title: gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input (2nd entry, with 3rd party extensions disabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1938435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938352] Re: gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input
@vanvugt the issue goes away when I log out. To clarify, do you want me to try: A: Leaving the above extensions enabled, try to disable them when the issue occurs, then see if the problem stops occurring? B: Turn off those extensions now, then see if I observe the issue happen again? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938352 Title: gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1938352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938352] [NEW] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input
Public bug reported: Further detailed information filed in gnome-shell bug filing: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4508#note_1213365 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 28 17:56:57 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-15 (13 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938352 Title: gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1938352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927768] Re: No Bluetooth device found
Thanks, it solved my problem. I installed this package by, sudo add-apt-repository ppa:blaze/rtbth-dkms sudo apt-get update sudo apt-get install rtbth-dkms And then, sudo modprobe rtbth It worked. Refer https://askubuntu.com/questions/756166/rt3290-ralink-driver-in- ubuntu for more. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927768 Title: No Bluetooth device found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927768] [NEW] No Bluetooth device found
Public bug reported: My laptop HP Probook 450 g0 has a bluetooth device. But my Ubuntu 20.04 can't find this device. I tried dmesg | grep -i blue -> No output I know my laptop has bluetooth device for sure. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-72-generic 5.4.0-72.80 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vivek 3179 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 7 22:07:40 2021 HibernationDevice: RESUME=UUID=91721efb-c835-42a1-a739-b90f5b9e1c5d InstallationDate: Installed on 2017-05-22 (1445 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP ProBook 450 G0 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=UUID=c3fba244-e5d3-42d6-ab29-cbc5d705c6e9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-72-generic N/A linux-backports-modules-5.4.0-72-generic N/A linux-firmware1.187.11 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRF Ver. F.63 dmi.board.name: 1949 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 90.0F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRFVer.F.63:bd06/03/2016:svnHewlett-Packard:pnHPProBook450G0:pvrA2018CD200:rvnHewlett-Packard:rn1949:rvrKBCVersion90.0F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 450 G0 dmi.product.sku: F9S12PA#ACJ dmi.product.version: A2018CD200 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927768 Title: No Bluetooth device found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892883] [NEW] Installation failure
Public bug reported: While installing get an error of Installer crash or Installation failed after I set the partitions/ progress with clean install. Sometime the system just hangs while installing at any screen and only way to come out of it is via force restart ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 25 20:47:23 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892883 Title: Installation failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1892883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878392] Re: Ubuntu 20.04 Focal Fossa desktop launchers not working
I think issue is with dash to panel, I checked with dash to dock and it didnt happen: When we click the launcher icon the menu background that displays the apps dont vanish when you reclick the launcher button to hide it. Maybe due to that the things become unresponsive. It just shows a 'X' mark on top left in my case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878392 Title: Ubuntu 20.04 Focal Fossa desktop launchers not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1878392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883841] [NEW] The dock has become inactive. Its not clickable and its not hiding automatically. Also cant switch between apps. Mouse is not clickable in desktop. On running dmesg "drm:intel_pipe
Public bug reported: The dock has become inactive. Its not clickable and its not hiding automatically. Also cant switch between apps. Mouse is not clickable in desktop. On running dmesg "drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.1.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 17 12:21:24 2020 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2020-06-02 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883841 Title: The dock has become inactive. Its not clickable and its not hiding automatically. Also cant switch between apps. Mouse is not clickable in desktop. On running dmesg "drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1883841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874865] [NEW] i can't upgrade my ubuntu 18.04 to 20.04,
Public bug reported: i can't upgrade my ubuntu 18.04 to 20.04, i this it my fault i chang my source.list without correct knowledge ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: GNOME Date: Fri Apr 24 23:07:04 2020 InstallationDate: Installed on 2018-01-28 (817 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-04-24 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874865 Title: i can't upgrade my ubuntu 18.04 to 20.04, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1874865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1872287] Re: I'm getting CPU freezing issues.
Already mentioned "freezes" while playing CSGO, while making disk operations, while opening programs etc etc. Tried using kernel versions higher than 5.4.x on ubuntu 18.04 but then nvidia xserver settings broke down, couldn't fix it without reinstallation. On Tue, Apr 14, 2020, 12:45 Daniel van Vugt wrote: > Please explain what "this" is. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1872287 > > Title: > I'm getting CPU freezing issues. > > Status in Ubuntu: > Incomplete > > Bug description: > The bugs are related to CSGO, getting fps drops after few minutes of > usage. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 > Uname: Linux 5.3.0-46-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: > '/proc/driver/nvidia/gpus/:01:00.0' > .proc.driver.nvidia.registry: Binary: "" > .proc.driver.nvidia.suspend: suspend hibernate resume > .proc.driver.nvidia.suspend_depth: default modeset uvm > .proc.driver.nvidia.version: >NVRM version: NVIDIA UNIX x86_64 Kernel Module 430.50 Thu Sep 5 > 22:36:31 CDT 2019 >GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) > ApportVersion: 2.20.9-0ubuntu7.14 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Sun Apr 12 16:23:27 2020 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > DkmsStatus: >acpi-call, 1.1.0, 5.3.0-46-generic, x86_64: installed >nvidia, 430.50, 5.3.0-46-generic, x86_64: installed > ExtraDebuggingInterest: Yes, including running git bisection searches > GraphicsCard: >Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA > controller]) > Subsystem: ASUSTeK Computer Inc. Device [1043:15e0] > Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] > [1043:15e0] > InstallationDate: Installed on 2020-04-10 (1 days ago) > InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 > (20200203.1) > MachineType: ASUSTeK COMPUTER INC. GL553VD > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic > root=UUID=e042896c-2375-42c9-9d7d-2af9ed9e2121 ro quiet splash vt.handoff=1 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 01/02/2018 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: GL553VD.306 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: GL553VD > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: GL > dmi.product.name: GL553VD > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 > version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 > version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A > version.xserver-xorg-core: xserver-xorg-core N/A > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A > version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+bug/1872287/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872287 Title: I'm getting CPU freezing issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1872287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1872287] Re: I'm getting CPU freezing issues.
acc. to me this happens when I make use of my storage(ssd), I tried switching to different ubuntu versions and kernels, I was not having this problem on 20.04 but I was having other problems related to package installations, thats why Iswitched back to 19.10 and then to 18.04. Nothing worked. On Tue, Apr 14, 2020 at 10:51 AM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Please explain in more detail what "CPU freezing issues" means. > > ** Changed in: xorg (Ubuntu) >Status: New => Incomplete > > ** Package changed: xorg (Ubuntu) => ubuntu > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1872287 > > Title: > I'm getting CPU freezing issues. > > Status in Ubuntu: > Incomplete > > Bug description: > The bugs are related to CSGO, getting fps drops after few minutes of > usage. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 > Uname: Linux 5.3.0-46-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: > '/proc/driver/nvidia/gpus/:01:00.0' > .proc.driver.nvidia.registry: Binary: "" > .proc.driver.nvidia.suspend: suspend hibernate resume > .proc.driver.nvidia.suspend_depth: default modeset uvm > .proc.driver.nvidia.version: >NVRM version: NVIDIA UNIX x86_64 Kernel Module 430.50 Thu Sep 5 > 22:36:31 CDT 2019 >GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) > ApportVersion: 2.20.9-0ubuntu7.14 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Sun Apr 12 16:23:27 2020 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > DkmsStatus: >acpi-call, 1.1.0, 5.3.0-46-generic, x86_64: installed >nvidia, 430.50, 5.3.0-46-generic, x86_64: installed > ExtraDebuggingInterest: Yes, including running git bisection searches > GraphicsCard: >Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA > controller]) > Subsystem: ASUSTeK Computer Inc. Device [1043:15e0] > Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] > [1043:15e0] > InstallationDate: Installed on 2020-04-10 (1 days ago) > InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 > (20200203.1) > MachineType: ASUSTeK COMPUTER INC. GL553VD > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic > root=UUID=e042896c-2375-42c9-9d7d-2af9ed9e2121 ro quiet splash vt.handoff=1 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 01/02/2018 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: GL553VD.306 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: GL553VD > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: GL > dmi.product.name: GL553VD > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 > version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 > version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A > version.xserver-xorg-core: xserver-xorg-core N/A > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A > version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+bug/1872287/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872287 Title: I'm getting CPU freezing issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1872287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872287] [NEW] I'm getting CPU freezing issues.
Public bug reported: The bugs are related to CSGO, getting fps drops after few minutes of usage. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 430.50 Thu Sep 5 22:36:31 CDT 2019 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 16:23:27 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.3.0-46-generic, x86_64: installed nvidia, 430.50, 5.3.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:15e0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:15e0] InstallationDate: Installed on 2020-04-10 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: ASUSTeK COMPUTER INC. GL553VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=e042896c-2375-42c9-9d7d-2af9ed9e2121 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL553VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872287 Title: I'm getting CPU freezing issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865254] [NEW] After fresh installation 19.10 on Dell vostro 15 3568 it is showing screen blinking when I try to unlock and locking with Super+L
Public bug reported: I am new to report such issues so I just don't know what to share here. though below is the kernel and syslog of the system. I having this issue with this model only as many of this model to test. Kernel: 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Syslog:- Feb 29 12:01:16 Bigstep-Vostro-15-3568 gnome-shell[1779]: == Stack trace for context 0x5603df1c4330 == Feb 29 12:01:16 Bigstep-Vostro-15-3568 gnome-shell[1779]: #0 5603e0fd7930 i resource:///org/gnome/shell/ui/workspace.js:709 (7fdf75972e50 @ 15) Feb 29 12:01:16 Bigstep-Vostro-15-3568 gnome-shell[1779]: #1 7ffceebe4f80 b self-hosted:975 (7fdf75834160 @ 392) Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: Object St.Button (0x5603e0eaccd0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: == Stack trace for context 0x5603df1c4330 == Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: #0 5603e0fd7930 i resource:///org/gnome/shell/ui/workspace.js:709 (7fdf75972e50 @ 15) Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: #1 7ffceebe4f80 b self-hosted:975 (7fdf75834160 @ 392) Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: Object St.Button (0x5603e0eaccd0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: == Stack trace for context 0x5603df1c4330 == Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: #0 7ffceebe4540 b resource:///org/gnome/shell/ui/workspace.js:709 (7fdf75972e50 @ 15) Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: #1 7ffceebe4f80 b self-hosted:975 (7fdf75834160 @ 392) Feb 29 12:01:18 Bigstep-Vostro-15-3568 gnome-shell[1779]: Object St.Button (0x5603e0eaccd0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Feb 29 12:01:18 Bigstep-Vostro-15-3568 gnome-shell[1779]: == Stack trace for context 0x5603df1c4330 == Feb 29 12:01:18 Bigstep-Vostro-15-3568 gnome-shell[1779]: #0 7ffceebe4ed0 b resource:///org/gnome/shell/ui/workspace.js:709 (7fdf75972e50 @ 15) Feb 29 12:01:18 Bigstep-Vostro-15-3568 gnome-shell[1779]: #1 7ffceebe4f80 b self-hosted:975 (7fdf75834160 @ 392) Feb 29 12:01:19 Bigstep-Vostro-15-3568 gnome-shell[1779]: Object St.Button (0x5603e0eaccd0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Feb 29 12:01:19 Bigstep-Vostro-15-3568 gnome-shell[1779]: == Stack trace for context 0x5603df1c4330 == Feb 29 12:01:19 Bigstep-Vostro-15-3568 gnome-shell[1779]: #0 7ffceebe4ed0 b resource:///org/gnome/shell/ui/workspace.js:709 (7fdf75972e50 @ 15) Feb 29 12:01:19 Bigstep-Vostro-15-3568 gnome-shell[1779]: #1 7ffceebe4f80 b self-hosted:975 (7fdf75834160 @ 392) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 29 11:49:13 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0793] InstallationDate: Installed on 2020-02-28 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Vostro 15-3568 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=e4c9da5a-c5ed-4509-ac83-acf0ed89a193 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 05HRPP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0793 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri:
[Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
I was able to run the command by making the bios and on default settings and booting again, but when reboot again it shows the error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
Hi I have the same issue on Acer Ryzen 5, How to confirm status of the bug as mentioned above, I have enterered the command for this and gave the permission for one week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
I was able to run the command by making the bios and on default settings and booting again, but when reboot again it shows the error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829656] [NEW] installer crashed in between the process
Public bug reported: it asked me for my location and then the installation process abruptly stopped ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sun May 19 19:38:39 2019 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid initrd=/casper/initrd quiet splash --- BOOT_IMAGE=/casper/vmlinuz LiveMediaBuild: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829656 Title: installer crashed in between the process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1829656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780394] [NEW] Unable to install 18.04 with something else option
Public bug reported: I have also tried this some other system, sometime it worked proper and OS installed but some of them installation was uncoplete with grub error. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 Date: Fri Jul 6 12:56:06 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780394 Title: Unable to install 18.04 with something else option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1780394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759836] Re: systemd-udevd consumes 100% of CPU
I also faced the same issue and thanks to the Lumar's comment, workaround mentioned in the link worked for me too: https://dev.solus-project.com/T5224 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769419] [NEW] grub2 installation failed
Public bug reported: installed system cannot boot ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sun May 6 08:13:28 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769419 Title: grub2 installation failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1769419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767583] [NEW] bootloader error while dual boot
Public bug reported: i want to dual boot my laptop with windows 10 as primary, while installing 18 LTS it showing error. Before installing ubantu 18 LTS, i was using ubantu 17 and its working fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 11:30:11 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767583 Title: bootloader error while dual boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1767583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766070] [NEW] package corosync 2.3.5-3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Corosync ProblemType: Package DistroRelease: Ubuntu 16.04 Package: corosync 2.3.5-3ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 AptOrdering: zotero-standalone: Install corosync: Configure zotero-standalone: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Apr 21 14:11:35 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-11-14 (524 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: corosync Title: package corosync 2.3.5-3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.corosync.corosync.conf: 2017-10-22T20:31:36.565339 ** Affects: corosync (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766070 Title: package corosync 2.3.5-3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1766070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757194] [NEW] package mysql-server-5.7 5.7.21-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: This crashes my software update every time I do update via software update. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: mysql-server-5.7 5.7.21-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic i686 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 Date: Sun Mar 18 18:48:42 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-05-08 (681 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) Logs.var.log.daemon.log: Logs.var.log.mysql.error.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf: [mysqld_safe] syslog MySQLVarLibDirListing: ['DATABASE', 'ib_logfile1', 'debian-5.7.flag', 'DBMSFinal', 'mysql_upgrade_info', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile0', 'ibdata1'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=3dace278-b1db-4184-b03a-5b955a8b2a86 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.25 SourcePackage: mysql-5.7 Title: package mysql-server-5.7 5.7.21-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-5.7 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757194 Title: package mysql-server-5.7 5.7.21-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1757194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713194] Re: package snmpd 5.7.3+dfsg-1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
vivek@vivek-VPCCB45FN:~$ sudo apt-get install snmp-mibs-downloader vivek@vivek-VPCCB45FN:~$ sudo apt-get install snmpd I AM TRING TO START SNMPD USING THE ABOVE COMMANDS AND BEING LEFT WITH THE BELOW ERROR.. WHAT IS THE PROBLEM??? HOW CAN I SOLVE THIS??? PLZZZ HELP.. THANK U IN ADVANCE.. Setting up snmpd (5.7.3+dfsg-1ubuntu4) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults update-rc.d: warning: stop runlevel arguments (1) do not match snmpd Default-Stop values (0 1 6) Job for snmpd.service failed because the control process exited with error code. See "systemctl status snmpd.service" and "journalctl -xe" for details. invoke-rc.d: initscript snmpd, action "start" failed. ● snmpd.service - LSB: SNMP agents Loaded: loaded (/etc/init.d/snmpd; bad; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2017-08-26 05:48:45 CEST; 5ms ago Docs: man:systemd-sysv-generator(8) Process: 6331 ExecStart=/etc/init.d/snmpd start (code=exited, status=127) Aug 26 05:48:45 vivek-VPCCB45FN systemd[1]: Starting LSB: SNMP agents... Aug 26 05:48:45 vivek-VPCCB45FN snmpd[6331]: * Starting SNMP services: Aug 26 05:48:45 vivek-VPCCB45FN snmpd[6331]: /usr/sbin/snmpd: symbol lookup error: /usr/sbin/snmpd: undefined symbol: smux_listen_sd Aug 26 05:48:45 vivek-VPCCB45FN systemd[1]: snmpd.service: Control process exited, code=exited status=127 Aug 26 05:48:45 vivek-VPCCB45FN systemd[1]: Failed to start LSB: SNMP agents. Aug 26 05:48:45 vivek-VPCCB45FN systemd[1]: snmpd.service: Unit entered failed state. Aug 26 05:48:45 vivek-VPCCB45FN systemd[1]: snmpd.service: Failed with result 'exit-code'. dpkg: error processing package snmpd (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: snmpd E: Sub-process /usr/bin/dpkg returned an error code (1) ** Changed in: net-snmp (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/net-snmp/+question/656995 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713194 Title: package snmpd 5.7.3+dfsg-1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1713194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1658803] Re: package snmpd 5.7.3 failed to install: subprocess installed post-installation script returned error exit status 1
** Changed in: net-snmp (Ubuntu) Status: Expired => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1658803 Title: package snmpd 5.7.3 failed to install: subprocess installed post- installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1658803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713194] [NEW] package snmpd 5.7.3+dfsg-1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Both the below commands are showing the problem attached below.. plzzz help.. vivek@vivek-VPCCB45FN:~$ sudo apt-get install snmp-mibs-downloader [sudo] password for vivek: Reading package lists... Done Building dependency tree Reading state information... Done snmp-mibs-downloader is already the newest version (1.1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up snmpd (5.7.3+dfsg-1ubuntu4) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults update-rc.d: warning: stop runlevel arguments (1) do not match snmpd Default-Stop values (0 1 6) Job for snmpd.service failed because the control process exited with error code. See "systemctl status snmpd.service" and "journalctl -xe" for details. invoke-rc.d: initscript snmpd, action "start" failed. ● snmpd.service - LSB: SNMP agents Loaded: loaded (/etc/init.d/snmpd; bad; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2017-08-26 05:48:00 CEST; 5ms ago Docs: man:systemd-sysv-generator(8) Process: 6220 ExecStart=/etc/init.d/snmpd start (code=exited, status=127) Aug 26 05:47:59 vivek-VPCCB45FN systemd[1]: Starting LSB: SNMP agents... Aug 26 05:48:00 vivek-VPCCB45FN snmpd[6220]: * Starting SNMP services: Aug 26 05:48:00 vivek-VPCCB45FN snmpd[6220]: /usr/sbin/snmpd: symbol lookup error: /usr/sbin/snmpd: undefined symbol: smux_listen_sd Aug 26 05:48:00 vivek-VPCCB45FN systemd[1]: snmpd.service: Control process exited, code=exited status=127 Aug 26 05:48:00 vivek-VPCCB45FN systemd[1]: Failed to start LSB: SNMP agents. Aug 26 05:48:00 vivek-VPCCB45FN systemd[1]: snmpd.service: Unit entered failed state. Aug 26 05:48:00 vivek-VPCCB45FN systemd[1]: snmpd.service: Failed with result 'exit-code'. dpkg: error processing package snmpd (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: snmpd E: Sub-process /usr/bin/dpkg returned an error code (1) ****** vivek@vivek-VPCCB45FN:~$ sudo apt-get install snmpd Reading package lists... Done Building dependency tree Reading state information... Done snmpd is already the newest version (5.7.3+dfsg-1ubuntu4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up snmpd (5.7.3+dfsg-1ubuntu4) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults update-rc.d: warning: stop runlevel arguments (1) do not match snmpd Default-Stop values (0 1 6) Job for snmpd.service failed because the control process exited with error code. See "systemctl status snmpd.service" and "journalctl -xe" for details. invoke-rc.d: initscript snmpd, action "start" failed. ● snmpd.service - LSB: SNMP agents Loaded: loaded (/etc/init.d/snmpd; bad; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2017-08-26 05:48:45 CEST; 5ms ago Docs: man:systemd-sysv-generator(8) Process: 6331 ExecStart=/etc/init.d/snmpd start (code=exited, status=127) Aug 26 05:48:45 vivek-VPCCB45FN systemd[1]: Starting LSB: SNMP agents... Aug 26 05:48:45 vivek-VPCCB45FN snmpd[6331]: * Starting SNMP services: Aug 26 05:48:45 vivek-VPCCB45FN snmpd[6331]: /usr/sbin/snmpd: symbol lookup error: /usr/sbin/snmpd: undefined symbol: smux_listen_sd Aug 26 05:48:45 vivek-VPCCB45FN systemd[1]: snmpd.service: Control process exited, code=exited status=127 Aug 26 05:48:45 vivek-VPCCB45FN systemd[1]: Failed to start LSB: SNMP agents. Aug 26 05:48:45 vivek-VPCCB45FN systemd[1]: snmpd.service: Unit entered failed state. Aug 26 05:48:45 vivek-VPCCB45FN systemd[1]: snmpd.service: Failed with result 'exit-code'. dpkg: error processing package snmpd (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: snmpd E: Sub-process /usr/bin/dpkg returned an error code (1) * ProblemType: Package DistroRelease: Ubuntu 16.04 Package: snmpd 5.7.3+dfsg-1ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76 Uname: Linux 4.4.0-92-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: snmpd: Install snmpd: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Aug 26 04:25:24 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-11-1
[Bug 1694152] [NEW] Installation Failed
Public bug reported: Ubuntu installation failed with fatal error while doing dual boot with Windows 10 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ubiquity 17.04.9 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CasperVersion: 1.380 Date: Sun May 28 20:16:00 2017 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: LANGUAGE=en_GB.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-17.04.9 ubuntu zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694152 Title: Installation Failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1694152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692001] [NEW] package vim-common 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is also in package vim 20170503-1
Public bug reported: When I update using apt update, these errors started to come. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: vim-common 2:7.4.1689-3ubuntu1.2 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri May 19 15:24:50 2017 DuplicateSignature: package:vim-common:2:7.4.1689-3ubuntu1.2 Unpacking vim-common (2:7.4.1689-3ubuntu1.2) ... dpkg: error processing archive /var/cache/apt/archives/vim-common_2%3a7.4.1689-3ubuntu1.2_amd64.deb (--unpack): trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is also in package vim 20170503-1 ErrorMessage: trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is also in package vim 20170503-1 InstallationDate: Installed on 2017-02-01 (107 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: vim Title: package vim-common 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is also in package vim 20170503-1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vim (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692001 Title: package vim-common 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is also in package vim 20170503-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1692001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576329] Re: package nginx-core 1.10.0-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
package nginx-core 1.10.0-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576329 Title: package nginx-core 1.10.0-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1576329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1650840] [NEW] Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module i915
Public bug reported: Doing sudo apt-get upgrade I got 'Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module i915'. When I further searched on this I found it may damage my machine. How can I fix it and will it really damage my machine? Thank You. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-30-generic 4.8.0-30.32 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vivekkmr 2930 F pulseaudio /dev/snd/controlC1: vivekkmr 2930 F pulseaudio CurrentDesktop: Unity Date: Sun Dec 18 09:54:57 2016 HibernationDevice: RESUME=UUID=d83a66d7-bd7b-4e8a-877f-d0c46667a633 InstallationDate: Installed on 2016-05-12 (219 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Hewlett-Packard HP Notebook ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic.efi.signed root=UUID=35e4ec29-8033-471e-b695-662c626a8697 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-30-generic N/A linux-backports-modules-4.8.0-30-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-11-17 (30 days ago) dmi.bios.date: 07/23/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C4 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.11 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.11:bd07/23/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C4:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650840 Title: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module i915 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642507] [NEW] Not internet after waking from suspend
Public bug reported: Release Information: Distributor ID: Ubuntu Description:Ubuntu 16.10 Release:16.10 Codename: yakkety Package Information: network-manager: Installed: 1.2.4-0ubuntu1 Candidate: 1.2.4-0ubuntu1 Version table: *** 1.2.4-0ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status System Information: Dell XPS 15 9550 Wireless: Network controller: Broad com Limited BCM43602 802.11ac Wireless LAN SoC (rev 01) Wired: Wired Ethernet via Apple USB Ethernet Adapter (ID 05ac:1402 Apple, Inc. Ethernet Adapter [A1277]) Problem Description: I have noticed the problem on both wired and wireless. Ever since upgrading to 16.10(from 16.04), the system loses internet after waking from suspend. Internet works fine after a reboot or when powering on normally. "service network-manager restart" fixes the problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 17 09:37:30 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-31 (169 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.80.1 dev enx7cc3a187f0f2 proto static metric 100 default via 192.168.80.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.80.0/24 dev enx7cc3a187f0f2 proto kernel scope link src 192.168.80.209 metric 100 192.168.80.0/24 dev wlp2s0 proto kernel scope link src 192.168.80.225 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2016-10-28 (19 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enx7cc3a187f0f2 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 e6493319-b925-3b33-92a7-259922dccdaa /org/freedesktop/NetworkManager/ActiveConnection/1 wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/1 whymusticry_fast 1 b51f9098-d053-45d7-ba42-97bf2e87bda2 /org/freedesktop/NetworkManager/ActiveConnection/0 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642507 Title: Not internet after waking from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1642507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640454] [NEW] Nautilus can not display Recent
Public bug reported: Release: Ubuntu 16.10 64 bits Package Info: nautilus: Installed: 1:3.20.3-1ubuntu3 Candidate: 1:3.20.3-1ubuntu3.1 Version table: 1:3.20.3-1ubuntu3.1 500 500 http://se.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 Packages *** 1:3.20.3-1ubuntu3 500 500 http://se.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status Expected behaviour: When a user open Files, and click Recent on the sidebar, the user expects to see a list of recently accessed files Current behaviour: The user sees an error message instead Additional notes: This error does not occur with a file uploader, for eg: from a browser ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 9 12:36:08 2016 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1033x685+1920+24'" b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2016-05-31 (161 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-28 (11 days ago) usr_lib_nautilus: dropbox2015.10.28 gnome-terminal 3.20.2-1ubuntu5 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug files nautilus yakkety ** Attachment added: "files_error.png" https://bugs.launchpad.net/bugs/1640454/+attachment/4774842/+files/files_error.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640454 Title: Nautilus can not display Recent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1640454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629589] [NEW] Ubuntu-Gnome Installer crashed. Showing 'grub-efi-amd64-signed' package failed to install into /target/. Afterwards, it asked to quit the installation. Now my Windows is also not b
Public bug reported: Report showed that ubiquity had some problem. I have tried once again doing resizing the partition (and formatting them)... but the result is same. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CasperVersion: 1.376 Date: Sat Oct 1 13:36:46 2016 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu-gnome.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63.2 ubuntu-gnome xenial ** Summary changed: - Ubuntu-Gnome Installer crashed. Showed 'grub-efi-amd64-signed' package failed to install into /target/. After it asked to quit the installation. Now my Windows is also booting. rather it shows the grub rescue screen. + Ubuntu-Gnome Installer crashed. Showing 'grub-efi-amd64-signed' package failed to install into /target/. Afterwards, it asked to quit the installation. Now my Windows is also not booting. rather it shows the grub rescue screen. ** Summary changed: - Ubuntu-Gnome Installer crashed. Showing 'grub-efi-amd64-signed' package failed to install into /target/. Afterwards, it asked to quit the installation. Now my Windows is also not booting. rather it shows the grub rescue screen. + Ubuntu-Gnome Installer crashed. Showing 'grub-efi-amd64-signed' package failed to install into /target/. Afterwards, it asked to quit the installation. Now my Windows is also not booting, rather it shows the grub rescue screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629589 Title: Ubuntu-Gnome Installer crashed. Showing 'grub-efi-amd64-signed' package failed to install into /target/. Afterwards, it asked to quit the installation. Now my Windows is also not booting, rather it shows the grub rescue screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1629589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592316] [NEW] couldn't install ubuntu
Public bug reported: After opting something else, new partition, providing 25gigs of memory for root, 6gigs for swap and rest for home directory. Then during installation this occurs. 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: Tue Jun 14 14:16:36 2016 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid initrd=/casper/initrd.lz quiet splash --- BOOT_IMAGE=/casper/vmlinuz.efi LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages ubiquity-2.21.63 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592316 Title: couldn't install ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1592316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589219] [NEW] Ubuntu installation crashed
Public bug reported: Ubuntu installation crashed ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubiquity 2.20.0 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 CasperVersion: 1.345 Date: Sun Jun 5 16:15:55 2016 InstallCmdLine: bootkbd=us console-setup/layoutcode=en_US console-setup/variantcode=nodeadkeys locale=us_us noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz splash -- maybe-ubiquity LiveMediaBuild: Ubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1) ProcEnviron: LANGUAGE=en_IN TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 ubiquity-2.20.0 ubuntu utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589219 Title: Ubuntu installation crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1589219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569342] [NEW] Airplane Mode cannot be turned off
Public bug reported: My hp laptop has a rt3290 chipset which stopped working while I used ubuntu 15.10 although it works on Windows 10 which I dual boot. I bought a usb wifi with a rt2870 chipset, which worked out of the box with ubuntu 15.10 but has stopped working since I upgraded to 16.04. Also, the airplane mode in connection settings is fixed at on and cannot be turned off. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: i3 Date: Wed Apr 13 05:28:34 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-11 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) IpRoute: default via 10.109.250.1 dev eno1 proto static metric 100 10.109.0.0/16 dev eno1 proto kernel scope link src 10.109.141.50 metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false WimaxEnabled=true ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 9d39a0f7-8bf2-4a7c-a64d-4cb5a359a51a 802-3-ethernet 1460505238 Wednesday 13 April 2016 05:23:58 AM IST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/0 yes eno1 activated /org/freedesktop/NetworkManager/ActiveConnection/0 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH eno1 ethernet connected /org/freedesktop/NetworkManager/Devices/1 Wired connection 1 9d39a0f7-8bf2-4a7c-a64d-4cb5a359a51a /org/freedesktop/NetworkManager/ActiveConnection/0 wlo1 wifi unavailable /org/freedesktop/NetworkManager/Devices/0 -- -- -- wlxc83a35ca4110 wifi unavailable /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569342 Title: Airplane Mode cannot be turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1569342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559639] [NEW] Similar to Bug #1234453. Clicking on an icon with 2 or more open windows reloads UI
Public bug reported: This happens specially on File Manager. Ubuntu version 15.10 (manually installed from USB live boot). Last updated : Mar 19th. RAM usage : 800 MB/ 4GB Machine : Compaq Laptop. Steps to reproduce the bug: Click on file icon : Opens a new window of your home folder. type +n to open a new window now try single/double click on the file manager icon on the dock. you see the desktop wallpaper, screen refreshes including the dock No loss of information. However very irritating. Addendum: 1. tested it on terminal window, by opening multiple windows and clicking on the terminal window icon, the UI still crashes. 2. Clicking multiple times (4-5 times) on the icon with multiple windows, renders the screen unresponsive for 4-5 seconds. Regards, Vivekanand Kini ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Description changed: - This happens specially on File Manager. - Ubuntu version 15.10 - Last updated : Mar 19th. + This happens specially on File Manager. + Ubuntu version 15.10 (manually installed from USB live boot). + Last updated : Mar 19th. + RAM usage : 800 MB/ 4GB + Machine : Compaq Laptop. Steps to reproduce the bug: Click on file icon : Opens a new window of your home folder. type +n to open a new window now try single/double click on the file manager icon on the doc. you see the desktop wallpaper, screen refreshes including the doc. No loss of information. However very irritating. + Addendum: + + 1. tested it on terminal window, by opening multiple windows and + clicking on the terminal window icon, the page still crashes. + + 2. Clicking multiple times (4-5 times) on the icon with multiple + windows, renders the screen unresponsive for 4-5 seconds. + Regards, Vivekanand Kini ** Description changed: This happens specially on File Manager. Ubuntu version 15.10 (manually installed from USB live boot). Last updated : Mar 19th. - RAM usage : 800 MB/ 4GB - Machine : Compaq Laptop. + RAM usage : 800 MB/ 4GB + Machine : Compaq Laptop. Steps to reproduce the bug: Click on file icon : Opens a new window of your home folder. type +n to open a new window - now try single/double click on the file manager icon on the doc. + now try single/double click on the file manager icon on the dock. - you see the desktop wallpaper, screen refreshes including the doc. + you see the desktop wallpaper, screen refreshes including the dock No loss of information. However very irritating. Addendum: 1. tested it on terminal window, by opening multiple windows and clicking on the terminal window icon, the page still crashes. 2. Clicking multiple times (4-5 times) on the icon with multiple windows, renders the screen unresponsive for 4-5 seconds. Regards, Vivekanand Kini ** Description changed: This happens specially on File Manager. Ubuntu version 15.10 (manually installed from USB live boot). Last updated : Mar 19th. RAM usage : 800 MB/ 4GB Machine : Compaq Laptop. Steps to reproduce the bug: Click on file icon : Opens a new window of your home folder. type +n to open a new window now try single/double click on the file manager icon on the dock. you see the desktop wallpaper, screen refreshes including the dock No loss of information. However very irritating. Addendum: 1. tested it on terminal window, by opening multiple windows and - clicking on the terminal window icon, the page still crashes. + clicking on the terminal window icon, the UI still crashes. 2. Clicking multiple times (4-5 times) on the icon with multiple windows, renders the screen unresponsive for 4-5 seconds. Regards, Vivekanand Kini -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559639 Title: Similar to Bug #1234453. Clicking on an icon with 2 or more open windows reloads UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1559639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 340222] Re: nautilus crashed with SIGSEGV in g_closure_invoke()
** Attachment added: "_usr_bin_nautilus.1000.crash" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/340222/+attachment/4565881/+files/_usr_bin_nautilus.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/340222 Title: nautilus crashed with SIGSEGV in g_closure_invoke() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/340222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492897] [NEW] package cairo-dock-data 3.4.1-0ubuntu1 failed to install/upgrade: package cairo-dock-data is already installed and configured
Public bug reported: automatically reboot when I change any setting in compiz. launcher auto- hide not working. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: cairo-dock-data 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-27.29-generic 3.19.8-ckt5 Uname: Linux 3.19.0-27-generic i686 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.4 AptdaemonVersion: 1.1.1+bzr982-0ubuntu3.1 Architecture: i386 Date: Mon Sep 7 04:12:28 2015 Dependencies: DuplicateSignature: package:cairo-dock-data:3.4.1-0ubuntu1:package cairo-dock-data is already installed and configured ErrorMessage: package cairo-dock-data is already installed and configured InstallationDate: Installed on 2015-08-11 (26 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.2 SourcePackage: dpkg Title: package cairo-dock-data 3.4.1-0ubuntu1 failed to install/upgrade: package cairo-dock-data is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed apport-package i386 vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492897 Title: package cairo-dock-data 3.4.1-0ubuntu1 failed to install/upgrade: package cairo-dock-data is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1492897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1443993] [NEW] E: Unable to locate package oracle-java7-installer
Public bug reported: vivek@Devoloper-Machine:~$ sudo apt-get install oracle-java7-installer Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package oracle-java7-installer vivek@Devoloper-Machine:~$ Always the error message arises whenever i try to install a new software.I have also tried changing the server but still the same error arises. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-terminal 2.32.1-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Date: Tue Apr 14 20:13:37 2015 ExecutablePath: /usr/bin/gnome-terminal InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_IN:en LANG=en_IN LC_MESSAGES=en_IN.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug apport-lpi i386 natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1443993 Title: E: Unable to locate package oracle-java7-installer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1443993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438130] [NEW] Firefox 36.0.4 reports plugins vulnerability sudo upgrade tells already updated
Public bug reported: I have recently updated system , firefox (36.0.4) reports that vlc and quicktime plugin(totem) is vulnerable, however when checked for updates via update browser-plugin-vlc and totem its says Already the newest version ** 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/1438130 Title: Firefox 36.0.4 reports plugins vulnerability sudo upgrade tells already updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1438130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 879218] Re: some users prefer the old grid behaviour (dividing each time the keybinding are used)
So is there a fix for making ctrl + alt + numpad 4 and numpad 6 cycle between the various widths for multiple keypresses instead of just being half? Because my compiz grid still does not work. I am on Ubuntu 12.04 LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/879218 Title: some users prefer the old grid behaviour (dividing each time the keybinding are used) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/879218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1378631] [NEW] BUG: Bad page map in process postgres pte:02000000 pmd:30b4f9067
Public bug reported: The problem occurs during bootup ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-36-generic 3.13.0-36.63 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vivek 3380 F pulseaudio /dev/snd/controlC0: vivek 3380 F pulseaudio Date: Tue Sep 30 19:15:40 2014 Failure: oops HibernationDevice: RESUME=UUID=9050a93d-5986-46b3-8e64-a8d4b3ba1965 InstallationDate: Installed on 2011-02-15 (1330 days ago) InstallationMedia: Ubuntu-Server 10.10 Maverick Meerkat - Release amd64 (20101007) IwConfig: eth1 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. XPS 8300 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=9e058c03-dccd-4733-8975-49e2adc31ffe ro quiet PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8 RfKill: SourcePackage: linux Title: BUG: Bad page map in process postgres pte:0200 pmd:30b4f9067 UpgradeStatus: Upgraded to trusty on 2014-09-20 (17 days ago) WifiSyslog: dmi.bios.date: 02/15/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0Y2MRG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd02/15/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8300 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops kernel-oops trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1378631 Title: BUG: Bad page map in process postgres pte:0200 pmd:30b4f9067 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1378631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1348062] [NEW] bluetooth is disabled ( ralink 3290)
Public bug reported: OS: Ubutu 14.04 root@Viv-PC:/home/viv# apt-cache policy bluetooth bluetooth: Installed: (none) Candidate: 4.101-0ubuntu13 Version table: 4.101-0ubuntu13 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages The combo button in HP laptop doesn't start blueooth (WiFI Works but not blinking) and there is no icon on the top right (control center) ** Affects: gnome-control-center (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/1348062 Title: bluetooth is disabled ( ralink 3290) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1348062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1347169] [NEW] Various storvsc bug fixes.
Public bug reported: Over last week we have made changes and fix bugs in storvsc , please include these patch set . [PATCH V3 1/7] Drivers: scsi: storvsc: Change the limits to reflect the values on the hostIn Hyper-V, each port/path/target maps to 1 scsi host adapter. In reality, the path/target is not used (ie always set to 0) so our scsi host adapter essentially has 1 bus with 1 target that contains up to 256 luns. http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/?id=01a1fc6a17a33edc6b43aca255b31f51497e2414 [PATCH V3 2/7] Drivers: scsi: storvsc: Set cmd_per_lun to reflect value supported by the HostSet cmd_per_lun to reflect value supported by the Host. http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/?id=4a1e22529bda70eacde631bf4611b61b7aac9ae6 [PATCH V3 3/7] Drivers: scsi: storvsc: Filter commands based on the storage protocol version Going forward it is possible that some of the commands that are not currently implemented will be implemented on future Windows hosts. Even if they are not implemented, we are told the host will corrrectly handle unsupported commands (by returning appropriate return code and sense information). Make command filtering depend on the host version. http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/?id=5aacedc1953dcaa1434a179147861319c919503e [PATCH V3 4/7] Drivers: scsi: storvsc: Fix a bug in handling VMBUS protocol version Based on the negotiated VMBUS protocol version, we adjust the size of the storage protocol messages. The two sizes we currently handle are pre-win8 and post-win8. In WS2012 R2, we are negotiating higher VMBUS protocol version than the win8 version. Make adjustments to correctly handle this. http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/?id=0d0da066835a1194f3a6c425054db90b089e74ea [PATCH 5/7] Drivers: scsi: storvsc: Implement a timedout handler On Azure, we have seen instances of unbounded I/O latencies. To deal with this issue, implement handler that can reset the timeout. Note that the host gaurantees that it will respond to each command that has been issued. http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/?id=ec5dafb2361fb393e12745bda837707be2041436 [PATCH 6/7] drivers: scsi: storvsc: Set srb_flags in all cases Correctly set SRB flags for all valid I/O directions. Some IHV drivers on the Windows host require this. The host validates the command and SRB flags prior to passing the command down to native driver stack. http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/?id=20e9f28dd87e62d10f2c434396c734da43329c57 [PATCH 7/7] drivers: scsi: storvsc: Correctly handle TEST_UNIT_READY failure On some Windows hosts on FC SANs, TEST_UNIT_READY can return SRB_STATUS_ERROR. Correctly handle this. Note that there is sufficient sense information to support scsi error handling even in this case. http://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/?id=27ac92916691eab6c9ca74db19a4b13084d5c78d Thanks, Abhishek ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1347169 Title: Various storvsc bug fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1347169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1347169] Re: Various storvsc bug fixes.
Hi Joseph, They are all upsteam and accepted . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1347169 Title: Various storvsc bug fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1347169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217177] Re: ubiquity freezes when run from live session
*** This bug is a duplicate of bug 1226912 *** https://bugs.launchpad.net/bugs/1226912 I'm stil facing the issue in the daily build. Is there a workaround? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217177 Title: ubiquity freezes when run from live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1217177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 759619] Re: banshee cannot access last.fm account
Even I have the same problem where I have entered the user name of my Last.fm account and then if I click on 'Finish logging in', it doesn't respond. If I click on 'try Again', then also it doesn't respond as a matter of fact it toggles between the two options. I am using Banshee 2.6.1 on Ubuntu 13.04. The ~/.config/banshee-1/log file had the following messages which might come in handy: [Warn 13:59:57.889] Error in Lastfm.Account.RequestAuthorization - System.NullReferenceException: Object reference not set to an instance of an object (in `Lastfm') at Lastfm.Account.RequestAuthorization () [0x0] in filename unknown:0 [8372:8403:0320/140002:ERROR:nss_util.cc(750)] After loading Root Certs, loaded==false: NSS error code: -8018 Created new window in existing browser session. [Warn 14:04:10.644] Audioscrobbler NowPlaying failed: Unknown [Warn 14:04:11.805] Caught an exception - System.Net.Sockets.SocketException: Connection refused (in `System') at System.Net.Sockets.Socket.Connect (System.Net.EndPoint remoteEP) [0x0] in filename unknown:0 at System.Net.WebConnection.Connect (System.Net.HttpWebRequest request) [0x0] in filename unknown:0 System.Net.WebException: Error: ConnectFailure (Connection refused) (in `System') at System.Net.HttpWebRequest.EndGetResponse (IAsyncResult asyncResult) [0x0] in filename unknown:0 at System.Net.HttpWebRequest.GetResponse () [0x0] in filename unknown:0 at Banshee.Metadata.MetadataServiceJob.GetHttpStream (System.Uri uri, System.String[] ignoreMimeTypes) [0x0] in filename unknown:0 at Banshee.Metadata.MetadataServiceJob.GetHttpStream (System.Uri uri) [0x0] in filename unknown:0 at Banshee.Metadata.Rhapsody.RhapsodyQueryJob.Run () [0x0] in filename unknown:0 at Banshee.Metadata.MetadataServiceJob.Run () [0x0] in filename unknown:0 [Info 14:05:35.205] Last.fm authorization result = TokenNotAuthorized [Warn 14:05:36.397] Error in Lastfm.Account.RequestAuthorization - System.NullReferenceException: Object reference not set to an instance of an object (in `Lastfm') at Lastfm.Account.RequestAuthorization () [0x0] in filename unknown:0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/759619 Title: banshee cannot access last.fm account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/759619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1266052] [NEW] software-property-gtk
Public bug reported: software-property-gtk crashed with aptsources.distro.nodistro template exception ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: software-properties-gtk 0.92.28 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sat Jan 4 21:33:00 2014 MarkForUpload: True PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy third-party-packages ** Attachment added: _usr_bin_software-properties-gtk.1001.crash https://bugs.launchpad.net/bugs/1266052/+attachment/3940510/+files/_usr_bin_software-properties-gtk.1001.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1266052 Title: software-property-gtk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1266052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094401] Re: Failed to install correctly, Errors were encountered while processing: man-db lintian localepurge man2html perlindex
Thanks Ronald. This fixes it. sudo mkdir /var/cache/debconf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094401 Title: Failed to install correctly, Errors were encountered while processing: man-db lintian localepurge man2html perlindex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1094401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1098561] Re: Unsupported hardware watermark appears when FGLRX is installed on 13.04
Confirmed on my Radeon HD 7870. ~ fglrxinfo display: :0 screen: 0 OpenGL vendor string: Advanced Micro Devices, Inc. OpenGL renderer string: AMD Radeon HD 7800 Series OpenGL version string: 4.2.11986 Compatibility Profile Context -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1098561 Title: Unsupported hardware watermark appears when FGLRX is installed on 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1098561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1172829] [NEW] notify-osd crashed with SIGABRT in raise()
Public bug reported: notify-osd crashed with SIGABRT in raise() ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: notify-osd 0.9.34-0ubuntu5 ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7 Uname: Linux 3.5.0-27-generic i686 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 Date: Thu Apr 25 23:31:51 2013 MachineType: Dell Inc. Latitude E6400 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-27-generic root=UUID=440cc8fc-751a-4be8-a39d-62976a6dfd03 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu4 libgl1-mesa-glx 9.0.3-0ubuntu0.1 libdrm2 2.4.39-0ubuntu1 xserver-xorg-video-intel 2:2.20.9-0ubuntu2.1 xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 SourcePackage: notify-osd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A29 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA29:bd04/13/2011:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6400 dmi.sys.vendor: Dell Inc. ** Affects: notify-osd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal third-party-packages ** Attachment added: _usr_lib_notify-osd_notify-osd.1000.crash https://bugs.launchpad.net/bugs/1172829/+attachment/3653524/+files/_usr_lib_notify-osd_notify-osd.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1172829 Title: notify-osd crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1172829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1156458] [NEW] Software center failed with DBBusException in call blocking()
Public bug reported: Software center failed with DBBusException in call blocking() Failed to execute oneconf service. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: software-center 5.4.1.4 ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic i686 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 Date: Mon Mar 18 11:16:04 2013 InstallationDate: Installed on 2013-03-12 (5 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MarkForUpload: True PackageArchitecture: all SourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal third-party-packages ** Attachment added: Software center failed with DBBusException in call blocking() failed to execute oneconf https://bugs.launchpad.net/bugs/1156458/+attachment/3580834/+files/_usr_share_software-center_software-center.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1156458 Title: Software center failed with DBBusException in call blocking() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1156458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1153553] [NEW] [g41] GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000002 IPEHR: 0x05000000
Public bug reported: These lockups occur when I minimize the screen in online videos. I get a plain white screen but the sound will still be playing. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-intel 2:2.21.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2 Uname: Linux 3.8.0-11-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.1-0ubuntu1 Architecture: amd64 Chipset: g41 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 11 16:01:18 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DuplicateSignature: [g41] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002 IPEHR: 0x0500 Ubuntu 13.04 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device [1458:d000] InstallationDate: Installed on 2013-01-24 (45 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130124) InterpreterPath: /usr/bin/python3.3 MachineType: Gigabyte Technology Co., Ltd. G41M-Combo MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-11-generic root=UUID=e9eabbeb-bdfd-4bc8-a691-25a55400f444 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu4 libdrm2 2.4.42-0ubuntu1 xserver-xorg-video-intel 2:2.21.3-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [g41] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002 IPEHR: 0x0500 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/09/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F3 dmi.board.name: G41M-Combo dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd06/09/2010:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41M-Combo dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.9~daily13.03.08-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.42-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu3 xserver.bootTime: Mon Mar 11 16:44:45 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputgspca_sn9c20xKEYBOARD, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 inputImExPS/2 Logitech Explorer Mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.2-0ubuntu3 xserver.video_driver: intel ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash compiz-0.9 freeze need-duplicate-check raring ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1153553 Title: [g41] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002 IPEHR: 0x0500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1153553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1127303] Re: [g41] False GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000002 IPEHR: 0x0a000002
I was not able to play any of my local music and movies. Rhythymbox player would not play the songs even if I hit the play button. The movie player crashed. But both the players started working fine after the reboot. On Mon, Feb 18, 2013 at 11:25 PM, Bryce Harrington 1127...@bugs.launchpad.net wrote: Can you explain in more detail about how your video players stopped playing movies and songs? E.g. were the media files available locally or over the network (e.g. cloud, nfs, etc.) I ask because there is also an error from your Atheros ethernet driver coincident to the gpu lockup. Iff those files were being loaded across the network, it's *possible* you have two different bugs (in which case the question becomes why did they occur simultaneously). Did the movie player crash, exit with an error, show a blank screen, ...? Also, can you confirm your system did *not* lock up in conjunction with the bug? Did it eventually recover and allow you to play movies normally, or did the issue persist until you rebooted? I assume after reboot everything got back to normal? ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1127303 Title: [g41] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002 IPEHR: 0x0a02 Status in “xserver-xorg-video-intel” package in Ubuntu: Incomplete Bug description: This came after Rhythymbox and Movie Player stopped playing any of my movies and songs. [ 849.292005] i915: render error detected, EIR: 0x0010 [ 849.292005] i915: IPEIR: 0x [ 849.292005] i915: IPEHR: 0x0a02 [ 849.292005] i915: INSTDONE_0: 0xfffe [ 849.292005] i915: INSTDONE_1: 0x [ 849.292005] i915: INSTDONE_2: 0x [ 849.292005] i915: INSTDONE_3: 0x [ 849.292005] i915: INSTPS: 0x0001e000 [ 849.292005] i915: ACTHD: 0x02e00b88 [ 849.292005] i915: page table error [ 849.292005] i915: PGTBL_ER: 0x0002 [ 849.292005] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x0010, masking [ 849.632014] atl1c :02:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-intel 2:2.21.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Chipset: g41 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Feb 16 21:01:51 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DuplicateSignature: [g41] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002 IPEHR: 0x0a02 Ubuntu 13.04 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device [1458:d000] InstallationDate: Installed on 2013-01-24 (23 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130124) InterpreterPath: /usr/bin/python3.3 MachineType: Gigabyte Technology Co., Ltd. G41M-Combo MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic root=UUID=e9eabbeb-bdfd-4bc8-a691-25a55400f444 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu4 libdrm2 2.4.42-0ubuntu1 xserver-xorg-video-intel 2:2.21.2-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [g41] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002 IPEHR: 0x0a02 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/09/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F3 dmi.board.name: G41M-Combo dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd06/09/2010:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41M-Combo dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2
[Bug 1127303] [NEW] [g41] False GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000002 IPEHR: 0x0a000002
Public bug reported: This came after Rhythymbox and Movie Player stopped playing any of my movies and songs. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-intel 2:2.21.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Chipset: g41 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Feb 16 21:01:51 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DuplicateSignature: [g41] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002 IPEHR: 0x0a02 Ubuntu 13.04 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device [1458:d000] InstallationDate: Installed on 2013-01-24 (23 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130124) InterpreterPath: /usr/bin/python3.3 MachineType: Gigabyte Technology Co., Ltd. G41M-Combo MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic root=UUID=e9eabbeb-bdfd-4bc8-a691-25a55400f444 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu4 libdrm2 2.4.42-0ubuntu1 xserver-xorg-video-intel 2:2.21.2-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [g41] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002 IPEHR: 0x0a02 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/09/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F3 dmi.board.name: G41M-Combo dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd06/09/2010:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41M-Combo dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.42-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu2 xserver.bootTime: Sun Feb 17 02:17:51 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputgspca_sn9c20xKEYBOARD, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 inputImExPS/2 Logitech Explorer Mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.2-0ubuntu2 xserver.video_driver: intel ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash compiz-0.9 false-gpu-hang freeze raring ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1127303 Title: [g41] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002 IPEHR: 0x0a02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1127303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070833] Re: Chromium-Browser crashed with SIGSEGV in operator new
Chromium browser crashed with SIGSEGV in operator new() ** Attachment added: Chromium browser crashed with SIGSEGV in operator new() https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1070833/+attachment/3513860/+files/_usr_lib_chromium-browser_chromium-browser.1001.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070833 Title: Chromium-Browser crashed with SIGSEGV in operator new To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1070833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1114844] [NEW] Python2.7 crashed with SIGSEGV with dbusmenus_menuitem_build_variant()
Public bug reported: Python2.7 crashed with SIGSEGV with dbusmenus_menuitem_build_variant() ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: python2.7 2.7.3-5ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic i686 NonfreeKernelModules: nvidia wl ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 Date: Mon Feb 4 09:19:20 2013 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: python2.7 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity ** Attachment added: Python2.7 crashed with SIGSEGV with dbusmenus_menuitem_build_variant() https://bugs.launchpad.net/bugs/1114844/+attachment/3513903/+files/_usr_bin_python2.7.1001.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1114844 Title: Python2.7 crashed with SIGSEGV with dbusmenus_menuitem_build_variant() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1114844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1112843] [NEW] update-manager crashed
Public bug reported: update-manager crashed ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: update-manager 1:0.174.4 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic i686 NonfreeKernelModules: nvidia wl ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 Date: Sat Feb 2 01:37:22 2013 DpkgHistoryLog.txt: Start-Date: 2013-02-02 01:34:28 Commandline: /usr/sbin/synaptic Purge: steam:i386 (1.0.0.17) End-Date: 2013-02-02 01:34:34 GsettingsChanges: b'com.ubuntu.update-manager' b'first-run' b'false' b'com.ubuntu.update-manager' b'launch-time' b'1359749100' b'com.ubuntu.update-manager' b'show-details' b'true' b'com.ubuntu.update-manager' b'window-height' b'646' b'com.ubuntu.update-manager' b'window-width' b'500' MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity ** Attachment added: _usr_bin_update-manager.1001.crash https://bugs.launchpad.net/bugs/1112843/+attachment/3510716/+files/_usr_bin_update-manager.1001.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1112843 Title: update-manager crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1112843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 36225] Re: Nautilus Crashes
Logs attached ** Attachment added: _usr_bin_nautilus.1001.crash https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/36225/+attachment/3502490/+files/_usr_bin_nautilus.1001.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/36225 Title: Nautilus Crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/36225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1104654] [NEW] Chromium browser crashed with SIGSEGV
Public bug reported: Chromium browser crashed with SIGSEGV Logs: ProblemType: Crash Architecture: i386 Date: Fri Jan 25 07:45:38 2013 DistroRelease: Ubuntu 12.10 ExecutablePath: /usr/lib/chromium-browser/chromium-browser ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: chromium-browser 23.0.1271.97-0ubuntu0.12.10.1 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic i686 NonfreeKernelModules: wl nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: i386 Date: Fri Jan 25 07:47:18 2013 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ DiskUsage: b'Filesystem Type Size Used Avail Use% Mounted on\n/dev/sda1 ext4 226G 96G 119G 45% /\nudev devtmpfs 2.0G 4.0K 2.0G 1% /dev\ntmpfs tmpfs 793M 1.2M 792M 1% /run\nnone tmpfs 5.0M 0 5.0M 0% /run/lock\nnone tmpfs 2.0G 156K 2.0G 1% /run/shm\nnone tmpfs 100M 68K 100M 1% /run/user\n' Inodes: b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda1 15M 489K 14M4% /\nudev 206K 526 205K1% /dev\ntmpfs 210K 454 209K1% /run\nnone 210K 4 210K1% /run/lock\nnone 210K 7 210K1% /run/shm\nnone 210K30 210K1% /run/user\n' Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n' ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1104654 Title: Chromium browser crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1104654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103795] [NEW] Problem with apport-gtk crashed with struct.error in read32(): unpack requires a byte object of length 4
Public bug reported: Problem with apport-gtk crashed with struct.error in read32(): unpack requires a byte object of length 4. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: apport-gtk 2.6.1-0ubuntu9 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic i686 NonfreeKernelModules: nvidia wl ApportLog: ApportVersion: 2.6.1-0ubuntu9 Architecture: i386 CrashReports: 640:1001:114:6228783:2013-01-23 13:44:23.920546000 +0530:2013-01-23 13:44:24.920546000 +0530:/var/crash/_usr_lib_chromium-browser_chromium-browser.1001.crash 600:105:114:0:2013-01-23 09:17:19.734404291 +0530:2013-01-04 10:41:44.185578899 +0530:/var/crash/_usr_bin_nautilus.1001.uploaded 640:1001:114:49635:2013-01-24 08:25:53.111399000 +0530:2013-01-24 08:25:54.111399000 +0530:/var/crash/_usr_share_apport_apport-gtk.1001.crash Date: Thu Jan 24 08:25:40 2013 InstallationDate: Installed on 2012-05-16 (252 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to quantal on 2012-09-18 (127 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity ** Attachment added: Problem with apport-gtk crashed with struct.error in read32(): unpack requires a byte object of length 4. https://bugs.launchpad.net/bugs/1103795/+attachment/3497728/+files/_usr_share_apport_apport-gtk.1001.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103795 Title: Problem with apport-gtk crashed with struct.error in read32(): unpack requires a byte object of length 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1103795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355846] Re: audacity stops recording after about a second when using software play-through
** Changed in: audacity (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/355846 Title: audacity stops recording after about a second when using software play-through To manage notifications about this bug go to: https://bugs.launchpad.net/audacity/+bug/355846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070833] Re: Chromium-Browser crashed with SIGSEGV in operator new
Chromium-browser crashed with SIGSEGV in new operator() ** Attachment added: _usr_lib_chromium-browser_chromium-browser.1001.crash https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1070833/+attachment/3419423/+files/_usr_lib_chromium-browser_chromium-browser.1001.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070833 Title: Chromium-Browser crashed with SIGSEGV in operator new To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1070833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1071974] [NEW] Cheese has closed unexpectedly with SIGABRT
Public bug reported: Cheese has closed unexpectedly with SIGABRT ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cheese 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 NonfreeKernelModules: nvidia wl ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 Date: Sat Oct 27 08:31:16 2012 InstallationDate: Installed on 2012-05-16 (163 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cheese UpgradeStatus: Upgraded to quantal on 2012-09-18 (38 days ago) ** Affects: cheese (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity ** Attachment added: _usr_bin_cheese.1001.crash https://bugs.launchpad.net/bugs/1071974/+attachment/3415031/+files/_usr_bin_cheese.1001.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1071974 Title: Cheese has closed unexpectedly with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1071974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070833] [NEW] Chromium-Browser crashed with SIGSEGV in operator new
Public bug reported: Chromium-Browser crashed with SIGSEGV in operator new ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: chromium-browser 22.0.1229.94~r161065-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 NonfreeKernelModules: wl nvidia ApportVersion: 2.6.1-0ubuntu3 Architecture: i386 ChromiumPrefs: can't open profile /root/.config/chromium/Default/Preferences Date: Wed Oct 24 18:34:30 2012 Desktop-Session: DESKTOP_SESSION = None XDG_CONFIG_DIRS = None XDG_DATA_DIRS = None DiskUsage: b'Filesystem Type Size Used Avail Use% Mounted on\n/dev/sda1 ext4 226G 82G 133G 39% /\nudev devtmpfs 2.0G 4.0K 2.0G 1% /dev\ntmpfs tmpfs 793M 1.1M 792M 1% /run\nnone tmpfs 5.0M 0 5.0M 0% /run/lock\nnone tmpfs 2.0G 720K 2.0G 1% /run/shm\nnone tmpfs 100M 40K 100M 1% /run/user\n' Inodes: b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda1 15M 380K 14M3% /\nudev 206K 548 205K1% /dev\ntmpfs 210K 478 209K1% /run\nnone 210K 4 210K1% /run/lock\nnone 210K 7 210K1% /run/shm\nnone 210K24 210K1% /run/user\n' Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: Upgraded to quantal on 2012-09-18 (36 days ago) chromium-default: CHROMIUM_FLAGS= gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n' ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal ** Attachment added: Chromium-Browser crashed with SIGSEGV in operator new https://bugs.launchpad.net/bugs/1070833/+attachment/3411680/+files/_usr_lib_chromium-browser_chromium-browser.1001.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070833 Title: Chromium-Browser crashed with SIGSEGV in operator new To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1070833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1069700] [NEW] package virtualbox-ose-guest-dkms 4.0.4-dfsg-1ubuntu4.1 failed to install/upgrade: virtualbox-ose-guest kernel module failed to build
Public bug reported: Error! Bad return status for module build on kernel: 3.6.2 (x86_64) Consult the make.log in the build directory /var/lib/dkms/virtualbox-ose/4.0.4/build/ for more information. * Stopping VirtualBox kernel modules [ OK ] * Starting VirtualBox kernel modules * No suitable module for running kernel found WARNING: The character device /dev/vboxdrv does not exist. Please install the virtualbox-ose-dkms package and the appropriate headers, most likely linux-headers-3.6.2. You will not be able to start VMs until this problem is fixed. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: virtualbox-ose-guest-dkms 4.0.4-dfsg-1ubuntu4.1 Uname: Linux 3.6.2 x86_64 Architecture: amd64 Date: Mon Oct 22 14:24:59 2012 ErrorMessage: virtualbox-ose-guest kernel module failed to build InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) PackageArchitecture: all PackageVersion: 4.0.4-dfsg-1ubuntu4.1 SourcePackage: virtualbox-ose Title: package virtualbox-ose-guest-dkms 4.0.4-dfsg-1ubuntu4.1 failed to install/upgrade: virtualbox-ose-guest kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) VirtualBoxOse.ModInfo: ** Affects: virtualbox-ose (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069700 Title: package virtualbox-ose-guest-dkms 4.0.4-dfsg-1ubuntu4.1 failed to install/upgrade: virtualbox-ose-guest kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox-ose/+bug/1069700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1069508] [NEW] [XPS M1530, SigmaTel STAC9228, Speaker, Internal] No sound at all
Public bug reported: I was not able to hear the right side speaker propoerly. Sorry cannot give much information as I am using Linux for the first time in my laptop. Got fed up with Windows... ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vivnjay1752 F pulseaudio Date: Mon Oct 22 00:47:25 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vivnjay1752 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [XPS M1530, SigmaTel STAC9228, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1530 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069508 Title: [XPS M1530, SigmaTel STAC9228, Speaker, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1069508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067179] [NEW] Nautilus crashed with SIGSEGV
Public bug reported: Nautilus crashed with SIGSEGV ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 NonfreeKernelModules: nvidia wl ApportVersion: 2.6.1-0ubuntu3 Architecture: i386 Date: Tue Oct 16 08:58:50 2012 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'800x550+562+355' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to quantal on 2012-09-18 (27 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity ** Attachment added: Nautilus crashed with SIGSEGV https://bugs.launchpad.net/bugs/1067179/+attachment/3399733/+files/_usr_bin_nautilus.1001.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067179 Title: Nautilus crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1067179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1057044] [NEW] DELUGE GTK CRASHED
Public bug reported: DELUGE GTK CRASHED ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: deluge-gtk 1.3.5-1ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4 Uname: Linux 3.5.0-15-generic i686 NonfreeKernelModules: nvidia wl ApportVersion: 2.5.2-0ubuntu4 Architecture: i386 Date: Wed Sep 26 22:38:14 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: deluge UpgradeStatus: Upgraded to quantal on 2012-09-18 (8 days ago) ** Affects: deluge (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1057044 Title: DELUGE GTK CRASHED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deluge/+bug/1057044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1057044] Re: DELUGE GTK CRASHED
** Attachment added: DELUGE GTK CRASHED https://bugs.launchpad.net/bugs/1057044/+attachment/3346004/+files/_usr_bin_deluge-gtk.1001.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1057044 Title: DELUGE GTK CRASHED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deluge/+bug/1057044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1054127] [NEW] unity-lens-photos crashed with attribute error in shotwell():'NoneType' object has no attribute 'cursor'
*** This bug is a duplicate of bug 1053266 *** https://bugs.launchpad.net/bugs/1053266 Public bug reported: unity-lens-photos crashed with attribute error in shotwell():'NoneType' object has no attribute 'cursor' ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity-lens-photos 0.6-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4 Uname: Linux 3.5.0-15-generic i686 NonfreeKernelModules: nvidia wl ApportVersion: 2.5.2-0ubuntu4 Architecture: i386 Date: Fri Sep 21 20:45:40 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-lens-photos UpgradeStatus: Upgraded to quantal on 2012-09-18 (3 days ago) ** Affects: unity-lens-photos (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054127 Title: unity-lens-photos crashed with attribute error in shotwell():'NoneType' object has no attribute 'cursor' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-photos/+bug/1054127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1054127] Re: unity-lens-photos crashed with attribute error in shotwell():'NoneType' object has no attribute 'cursor'
*** This bug is a duplicate of bug 1053266 *** https://bugs.launchpad.net/bugs/1053266 ** Attachment added: unity-lens-photos crashed with attribute error in shotwell():'NoneType' object has no attribute 'cursor' https://bugs.launchpad.net/bugs/1054127/+attachment/3328623/+files/_usr_lib_unity-lens-photos_unity-lens-photos.1001.crash ** This bug has been marked a duplicate of bug 1053266 unity-lens-photos crashed with AttributeError in shotwell(): 'NoneType' object has no attribute 'cursor' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054127 Title: unity-lens-photos crashed with attribute error in shotwell():'NoneType' object has no attribute 'cursor' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-photos/+bug/1054127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
