[Bug 1946525] Re: Removable media are not mounted automatically
I'm having the same issue on Ubuntu 21.10. It's NOT a VirtualBox virtual machine, but an Ubuntu desktop installation on a physical volume. When I insert any usb device, it doesn't get mounted, despite org.gnome.desktop.media-handling configuration: $ gsettings get org.gnome.desktop.media-handling automount true $ gsettings get org.gnome.desktop.media-handling automount-open true Here is dmesg log after connecting my smartphone via usb: [13254.311575] usb 3-6: USB disconnect, device number 5 [13265.122249] usb 3-6: new high-speed USB device number 7 using xhci_hcd [13265.250291] usb 3-6: device descriptor read/64, error -32 [13265.506983] usb 3-6: New USB device found, idVendor=2717, idProduct=ff40, bcdDevice= 4.04 [13265.506991] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [13265.506994] usb 3-6: Product: Redmi 9 [13265.506996] usb 3-6: Manufacturer: Xiaomi [13265.506998] usb 3-6: SerialNumber: cX [13272.500089] usb 3-6: USB disconnect, device number 7 [13272.946154] usb 3-6: new high-speed USB device number 8 using xhci_hcd [13273.094848] usb 3-6: New USB device found, idVendor=2717, idProduct=ff40, bcdDevice= 4.04 [13273.094862] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [13273.094867] usb 3-6: Product: Redmi 9 [13273.094872] usb 3-6: Manufacturer: Xiaomi [13273.094875] usb 3-6: SerialNumber: cX -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946525 Title: Removable media are not mounted automatically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1946525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939961] [NEW] Memory leak when video is left paused leads to system hang
Public bug reported: vlc version: 3.0.12-3 on Ubuntu 21.04 When a video is being played and then gets paused, vlc starts to drain memory until a complete system hang occurs. Steps to reproduce: - play a mp4 video (haven't tried with other formats yet) - pause the video - leave the vlc window open and switch to any other application - in a few tens seconds/minutes at most, the system will hang I had to switch to a virtual terminal by hitting ctrl-Alt-F3, login and then use top to show memory usage. Xorg was consuming more than 100% CPU, while vlc was a little below. I could switch back to the desktop only after killing vlc from the virtual terminal. ** Affects: vlc (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/1939961 Title: Memory leak when video is left paused leads to system hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1939961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] Re: Fail to resume after hibernate. Image mismatch: architecture specific data
Thank you, I have already installed it. The missing one is for 5.11.0-24, as I said before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] Re: Fail to resume after hibernate. Image mismatch: architecture specific data
Yet another issue: after resuming, the desktop is corrupted ** Attachment added: "Corrupted desktop after resuming from hibernate" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+attachment/5515080/+files/Schermata%20da%202021-08-01%2013-33-28.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] Re: Fail to resume after hibernate. Image mismatch: architecture specific data
I confirm hibernate is working with 5.11.0-26.28 kernel. It does work on 5.11.0-24 too, but I'm having another issue with it: the nvidia driver does not work, since the package linux-modules-nvidia-390-5.11.0-24-generic is missing from the repositories. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] Re: Fail to resume after hibernate. Image mismatch: architecture specific data
** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+attachment/5514348/+files/WifiSyslog.txt ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+attachment/5514356/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] Re: Fail to resume after hibernate. Image mismatch: architecture specific data
** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+attachment/5514353/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] Re: Fail to resume after hibernate. Image mismatch: architecture specific data
** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+attachment/5514332/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] Re: Fail to resume after hibernate. Image mismatch: architecture specific data
I don't like to make all those log files publicly available: they might contain sensitive data. How can they made visible to devs only? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1938221/+attachment/5514349/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1938221/+attachment/5514348/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1938221/+attachment/5514347/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1938221/+attachment/5514346/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1938221/+attachment/5514345/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1938221/+attachment/5514344/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1938221/+attachment/5514343/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1938221/+attachment/5514342/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1938221/+attachment/5514341/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1938221/+attachment/5514340/+files/PaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1938221/+attachment/5514339/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1938221/+attachment/5514338/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1938221/+attachment/5514337/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1938221/+attachment/5514336/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1938221/+attachment/5514335/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1938221/+attachment/5514334/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] HookError_ubuntu.txt
apport information ** Attachment added: "HookError_ubuntu.txt" https://bugs.launchpad.net/bugs/1938221/+attachment/5514333/+files/HookError_ubuntu.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1938221/+attachment/5514332/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1938221/+attachment/5514331/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938221] Re: Fail to resume after hibernate. Image mismatch: architecture specific data
apport information
** Tags added: apport-collected hirsute staging
** Description changed:
I'm running Ubuntu 21.04 on a laptop and have been using hibernate flawlessly
for a couple of months.
More recently, resuming from hibernation stopped working and now falls back
to complete restart.
This is what I get from dmesg:
[ 17.407048] kernel: PM: hibernation: resume from hibernation
[ 17.409714] kernel: PM: hibernation: Marking nosave pages: [mem
0x-0x0fff]
[ 17.409717] kernel: PM: hibernation: Marking nosave pages: [mem
0x0004f000-0x0004]
[ 17.409718] kernel: PM: hibernation: Marking nosave pages: [mem
0x0009e000-0x000f]
[ 17.409721] kernel: PM: hibernation: Marking nosave pages: [mem
0xae6e9000-0xae6e]
[ 17.409723] kernel: PM: hibernation: Marking nosave pages: [mem
0xaf0cd000-0xaf5abfff]
[ 17.409744] kernel: PM: hibernation: Marking nosave pages: [mem
0xb1e4c000-0xb1ed3fff]
[ 17.409747] kernel: PM: hibernation: Marking nosave pages: [mem
0xb2698000-0xb2698fff]
[ 17.409748] kernel: PM: hibernation: Marking nosave pages: [mem
0xb54af000-0xb54a]
[ 17.409749] kernel: PM: hibernation: Marking nosave pages: [mem
0xb54d8000-0xb54d8fff]
[ 17.409751] kernel: PM: hibernation: Marking nosave pages: [mem
0xb7db3000-0xb7ff]
[ 17.409761] kernel: PM: hibernation: Marking nosave pages: [mem
0xb8759000-0xb87f]
[ 17.409765] kernel: PM: hibernation: Marking nosave pages: [mem
0xb8f9d000-0xb8ff]
[ 17.409767] kernel: PM: hibernation: Marking nosave pages: [mem
0xba6f5000-0xba7f]
[ 17.409773] kernel: PM: hibernation: Marking nosave pages: [mem
0xbbcec000-0x]
[ 17.410626] kernel: PM: hibernation: Basic memory bitmaps created
[ 17.481616] kernel: PM: Using 3 thread(s) for decompression
[ 17.481620] kernel: PM: Loading and decompressing image data (835177
pages)...
[ 17.481626] kernel: PM: hibernation: Image mismatch: architecture specific
data
[ 17.481627] kernel: PM: hibernation: Read 3340708 kbytes in 0.01 seconds
(334070.80 MB/s)
[ 17.482589] kernel: PM: Error -1 resuming
[ 17.482594] kernel: PM: hibernation: Failed to load image, recovering.
[ 17.482992] kernel: PM: hibernation: Basic memory bitmaps freed
[ 17.483572] kernel: PM: hibernation: resume failed (-1)
Here is some system information:
$ cat /proc/version_signature
Ubuntu 5.11.0-25.27-generic 5.11.22
$ cat /sys/power/state
freeze mem disk
$ cat /sys/power/disk
[platform] shutdown reboot suspend test_resume
$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet
splash resume=UUID=a2be2098-* mem_sleep_default=deep
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu65.1
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: giacof 2186 F pulseaudio
+ /dev/snd/controlC2: giacof 2186 F pulseaudio
+ /dev/snd/controlC0: giacof 2186 F pulseaudio
+ CasperMD5json:
+ {
+"result": "skip"
+ }
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 21.04
+ InstallationDate: Installed on 2021-05-17 (71 days ago)
+ InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
+ MachineType: Dell Inc. Precision M4800
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcEnviron:
+ TERM=xterm-256color
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=it_IT.UTF-8
+ SHELL=/bin/bash
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-25-generic
root=/dev/mapper/vgubuntu-root ro quiet splash
resume=UUID=a2be2098-8e7d-4460-845d-c2b3b22def13 mem_sleep_default=deep
+ ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
+ RelatedPackageVersions:
+ linux-restricted-modules-5.11.0-25-generic N/A
+ linux-backports-modules-5.11.0-25-generic N/A
+ linux-firmware 1.197.2
+ StagingDrivers: ashmem_linux
+ Tags: hirsute staging
+ Uname: Linux 5.11.0-25-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
+ _MarkForUpload: True
+ dmi.bios.date: 10/08/2018
+ dmi.bios.release: 65.25
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: A25
+ dmi.board.name: 0T3YTY
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 9
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias:
dmi:bvnDellInc.:bvrA25:bd10/08/2018:br65.25:svnDellInc.:pnPrecisionM4800:pvr00:rvnDellInc.:rn0T3YTY:rvrA00:cvnDellInc.:ct9:cvr:
+ dmi.product.name: Precision M4800
+ dmi.product.sku: 05CC
+ dmi.product.version: 00
+ dmi.sys.vendor: Dell Inc.
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1938221/+attachment/5514330/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bu
[Bug 1938221] [NEW] Fail to resume after hibernate. Image mismatch: architecture specific data
Public bug reported: I'm running Ubuntu 21.04 on a laptop and have been using hibernate flawlessly for a couple of months. More recently, resuming from hibernation stopped working and now falls back to complete restart. This is what I get from dmesg: [ 17.407048] kernel: PM: hibernation: resume from hibernation [ 17.409714] kernel: PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] [ 17.409717] kernel: PM: hibernation: Marking nosave pages: [mem 0x0004f000-0x0004] [ 17.409718] kernel: PM: hibernation: Marking nosave pages: [mem 0x0009e000-0x000f] [ 17.409721] kernel: PM: hibernation: Marking nosave pages: [mem 0xae6e9000-0xae6e] [ 17.409723] kernel: PM: hibernation: Marking nosave pages: [mem 0xaf0cd000-0xaf5abfff] [ 17.409744] kernel: PM: hibernation: Marking nosave pages: [mem 0xb1e4c000-0xb1ed3fff] [ 17.409747] kernel: PM: hibernation: Marking nosave pages: [mem 0xb2698000-0xb2698fff] [ 17.409748] kernel: PM: hibernation: Marking nosave pages: [mem 0xb54af000-0xb54a] [ 17.409749] kernel: PM: hibernation: Marking nosave pages: [mem 0xb54d8000-0xb54d8fff] [ 17.409751] kernel: PM: hibernation: Marking nosave pages: [mem 0xb7db3000-0xb7ff] [ 17.409761] kernel: PM: hibernation: Marking nosave pages: [mem 0xb8759000-0xb87f] [ 17.409765] kernel: PM: hibernation: Marking nosave pages: [mem 0xb8f9d000-0xb8ff] [ 17.409767] kernel: PM: hibernation: Marking nosave pages: [mem 0xba6f5000-0xba7f] [ 17.409773] kernel: PM: hibernation: Marking nosave pages: [mem 0xbbcec000-0x] [ 17.410626] kernel: PM: hibernation: Basic memory bitmaps created [ 17.481616] kernel: PM: Using 3 thread(s) for decompression [ 17.481620] kernel: PM: Loading and decompressing image data (835177 pages)... [ 17.481626] kernel: PM: hibernation: Image mismatch: architecture specific data [ 17.481627] kernel: PM: hibernation: Read 3340708 kbytes in 0.01 seconds (334070.80 MB/s) [ 17.482589] kernel: PM: Error -1 resuming [ 17.482594] kernel: PM: hibernation: Failed to load image, recovering. [ 17.482992] kernel: PM: hibernation: Basic memory bitmaps freed [ 17.483572] kernel: PM: hibernation: resume failed (-1) Here is some system information: $ cat /proc/version_signature Ubuntu 5.11.0-25.27-generic 5.11.22 $ cat /sys/power/state freeze mem disk $ cat /sys/power/disk [platform] shutdown reboot suspend test_resume $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-5.11.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash resume=UUID=a2be2098-* mem_sleep_default=deep ** 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/1938221 Title: Fail to resume after hibernate. Image mismatch: architecture specific data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862229] Re: gnome session crash on boot with kernel 5.3.0-29-generic
Sorry for delay. I found the following related links: https://errors.ubuntu.com/oops/b749b11e-485f-11ea-a808-fa163ee63de6 https://errors.ubuntu.com/oops/70a4e6e4-4a75-11ea-a63e-fa163ee63de6 Many thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862229 Title: gnome session crash on boot with kernel 5.3.0-29-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862229] Re: gnome session crash on boot with kernel 5.3.0-29-generic
Sorry, how can I get the ID of the newly-created bugs? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862229 Title: gnome session crash on boot with kernel 5.3.0-29-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862229] Re: gnome session crash on boot with kernel 5.3.0-29-generic
I did it for both _usr_bin_gnome-shell.1000.crash and _usr_lib_gnome- session_gnome-session-binary.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/1862229 Title: gnome session crash on boot with kernel 5.3.0-29-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862229] Re: gnome session crash on boot with kernel 5.3.0-29-generic
Hi, in /var/crash I have the following files: -rw-r- 1 giacof whoopsie 188300182 feb 1 15:34 _usr_bin_gnome-shell.1000.crash -rw-r--r-- 1 giacof whoopsie 0 feb 1 15:38 _usr_bin_gnome-shell.1000.upload -rw--- 1 whoopsie whoopsie37 feb 5 22:37 _usr_bin_gnome-shell.1000.uploaded -rw-r- 1 giacof whoopsie961440 feb 6 14:24 _usr_lib_gnome-session_gnome-session-binary.1000.crash Which one shall I choose? Many thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862229 Title: gnome session crash on boot with kernel 5.3.0-29-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862229] [NEW] gnome session crash on boot with kernel 5.3.0-29-generic
Public bug reported: lsb_release -rd Description:Ubuntu 19.10 Release:19.10 apt-cache policy gnome-shell gnome-shell: Installato: 3.34.1+git20191024-1ubuntu1~19.10.1 Candidato: 3.34.1+git20191024-1ubuntu1~19.10.1 Tabella versione: *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://it.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu eoan/main amd64 Packages First there was an issue with hibernation: after resuming, the gnome session was not restored and a new one was created (I had to login again from start). Here are some relevant log lines: [ 21.375254] PM: Image signature found, resuming [ 21.375255] PM: resume from hibernation [ 21.375607] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 21.376719] OOM killer disabled. [ 21.376832] PM: Marking nosave pages: [mem 0x-0x0fff] [ 21.376834] PM: Marking nosave pages: [mem 0x0004f000-0x0004] [ 21.376834] PM: Marking nosave pages: [mem 0x0009d000-0x0009efff] [ 21.376835] PM: Marking nosave pages: [mem 0x000a-0x000f] [ 21.376837] PM: Marking nosave pages: [mem 0xae7a8000-0xae7aefff] [ 21.376838] PM: Marking nosave pages: [mem 0xaf18c000-0xaf66afff] [ 21.376856] PM: Marking nosave pages: [mem 0xb7db3000-0xb7ff] [ 21.376865] PM: Marking nosave pages: [mem 0xb8759000-0xb87f] [ 21.376868] PM: Marking nosave pages: [mem 0xb8f9d000-0xb8ff] [ 21.376870] PM: Marking nosave pages: [mem 0xba6f5000-0xba7f] [ 21.376875] PM: Marking nosave pages: [mem 0xbbcec000-0x] [ 21.377562] PM: Basic memory bitmaps created [ 24.367114] PM: Using 3 thread(s) for decompression [ 24.367115] PM: Loading and decompressing image data (1585416 pages)... [ 24.367127] Hibernate inconsistent memory map detected! [ 24.367138] fbcon: Taking over console [ 24.367139] PM: Image mismatch: architecture specific data [ 24.367141] PM: Read 6341664 kbytes in 0.01 seconds (634166.40 MB/s) [ 24.368077] PM: Error -1 resuming [ 24.368079] PM: Failed to load hibernation image, recovering. [ 24.368347] PM: Basic memory bitmaps freed [ 24.368347] OOM killer enabled. [ 24.368347] Restarting tasks ... done. [ 24.384357] Console: switching to colour frame buffer device 240x67 [ 24.404345] PM: resume from hibernation failed (-1) Then, since next restart I cannot login anymore, as the session keeps crashing immediately after entering user's password. The only way I could login back was by selecting the previous kernel version on boot (5.3.0-26-generic instead of 5.3.0-29-generic). I also noticed all gnome extensions (Applications Menu and Hibernate Status Button ) stopped working and were disabled. Boot journal attached. ** 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/1862229 Title: gnome session crash on boot with kernel 5.3.0-29-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862229] Re: gnome session crash on boot kernel 5.3.0-29-generic
** Attachment added: "boot journal" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862229/+attachment/5326021/+files/journal.txt ** Description changed: lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 apt-cache policy gnome-shell gnome-shell: - Installato: 3.34.1+git20191024-1ubuntu1~19.10.1 - Candidato: 3.34.1+git20191024-1ubuntu1~19.10.1 - Tabella versione: - *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 - 500 http://it.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 3.34.1-1ubuntu1 500 - 500 http://it.archive.ubuntu.com/ubuntu eoan/main amd64 Packages + Installato: 3.34.1+git20191024-1ubuntu1~19.10.1 + Candidato: 3.34.1+git20191024-1ubuntu1~19.10.1 + Tabella versione: + *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 + 500 http://it.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 3.34.1-1ubuntu1 500 + 500 http://it.archive.ubuntu.com/ubuntu eoan/main amd64 Packages First there was an issue with hibernation: after resuming, the gnome session was not restored and a new one was created (I had to login again from start). Here are some relevant log lines: [ 21.375254] PM: Image signature found, resuming [ 21.375255] PM: resume from hibernation [ 21.375607] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 21.376719] OOM killer disabled. [ 21.376832] PM: Marking nosave pages: [mem 0x-0x0fff] [ 21.376834] PM: Marking nosave pages: [mem 0x0004f000-0x0004] [ 21.376834] PM: Marking nosave pages: [mem 0x0009d000-0x0009efff] [ 21.376835] PM: Marking nosave pages: [mem 0x000a-0x000f] [ 21.376837] PM: Marking nosave pages: [mem 0xae7a8000-0xae7aefff] [ 21.376838] PM: Marking nosave pages: [mem 0xaf18c000-0xaf66afff] [ 21.376856] PM: Marking nosave pages: [mem 0xb7db3000-0xb7ff] [ 21.376865] PM: Marking nosave pages: [mem 0xb8759000-0xb87f] [ 21.376868] PM: Marking nosave pages: [mem 0xb8f9d000-0xb8ff] [ 21.376870] PM: Marking nosave pages: [mem 0xba6f5000-0xba7f] [ 21.376875] PM: Marking nosave pages: [mem 0xbbcec000-0x] [ 21.377562] PM: Basic memory bitmaps created [ 24.367114] PM: Using 3 thread(s) for decompression [ 24.367115] PM: Loading and decompressing image data (1585416 pages)... [ 24.367127] Hibernate inconsistent memory map detected! [ 24.367138] fbcon: Taking over console [ 24.367139] PM: Image mismatch: architecture specific data [ 24.367141] PM: Read 6341664 kbytes in 0.01 seconds (634166.40 MB/s) [ 24.368077] PM: Error -1 resuming [ 24.368079] PM: Failed to load hibernation image, recovering. [ 24.368347] PM: Basic memory bitmaps freed [ 24.368347] OOM killer enabled. [ 24.368347] Restarting tasks ... done. [ 24.384357] Console: switching to colour frame buffer device 240x67 [ 24.404345] PM: resume from hibernation failed (-1) Then, since next restart I cannot login anymore, as the session keeps crashing immediately after entering user's password. The only way I could login back was by selecting the previous kernel version on boot (5.3.0-26-generic instead of 5.3.0-29-generic). + I also noticed all gnome extensions (Applications Menu and Hibernate + Status Button ) stopped working and were disabled. + Boot journal attached. ** Summary changed: - gnome session crash on boot kernel 5.3.0-29-generic + gnome session crash on boot with kernel 5.3.0-29-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862229 Title: gnome session crash on boot with kernel 5.3.0-29-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835654] [NEW] Extracting a zip archieve creates a new unwanted folder
Public bug reported: version of the package file-roller: 3.32.1-1 on Ubuntu 19.04 If I right click on the .zip file and choose "extract here" from the context menu, then the archieve content is extracted into a newly created folder, with the same name as the zip file. The expected behavior would be extracting the content into the folder where the archieve is located. Note this does NOT occur for tar.xz archieves, which are correctly extracted into the current folder instead. ** Affects: file-roller (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/1835654 Title: Extracting a zip archieve creates a new unwanted folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1835654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791981] Re: X Server session crash for "No space left on device"
The bug is still occurring, it is a severe bug as it makes suspend functionality totally unusable! Do you need any further information? ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791981 Title: X Server session crash for "No space left on device" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1791981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791981] Re: X Server session crash for "No space left on device"
By the way, I also did check my HDD and can confirm it is not full. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791981 Title: X Server session crash for "No space left on device" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1791981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791981] Re: X Server session crash for "No space left on device"
I found the file _usr_bin_nautilus.1000.crash in the directory /var/crash. Running ubuntu-bug on that file only shows a popup and then exits, but there's an older bug I already submitted a few weeks ago: it's https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1788512 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791981 Title: X Server session crash for "No space left on device" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1791981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791981] Re: X Server session crash for "No space left on device"
** Attachment added: "lsusb" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1791981/+attachment/5187651/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791981 Title: X Server session crash for "No space left on device" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1791981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791981] Re: X Server session crash for "No space left on device"
** Attachment added: "lspci -v" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1791981/+attachment/5187650/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791981 Title: X Server session crash for "No space left on device" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1791981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780677] Re: X session crash after resuming from suspend
** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780677/+attachment/5161172/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780677 Title: X session crash after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791981] [NEW] X Server session crash for "No space left on device"
Public bug reported: Ubuntu Release: Ubuntu 18.04.1 LTS Package version: xserver-xorg: 1:7.7+19ubuntu7.1 When my laptop resumes after suspend, the desktop session crashes and a new one is started. So each time I lose all open applications and unsaved data! The expected behavior would be obviously to restore the suspended session. I had a look through log files and found that Xorg.0.log ends with the following error lines: [ 6004.019] (II) NVIDIA(0): Setting mode "NULL" [ 6004.026] (EE) modeset(G0): failed to set mode: No space left on device [ 6004.026] (EE) Fatal server error: [ 6004.026] (EE) EnterVT failed for gpu screen 0 [ 6004.027] (EE) [ 6004.027] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 6004.027] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 6004.027] (EE) [ 6004.065] (EE) Server terminated with error (1). Closing log file. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: crash nvidia suspend-resume xorg ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/bugs/1791981/+attachment/5187649/+files/Xorg.0.log.old -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791981 Title: X Server session crash for "No space left on device" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1791981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780677] Re: X session crash after resuming from suspend
Now there are errors at the bottom of the attached Xorg.1.log file: [ 4387.635] (EE) modeset(G0): failed to set mode: No space left on device [ 4387.635] (EE) Fatal server error: [ 4387.635] (EE) EnterVT failed for gpu screen 0 [ 4387.635] (EE) [ 4387.635] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 4387.635] (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information. [ 4387.635] (EE) [ 4387.672] (EE) Server terminated with error (1). Closing log file. ** Attachment added: "Xorg.1.log" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780677/+attachment/5181091/+files/Xorg.1.log.old -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780677 Title: X session crash after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780677] Re: X session crash after resuming from suspend
The issue is still happening when the laptop stays in standby for several hours! This time I found something in the /var/crash directory: the new bug ID is #1788512, I'm not sure if it's related to this bug. Please help to find the root cause and some workaround while it get fixed. Than you ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780677 Title: X session crash after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780677] Re: X session crash after resuming from suspend
I noticed the status is still incomplete. What additional information should be provided? Thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780677 Title: X session crash after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780677] Re: X session crash after resuming from suspend
Hi, I did apply the workaround, yet I can't find anything related in the /var/crash directory. With my ID I only find a systemd crash on 2018-06-21 and other issues dated back to 2017 and older. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780677 Title: X session crash after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780677] Re: X session crash after resuming from suspend
Actually, this is the content of the /var/crash directory: _usr_lib_virtualbox_VBoxHeadless.0.crash _usr_lib_virtualbox_VBoxHeadless.0.upload -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780677 Title: X session crash after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780677] [NEW] X session crash after resuming from suspend
Public bug reported: Description:Ubuntu 18.04 LTS Release:18.04 xorg: Installed: 1:7.7+19ubuntu7 First I suspended my laptop, while a few applications were running (Firefox, Chrome and some others much smaller). A couple of hours later, I opened the lid and expected the Gnome session would resume. What happened instead was a crash of the X server, then the login page was shown again and a new Gnome session started: the old session got killed! In the Xorg.0.log.old file I found this, not sure if related: [ 21189.337] (II) NVIDIA(GPU-0): Deleting GPU-0 [ 21189.338] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error [ 21189.338] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error [ 21189.338] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error [ 21189.338] (II) Server terminated successfully (0). Closing log file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 8 23:03:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-23-generic, x86_64: installed nvidia, 390.48, 4.15.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05cc] NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GK107GLM [Quadro K1100M] [1028:15cc] InstallationDate: Installed on 2018-06-21 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=/dev/mapper/vg-root ro scsi_mod.scan=sync quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0T3YTY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd01/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0T3YTY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: 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/1780677 Title: X session crash after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1780677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705345] Re: Installing new kernel hangs on plymouth --ping
** Description changed: I tried to upgrade linux kernel, from 4.10.0-26 to 4.10.0-28, but the - installation hangs on the following output lines: + installation hung on the following output lines: sudo apt-get install unrar linux-generic linux-headers-generic linux-image-generic linux-signed-generic linux-signed-image-generic Configurazione di linux-image-4.10.0-28-generic (4.10.0-28.32)... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.10.0-28-generic /boot/vmlinuz-4.10.0-28-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.10.0-28-generic /boot/vmlinuz-4.10.0-28-generic - Then I used ps to see running processes on the console, and notice this - one was blocking post-installation: + Then I looked at the running processes, and noticed this one was + blocking post-installation: plymouth --ping - I could not but manually kill plymouth, then the script resumed but then + I could not but manually kill plymouth, then the script resumed just to froze again a few line later and so on, but is that safe for the installation? ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: plymouth 0.9.2-3ubuntu15 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jul 19 22:32:14 2017 DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-logo/ubuntu-gnome-logo.plymouth InstallationDate: Installed on 2017-05-22 (58 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Precision M4800 ProcCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic.efi.signed root=/dev/mapper/vg-root ro quiet splash vt.handoff=7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic.efi.signed root=/dev/mapper/vg-root ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0T3YTY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd01/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0T3YTY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Description changed: I tried to upgrade linux kernel, from 4.10.0-26 to 4.10.0-28, but the installation hung on the following output lines: sudo apt-get install unrar linux-generic linux-headers-generic linux-image-generic linux-signed-generic linux-signed-image-generic Configurazione di linux-image-4.10.0-28-generic (4.10.0-28.32)... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.10.0-28-generic /boot/vmlinuz-4.10.0-28-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.10.0-28-generic /boot/vmlinuz-4.10.0-28-generic Then I looked at the running processes, and noticed this one was blocking post-installation: plymouth --ping I could not but manually kill plymouth, then the script resumed just to - froze again a few line later and so on, but is that safe for the + freeze again a few line later and so on, but is that safe for the installation? ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: plymouth 0.9.2-3ubuntu15 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jul 19 22:32:14 2017 DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-logo/ubuntu-gnome-logo.plymouth InstallationDate: Installed on 2017-05-22 (58 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Precision M4800 ProcCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic.efi.signed root=/dev/mapper/vg-root ro quiet splash vt.handoff=7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic.efi.signed root=/dev/mapper/vg-root ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth:
[Bug 1705345] Re: Installing new kernel hangs on plymouth --ping
Here is mine. It actually hangs on the last line. ** Attachment added: "output of `strace plymouth --ping`" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1705345/+attachment/4976707/+files/plym.strace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705345 Title: Installing new kernel hangs on plymouth --ping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1705345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705345] Re: Installing new kernel hangs on plymouth --ping
** Description changed: I tried to upgrade linux kernel, from 4.10.0-26 to 4.10.0-28, but the installation hangs on the following output lines: sudo apt-get install unrar linux-generic linux-headers-generic linux-image-generic linux-signed-generic linux-signed-image-generic Configurazione di linux-image-4.10.0-28-generic (4.10.0-28.32)... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.10.0-28-generic /boot/vmlinuz-4.10.0-28-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.10.0-28-generic /boot/vmlinuz-4.10.0-28-generic Then I used ps to see running processes on the console, and notice this one was blocking post-installation: plymouth --ping I could not but manually kill plymouth, then the script resumed but then froze again a few line later and so on, but is that safe for the installation? - $ lsb_release -rd - Description: Ubuntu 17.04 - Release: 17.04 - - $ apt-cache policy plymouth - plymouth: - Installato: 0.9.2-3ubuntu15 - Candidato: 0.9.2-3ubuntu15 - Tabella versione: - *** 0.9.2-3ubuntu15 500 - 500 http://ubuntu.mirror.garr.it/ubuntu zesty/main amd64 Packages - 100 /var/lib/dpkg/status - ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: plymouth 0.9.2-3ubuntu15 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jul 19 22:32:14 2017 DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-logo/ubuntu-gnome-logo.plymouth InstallationDate: Installed on 2017-05-22 (58 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Precision M4800 ProcCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic.efi.signed root=/dev/mapper/vg-root ro quiet splash vt.handoff=7 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=it_IT.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=it_IT.UTF-8 + SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic.efi.signed root=/dev/mapper/vg-root ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0T3YTY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd01/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0T3YTY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705345 Title: Installing new kernel hangs on plymouth --ping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1705345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705345] [NEW] Installing new kernel hangs on plymouth --ping
Public bug reported: I tried to upgrade linux kernel, from 4.10.0-26 to 4.10.0-28, but the installation hangs on the following output lines: sudo apt-get install unrar linux-generic linux-headers-generic linux-image-generic linux-signed-generic linux-signed-image-generic Configurazione di linux-image-4.10.0-28-generic (4.10.0-28.32)... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.10.0-28-generic /boot/vmlinuz-4.10.0-28-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.10.0-28-generic /boot/vmlinuz-4.10.0-28-generic Then I used ps to see running processes on the console, and notice this one was blocking post-installation: plymouth --ping I could not but manually kill plymouth, then the script resumed but then froze again a few line later and so on, but is that safe for the installation? ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: plymouth 0.9.2-3ubuntu15 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jul 19 22:32:14 2017 DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-logo/ubuntu-gnome-logo.plymouth InstallationDate: Installed on 2017-05-22 (58 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Precision M4800 ProcCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic.efi.signed root=/dev/mapper/vg-root ro quiet splash vt.handoff=7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic.efi.signed root=/dev/mapper/vg-root ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0T3YTY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd01/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0T3YTY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705345 Title: Installing new kernel hangs on plymouth --ping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1705345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694750] Re: kernel BUG at /build/linux-lz1RHE/linux-4.10.0/include/linux/swapops.h:129. Computer frozen!
*** This bug is a duplicate of bug 1674838 *** https://bugs.launchpad.net/bugs/1674838 ** Attachment added: "Output of sudo lspci -vnvn" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694750/+attachment/4886811/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694750 Title: kernel BUG at /build/linux- lz1RHE/linux-4.10.0/include/linux/swapops.h:129. Computer frozen! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694750] [NEW] kernel BUG at /build/linux-lz1RHE/linux-4.10.0/include/linux/swapops.h:129. Computer frozen!
*** This bug is a duplicate of bug 1674838 *** https://bugs.launchpad.net/bugs/1674838 Public bug reported: $ lsb_release -rd Description:Ubuntu 17.04 Release:17.04 $ uname -a Linux Home 4.10.0-21-generic #23-Ubuntu SMP Fri Apr 28 16:14:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ cat /proc/version_signature Ubuntu 4.10.0-21.23-generic 4.10.11 Right after opening a new tab in Chrome, Chrome process peaked to 188%, then the system became totally unresponsive: neither virtual terminals nor magic keys were working. I could not but switch power off. This comes from kern.log: May 31 13:44:18 Home kernel: [ 6611.343628] [ cut here ] May 31 13:44:18 Home kernel: [ 6611.343658] kernel BUG at /build/linux-lz1RHE/linux-4.10.0/include/linux/swapops.h:129! May 31 13:44:18 Home kernel: [ 6611.343691] invalid opcode: [#1] SMP May 31 13:44:18 Home kernel: [ 6611.343709] Modules linked in: uas usb_storage ccm rfcomm nf_log_ipv4 nf_log_common xt_tcpudp xt_conntrack nf_conntrack_irc nf_conntrack_ftp xt_state xt_limit xt_LOG nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack iptable_filter bbswitch(OE) cmac bnep pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) nls_iso8859_1 nvidia_uvm(POE) uvcvideo videobuf2_vmalloc dell_wmi sparse_keymap intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel videobuf2_memops arc4 videobuf2_v4l2 videobuf2_core videodev dell_laptop dell_smbios dcdbas dell_smm_hwmon ath9k ath9k_common ath9k_hw kvm media ath mac80211 ath3k btusb btrtl btbcm btintel bluetooth cfg80211 input_leds snd_hda_codec_hdmi snd_hda_codec_realtek snd_soc_rt5640 snd_soc_rl6231 irqbypass intel_cstate snd_soc_core intel_rapl_perf mei_me May 31 13:44:18 Home kernel: [ 6611.344004] mei snd_hda_codec_generic joydev serio_raw snd_hda_intel snd_hda_codec wmi snd_compress snd_hda_core ac97_bus snd_pcm_dmaengine snd_hwdep snd_pcm ie31200_edac edac_core lpc_ich shpchp dw_dmac elan_i2c dw_dmac_core snd_soc_sst_acpi snd_soc_sst_match snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device 8250_dw snd_timer snd soundcore spi_pxa2xx_platform mac_hid i2c_designware_platform i2c_designware_core dell_rbtn dell_smo8800 parport_pc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt hid_logitech_hidpp hid_logitech_dj usbhid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 nvidia_drm(POE) nvidia_modeset(POE) aesni_intel nvidia(POE) aes_x86_64 crypto_simd i2c_algo_bit glue_helper cryptd drm_kms_helper syscopyarea psmouse sysfillrect e1000e May 31 13:44:18 Home kernel: [ 6611.344304] ahci sysimgblt fb_sys_fops libahci sdhci_pci drm ptp pps_core sdhci_acpi video sdhci i2c_hid hid fjes May 31 13:44:18 Home kernel: [ 6611.344354] CPU: 7 PID: 3439 Comm: chrome Tainted: P OE 4.10.0-21-generic #23-Ubuntu May 31 13:44:18 Home kernel: [ 6611.344392] Hardware name: Dell Inc. Precision M4800/0T3YTY, BIOS A06 01/02/2014 May 31 13:44:18 Home kernel: [ 6611.344424] task: 881da351 task.stack: a71188acc000 May 31 13:44:18 Home kernel: [ 6611.344453] RIP: 0010:__migration_entry_wait+0x16a/0x180 May 31 13:44:18 Home kernel: [ 6611.344476] RSP: :a71188acfd68 EFLAGS: 00010246 May 31 13:44:18 Home kernel: [ 6611.344499] RAX: 0017c0048078 RBX: d05c0e021d30 RCX: d05c0e021d30 May 31 13:44:18 Home kernel: [ 6611.344530] RDX: 0001 RSI: 881d40874820 RDI: d05c0b69c100 May 31 13:44:18 Home kernel: [ 6611.344561] RBP: a71188acfd80 R08: 881de2239740 R09: 881de2239740 May 31 13:44:18 Home kernel: [ 6611.344591] R10: 002ff23c05ed349b R11: 0001 R12: d05c0b69c100 May 31 13:44:18 Home kernel: [ 6611.344621] R13: 3e2da704 R14: a71188acfe30 R15: 881d7574fbb8 May 31 13:44:18 Home kernel: [ 6611.344652] FS: 7f2677e09480() GS:881dfebc() knlGS: May 31 13:44:18 Home kernel: [ 6611.344687] CS: 0010 DS: ES: CR0: 80050033 May 31 13:44:18 Home kernel: [ 6611.344715] CR2: 285fbdf04d80 CR3: 0003dfb78000 CR4: 001406e0 May 31 13:44:18 Home kernel: [ 6611.344747] DR0: DR1: DR2: May 31 13:44:18 Home kernel: [ 6611.344777] DR3: DR6: fffe0ff0 DR7: 0400 May 31 13:44:18 Home kernel: [ 6611.344808] Call Trace: May 31 13:44:18 Home kernel: [ 6611.344823] migration_entry_wait+0x74/0x80 May 31 13:44:18 Home kernel: [ 6611.344844] do_swap_page+0x5b3/0x770 May 31 13:44:18 Home kernel: [ 6611.344863] handle_mm_fault+0x873/0x1360 May 31 13:44:18 Home kernel: [ 6611.344883] __do_page_fault+0x23e/0x4e0 May 31 13:44:18 Home kernel: [ 6611.344902] do_page_fault+0x22/0x30 May 31 13:44:18 Home kernel: [ 6611.344921] page_fault+0x28/0x30 May 31 13:44:18 Home kernel: [ 6611.344937] RIP: 0033:0x5638d574b0ba May 31 13:44:18 Home kernel: [ 6611.344955] RSP: 002b:7fff86edb210 EFLAGS:
[Bug 1598814] Re: tracker-miner-fs syslog spam: Could not execute sparql
Same in Ubuntu Gnome 17.04. I get zillions of errors in syslog: May 31 14:32:00 Home tracker-miner-f[3366]: (Sparql buffer) Error in task 1 (file:///home/giacof/***) of the array-update: UNIQUE constraint failed: nie:DataObject.nie:url (str error of errno (not necessarily related): Risorsa temporaneamente non disponibile) May 31 14:32:00 Home tracker-miner-f[3366]: Could not execute sparql: UNIQUE constraint failed: nie:DataObject.nie:url (strerror of errno (not necessarily related): Risorsa temporaneamente non disp onibile) May 31 14:32:00 Home tracker-miner-f[3366]: (Sparql buffer) Error in task 2 (file:///home/giacof/***) of the array-update: UNIQUE con straint failed: nie:DataObject.nie:url (strerror of errno (not necessarily related): Risorsa temporaneamente non disponibile) May 31 14:32:00 Home tracker-miner-f[3366]: Could not execute sparql: UNIQUE constraint failed: nie:DataObject.nie:url (strerror of errno (not necessarily related): Risorsa temporaneamente non disp onibile) May 31 14:32:00 Home tracker-miner-f[3366]: (Sparql buffer) Error in task 3 (file:///home/giacof/***) of the array-update: UNIQUE constraint failed: nie:DataObject.nie:url (strerror of errno (not necessarily related): Risorsa temporaneamente non disponibile) [...] $ apt-cache policy tracker tracker: Installato: 1.12.0-0ubuntu1 Candidato: 1.12.0-0ubuntu1 Tabella versione: *** 1.12.0-0ubuntu1 500 500 http://ubuntu.mirror.garr.it/ubuntu zesty/universe amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598814 Title: tracker-miner-fs syslog spam: Could not execute sparql To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1598814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1606019] Re: package polipo 1.1.1-7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Same here on 17.04: $ lsb_release -rd Description:Ubuntu 17.04 Release:17.04 $ apt-cache policy polipo polipo: Installato: 1.1.1-7 Candidato: 1.1.1-7 Tabella versione: *** 1.1.1-7 500 500 http://ubuntu.mirror.garr.it/ubuntu zesty/universe amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1606019 Title: package polipo 1.1.1-7 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/polipo/+bug/1606019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626729] [NEW] Evolution keeps using wrong password instead of asking it again
Public bug reported: I sent an email via SMTP and mistyped the password, so the server rejected the message. Then I tried to send again the same message. Expected behavior: a new dialog should have prompted for the correct password. What happened instead: Evolution did NOT ask the password again, but tried to send the message reusing the wrong one! The following popup was then displayed: The reported error was "AUTH command failed: ...authentication rejected" Below the message are three buttons, the last of which is "Retry", but it keeps using the wrong password I even tried to exit Evolution and restart it, but it was still remembering the wrong password instead of asking it! Package Version: 3.18.5.2 OS: Ubuntu Gnome 16.04.1 LTS ** Affects: evolution (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/1626729 Title: Evolution keeps using wrong password instead of asking it again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1626729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556735] Re: surf crashed with SIGSEGV in JSC::JSCell::getPrimitiveNumber()
I'm having similar issue with Eclipse, which crashed after the following exception: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7f88441d39c0, pid=7412, tid=140228481140480 # # JRE version: OpenJDK Runtime Environment (8.0_91-b14) (build 1.8.0_91-8u91-b14-3ubuntu1~16.04.1-b14) # Java VM: OpenJDK 64-Bit Server VM (25.91-b14 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libjavascriptcoregtk-3.0.so.0+0x4629c0] JSC::JSCell::getPrimitiveNumber(JSC::ExecState*, double&, JSC::JSValue&) const+0x0 [...] Stack: [0x7f897cbe4000,0x7f897cce5000], sp=0x7f897cce2138, free space=1016k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) C [libjavascriptcoregtk-3.0.so.0+0x4629c0] JSC::JSCell::getPrimitiveNumber(JSC::ExecState*, double&, JSC::JSValue&) const+0x0 C 0x7f87fe5ea4e8 Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) J 8160 org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(JZ)Z (0 bytes) @ 0x7f8966704084 [0x7f8966704040+0x44] J 11091 C2 org.eclipse.swt.widgets.Display.readAndDispatch()Z (71 bytes) @ 0x7f896656a890 [0x7f896656a5c0+0x2d0] J 0% C2 org.eclipse.jface.window.Window.runEventLoop(Lorg/eclipse/swt/widgets/Shell;)V (70 bytes) @ 0x7f8966abf310 [0x7f8966abf240+0xd0] j org.eclipse.jface.window.Window.open()I+49 j org.python.pydev.editor.PydevShowBrowserMessage$1.run()V+32 j org.eclipse.swt.widgets.RunnableLock.run()V+11 j org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Z)Z+37 j org.eclipse.swt.widgets.Display.runAsyncMessages(Z)Z+5 j org.eclipse.swt.widgets.Display.readAndDispatch()Z+61 j org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run()V+530 j org.eclipse.core.databinding.observable.Realm.runWithDefault(Lorg/eclipse/core/databinding/observable/Realm;Ljava/lang/Runnable;)V+12 j org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(Lorg/eclipse/e4/ui/model/application/MApplicationElement;Lorg/eclipse/e4/core/contexts/IEclipseContext;)Ljava/lang/Object;+57 j org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(Lorg/eclipse/e4/ui/model/application/MApplicationElement;)V+20 j org.eclipse.ui.internal.Workbench$5.run()V+436 j org.eclipse.core.databinding.observable.Realm.runWithDefault(Lorg/eclipse/core/databinding/observable/Realm;Ljava/lang/Runnable;)V+12 j org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Lorg/eclipse/swt/widgets/Display;Lorg/eclipse/ui/application/WorkbenchAdvisor;)I+18 j org.eclipse.ui.PlatformUI.createAndRunWorkbench(Lorg/eclipse/swt/widgets/Display;Lorg/eclipse/ui/application/WorkbenchAdvisor;)I+2 j org.eclipse.ui.internal.ide.application.IDEApplication.start(Lorg/eclipse/equinox/app/IApplicationContext;)Ljava/lang/Object;+105 j org.eclipse.equinox.internal.app.EclipseAppHandle.run(Ljava/lang/Object;)Ljava/lang/Object;+135 j org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Ljava/lang/Object;)Ljava/lang/Object;+85 j org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Ljava/lang/Object;)Ljava/lang/Object;+82 j org.eclipse.core.runtime.adaptor.EclipseStarter.run(Ljava/lang/Object;)Ljava/lang/Object;+105 j org.eclipse.core.runtime.adaptor.EclipseStarter.run([Ljava/lang/String;Ljava/lang/Runnable;)Ljava/lang/Object;+132 v ~StubRoutines::call_stub j sun.reflect.NativeMethodAccessorImpl.invoke0(Ljava/lang/reflect/Method;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+0 j sun.reflect.NativeMethodAccessorImpl.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+100 j sun.reflect.DelegatingMethodAccessorImpl.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+6 j java.lang.reflect.Method.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+56 j org.eclipse.equinox.launcher.Main.invokeFramework([Ljava/lang/String;[Ljava/net/URL;)V+265 j org.eclipse.equinox.launcher.Main.basicRun([Ljava/lang/String;)V+160 j org.eclipse.equinox.launcher.Main.run([Ljava/lang/String;)I+4 j org.eclipse.equinox.launcher.Main.main([Ljava/lang/String;)V+10 v ~StubRoutines::call_stub -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556735 Title: surf crashed with SIGSEGV in JSC::JSCell::getPrimitiveNumber() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/surf/+bug/1556735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511817] [NEW] bluetoothd consumes 100% CPU when scanning for devices, system hangs
Public bug reported: I'm trying to use the bluedevil wizard on Kubuntu 15.04 to add a new device (BT headset). The scan window opens but no device is found. Meanwhile, both cpu and memory usage start to increase until memory is 100% full and the system hangs! If I just kill bluedevil, then dbus-daemon keeps using 100% cpu, the only way to stop it is by manually stopping the bluetooth service. $ uname -a Linux Home1 3.19.0-32-generic #37-Ubuntu SMP Wed Oct 21 10:23:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ hciconfig -a hci0: Type: BR/EDR Bus: USB BD Address: 44:39:C4:19:43:C9 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:564 acl:0 sco:0 events:29 errors:0 TX bytes:358 acl:0 sco:0 commands:29 errors:0 Features: 0xff 0xfe 0x0d 0xfe 0xd8 0x7f 0x7b 0x8f Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF Link mode: SLAVE ACCEPT $ rfkill list 1: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no 2: dell-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 3: phy0: Wireless LAN Soft blocked: no Hard blocked: no 4: hci0: Bluetooth Soft blocked: no Hard blocked: no $ lsmod | grep blue bluetooth 491520 23 bnep,ath3k,btusb,rfcomm $ lsusb Bus 004 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor Bus 004 Device 005: ID 0cf3:817a Atheros Communications, Inc. Bus 004 Device 002: ID 8087:8000 Intel Corp. Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 0c45:649d Microdia Bus 003 Device 002: ID 8087:8008 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub $ lsusb -s 004:005 -v Bus 004 Device 005: ID 0cf3:817a Atheros Communications, Inc. Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 224 Wireless bDeviceSubClass 1 Radio Frequency bDeviceProtocol 1 Bluetooth bMaxPacketSize064 idVendor 0x0cf3 Atheros Communications, Inc. idProduct 0x817a bcdDevice0.02 iManufacturer 1 iProduct2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 177 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 4 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes1 Transfer TypeIsochronous Synch Type None Usage Type
[Bug 1479378] Re: Nvidia prime black screen on boot
** Description changed: $ lsb_release -rd Description:Ubuntu 15.04 Release:15.04 $ apt-cache policy nvidia-346 nvidia-prime nvidia-346: Installato: 346.59-0ubuntu1 Candidato: 346.59-0ubuntu1 Tabella versione: *** 346.59-0ubuntu1 0 500 http://it.archive.ubuntu.com/ubuntu/ vivid/restricted amd64 Packages 100 /var/lib/dpkg/status 346.46-0ubuntu1 0 500 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1410/x86_64/ Packages nvidia-prime: Installato: 0.8.1 Candidato: 0.8.1 Tabella versione: *** 0.8.1 0 500 http://it.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status $ lspci -v [...] 01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K1100M] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device 15cc Flags: bus master, fast devsel, latency 0, IRQ 38 Memory at f300 (32-bit, non-prefetchable) [size=16M] Memory at d000 (64-bit, prefetchable) [size=256M] Memory at e000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [size=128] [virtual] Expansion ROM at f400 [disabled] [size=512K] Capabilities: access denied Kernel driver in use: nvidia I'm using Nvidia prime with a Quadro K1100M card. - When I switch from intel to nvidia, then after booting I randomly get a black screen about 50% of the times. I can't but switch to a virtual console by pressing [Ctrl+Alt+Fn] and then reboot. If I'm lucky, then the normal Kubuntu login screen appears, otherwise I get yet another black screen and have to reboot again. + When I switch from intel to nvidia, then after booting I randomly get a black screen [about 50% of the times]. EDIT: after latest kernel update, now it happens ALL the times! + + I can't but switch to a virtual console by pressing [Ctrl+Alt+Fn] and + then reboot. output of nvidia-bug-report.sh attached -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1479378 Title: Nvidia prime black screen on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1479378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1479378] [NEW] Nvidia prime black screen on login
Public bug reported: $ lsb_release -rd Description:Ubuntu 15.04 Release:15.04 $ apt-cache policy nvidia-346 nvidia-prime nvidia-346: Installato: 346.59-0ubuntu1 Candidato: 346.59-0ubuntu1 Tabella versione: *** 346.59-0ubuntu1 0 500 http://it.archive.ubuntu.com/ubuntu/ vivid/restricted amd64 Packages 100 /var/lib/dpkg/status 346.46-0ubuntu1 0 500 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1410/x86_64/ Packages nvidia-prime: Installato: 0.8.1 Candidato: 0.8.1 Tabella versione: *** 0.8.1 0 500 http://it.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status $ lspci -v [...] 01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K1100M] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device 15cc Flags: bus master, fast devsel, latency 0, IRQ 38 Memory at f300 (32-bit, non-prefetchable) [size=16M] Memory at d000 (64-bit, prefetchable) [size=256M] Memory at e000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [size=128] [virtual] Expansion ROM at f400 [disabled] [size=512K] Capabilities: access denied Kernel driver in use: nvidia I'm using Nvidia prime with a Quadro K1100M card. When I switch from intel to nvidia, then after booting I get a black screen about 50% of the times. I can't but switch to a virtual console by pressing [Ctrl+Alt+Fn] and then reboot. If I'm lucky, then the normal Kubuntu login screen appears, otherwise I get yet another black screen and have to reboot again. output of nvidia-bug-report.sh attached ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Tags: nvidia prime ** Attachment added: output of nvidia-bug-report.sh https://bugs.launchpad.net/bugs/1479378/+attachment/4435800/+files/nvidia-bug-report.log.gz ** Package changed: kwallet (Ubuntu) = nvidia-prime (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1479378 Title: Nvidia prime black screen on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1479378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1479378] Re: Nvidia prime black screen on login
** Description changed: $ lsb_release -rd Description:Ubuntu 15.04 Release:15.04 $ apt-cache policy nvidia-346 nvidia-prime nvidia-346: - Installato: 346.59-0ubuntu1 - Candidato: 346.59-0ubuntu1 - Tabella versione: - *** 346.59-0ubuntu1 0 - 500 http://it.archive.ubuntu.com/ubuntu/ vivid/restricted amd64 Packages - 100 /var/lib/dpkg/status - 346.46-0ubuntu1 0 - 500 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1410/x86_64/ Packages + Installato: 346.59-0ubuntu1 + Candidato: 346.59-0ubuntu1 + Tabella versione: + *** 346.59-0ubuntu1 0 + 500 http://it.archive.ubuntu.com/ubuntu/ vivid/restricted amd64 Packages + 100 /var/lib/dpkg/status + 346.46-0ubuntu1 0 + 500 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1410/x86_64/ Packages nvidia-prime: - Installato: 0.8.1 - Candidato: 0.8.1 - Tabella versione: - *** 0.8.1 0 - 500 http://it.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages - 100 /var/lib/dpkg/status + Installato: 0.8.1 + Candidato: 0.8.1 + Tabella versione: + *** 0.8.1 0 + 500 http://it.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages + 100 /var/lib/dpkg/status $ lspci -v [...] 01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K1100M] (rev a1) (prog-if 00 [VGA controller]) - Subsystem: Dell Device 15cc - Flags: bus master, fast devsel, latency 0, IRQ 38 - Memory at f300 (32-bit, non-prefetchable) [size=16M] - Memory at d000 (64-bit, prefetchable) [size=256M] - Memory at e000 (64-bit, prefetchable) [size=32M] - I/O ports at e000 [size=128] - [virtual] Expansion ROM at f400 [disabled] [size=512K] - Capabilities: access denied - Kernel driver in use: nvidia - + Subsystem: Dell Device 15cc + Flags: bus master, fast devsel, latency 0, IRQ 38 + Memory at f300 (32-bit, non-prefetchable) [size=16M] + Memory at d000 (64-bit, prefetchable) [size=256M] + Memory at e000 (64-bit, prefetchable) [size=32M] + I/O ports at e000 [size=128] + [virtual] Expansion ROM at f400 [disabled] [size=512K] + Capabilities: access denied + Kernel driver in use: nvidia I'm using Nvidia prime with a Quadro K1100M card. - When I switch from intel to nvidia, then after booting I get a black screen about 50% of the times. I can't but switch to a virtual console by pressing [Ctrl+Fn] and then reboot. If I'm lucky, then the normal Kubuntu login screen appears, otherwise I get yet another black screen and have to reboot again. + When I switch from intel to nvidia, then after booting I get a black screen about 50% of the times. I can't but switch to a virtual console by pressing [Ctrl+Alt+Fn] and then reboot. If I'm lucky, then the normal Kubuntu login screen appears, otherwise I get yet another black screen and have to reboot again. output of nvidia-bug-report.sh attached ** Summary changed: - Nvidia prime black screen on login + Nvidia prime black screen on boot ** Description changed: $ lsb_release -rd Description:Ubuntu 15.04 Release:15.04 $ apt-cache policy nvidia-346 nvidia-prime nvidia-346: Installato: 346.59-0ubuntu1 Candidato: 346.59-0ubuntu1 Tabella versione: *** 346.59-0ubuntu1 0 500 http://it.archive.ubuntu.com/ubuntu/ vivid/restricted amd64 Packages 100 /var/lib/dpkg/status 346.46-0ubuntu1 0 500 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1410/x86_64/ Packages nvidia-prime: Installato: 0.8.1 Candidato: 0.8.1 Tabella versione: *** 0.8.1 0 500 http://it.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status $ lspci -v [...] 01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K1100M] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device 15cc Flags: bus master, fast devsel, latency 0, IRQ 38 Memory at f300 (32-bit, non-prefetchable) [size=16M] Memory at d000 (64-bit, prefetchable) [size=256M] Memory at e000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [size=128] [virtual] Expansion ROM at f400 [disabled] [size=512K] Capabilities: access denied Kernel driver in use: nvidia I'm using Nvidia prime with a Quadro K1100M card. - When I switch from intel to nvidia, then after booting I get a black screen about 50% of the times. I can't but switch to a virtual console by pressing [Ctrl+Alt+Fn] and then reboot. If I'm lucky, then the normal Kubuntu login screen appears, otherwise I get yet another black screen and have to reboot again. + When I switch from intel to nvidia, then after booting I randomly get
[Bug 1354711] Re: incoming call popup disappears after a few seconds
** Changed in: ekiga (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1354711 Title: incoming call popup disappears after a few seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ekiga/+bug/1354711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429478] Re: Kubuntu Vivid 1 Beta 15.04: Kwallet ask for upgrading password safe on fresh installation
The bug is still present in the official 15.04 release -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwallet in Ubuntu. https://bugs.launchpad.net/bugs/1429478 Title: Kubuntu Vivid 1 Beta 15.04: Kwallet ask for upgrading password safe on fresh installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwallet/+bug/1429478/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1434052] Re: kwallet wants to migrate empty kwallet4
I have installed the package libkf5wallet5:amd64 version 5.9.0-0ubuntu1.1 and this issue is NOT fixed to me. As a consequence, I cannot connect to any encrypted Wifi network, as Network Manager keeps asking for the password forever (the passwork is 100% correct as I chose it on my own network). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1434052 Title: kwallet wants to migrate empty kwallet4 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1434052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460731] [NEW] Cannot set proxy for Kmail
Public bug reported: I'm using Kmail on Kubuntu 15.04: uname -r 3.19.0-18-generic apt-cache policy kdepim kdepim: Installed: 4:4.14.6-0ubuntu1 Candidate: 4:4.14.6-0ubuntu1 Version table: *** 4:4.14.6-0ubuntu1 0 500 http://it.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages 100 /var/lib/dpkg/status I tried to set a proxy for Kmail from the menu Settings - Configure Kmail... and then selecting the Proxy tab. I expected to find a form to enter proxy settings, but instead I read the following errors: Cannot find module The diagnosis is: The desktop file was not found (Note: text translated from local language into English) ** Affects: kdepim (Ubuntu) Importance: Undecided Status: New ** Tags: kmail proxy ** Description changed: I'm using Kmail on Kubuntu 15.04: + + uname -a + Linux Home1 3.19.0-18-generic #18-Ubuntu SMP Tue May 19 18:31:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux apt-cache policy kdepim kdepim: - Installed: 4:4.14.6-0ubuntu1 - Candidate: 4:4.14.6-0ubuntu1 - Version table: - *** 4:4.14.6-0ubuntu1 0 - 500 http://it.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages - 100 /var/lib/dpkg/status + Installed: 4:4.14.6-0ubuntu1 + Candidate: 4:4.14.6-0ubuntu1 + Version table: + *** 4:4.14.6-0ubuntu1 0 + 500 http://it.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages + 100 /var/lib/dpkg/status I tried to set a proxy for Kmail from the menu Settings - Configure Kmail... and then selecting the Proxy tab. I expected to find a form to enter proxy settings, but instead I read the following errors: Cannot find module The diagnosis is: The desktop file was not found (Note: text translated from local language into English) ** Description changed: I'm using Kmail on Kubuntu 15.04: - uname -a - Linux Home1 3.19.0-18-generic #18-Ubuntu SMP Tue May 19 18:31:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux + uname -r + 3.19.0-18-generic apt-cache policy kdepim kdepim: Installed: 4:4.14.6-0ubuntu1 Candidate: 4:4.14.6-0ubuntu1 Version table: *** 4:4.14.6-0ubuntu1 0 500 http://it.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages 100 /var/lib/dpkg/status I tried to set a proxy for Kmail from the menu Settings - Configure Kmail... and then selecting the Proxy tab. I expected to find a form to enter proxy settings, but instead I read the following errors: Cannot find module The diagnosis is: The desktop file was not found (Note: text translated from local language into English) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460731 Title: Cannot set proxy for Kmail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/1460731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318951] Re: kernel update fails with /boot on FAT32
I had the same issue with kernel 3.13.0-40.69. I could successfully update the kernel by editing the configuration file /etc/kernel-img.conf as follows: do_symlinks = no -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318951 Title: kernel update fails with /boot on FAT32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1291526] Re: could not start ksmserver with nvidia-prime at next login
This was NOT fixed to me: I'm having a very similar issue (see https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1370725) Please consider reopening this bug in case mine is marked as a duplicate! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1291526 Title: could not start ksmserver with nvidia-prime at next login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1291526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1370725] Re: nvidia prime broken: kserver crash with Quadro K1100M
** Description changed: lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 uname -a Linux Work 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux apt-cache policy nvidia-331 nvidia-prime nvidia-331: - Installato: 331.38-0ubuntu7.1 - Candidato: 331.38-0ubuntu7.1 - Tabella versione: - *** 331.38-0ubuntu7.1 0 - 500 http://it.archive.ubuntu.com/ubuntu/ trusty-updates/restricted amd64 Packages - 100 /var/lib/dpkg/status - 331.38-0ubuntu7 0 - 500 http://it.archive.ubuntu.com/ubuntu/ trusty/restricted amd64 Packages + Installato: 331.38-0ubuntu7.1 + Candidato: 331.38-0ubuntu7.1 + Tabella versione: + *** 331.38-0ubuntu7.1 0 + 500 http://it.archive.ubuntu.com/ubuntu/ trusty-updates/restricted amd64 Packages + 100 /var/lib/dpkg/status + 331.38-0ubuntu7 0 + 500 http://it.archive.ubuntu.com/ubuntu/ trusty/restricted amd64 Packages nvidia-prime: - Installato: 0.6.2 - Candidato: 0.6.2 - Tabella versione: - *** 0.6.2 0 - 500 http://it.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages - 100 /var/lib/dpkg/status + Installato: 0.6.2 + Candidato: 0.6.2 + Tabella versione: + *** 0.6.2 0 + 500 http://it.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages + 100 /var/lib/dpkg/status cat /var/log/prime-supported.log Requires offloading lspci -v 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06) - Subsystem: Dell Device 05cc - Flags: bus master, fast devsel, latency 0 - Capabilities: access denied + Subsystem: Dell Device 05cc + Flags: bus master, fast devsel, latency 0 + Capabilities: access denied 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) (prog-if 00 [Normal decode]) - Flags: bus master, fast devsel, latency 0 - Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 - I/O behind bridge: e000-efff - Memory behind bridge: f300-f40f - Prefetchable memory behind bridge: d000-e1ff - Capabilities: access denied - Kernel driver in use: pcieport + Flags: bus master, fast devsel, latency 0 + Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 + I/O behind bridge: e000-efff + Memory behind bridge: f300-f40f + Prefetchable memory behind bridge: d000-e1ff + Capabilities: access denied + Kernel driver in use: pcieport 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller]) - Subsystem: Dell Device 05cc - Flags: bus master, fast devsel, latency 0, IRQ 255 - Memory at f540 (64-bit, non-prefetchable) [size=4M] - Memory at c000 (64-bit, prefetchable) [size=256M] - I/O ports at f000 [size=64] - Expansion ROM at unassigned [disabled] - Capabilities: access denied + Subsystem: Dell Device 05cc + Flags: bus master, fast devsel, latency 0, IRQ 255 + Memory at f540 (64-bit, non-prefetchable) [size=4M] + Memory at c000 (64-bit, prefetchable) [size=256M] + I/O ports at f000 [size=64] + Expansion ROM at unassigned [disabled] + Capabilities: access denied 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) - Subsystem: Dell Device 05cc - Flags: bus master, fast devsel, latency 0, IRQ 52 - Memory at f7734000 (64-bit, non-prefetchable) [size=16K] - Capabilities: access denied - Kernel driver in use: snd_hda_intel + Subsystem: Dell Device 05cc + Flags: bus master, fast devsel, latency 0, IRQ 52 + Memory at f7734000 (64-bit, non-prefetchable) [size=16K] + Capabilities: access denied + Kernel driver in use: snd_hda_intel 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04) (prog-if 30 [XHCI]) - Subsystem: Dell Device 05cc - Flags: bus master, medium devsel, latency 0, IRQ 47 - Memory at f772 (64-bit, non-prefetchable) [size=64K] - Capabilities: access denied - Kernel driver in use: xhci_hcd + Subsystem: Dell Device 05cc + Flags: bus master, medium devsel, latency 0, IRQ 47 + Memory at f772 (64-bit, non-prefetchable) [size=64K] + Capabilities: access denied + Kernel driver in use: xhci_hcd 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) - Subsystem: Dell Device 05cc -
[Bug 1370725] Re: nvidia prime broken on Kubuntu with Quadro K1100M: kserver crash on login
** Summary changed: - nvidia prime broken: kserver crash with Quadro K1100M + nvidia prime broken on Kubuntu with Quadro K1100M: kserver crash on login ** Description changed: lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 uname -a Linux Work 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux + + KDE version: 4.13.3 apt-cache policy nvidia-331 nvidia-prime nvidia-331: Installato: 331.38-0ubuntu7.1 Candidato: 331.38-0ubuntu7.1 Tabella versione: *** 331.38-0ubuntu7.1 0 500 http://it.archive.ubuntu.com/ubuntu/ trusty-updates/restricted amd64 Packages 100 /var/lib/dpkg/status 331.38-0ubuntu7 0 500 http://it.archive.ubuntu.com/ubuntu/ trusty/restricted amd64 Packages nvidia-prime: Installato: 0.6.2 Candidato: 0.6.2 Tabella versione: *** 0.6.2 0 500 http://it.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status cat /var/log/prime-supported.log Requires offloading lspci -v 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06) Subsystem: Dell Device 05cc Flags: bus master, fast devsel, latency 0 Capabilities: access denied 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: e000-efff Memory behind bridge: f300-f40f Prefetchable memory behind bridge: d000-e1ff Capabilities: access denied Kernel driver in use: pcieport 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Device 05cc Flags: bus master, fast devsel, latency 0, IRQ 255 Memory at f540 (64-bit, non-prefetchable) [size=4M] Memory at c000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] Expansion ROM at unassigned [disabled] Capabilities: access denied 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) Subsystem: Dell Device 05cc Flags: bus master, fast devsel, latency 0, IRQ 52 Memory at f7734000 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied Kernel driver in use: snd_hda_intel 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04) (prog-if 30 [XHCI]) Subsystem: Dell Device 05cc Flags: bus master, medium devsel, latency 0, IRQ 47 Memory at f772 (64-bit, non-prefetchable) [size=64K] Capabilities: access denied Kernel driver in use: xhci_hcd 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) Subsystem: Dell Device 05cc Flags: bus master, fast devsel, latency 0, IRQ 49 Memory at f774 (64-bit, non-prefetchable) [size=16] Capabilities: access denied Kernel driver in use: mei_me 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 04) Subsystem: Dell Device 05cc Flags: bus master, fast devsel, latency 0, IRQ 50 Memory at f770 (32-bit, non-prefetchable) [size=128K] Memory at f773d000 (32-bit, non-prefetchable) [size=4K] I/O ports at f080 [disabled] [size=32] Capabilities: access denied Kernel driver in use: e1000e 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04) (prog-if 20 [EHCI]) Subsystem: Dell Device 05cc Flags: bus master, medium devsel, latency 0, IRQ 16 Memory at f773c000 (32-bit, non-prefetchable) [size=1K] Capabilities: access denied Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04) Subsystem: Dell Device 05cc Flags: bus master, fast devsel, latency 0, IRQ 51 Memory at f773 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied Kernel driver in use: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: 2000-2fff Memory behind bridge:
[Bug 1370725] Re: ksmserver crash on login on Kubuntu with Nvidia Quadro K1100M
I tried to restore the desktop environment by typing from a virtual console: sudo apt-get purge nvidia* sudo apt-get install nvidia-331 nvidia-prime Since then, I'm able to login into lightdm only by booting in failsafe mode at grub menu, but one odd thing is the lame nvidia-settings window shown in the attached picture. Also, the file /etc/X11/xorg.conf is now missing. I also tried to select the intel card with the command: sudo prime-select intel but then I get plenty of errors in kernel.log: Sep 17 21:08:24 Work kernel: [ 60.878559] [ cut here ] Sep 17 21:08:24 Work kernel: [ 60.878591] WARNING: CPU: 5 PID: 198 at /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_pm.c:5873 i915_release_power_well+0x5a/0x60 [i915]() Sep 17 21:08:24 Work kernel: [ 60.878592] Modules linked in: pci_stub vboxpci(OX) vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) xt_tcpudp xt_conntrack nf_conntrack_irc nf_conntrack_ftp xt_state xt_limit xt_LOG nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack iptable_filter ip_tables x_tables rfcomm bnep nls_iso8859_1 lp nvidia(POX) joydev uvcvideo hid_logitech_dj videobuf2_vmalloc videobuf2_memops videobuf2_core usbhid snd_hda_codec_hdmi hid videodev snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm ath3k arc4 btusb dell_wmi snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq ath9k bluetooth snd_seq_device sparse_keymap snd_timer ath9k_common ath9k_hw ppdev x86_pkg_temp_thermal ath snd mac80211 intel_powerclamp coretemp dell_laptop e1000e dcdbas cfg80211 kvm_intel mei_me kvm psmouse parport_pc parport mei ptp sdhci_pci pps_core sdhci wmi serio_raw mac_hid lpc_ich crct10dif_pclmul crc32_pclmul soundcore ghash_clmulni_intel dm_crypt i915 aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd i2c_algo_bit ahci drm_kms_helper libahci drm video Sep 17 21:08:24 Work kernel: [ 60.878626] CPU: 5 PID: 198 Comm: kworker/u16:4 Tainted: PW OX 3.13.0-36-generic #63-Ubuntu Sep 17 21:08:24 Work kernel: [ 60.878628] Hardware name: Dell Inc. Precision M4800/0T3YTY, BIOS A06 01/02/2014 Sep 17 21:08:24 Work kernel: [ 60.878634] Workqueue: hd-audio0 hda_power_work [snd_hda_codec] Sep 17 21:08:24 Work kernel: [ 60.878635] 0009 880424fcdc00 8171e569 Sep 17 21:08:24 Work kernel: [ 60.878637] 880424fcdc38 8106775d a06579c0 Sep 17 21:08:24 Work kernel: [ 60.878639] 813a81d0 880427ddd098 880424fcdc48 Sep 17 21:08:24 Work kernel: [ 60.878641] Call Trace: Sep 17 21:08:24 Work kernel: [ 60.878645] [8171e569] dump_stack+0x45/0x56 Sep 17 21:08:24 Work kernel: [ 60.878648] [8106775d] warn_slowpath_common+0x7d/0xa0 Sep 17 21:08:24 Work kernel: [ 60.878651] [813a81d0] ? pci_legacy_suspend_late+0xf0/0xf0 Sep 17 21:08:24 Work kernel: [ 60.878653] [8106783a] warn_slowpath_null+0x1a/0x20 Sep 17 21:08:24 Work kernel: [ 60.878665] [a01743ea] i915_release_power_well+0x5a/0x60 [i915] Sep 17 21:08:24 Work kernel: [ 60.878669] [a0655f38] hda_display_power+0x28/0x40 [snd_hda_intel] Sep 17 21:08:24 Work kernel: [ 60.878672] [a065302f] azx_runtime_suspend+0x8f/0xb0 [snd_hda_intel] Sep 17 21:08:24 Work kernel: [ 60.878674] [813a8231] pci_pm_runtime_suspend+0x61/0x140 Sep 17 21:08:24 Work kernel: [ 60.878676] [813a81d0] ? pci_legacy_suspend_late+0xf0/0xf0 Sep 17 21:08:24 Work kernel: [ 60.878679] [814a0fc6] __rpm_callback+0x36/0xc0 Sep 17 21:08:24 Work kernel: [ 60.878682] [a0652ceb] ? azx_get_response+0xfb/0x320 [snd_hda_intel] Sep 17 21:08:24 Work kernel: [ 60.878684] [814a1074] rpm_callback+0x24/0x80 Sep 17 21:08:24 Work kernel: [ 60.878685] [814a11f6] rpm_suspend+0x126/0x6e0 Sep 17 21:08:24 Work kernel: [ 60.878688] [810aab84] ? __wake_up+0x44/0x50 Sep 17 21:08:24 Work kernel: [ 60.878690] [814a1976] rpm_idle+0xd6/0x2b0 Sep 17 21:08:24 Work kernel: [ 60.878692] [814a1bad] __pm_runtime_idle+0x5d/0x80 Sep 17 21:08:24 Work kernel: [ 60.878694] [a0650a3d] azx_power_notify+0x2d/0x40 [snd_hda_intel] Sep 17 21:08:24 Work kernel: [ 60.878699] [a0591e6e] hda_power_work+0x9e/0xa0 [snd_hda_codec] Sep 17 21:08:24 Work kernel: [ 60.878702] [810839d2] process_one_work+0x182/0x450 Sep 17 21:08:24 Work kernel: [ 60.878704] [810847c1] worker_thread+0x121/0x410 Sep 17 21:08:24 Work kernel: [ 60.878706] [810846a0] ? rescuer_thread+0x430/0x430 Sep 17 21:08:24 Work kernel: [ 60.878708] [8108b4a2] kthread+0xd2/0xf0 Sep 17 21:08:24 Work kernel: [ 60.878710] [8108b3d0] ? kthread_create_on_node+0x1c0/0x1c0 Sep 17 21:08:24 Work kernel: [ 60.878711] [8172eefc] ret_from_fork+0x7c/0xb0 Sep 17 21:08:24 Work kernel: [ 60.878713] [8108b3d0]
[Bug 1370725] Re: nvidia prime broken: kserver crash with Quadro K1100M
** Attachment added: x-0.log https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1370725/+attachment/4206788/+files/x-0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1370725 Title: nvidia prime broken: kserver crash with Quadro K1100M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1370725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1370725] Re: nvidia prime broken: kserver crash with Quadro K1100M
** Attachment added: gpu-manager.log https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1370725/+attachment/4206786/+files/gpu-manager.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1370725 Title: nvidia prime broken: kserver crash with Quadro K1100M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1370725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1370725] Re: nvidia prime broken: kserver crash with Quadro K1100M
** Attachment added: x-0-greeter.log https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1370725/+attachment/4206787/+files/x-0-greeter.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1370725 Title: nvidia prime broken: kserver crash with Quadro K1100M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1370725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1370725] [NEW] nvidia prime broken: kserver crash with Quadro K1100M
Public bug reported: lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 uname -a Linux Work 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux apt-cache policy nvidia-331 nvidia-prime nvidia-331: Installato: 331.38-0ubuntu7.1 Candidato: 331.38-0ubuntu7.1 Tabella versione: *** 331.38-0ubuntu7.1 0 500 http://it.archive.ubuntu.com/ubuntu/ trusty-updates/restricted amd64 Packages 100 /var/lib/dpkg/status 331.38-0ubuntu7 0 500 http://it.archive.ubuntu.com/ubuntu/ trusty/restricted amd64 Packages nvidia-prime: Installato: 0.6.2 Candidato: 0.6.2 Tabella versione: *** 0.6.2 0 500 http://it.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status cat /var/log/prime-supported.log Requires offloading lspci -v 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06) Subsystem: Dell Device 05cc Flags: bus master, fast devsel, latency 0 Capabilities: access denied 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: e000-efff Memory behind bridge: f300-f40f Prefetchable memory behind bridge: d000-e1ff Capabilities: access denied Kernel driver in use: pcieport 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Device 05cc Flags: bus master, fast devsel, latency 0, IRQ 255 Memory at f540 (64-bit, non-prefetchable) [size=4M] Memory at c000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] Expansion ROM at unassigned [disabled] Capabilities: access denied 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) Subsystem: Dell Device 05cc Flags: bus master, fast devsel, latency 0, IRQ 52 Memory at f7734000 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied Kernel driver in use: snd_hda_intel 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04) (prog-if 30 [XHCI]) Subsystem: Dell Device 05cc Flags: bus master, medium devsel, latency 0, IRQ 47 Memory at f772 (64-bit, non-prefetchable) [size=64K] Capabilities: access denied Kernel driver in use: xhci_hcd 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) Subsystem: Dell Device 05cc Flags: bus master, fast devsel, latency 0, IRQ 49 Memory at f774 (64-bit, non-prefetchable) [size=16] Capabilities: access denied Kernel driver in use: mei_me 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 04) Subsystem: Dell Device 05cc Flags: bus master, fast devsel, latency 0, IRQ 50 Memory at f770 (32-bit, non-prefetchable) [size=128K] Memory at f773d000 (32-bit, non-prefetchable) [size=4K] I/O ports at f080 [disabled] [size=32] Capabilities: access denied Kernel driver in use: e1000e 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04) (prog-if 20 [EHCI]) Subsystem: Dell Device 05cc Flags: bus master, medium devsel, latency 0, IRQ 16 Memory at f773c000 (32-bit, non-prefetchable) [size=1K] Capabilities: access denied Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04) Subsystem: Dell Device 05cc Flags: bus master, fast devsel, latency 0, IRQ 51 Memory at f773 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied Kernel driver in use: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: 2000-2fff Memory behind bridge: bf20-bf3f Prefetchable memory behind bridge: bf40-bf5f Capabilities: access denied Kernel driver in use: pcieport 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d4) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00,
[Bug 680192] Re: Vidalia was unable to start Tor. Check your settings to ensure the correct name and location of your Tor executable is specified.
Confirmed on Kubuntu 14.04.1 LTS Vidalia is unusable to me -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/680192 Title: Vidalia was unable to start Tor. Check your settings to ensure the correct name and location of your Tor executable is specified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vidalia/+bug/680192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1354711] [NEW] incoming call popup disappears after a few seconds
Public bug reported: ekiga: 4.0.1-4 on Kubuntu 14.04.1 LTS Whenever there is an incoming call, the popup window with the accept button is shown for just a few seconds, then it disappears. So if I fail to click the button within that short time, I can still hear the ringing phone sound but there is no way to answer the call! Expected behavior: the popup window should be displayed as long as the phone is ringing ** Affects: ekiga (Ubuntu) Importance: Undecided Status: New ** Description changed: - ekiga: 4.0.1-4 on Ubuntu 14.04.1 LTS + ekiga: 4.0.1-4 on Kubuntu 14.04.1 LTS Whenever there is an incoming call, the popup window with the accept button is shown for just a few seconds, then it disappears. So if I fail to click the button within that short time, I can still hear the ringing phone sound but there is no way to answer the call! Expected behavior: the popup window should be displayed as long as the phone is ringing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1354711 Title: incoming call popup disappears after a few seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ekiga/+bug/1354711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 680192] Re: Vidalia was unable to start Tor. Check your settings to ensure the correct name and location of your Tor executable is specified.
I confirm this bug on saucy. Adding the /usr/sbin/tor Ux, line to AppArmor configuration does NOT fix the issue to me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/680192 Title: Vidalia was unable to start Tor. Check your settings to ensure the correct name and location of your Tor executable is specified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vidalia/+bug/680192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 680192] Re: Vidalia was unable to start Tor. Check your settings to ensure the correct name and location of your Tor executable is specified.
In the kernel log I found the following lines: Feb 11 13:14:34 Base kernel: [ 515.502544] type=1400 audit(1392120874.882:50): apparmor=DENIED operation=open parent=2110 profile=/usr/bin/vidalia name=/usr/share/kde4/config/kdebugrc pid=5065 comm=vidalia requested_mask=r denied_mask=r fsuid=1000 ouid=0 Feb 11 13:14:34 Base kernel: [ 515.502609] type=1400 audit(1392120874.882:51): apparmor=DENIED operation=open parent=2110 profile=/usr/bin/vidalia name=/usr/share/kubuntu-default-settings/kde4-profile/default/share/config/kdebugrc pid=5065 comm=vidalia requested_mask=r denied_mask=r fsuid=1000 ouid=0 Feb 11 13:15:07 Base kernel: [ 548.148103] audit_printk_skb: 90 callbacks suppressed Feb 11 13:15:07 Base kernel: [ 548.148107] type=1400 audit(1392120907.506:82): apparmor=DENIED operation=rename_src parent=1 profile=system_tor name=/etc/tor/torrc pid=1773 comm=tor requested_mask=wd denied_mask=wd fsuid=109 ouid=0 Feb 11 13:15:10 Base kernel: [ 551.304020] type=1400 audit(1392120910.662:83): apparmor=DENIED operation=exec parent=5065 profile=/usr/bin/vidalia name=/usr/bin/tor pid=5156 comm=vidalia requested_mask=x denied_mask=x fsuid=1000 ouid=0 Feb 11 13:20:15 Base kernel: [ 856.643244] type=1400 audit(1392121215.814:84): apparmor=DENIED operation=exec parent=5065 profile=/usr/bin/vidalia name=/usr/bin/tor pid=8816 comm=vidalia requested_mask=x denied_mask=x fsuid=1000 ouid=0 Feb 11 13:20:40 Base kernel: [ 881.196426] perf samples too long (2511 2500), lowering kernel.perf_event_max_sample_rate to 5 Feb 11 13:40:50 Base kernel: [ 2091.621962] type=1400 audit(1392122450.042:85): apparmor=DENIED operation=open parent=2110 profile=/usr/bin/vidalia name=/home/tuxx/.kde/share/config/kdebugrc pid=5065 comm=vidalia requested_mask=r denied_mask=r fsuid=1000 ouid=1000 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/680192 Title: Vidalia was unable to start Tor. Check your settings to ensure the correct name and location of your Tor executable is specified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vidalia/+bug/680192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1169984] Re: 3.8.0-18 HDMI audio regression: Either oops or opening device fails with -ENODEV
I installed the 64bit kernel on the #17 link, but I still get this from dmesg: [ 35.066792] Request for unknown module key 'Magrathea: Glacier signing key: d490763cc418e29de79f40a5aa7d97747ec8882c' err -11 [ 35.156528] BUG: Bad page map in process S55urandom pte:1ee0 pmd:114e5f067 [ 35.156563] addr:7fffb1bfe000 vm_flags:00040075 anon_vma: (null) mapping: (null) index:7fffb1bfe [ 35.156599] vma-vm_ops-fault: special_mapping_fault+0x0/0x80 [ 35.156624] Pid: 1160, comm: S55urandom Tainted: GF 3.8.0-19-generic #29lp1169984v201304261303 [ 35.156627] Call Trace: [ 35.156636] [8115477d] print_bad_pte+0x1dd/0x250 [ 35.156642] [81156df9] unmap_page_range+0x529/0x750 [ 35.156648] [8107db21] ? __wake_up_bit+0x31/0x40 [ 35.156653] [811570aa] unmap_single_vma+0x8a/0x100 [ 35.156658] [81157909] unmap_vmas+0x49/0x90 [ 35.156664] [8115fcf8] exit_mmap+0x98/0x170 [ 35.156672] [810559e4] mmput+0x64/0x100 [ 35.156677] [8105e302] do_exit+0x242/0x9d0 [ 35.156682] [8105eb0f] do_group_exit+0x3f/0xa0 [ 35.156686] [8105eb87] sys_exit_group+0x17/0x20 [ 35.156694] [816d379d] system_call_fastpath+0x1a/0x1f [ 35.156698] swap_free: Bad swap file entry 402 [ 35.156719] BUG: Bad page map in process S55urandom pte:0404 pmd:114e5f067 [ 35.156743] addr:7fffb1bff000 vm_flags:00040075 anon_vma: (null) mapping: (null) index:7fffb1bff [ 35.156775] vma-vm_ops-fault: special_mapping_fault+0x0/0x80 [ 35.156796] Pid: 1160, comm: S55urandom Tainted: GF B 3.8.0-19-generic #29lp1169984v201304261303 [ 35.156798] Call Trace: [ 35.156803] [8115477d] print_bad_pte+0x1dd/0x250 [ 35.156808] [81156df9] unmap_page_range+0x529/0x750 [ 35.156812] [8107db21] ? __wake_up_bit+0x31/0x40 [ 35.156817] [811570aa] unmap_single_vma+0x8a/0x100 [ 35.156822] [81157909] unmap_vmas+0x49/0x90 [ 35.156827] [8115fcf8] exit_mmap+0x98/0x170 [ 35.156832] [810559e4] mmput+0x64/0x100 [ 35.156837] [8105e302] do_exit+0x242/0x9d0 [ 35.156842] [8105eb0f] do_group_exit+0x3f/0xa0 [ 35.156846] [8105eb87] sys_exit_group+0x17/0x20 [ 35.156852] [816d379d] system_call_fastpath+0x1a/0x1f [ 35.157410] BUG: Bad rss-counter state mm:8801151ddf80 idx:0 val:1 [ 35.157460] BUG: Bad rss-counter state mm:8801151ddf80 idx:2 val:-1 [ 35.166246] Request for unknown module key 'Magrathea: Glacier signing key: d490763cc418e29de79f40a5aa7d97747ec8882c' err -11 [ 35.367966] Request for unknown module key 'Magrathea: Glacier signing key: d490763cc418e29de79f40a5aa7d97747ec8882c' err -11 [ 35.566423] Request for unknown module key 'Magrathea: Glacier signing key: d490763cc418e29de79f40a5aa7d97747ec8882c' err -11 [ 35.586761] Request for unknown module key 'Magrathea: Glacier signing key: d490763cc418e29de79f40a5aa7d97747ec8882c' err -11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1169984 Title: 3.8.0-18 HDMI audio regression: Either oops or opening device fails with -ENODEV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1169984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1175217] Re: Kernel oops during boot
*** This bug is a duplicate of bug 1169984 *** https://bugs.launchpad.net/bugs/1169984 ** Attachment removed: BootDmesg.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1175217/+attachment/3661526/+files/BootDmesg.txt ** Attachment removed: CurrentDmesg.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1175217/+attachment/3661528/+files/CurrentDmesg.txt ** Attachment removed: Lsusb.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1175217/+attachment/3661532/+files/Lsusb.txt ** Attachment removed: PulseList.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1175217/+attachment/3661537/+files/PulseList.txt ** Attachment removed: UdevDb.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1175217/+attachment/3661539/+files/UdevDb.txt ** Attachment removed: UdevLog.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1175217/+attachment/3661540/+files/UdevLog.txt ** Attachment removed: AlsaInfo.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1175217/+attachment/3661525/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175217 Title: Kernel oops during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1175217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1169984] Re: 3.8.0-18 HDMI audio regression: Either oops or opening device fails with -ENODEV
@Cody Smith well, that wouldn't explain why they didn't apply the #17 patch on latest 3.8.0-19.30 kernel, though -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1169984 Title: 3.8.0-18 HDMI audio regression: Either oops or opening device fails with -ENODEV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1169984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1175217] [NEW] Kernel oops during boot
Public bug reported: The Kubuntu 13.04 system halted on boot and had to be shut down manually. Attached is an extract from the syslog, where a kernel oops is reported. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giacof 3008 F pulseaudio Date: Wed May 1 17:51:09 2013 HibernationDevice: RESUME=UUID=4a069a6c-2e98-4637-958b-8dfed3405d3f InstallationDate: Installed on 2013-04-28 (2 days ago) InstallationMedia: Kubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: SAMSUNG ELECTRONICS CO., LTD. R580/R590 MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-19-generic root=/dev/mapper/vg-kuburoot ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 11JB.M044.20100622.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R580/R590 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr11JB.M044.20100622.hkk:bd06/22/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR580/R590:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR580/R590:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R580/R590 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug raring ** Attachment added: Kernel oops in syslog https://bugs.launchpad.net/bugs/1175217/+attachment/3661524/+files/kernelOops.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175217 Title: Kernel oops during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1175217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1175217] Re: Kernel oops during boot
** Attachment removed: WifiSyslog.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1175217/+attachment/3661541/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175217 Title: Kernel oops during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1175217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 554183] Re: paste special does not work
Same problem here with writer. It just works for a few times, then it gets back only after application restart. Using LibreOffice 3.4.4 OOO340m1 (Build:402) on Kubuntu 11.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/554183 Title: paste special does not work To manage notifications about this bug go to: https://bugs.launchpad.net/openoffice/+bug/554183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 554183] Re: paste special does not work
EDIT: sorry, the Paste Special command is also restored by using Ctrl-V as described above by Rolf Broberg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/554183 Title: paste special does not work To manage notifications about this bug go to: https://bugs.launchpad.net/openoffice/+bug/554183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 237773] Re: Cannot send fax: no carrier
Hello, I installed Ahmed's fix on Kubuntu 8.10 and I confirm it works now! Many thanks! ** Changed in: sl-modem (Ubuntu) Status: Incomplete = Fix Released -- Cannot send fax: no carrier https://bugs.launchpad.net/bugs/237773 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367849] Re: Network Management not allowing to connect to saved network
** Summary changed: - Network Managment not allowing to connect to saved network + Network Management not allowing to connect to saved network ** Description changed: Binary package hint: plasma-widget-network-manager - I right-click the plasma icon for NetworkManager, and select 'Network Managment'. Then I setup a wireless network with a WEP key and save it. + I right-click the plasma icon for NetworkManager, and select 'Network Management'. Then I setup a wireless network with a WEP key and save it. I can now see the new entry in the 'Wireless' tab, but it is unusable: there is no way to connect to that network by selecting and clicking on the corresponding line, nor can I find any 'connect' button. If I left-click the plasma icon, I can see the same wireless SSID, but when attempting to connect to it a dialog pops up asking again for network configuration data, including the WEP key! $ lsb_release -rd Description:Ubuntu 9.04 Release:9.04 $ apt-cache policy plasma-widget-network-manager plasma-widget-network-manager: Installato: 0.0+svn930811-0ubuntu2 Candidato: 0.0+svn930811-0ubuntu2 Tabella versione: *** 0.0+svn930811-0ubuntu2 0 500 http://it.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status -- Network Management not allowing to connect to saved network https://bugs.launchpad.net/bugs/367849 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 160268] Re: Cannot cancel authorization dialog if periodic check was deselected in preferences
I confirm this bug in Jaunty (KDE 4.2.2). -- Cannot cancel authorization dialog if periodic check was deselected in preferences https://bugs.launchpad.net/bugs/160268 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdepim in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 312270] Re: [i965] X freezes during KDE startup
I'm sorry but I cannot do any debug with it as I changed my old laptop. -- [i965] X freezes during KDE startup https://bugs.launchpad.net/bugs/312270 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 367849] [NEW] Network Managment not allowing to connect to saved network
Public bug reported: Binary package hint: plasma-widget-network-manager I right-click the plasma icon for NetworkManager, and select 'Network Managment'. Then I setup a wireless network with a WEP key and save it. I can now see the new entry in the 'Wireless' tab, but it is unusable: there is no way to connect to that network by selecting and clicking on the corresponding line, nor can I find any 'connect' button. If I left-click the plasma icon, I can see the same wireless SSID, but when attempting to connect to it a dialog pops up asking again for network configuration data, including the WEP key! $ lsb_release -rd Description:Ubuntu 9.04 Release:9.04 $ apt-cache policy plasma-widget-network-manager plasma-widget-network-manager: Installato: 0.0+svn930811-0ubuntu2 Candidato: 0.0+svn930811-0ubuntu2 Tabella versione: *** 0.0+svn930811-0ubuntu2 0 500 http://it.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status ** Affects: plasma-widget-network-manager (Ubuntu) Importance: Undecided Status: New -- Network Managment not allowing to connect to saved network https://bugs.launchpad.net/bugs/367849 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-network-manager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 367862] [NEW] Cannot resize columns in Kmail folder view
Public bug reported: Binary package hint: kdepim In the folder view in Kmail (version 1.11.2) I added the 'total' column to display the total number of messages in a folder. When the mouse hovers on the column headers, the resize cursor does not appear and the column size cannot be adjusted. $ lsb_release -rd Description:Ubuntu 9.04 Release:9.04 gia...@new-host3:~$ apt-cache policy kmail kmail: Installato: 4:4.2.2-0ubuntu1 Candidato: 4:4.2.2-0ubuntu1 Tabella versione: *** 4:4.2.2-0ubuntu1 0 500 http://it.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status ** Affects: kdepim (Ubuntu) Importance: Undecided Status: New -- Cannot resize columns in Kmail folder view https://bugs.launchpad.net/bugs/367862 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 353371] Re: NetworkManager plasma widget does not retrieve saved WiFi keys from kwallet
Confirmed on Jaunty beta. I really cannot figure out why on the Manage network connections panel there is no connect button to quickly connect to any configured network. Seriously considering to switch to wicd. -- NetworkManager plasma widget does not retrieve saved WiFi keys from kwallet https://bugs.launchpad.net/bugs/353371 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-network-manager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 335777] Re: (Jaunty) plasmoid-network-manager does not remember configured connection
Confirmed on Kubuntu Jaunty beta. dpkg -l | grep network-manager ii network-manager0.7.1~rc3.2.gitb8fc83a7-0ubuntu1 network management framework daemon ii plasma-widget-network-manager 0.0+svn930811-0ubuntu2 KDE plasma applet for controlling NetworkMan ** Changed in: plasma-widget-network-manager (Ubuntu) Status: New = Confirmed -- (Jaunty) plasmoid-network-manager does not remember configured connection https://bugs.launchpad.net/bugs/335777 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-network-manager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 354650] [NEW] fail to run/install firewall
Public bug reported: Binary package hint: kmyfirewall I installed kmyfirewall version 1.1.1-2ubuntu1 on Kubuntu Jaunty beta (KDE 4.2.2). I used a saved configuration file (.kmfnet) which was working fine in Intrepid, but as I tried to run or install the firewall, I got an ugly error dialog (see attached screenshot). From the console I also read the following error lines: QGDict::hashKeyString: Invalid null key QGDict::hashKeyString: Invalid null key ** Affects: kmyfirewall (Ubuntu) Importance: Undecided Status: New -- fail to run/install firewall https://bugs.launchpad.net/bugs/354650 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354650] Re: fail to run/install firewall
** Attachment added: kmf_screenshot.jpeg http://launchpadlibrarian.net/24762851/kmf_screenshot.jpeg -- fail to run/install firewall https://bugs.launchpad.net/bugs/354650 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 330067] Re: [i965] X server crash while running Google Earth
Sorry but I cannot do any further test as I recently changed my laptop, and now have a different video chipset. All the same, thank you for your care about it. -- [i965] X server crash while running Google Earth https://bugs.launchpad.net/bugs/330067 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 321972] Re: [i965] kernel panic after touching touchpad
Can you then confirm the screenshot was useful to investigate the panic? Regards -- [i965] kernel panic after touching touchpad https://bugs.launchpad.net/bugs/321972 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
