[Bug 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low
To complete the list of products: In addition to games, this change is also useful for users of Elasticsearch and/or Opensearch and Apache Lucene/Solr on large clusters. Elasticsearch also suggests raising the value, although not so high: https://www.elastic.co/guide/en/elasticsearch/reference/current/vm-max-map-count.html Opensearch: https://opensearch.org/docs/latest/install-and-configure/install-opensearch/index/#important-settings Apache Solr: https://solr.apache.org/guide/solr/latest/deployment-guide/taking-solr-to-production.html If you e.g. start Elasticsearch without a large enough vm.max_map_count, it will print a log message to raise it and exit. My personal opinion: Actually the game issues described here should better be fixed in Steam's launcher when starting such a game (or in Wine). The downstream software should better ask the user to raise the value upon starting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/2057792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969294] Re: Ubuntu 22.04 gdm3 freezes with Nvidia GPU
i have a similar issue. ubuntu 22.04 installed, nvidia 510 driver on desktop. after boot, login using any application the screen freezes. the timing seems random, sometimes earlier, sometimes later. can only do ALT-PrtScr-B to reboot. the strange thing is: after this reboot, the screen no longer freezes! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969294 Title: Ubuntu 22.04 gdm3 freezes with Nvidia GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971058] Re: package yaru-theme-gnome-shell 21.10.2 failed to install/upgrade: new yaru-theme-gnome-shell package pre-installation script subprocess returned error exit status 1
same bug now in 22.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971058 Title: package yaru-theme-gnome-shell 21.10.2 failed to install/upgrade: new yaru-theme-gnome-shell package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1971058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967501] Re: Trying to save a PDF file in Chrome causes an error in Ubuntu before the Save file dialogue opens
*** This bug is a duplicate of bug 1966784 *** https://bugs.launchpad.net/bugs/1966784 I am sorry, I can't look at the other bug because apparently I lack any rights to see the bug #1966784. Thanks for the fast reply. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967501 Title: Trying to save a PDF file in Chrome causes an error in Ubuntu before the Save file dialogue opens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/1967501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966053] [NEW] Installing Ubuntu 21.10 fails because the installer hangs at installing Firefox from snap
Public bug reported: My Lenovo desktop running Ubuntu 21.10 became unstable and bloated and in the interest of time, I decided to just reinstall the entire system using a fresh installation iso. The system boots properly and the installer works without hassle until it tries to install firefox (apparently using snap). This is a behavior I could reproduce. The only workaround was to deactive network during installation. At this stage, the installation went comepletely fine. After rebooting, the system hangs after clicking on the "Firefox" icon. Installing a current Firefox using apt does not cause any crash. I am not sure if this is related to bug #1947352. ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Tags: impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966053 Title: Installing Ubuntu 21.10 fails because the installer hangs at installing Firefox from snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1966053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
Hello, I updated to 5.13.0-25 and I confirm it works properly on a Ryzen 5-3600G. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956469] [NEW] GPU related problems after kernel update
Public bug reported: After the last stable kernel update, my system is slow, browsers fail to start and crash and dmesg is full of gpu related error messages. Loading the previous kernel does not result in any problems. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 5 14:57:16 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.5, 5.13.0-22-generic, x86_64: installed v4l2loopback, 0.12.5, 5.13.0-23-generic, x86_64: installed virtualbox, 6.1.26, 5.13.0-22-generic, x86_64: installed virtualbox, 6.1.26, 5.13.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:8643] InstallationDate: Installed on 2021-07-16 (172 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210715) MachineType: HP HP Desktop M01-F0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2019 dmi.bios.release: 15.17 dmi.bios.vendor: AMI dmi.bios.version: F.11 dmi.board.name: 8643 dmi.board.vendor: HP dmi.board.version: SMVB dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 52.38 dmi.modalias: dmi:bvnAMI:bvrF.11:bd11/26/2019:br15.17:efr52.38:svnHP:pnHPDesktopM01-F0xxx:pvr:rvnHP:rn8643:rvrSMVB:cvnHP:ct3:cvr:sku8KX18EA#ABD: dmi.product.family: 103C_53311M HP Desktop PC dmi.product.name: HP Desktop M01-F0xxx dmi.product.sku: 8KX18EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze impish ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956469 Title: GPU related problems after kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1956469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939740] [NEW] Reporting a bug fails because of error message "Invalid core dump"
Public bug reported: After starting my desktop, I received a message that (I believe) gnome- shell encountered an issue and I confirmed to send this report to ubuntu. However, the submission process failed because of the following error message: "Problem in gnome-shell Das Problem kann nicht gemeldet werden: Invalid core dump: BFD:warning: /tmp/apport_core_wu53zz5_ is truncated: expected core file size >= 611393536, found: 356581376" ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 12 20:41:22 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-16 (27 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210715) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939740 Title: Reporting a bug fails because of error message "Invalid core dump" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1939740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933318] Re: package proftpd-core 1.3.7a+dfsg-12 failed to install/upgrade: installed proftpd-core package post-installation script subprocess returned error exit status 1
it was always the proftpd-core config problem the following solved it for me: sudo apt remove proftpd* sudp apt purge proftpd* sudo apt-get install proftpd* sudo service proftpd start proftpd.service - ProFTPD FTP Server Loaded: loaded (/lib/systemd/system/proftpd.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2021-07-19 12:53:36 +07; 9min ago Main PID: 12406 (proftpd) Tasks: 1 (limit: 4632) Memory: 4.1M -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933318 Title: package proftpd-core 1.3.7a+dfsg-12 failed to install/upgrade: installed proftpd-core package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/proftpd-dfsg/+bug/1933318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928763] [NEW] Ubuntu does not recognize the touchpad
Public bug reported: The device in question is a Lenovo IdeaPad 5 15ARE05. Using the touchpad does not work in Ubuntu. Input does not get recognized. Using an external USB mouse works fine. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 18 10:07:58 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:381b] InstallationDate: Installed on 2021-03-24 (54 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210322) MachineType: LENOVO 81YQ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=216cd85a-60ae-4f84-b68c-ba90f8154877 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN39WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ARE05 dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvrE7CN39WW:bd01/14/2021:br1.39:efr1.39:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928763 Title: Ubuntu does not recognize the touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1928763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926121] [NEW] After suspending, no video signal appears after waking up
Public bug reported: No video signal appears after waking up my computer from suspending it and leaving it in this state for a while. This issue has appeared after upgrading from Ubuntu 20.10 (where suspending and waking up worked flawlessly) to 21.04. The computer in question is a HP Desktop - M01-F0230ng with a Ryzen 5 3400G processor. A similar issue exists with a Lenovo Desktop and a Ryzen 7 4600G. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 07:12:31 2021 DistUpgraded: 2021-04-22 20:20:35,886 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Konnte Unterprozess "./xorg_fix_proprietary.py" nicht ausführen: Failed to execve: Datei oder Verzeichnis nicht gefunden (1)) DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:8643] InstallationDate: Installed on 2020-03-28 (393 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200328) MachineType: HP HP Desktop M01-F0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8fc8c49e-2944-4e22-9137-fd8870710ea3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-04-22 (3 days ago) dmi.bios.date: 11/26/2019 dmi.bios.release: 15.17 dmi.bios.vendor: AMI dmi.bios.version: F.11 dmi.board.name: 8643 dmi.board.vendor: HP dmi.board.version: SMVB dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 52.38 dmi.modalias: dmi:bvnAMI:bvrF.11:bd11/26/2019:br15.17:efr52.38:svnHP:pnHPDesktopM01-F0xxx:pvr:rvnHP:rn8643:rvrSMVB:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Desktop PC dmi.product.name: HP Desktop M01-F0xxx dmi.product.sku: 8KX18EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute third-party-packages ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926121 Title: After suspending, no video signal appears after waking up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1926121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)
this bug is still not solved in 20.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670041 Title: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877398] [NEW] virtual camera function does not work in version 8.6.1
Public bug reported: Greetings, This bug has already been reported to the creator of the software, the current version is 8.7.1 and the problem is supposed to be fixed in this version. Would it be possible to upgrade the webcamoid-package in ubuntu (focal) to said version? best regards, ** Affects: webcamoid (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/1877398 Title: virtual camera function does not work in version 8.6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webcamoid/+bug/1877398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
It would be good that somebody else adds the correct tags so this fix gets delivered to all distributions using the 5.x kernels. I am not sure if 4.x needs the fix at all, as according to the latest non-hwe kernel I used in bionic, the bad realtek IDs were not added to the unusual devices. But maybe that changed in the meantime. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
Hi, using the "-proposed" thingie in Bionic with the HWE kernel did not work even after the last query. So I did it the hard way (without any PPA used with APT/APT-GET). I downloaded the kernel manually and installed the following files: root@sirius:~/kernel-pkg# ls -l total 66160 -rw-r--r-- 1 root root 10758372 Oct 4 13:58 linux-headers-5.0.0-32_5.0.0-32.34_all.deb -rw-r--r-- 1 root root 1245844 Oct 4 13:58 linux-headers-5.0.0-32-generic_5.0.0-32.34_amd64.deb -rw-r--r-- 1 root root 8424200 Oct 4 16:18 linux-image-5.0.0-32-generic_5.0.0-32.34_amd64.deb -rw-r--r-- 1 root root 13831532 Oct 4 13:58 linux-modules-5.0.0-32-generic_5.0.0-32.34_amd64.deb -rw-r--r-- 1 root root 33478212 Oct 4 13:58 linux-modules-extra-5.0.0-32-generic_5.0.0-32.34_amd64.deb After removing the special module params and rebuilding initramfs, the kernel booted perfectly and ums-realtek worked. The module-info was correct: root@sirius:~# modinfo ums-realtek filename: /lib/modules/5.0.0-32-generic/kernel/drivers/usb/storage/ums-realtek.ko license:GPL author: wwang description:Driver for Realtek USB Card Reader srcversion: EA294247A6C868AE3685D12 alias: usb:v0BDAp0184d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v0BDAp0177d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v0BDAp0159d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v0BDAp0158d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v0BDAp0153d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v0BDAp0138d*dc*dsc*dp*ic*isc*ip*in* depends:usb-storage retpoline: Y intree: Y name: ums_realtek vermagic: 5.0.0-32-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: auto_delink_en:auto delink mode (0=firmware, 1=software [default]) (int) parm: enable_mmc:enable mmc support (int) parm: ss_en:enable selective suspend (int) parm: ss_delay:seconds to delay before entering selective suspend (int) So I can confirm the HWE kernel in 18.04 is fine, too. Nevertheless, I have no idea if or why the bionic default kernel was affected at all. I opened the issue only on the HWE kernel, so maybe the kernel bot should be improved to actually understand before sending stupid messages to me about stuff I can't check. I will add the disco verification. I will keep the bionic verification and set it back to the default, although I can't test it. I will remove the bionic-verification failed tag. Uwe ** Tags removed: verification-failed-bionic verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
For confirmation that my auto_delink_en setting was kept by the default after rebooting (so I made sure that initramfs was containing correct settings): root@sirius:~# cat /sys/module/ums_realtek/parameters/auto_delink_en 1 So it looks like the module boots correctly and having the default auto_delink_en setting, but for the specific device it's not using the setting. So fix confirmed! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
OK, so how comes that the bot sent me this message that I should test "-proposed"? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
Hi, I installed the latest -proposed kernel image in bionic (HWE variant), but the bug is not fixed there. It looks like it's not merged into the 5.0 kernel there. That's easy to see, because modinfo, still shows the old parameter description: root@sirius:~# modinfo ums-realtek filename: /lib/modules/5.0.0-31-generic/kernel/drivers/usb/storage/ums-realtek.ko license:GPL author: wwang description:Driver for Realtek USB Card Reader srcversion: 644B44C347E6C4FFEFDA3C7 alias: usb:v0BDAp0184d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v0BDAp0177d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v0BDAp0159d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v0BDAp0158d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v0BDAp0153d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v0BDAp0138d*dc*dsc*dp*ic*isc*ip*in* depends:usb-storage retpoline: Y intree: Y name: ums_realtek vermagic: 5.0.0-31-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: auto_delink_en:enable auto delink (int) parm: enable_mmc:enable mmc support (int) parm: ss_en:enable selective suspend (int) parm: ss_delay:seconds to delay before entering selective suspend (int) This is wrong: auto_delink_en:enable auto delink (int) According to the kernel patch (https://lkml.org/lkml/2019/9/4/1276) it should be: auto_delink_en:auto delink mode (0=firmware, 1=software [default]) (int) To fix the problem I still need the workaround by setting auto_delink_en to "0". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
This is the kernel that was installed from "-proposed": Linux sirius 5.0.0-31-generic #33~18.04.1-Ubuntu SMP Tue Oct 1 10:20:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ** Tags removed: verification-needed-bionic ** Tags added: verification-failed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
Thanks, looks fine, well understood. It would be good to keep me in CC once Realtek provides a new patch. I can help to test. Of course this issue is solved after the workaround with limiting auto-delink to the three "original IDs" only. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
Hi Kai-Heng, I installed your kernel, removed module parameters, recreated initramfs and rebooted with full shutdown/powerplugged. It looks like it's coming up without any warnings showing. It also detects no phantom cards. I was also able to insert a SD card and was able to mount it. So looks like it's working. What did you change exactly? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
Hi Kai-Heng, I was on vacation last week, will test this soon! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
Here is the full output attached. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+attachment/5282471/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
Hi, after enabling that option, there were not many additional lines in dmesg. Asking the debugfs was not possible due to kernel-lockdown. [3.632200] usb 1-5.1: New USB device found, idVendor=0bda, idProduct=0153, bcdDevice=57.13 [3.632203] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [3.632205] usb 1-5.1: Product: USB2.0-CRW [3.632207] usb 1-5.1: Manufacturer: Generic [3.632209] usb 1-5.1: SerialNumber: 2012092657120 [3.644643] usbcore: registered new interface driver usb-storage [3.647784] usbcore: registered new interface driver uas [3.650941] ums-realtek 1-5.1:1.0: Probe Realtek Card Reader! [3.650943] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [3.656160] scsi host2: usb-storage 1-5.1:1.0 [3.656374] usbcore: registered new interface driver ums-realtek [...] [4.667215] sd 2:0:0:0: Attached scsi generic sg1 type 0 [4.671782] sd 2:0:0:0: [sdb] Attached SCSI removable disk When inserting cards: [ 95.427175] sd 2:0:0:0: [sdb] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB) [ 95.437260] sdb: sdb1 [ 419.518691] sd 2:0:0:0: [sdb] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB) [ 419.529411] sdb: sdb1 [ 887.138965] sd 2:0:0:0: [sdb] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB) [ 887.150594] sdb: sdb1 [ 2140.600999] sd 2:0:0:0: [sdb] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB) [ 2140.611660] sdb: sdb1 [...] [54170.761092] sd 2:0:0:0: [sdb] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB) [54170.771448] sdb: sdb1 Interestingly, this time the device gave not up after half of a day. So maybe the timeouts yesterday was more a problem with the card, although it did respond after reboot again. So how should we proceed? It looks like the "auto_delink_en=0" helps for this device. I can keep this in my config file. Maybe it's a problem of my device only, but still there is the strange thing that it never caused any problems with the default driver. If it also affects other devices with the same vendor/device id, maybe the module should disable the auto_delink_en automatically. Maybe this can be added to the unusual device config. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
Should I maybe disable selective suspend and try again? root@sirius:~# cat /sys/module/ums_realtek/parameters/ss_en 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
Of course, I forgot to add: I did the test with current stable 5.0 kernel. If I should repeat all tests with latest (unsigned) kernel, please tell me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
Hi, I can confirm, if I add this parameter to /etc/modprobe.d/realtek.conf: options ums-realtek auto_delink_en=0 ...and rebuild the initramfs, after a full shutdown with power coord removed, it works correctly - but only initially!!! FYI, just rebooting is not enough and brings crazy error messages about device errors (I think the device state was not sane; you mentioned this before). After reboot, I see the /dev/sdb device with no partitions: root@sirius:~# dd if=/dev/sdb of=/dev/null dd: failed to open '/dev/sdb': No medium found After that, I did some tests and all worked fine: After inserting a SD card, it recognizes the partiontions and I was able to mount: [ 67.620372] sd 2:0:0:0: [sdb] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB) [ 67.630565] sdb: sdb1 root@sirius:~# mount /dev/sdb1 /mnt root@sirius:~# ls -l /mnt/ total 8 drwxr-xr-x 2 root root 8192 Aug 4 19:22 'System Volume Information' root@sirius:~# umount /mnt After removing the card, the partition /dev/sdb1 disappeared. Reinserting the card directly after removal worked fine: I was able to see the card and do the same tests again. But now the problem: I waited 15 minutes and tried again: After inserting the card, no kernel messages about detected partitions. If I do the "dd" on /dev/sdb it hangs completely. You cannot even kill the dd process from another terminal. Kernel messages: [ 1209.490442] INFO: task kworker/u8:4:305 blocked for more than 120 seconds. [ 1209.490454] Not tainted 5.0.0-23-generic #24~18.04.1-Ubuntu [ 1209.490459] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1209.490467] kworker/u8:4D0 305 2 0x8000 [ 1209.490502] Workqueue: scsi_tmf_2 scmd_eh_abort_handler [ 1209.490511] Call Trace: [ 1209.490543] __schedule+0x2bd/0x850 [ 1209.490561] schedule+0x2c/0x70 [ 1209.490572] schedule_timeout+0x1db/0x360 [ 1209.490584] ? __switch_to_asm+0x40/0x70 [ 1209.490593] ? __switch_to_asm+0x34/0x70 [ 1209.490602] ? __switch_to_asm+0x40/0x70 [ 1209.490611] ? __switch_to_asm+0x34/0x70 [ 1209.490620] ? __switch_to_asm+0x40/0x70 [ 1209.490629] ? __switch_to_asm+0x34/0x70 [ 1209.490638] ? __switch_to_asm+0x40/0x70 [ 1209.490647] ? __switch_to_asm+0x34/0x70 [ 1209.490658] wait_for_completion+0xba/0x140 [ 1209.490671] ? wake_up_q+0x80/0x80 [ 1209.490700] command_abort+0x60/0xa0 [usb_storage] [ 1209.490712] scmd_eh_abort_handler+0x5e/0x230 [ 1209.490726] process_one_work+0x1fd/0x400 [ 1209.490738] worker_thread+0x34/0x410 [ 1209.490753] kthread+0x121/0x140 [ 1209.490762] ? process_one_work+0x400/0x400 [ 1209.490773] ? kthread_park+0x90/0x90 [ 1209.490784] ret_from_fork+0x35/0x40 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
Hi, I was able to try the 5.3.0 kernel from the PPA as stated above. It was a bit complicated, as I had to disable secure boot first, so it was good that I did not try it from remote (my wife would have killed me!). In short: The problem persists. The ums-realtek driver does not work with this device ID. Same kernel messages, 3 retries to find the phantom device (sdb in my case) and always it gave up after timeout. After 3 tries the device is blocked completely. This happened also after completely switching of system and disconnecting from power coord. In short: The device ID added in the latest commit to ums-realtek does not work, so please revert it and also tell this upstream. @Kai-Heng: When you committed that to upstream kernel, did you test this on a real device? To me it's completely un-understandable why to forcefully switch a device which works perfectly well with the default USB storage driver to a custom vendor-specific driver without any reason! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
NSI: 4 > [ 331.953686] sd 2:0:0:0: Attached scsi generic sg1 type 0 > [ 331.960126] sd 2:0:0:0: [sdb] Attached SCSI removable disk > [ 488.343981] usb 1-5.1: USB disconnect, device number 9 > [ 488.354292] scsi 2:0:0:0: rejecting I/O to dead device >[ 488.356453] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: >hostbyte=DID_OK driverbyte=DRIVER_ERROR > [ 488.356458] scsi 2:0:0:0: [sdb] Sense not available. > > After time 488, any SD card inserted is no longer detected, because > driver gave up. > > Please revert adding the device with idVendor=0bda, idProduct=0153 to > ums-realtek and let it be handled by default driver and please also > report this bug upstream. > >After this change it's unfortunately no longet possible to force the >kernel to use the default driver, or is there a module option? > --- > ProblemType: Bug >AlsaVersion: Advanced Linux Sound Architecture Driver Version >k5.0.0-23-generic. >AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': >'aplay' > ApportVersion: 2.20.9-0ubuntu7.7 > Architecture: amd64 >ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': >'arecord' >AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', >'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', >'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', >'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', >'/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: >Card0.Amixer.info: Error: [Errno 2] No such file or directory: >'amixer': 'amixer' >Card0.Amixer.values: Error: [Errno 2] No such file or directory: >'amixer': 'amixer' > DistroRelease: Ubuntu 18.04 > InstallationDate: Installed on 2017-09-12 (690 days ago) >InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release >amd64 (20170801) > Lsusb: > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 006: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 >DVB-T > Bus 001 Device 005: ID 8087:0a2a Intel Corp. > Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: ZOTAC ZBOX-CI323NANO > Package: linux (not installed) > ProcEnviron: > TERM=cygwin > PATH=(custom, no user) > XDG_RUNTIME_DIR= > LANG=en_US.UTF-8 > SHELL=/bin/bash > ProcFB: 0 inteldrmfb >ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic >root=UUID=e5aafb31-5d5d-4f35-bd44-b3965316331a ro net.ifnames=0 > ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 > RelatedPackageVersions: > linux-restricted-modules-5.0.0-23-generic N/A > linux-backports-modules-5.0.0-23-generic N/A > linux-firmware1.173.9 > RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' > Tags: bionic > Uname: Linux 5.0.0-23-generic x86_64 > UpgradeStatus: Upgraded to bionic on 2018-08-15 (353 days ago) > UserGroups: > > _MarkForUpload: True > dmi.bios.date: 03/07/2017 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: B301P021 > dmi.board.asset.tag: N/A > dmi.board.name: ZBOX-CI323NANO > dmi.board.vendor: ZOTAC > dmi.board.version: XX > dmi.chassis.asset.tag: Default string > dmi.chassis.type: 2 > dmi.chassis.vendor: Default string > dmi.chassis.version: Default string >dmi.modalias: >dmi:bvnAmericanMegatrendsInc.:bvrB301P021:bd03/07/2017:svnZOTAC:pnZBOX-CI323NANO:pvrXX:rvnZOTAC:rnZBOX-CI323NANO:rvrXX:cvnDefaultstring:ct2:cvrDefaultstring: > dmi.product.family: N/A > dmi.product.name: ZBOX-CI323NANO > dmi.product.sku: N/A > dmi.product.version: XX > dmi.sys.vendor: ZOTAC > >To manage notifications about this bug go to: >https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- Uwe Schindler Achterdiek 19, 28357 Bremen https://www.thetaphi.de -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
As said before I have no physical access anymore. But yes, it was all tested. I am developer like you, so I know what I am doing. Uwe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
Ok, does this build contain any changes regarding to this? Since the commit on upstream mentioned above there were no changes in ums-realtek so I don't think this will help. IMHO, reverting the patch is the only right thing to do. The device id used for this device is much older than the other ones, so I don't think it can ever work with this driver. Let's just use the default driver. Works and is tested. I don't care about MMC. I am currently on travel this week, so I can only try when back at office. Installing such a kernel from remote on the router at home seems a bad idea. Uwe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
Some more info: I was not able to run the device with new kernel, not even with blacklisted ums-realtek. It looks like the native usb-storage driver ignores the device id. On 4.17 kernel I verified that the device loads perfectly with the default usb-storage driver uas. I have no idea why this was changed at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
Thanks. If you need any more information, I am happy to help. Is there any way to tell usb-storage to not use the realtek driver and instead the default one? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1838886/+attachment/5280766/+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/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1838886/+attachment/5280768/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1838886/+attachment/5280767/+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/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] Card0.Codecs.codec.2.txt
apport information ** Attachment added: "Card0.Codecs.codec.2.txt" https://bugs.launchpad.net/bugs/1838886/+attachment/5280758/+files/Card0.Codecs.codec.2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1838886/+attachment/5280757/+files/Card0.Codecs.codec.0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1838886/+attachment/5280764/+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/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1838886/+attachment/5280765/+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/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1838886/+attachment/5280763/+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/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1838886/+attachment/5280761/+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/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1838886/+attachment/5280759/+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/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1838886/+attachment/5280762/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1838886/+attachment/5280760/+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/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
apport information ** Tags added: apport-collected bionic ** Description changed: When installing the latest HWE stack (Linux 5.0) to Ubuntu 18.04, the Realtek cardreader in my ZOTAC ZBOX-CI323NANO stops working correctly. Previously it accepted SD cards all the time. Now it looks like you have to insert the card on booting or shortly after booting to access it. If you wait longer, it no longer detects the card. The reason for this can be found in the kernel log (dmes). On boot it seems to detect a card in the reader, although there is none. After a while it says "Read capacity failed" and "scsi 2:0:0:0: rejecting I/O to dead device" and then resets the device. It tries this 3 times and then gives up completely. After that any real device plugged is no longer detected. The device is: idVendor=0bda, idProduct=0153, bcdDevice=57.13 Support for this was added in mainline kernel: https://github.com/torvalds/linux/commit/1a6dd3fea131276a4fc44ae77b0f471b0b473577 And this seems to be backported to 5.0 kernel in Ubuntu 18.04 HWE stack. Full log on boot (no card inserted): [3.689559] usb 1-5.1: new high-speed USB device number 4 using xhci_hcd [3.898312] usb 1-5.1: New USB device found, idVendor=0bda, idProduct=0153, bcdDevice=57.13 [3.898316] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [3.898319] usb 1-5.1: Product: USB2.0-CRW [3.898322] usb 1-5.1: Manufacturer: Generic [3.898324] usb 1-5.1: SerialNumber: 2012092657120 [3.911571] usbcore: registered new interface driver usb-storage [3.914796] usbcore: registered new interface driver uas [3.917676] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [3.924478] scsi host2: usb-storage 1-5.1:1.0 [3.924649] usbcore: registered new interface driver ums-realtek [...] [ 13.477360] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [ 13.509592] scsi host2: usb-storage 1-5.1:1.0 [ 14.544213] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 PQ: 0 ANSI: 4 [ 14.545237] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 14.549430] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 170.961728] scsi 2:0:0:0: rejecting I/O to dead device [ 170.962069] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_ERROR [ 170.962073] scsi 2:0:0:0: [sdb] Sense not available. [ 171.985846] usb 1-5.1: new high-speed USB device number 8 using xhci_hcd [ 172.194299] usb 1-5.1: New USB device found, idVendor=0bda, idProduct=0153, bcdDevice=57.13 [ 172.194317] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 172.194327] usb 1-5.1: Product: USB2.0-CRW [ 172.194338] usb 1-5.1: Manufacturer: Generic [ 172.194346] usb 1-5.1: SerialNumber: 2012092657120 [ 172.200625] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [ 172.212503] scsi host2: usb-storage 1-5.1:1.0 [ 173.233036] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 PQ: 0 ANSI: 4 [ 173.233796] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 173.239620] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 329.654468] usb 1-5.1: USB disconnect, device number 8 [ 329.665905] scsi 2:0:0:0: rejecting I/O to dead device [ 329.665970] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_ERROR [ 329.665976] scsi 2:0:0:0: [sdb] Sense not available. [ 330.701685] usb 1-5.1: new high-speed USB device number 9 using xhci_hcd [ 330.910415] usb 1-5.1: New USB device found, idVendor=0bda, idProduct=0153, bcdDevice=57.13 [ 330.910433] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 330.910444] usb 1-5.1: Product: USB2.0-CRW [ 330.910455] usb 1-5.1: Manufacturer: Generic [ 330.910463] usb 1-5.1: SerialNumber: 2012092657120 [ 330.917013] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [ 330.932295] scsi host2: usb-storage 1-5.1:1.0 [ 331.952829] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 PQ: 0 ANSI: 4 [ 331.953686] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 331.960126] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 488.343981] usb 1-5.1: USB disconnect, device number 9 [ 488.354292] scsi 2:0:0:0: rejecting I/O to dead device [ 488.356453] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_ERROR [ 488.356458] scsi 2:0:0:0: [sdb] Sense not available. After time 488, any SD card inserted is no longer detected, because driver gave up. Please revert adding the device with idVendor=0bda, idProduct=0153 to ums-realtek and let it be handled by default driver and please also report this bug upstream. - After this change it's unfortunately no longet possible to force the - kernel to use the default driver, or is there a module option? + After this change
[Bug 1838886] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1838886/+attachment/5280756/+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/1838886 Title: New ID in ums-realtek module breaks cardreader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838886] [NEW] New ID in ums-realtek module breaks cardreader
Public bug reported: When installing the latest HWE stack (Linux 5.0) to Ubuntu 18.04, the Realtek cardreader in my ZOTAC ZBOX-CI323NANO stops working correctly. Previously it accepted SD cards all the time. Now it looks like you have to insert the card on booting or shortly after booting to access it. If you wait longer, it no longer detects the card. The reason for this can be found in the kernel log (dmes). On boot it seems to detect a card in the reader, although there is none. After a while it says "Read capacity failed" and "scsi 2:0:0:0: rejecting I/O to dead device" and then resets the device. It tries this 3 times and then gives up completely. After that any real device plugged is no longer detected. The device is: idVendor=0bda, idProduct=0153, bcdDevice=57.13 Support for this was added in mainline kernel: https://github.com/torvalds/linux/commit/1a6dd3fea131276a4fc44ae77b0f471b0b473577 And this seems to be backported to 5.0 kernel in Ubuntu 18.04 HWE stack. Full log on boot (no card inserted): [3.689559] usb 1-5.1: new high-speed USB device number 4 using xhci_hcd [3.898312] usb 1-5.1: New USB device found, idVendor=0bda, idProduct=0153, bcdDevice=57.13 [3.898316] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [3.898319] usb 1-5.1: Product: USB2.0-CRW [3.898322] usb 1-5.1: Manufacturer: Generic [3.898324] usb 1-5.1: SerialNumber: 2012092657120 [3.911571] usbcore: registered new interface driver usb-storage [3.914796] usbcore: registered new interface driver uas [3.917676] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [3.924478] scsi host2: usb-storage 1-5.1:1.0 [3.924649] usbcore: registered new interface driver ums-realtek [...] [ 13.477360] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [ 13.509592] scsi host2: usb-storage 1-5.1:1.0 [ 14.544213] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 PQ: 0 ANSI: 4 [ 14.545237] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 14.549430] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 170.961728] scsi 2:0:0:0: rejecting I/O to dead device [ 170.962069] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_ERROR [ 170.962073] scsi 2:0:0:0: [sdb] Sense not available. [ 171.985846] usb 1-5.1: new high-speed USB device number 8 using xhci_hcd [ 172.194299] usb 1-5.1: New USB device found, idVendor=0bda, idProduct=0153, bcdDevice=57.13 [ 172.194317] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 172.194327] usb 1-5.1: Product: USB2.0-CRW [ 172.194338] usb 1-5.1: Manufacturer: Generic [ 172.194346] usb 1-5.1: SerialNumber: 2012092657120 [ 172.200625] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [ 172.212503] scsi host2: usb-storage 1-5.1:1.0 [ 173.233036] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 PQ: 0 ANSI: 4 [ 173.233796] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 173.239620] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 329.654468] usb 1-5.1: USB disconnect, device number 8 [ 329.665905] scsi 2:0:0:0: rejecting I/O to dead device [ 329.665970] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_ERROR [ 329.665976] scsi 2:0:0:0: [sdb] Sense not available. [ 330.701685] usb 1-5.1: new high-speed USB device number 9 using xhci_hcd [ 330.910415] usb 1-5.1: New USB device found, idVendor=0bda, idProduct=0153, bcdDevice=57.13 [ 330.910433] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 330.910444] usb 1-5.1: Product: USB2.0-CRW [ 330.910455] usb 1-5.1: Manufacturer: Generic [ 330.910463] usb 1-5.1: SerialNumber: 2012092657120 [ 330.917013] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [ 330.932295] scsi host2: usb-storage 1-5.1:1.0 [ 331.952829] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 PQ: 0 ANSI: 4 [ 331.953686] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 331.960126] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 488.343981] usb 1-5.1: USB disconnect, device number 9 [ 488.354292] scsi 2:0:0:0: rejecting I/O to dead device [ 488.356453] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_ERROR [ 488.356458] scsi 2:0:0:0: [sdb] Sense not available. After time 488, any SD card inserted is no longer detected, because driver gave up. Please revert adding the device with idVendor=0bda, idProduct=0153 to ums-realtek and let it be handled by default driver and please also report this bug upstream. After this change it's unfortunately no longet possible to force the kernel to use the default driver, or is there a module option? ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New
[Bug 1768121] Re: Mainline Kernel since 4.16.4 has postinstall script error
same problem here with 16.4,5,6 16.3 installed fine -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768121 Title: Mainline Kernel since 4.16.4 has postinstall script error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755726] [NEW] package ca-certificates-java 20170930 failed to install/upgrade: Unterprozess installed ca-certificates-java package post-installation script gab den Fehler-Ausgangsstatus 127 zurü
Public bug reported: I tried to install java-jre 10 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates-java 20170930 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Wed Mar 14 09:57:28 2018 ErrorMessage: Unterprozess installed ca-certificates-java package post-installation script gab den Fehler-Ausgangsstatus 127 zurück InstallationDate: Installed on 2018-03-13 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~beta1 SourcePackage: ca-certificates-java Title: package ca-certificates-java 20170930 failed to install/upgrade: Unterprozess installed ca-certificates-java package post-installation script gab den Fehler-Ausgangsstatus 127 zurück UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ca-certificates-java (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755726 Title: package ca-certificates-java 20170930 failed to install/upgrade: Unterprozess installed ca-certificates-java package post-installation script gab den Fehler-Ausgangsstatus 127 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1755726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747262] Re: gnucash hangs while saving data
confirmed, same problem here -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747262 Title: gnucash hangs while saving data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1747262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261177] Re: initctl does not terminate at computer shutdown
got this problem with network manager on my 64 bit laptop since kernel 4.13.x does not appear on my 32 bit pc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261177 Title: initctl does not terminate at computer shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1261177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c
thx Manfred -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1264368 Title: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c To manage notifications about this bug go to: https://bugs.launchpad.net/androidsdk/+bug/1264368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c
old and still not fixed: (SWT:7981): GLib-CRITICAL **: Source ID 383 was not found when attempting to remove it Ubuntu 16.10 kernel 4.11.8-041108-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1264368 Title: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c To manage notifications about this bug go to: https://bugs.launchpad.net/androidsdk/+bug/1264368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575484] Re: "Set document metadata failed"
also in 16.10 i got this -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575484 Title: "Set document metadata failed" To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1575484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1693854] Re: linux-image-4.8.0-53-generic on 64bit Ubuntu installations causes problems with 32bit Java (e.g., ThreadLocal problems)
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1693854 Title: linux-image-4.8.0-53-generic on 64bit Ubuntu installations causes problems with 32bit Java (e.g., ThreadLocal problems) To manage notifications about this bug go to: https://bugs.launchpad.net/lucene/+bug/1693854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1693854] Re: linux-image-4.8.0-53-generic on 64bit Ubuntu installations causes problems with 32bit Java (e.g., ThreadLocal problems)
** Changed in: lucene Assignee: (unassigned) => Uwe Schindler (uwe-thetaphi) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1693854 Title: linux-image-4.8.0-53-generic on 64bit Ubuntu installations causes problems with 32bit Java (e.g., ThreadLocal problems) To manage notifications about this bug go to: https://bugs.launchpad.net/lucene/+bug/1693854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1693854] Re: linux-image-4.8.0-53-generic on 64bit Ubuntu installations causes problems with 32bit Java (e.g., ThreadLocal problems)
** Bug watch added: Email to dev@lucene # mailto:d...@lucene.apache.org ** Also affects: lucene via mailto:d...@lucene.apache.org Importance: Undecided Status: New ** Bug watch added: Email to rory.odonnell@oracle # mailto:rory.odonn...@oracle.com ** Also affects: openjdk via mailto:rory.odonn...@oracle.com Importance: Undecided Status: New ** Changed in: lucene Remote watch: Email to dev@lucene # => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1693854 Title: linux-image-4.8.0-53-generic on 64bit Ubuntu installations causes problems with 32bit Java (e.g., ThreadLocal problems) To manage notifications about this bug go to: https://bugs.launchpad.net/lucene/+bug/1693854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1693854] [NEW] linux-image-4.8.0-53-generic on 64bit Ubuntu installations causes problems with 32bit Java (e.g., ThreadLocal problems)
Public bug reported: I am running the famous Jenkins server that tests Oracle's Java releases with Apache Lucene. When migrating to new hardware and installing Ubuntu 16.04.2, the tests failed with strange errors: The system is Ubuntu 16.04.2 (64bits) with linux-image-4.8.0-53-generic. Java 7, Java 8 and Java 9 preview releases run without any problems if it is 64 bit versions (downloaded from Oracle's homepage). We don't run OpenJDK from Ubuntu package reporsitories, as we have many different combinations of JVMs running tests (also inside VirtualBox). If tests are using 32 bit JVM versions, the 32 bit compilation fails in most cases. For 32 bit support we use Multiarch i386 packages and installed libc6. This was same setup as Ubuntu 14.04 with Kernel 4.4. Sometimes the compilation with Apache Ant works, but then it fails horribly during running tests. The most often seen stack trace is: jenkins@serv1:~/tools/java/32bit/jdk1.8.0_131/bin$ ./java -version java version "1.8.0_131" Java(TM) SE Runtime Environment (build 1.8.0_131-b11) Java HotSpot(TM) Server VM (build 25.131-b11, mixed mode) > java.lang.NullPointerException > at > java.lang.ThreadLocal$ThreadLocalMap.getEntryAfterMiss(ThreadLocal.java:440) > at java.lang.ThreadLocal$ThreadLocalMap.getEntry(ThreadLocal.java:419) > at java.lang.ThreadLocal$ThreadLocalMap.access$000(ThreadLocal.java:298) > at java.lang.ThreadLocal.get(ThreadLocal.java:163) > at > org.apache.tools.ant.property.LocalProperties.current(LocalProperties.java:70) > at > org.apache.tools.ant.property.LocalProperties.enterScope(LocalProperties.java:89) jenkins@serv1:~/tools/java/32bit/jdk-9-ea+168/bin$ ./java -version java version "9-ea" Java(TM) SE Runtime Environment (build 9-ea+168) Java HotSpot(TM) Server VM (build 9-ea+168, mixed mode) > java.lang.NullPointerException > at > __randomizedtesting.SeedInfo.seed([716594A5FB7EBE0D:B81AAD979BE8FE98]:0) > at > java.base/java.lang.ThreadLocal$ThreadLocalMap.getEntryAfterMiss(ThreadLocal.java:442) > at > java.base/java.lang.ThreadLocal$ThreadLocalMap.getEntry(ThreadLocal.java:418) > at > java.base/java.lang.ThreadLocal$ThreadLocalMap.access$000(ThreadLocal.java:298) > at java.base/java.lang.ThreadLocal.get(ThreadLocal.java:163) > at > org.apache.lucene.util.CloseableThreadLocal.get(CloseableThreadLocal.java:78) > at > org.apache.lucene.index.SegmentReader.getFieldsReader(SegmentReader.java:234) I was not sure what exactly this is caused by and I found out: When updating to the recent linux-hwe-edge kernel (4.10.0-21-generic #23~16.04.1-Ubuntu) the problems are gone, it works as fine as in Ubuntu 14.04 with 4.4 kernel. So it is not an libc issue or any other hardware-related problem. I think it is caused by some wrongly backported patch. My first guess is some 32bit fix for pthreads, I just don't find the bug report anymore (launchpad search down). To reproduce this, use the following approach: - install Ubuntu 16.04.2 with HWE stack on 64 bit platform - install the i386 multiarch and a basic libc run run 32 bit Java: apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386 - download a 32 bit package of Java 8u131 and untar it - try to compile some larger Java program, e.g. Apache Lucene! The workaround is currently to go back to 4.4.0 kernel or install the edge HWE (kernel 4.10.0). ** Affects: linux-hwe (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/1693854 Title: linux-image-4.8.0-53-generic on 64bit Ubuntu installations causes problems with 32bit Java (e.g., ThreadLocal problems) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1693854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1693651] [NEW] package samba 2:4.4.5+dfsg-2ubuntu5.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Job for smbd.service failed because the control process exited with error code. See "systemctl status smbd.service" and "journalctl -xe" for details. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: samba 2:4.4.5+dfsg-2ubuntu5.6 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 BothFailedConnect: Yes Date: Fri May 26 06:31:42 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-04-17 (38 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) NmbdLog: RelatedPackageVersions: dpkg 1.18.10ubuntu1.1 apt 1.3.5 SambaServerRegression: Yes SmbConfIncluded: Yes SmbLog: SourcePackage: samba Title: package samba 2:4.4.5+dfsg-2ubuntu5.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1693651 Title: package samba 2:4.4.5+dfsg-2ubuntu5.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1693651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582209] Re: mysql_secure_installation does not update /etc/mysql/debian.cnf
See also http://askubuntu.com/questions/772785/16-04-mariadb-error-in-syslog-mysqlcheck or here for further details: http://ubuntuforums.org/showthread.php?t=2324472 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582209 Title: mysql_secure_installation does not update /etc/mysql/debian.cnf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.0/+bug/1582209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582209] [NEW] mysql_secure_installation does not update /etc/mysql/debian.cnf
Public bug reported: adminuser@fortuna:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 adminuser@fortuna:~$ apt-cache policy mariadb-server mariadb-server: Installiert: 10.0.24-7 Installationskandidat: 10.0.24-7 Versionstabelle: *** 10.0.24-7 500 500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu xenial/universe i386 Packages 100 /var/lib/dpkg/status I've found the following failure in my syslog after installing Ubuntu 16.04 and MariaDB from the Scratch using this really awesome tutorial https://www.howtoforge.com/tutorial/install-apache-with-php-and-mysql- on-ubuntu-16-04-lamp/ May 14 12:00:13 fortuna /etc/mysql/debian-start[1466]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored May 14 12:00:13 fortuna /etc/mysql/debian-start[1466]: Looking for 'mysql' as: /usr/bin/mysql May 14 12:00:13 fortuna /etc/mysql/debian-start[1466]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck May 14 12:00:13 fortuna /etc/mysql/debian-start[1466]: Version check failed. Got the following error when calling the 'mysql' command line client May 14 12:00:13 fortuna /etc/mysql/debian-start[1466]: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO) May 14 12:00:13 fortuna /etc/mysql/debian-start[1466]: FATAL ERROR: Upgrade failed May 14 12:00:13 fortuna /etc/mysql/debian-start[1487]: Checking for insecure root accounts. May 14 12:00:13 fortuna mysql[1020]: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO) I've already created a .my.cnf in the /root directory. If i run "mysql" as root i can login without a password. (See below) root@fortuna:~# mysql Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 7071 Server version: 10.0.24-MariaDB-7 Ubuntu 16.04 Copyright (c) 2000, 2016, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]> But if i try to use mysqlcheck check i get an error like this: root@fortuna:~# /usr/bin/mysqlcheck --defaults-file=/etc/mysql/debian.cnf --all-databases --fast --silent /usr/bin/mysqlcheck: Got error: 1045: Access denied for user 'root'@'localhost' (using password: NO) when trying to connect If i took a closer look then i found out that there is a file /etc/mysql/debian.cnf which should contain the passwords. But there is no password listed in there. On the other hand i should not type it in here because it say's DO NOT TOUCH! What shall I do? # Automatically generated for Debian scripts. DO NOT TOUCH! [client] host = localhost user = root password = socket = /var/run/mysqld/mysqld.sock [mysql_upgrade] host = localhost user = root password = socket = /var/run/mysqld/mysqld.sock basedir = /usr What you expected to happen: The password should be also entered in the /etc/mysql/debian.cnf file What happened instead: See above, there is an error while the startup process and the file does not contain the updated password. ** Affects: mariadb-10.0 (Ubuntu) Importance: Undecided Status: New ** Tags: 16.04 mariadb mariadb-server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582209 Title: mysql_secure_installation does not update /etc/mysql/debian.cnf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.0/+bug/1582209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1538445] Re: davfs2 often freezes any program that uses it
After some testing with own debug output, I found the cause for the hang and I added a support request for davfs2: https://savannah.nongnu.org/support/?109009 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1538445 Title: davfs2 often freezes any program that uses it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/davfs2/+bug/1538445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1538445] Re: davfs2 often freezes any program that uses it
I can confirm the same problems on Ubuntu Server 15.10 which comes with davfs2 1.5.2. A reboot is the only way to resolve that error. And sometimes even the reboot is not correctly finished and a reset of the machine is needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1538445 Title: davfs2 often freezes any program that uses it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/davfs2/+bug/1538445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516269] Re: ata NCQ error with md, drbd and high load
It is a headless server in a datacenter with remote access only. Is there another way to use apport-collect? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1516269 Title: ata NCQ error with md, drbd and high load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516269] Re: ata NCQ error with md, drbd and high load
The ReportingBugs documentation says I should send the apport file via ubuntu-bug -c -u But this gives me: Usage: ubuntu-bug [options] [symptom|pid|package|program path|.apport/.crash file] ubuntu-bug: error: -u/--update-bug option cannot be used together with options for a new report Shall I just add the .apport file here as attachment to this bug-report? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1516269 Title: ata NCQ error with md, drbd and high load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516269] Re: ata NCQ error with md, drbd and high load
When I use apport-cli -u 1516269 it returns: ERROR: You need to use apport-collect for updating an existing bug ** Attachment added: "linux.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516269/+attachment/4519669/+files/linux.apport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1516269 Title: ata NCQ error with md, drbd and high load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516269] Re: ata NCQ error with md, drbd and high load
Cannot run apport-collect (error on headless server). ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1516269 Title: ata NCQ error with md, drbd and high load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516269] [NEW] ata NCQ error with md, drbd and high load
Public bug reported:
With Ubuntu wily kernel 4.2.0-18-generic a SyncTarget to a DRBD on LVM
on MD Raid1 produces errors:
Nov 14 17:46:20 kobol kernel: [ 198.351892] ata1.00: exception Emask 0x60 SAct
0x38 SErr 0x800 action 0x6 frozen
Nov 14 17:46:20 kobol kernel: [ 198.351922] ata1.00: irq_stat 0x2000, host
bus error
Nov 14 17:46:20 kobol kernel: [ 198.351935] ata1: SError: { HostInt }
Nov 14 17:46:20 kobol kernel: [ 198.351944] ata1.00: failed command: WRITE
FPDMA QUEUED
Nov 14 17:46:20 kobol kernel: [ 198.351957] ata1.00: cmd
61/48:18:00:d8:95/05:00:07:00:00/40 tag 3 ncq 692224 out
Nov 14 17:46:20 kobol kernel: [ 198.351957] res
40/00:20:40:e1:95/00:00:07:00:00/40 Emask 0x60 (host bus error)
Nov 14 17:46:20 kobol kernel: [ 198.351988] ata1.00: status: { DRDY }
Nov 14 17:46:20 kobol kernel: [ 198.351997] ata1.00: failed command: WRITE
FPDMA QUEUED
Nov 14 17:46:20 kobol kernel: [ 198.352009] ata1.00: cmd
61/40:20:40:e1:95/00:00:07:00:00/40 tag 4 ncq 32768 out
Nov 14 17:46:20 kobol kernel: [ 198.352009] res
40/00:20:40:e1:95/00:00:07:00:00/40 Emask 0x60 (host bus error)
Nov 14 17:46:20 kobol kernel: [ 198.352039] ata1.00: status: { DRDY }
Nov 14 17:46:20 kobol kernel: [ 198.352047] ata1.00: failed command: WRITE
FPDMA QUEUED
Nov 14 17:46:20 kobol kernel: [ 198.352059] ata1.00: cmd
61/80:28:80:e1:95/00:00:07:00:00/40 tag 5 ncq 65536 out
Nov 14 17:46:20 kobol kernel: [ 198.352059] res
40/00:20:40:e1:95/00:00:07:00:00/40 Emask 0x60 (host bus error)
Nov 14 17:46:20 kobol kernel: [ 198.352090] ata1.00: status: { DRDY }
Nov 14 17:46:20 kobol kernel: [ 198.352099] ata1: hard resetting link
Nov 14 17:46:20 kobol kernel: [ 198.352106] ata2.00: exception Emask 0x60 SAct
0x7 SErr 0x800 action 0x6 frozen
Nov 14 17:46:20 kobol kernel: [ 198.352133] ata2.00: irq_stat 0x2000, host
bus error
Nov 14 17:46:20 kobol kernel: [ 198.352145] ata2: SError: { HostInt }
Nov 14 17:46:20 kobol kernel: [ 198.352154] ata2.00: failed command: WRITE
FPDMA QUEUED
Nov 14 17:46:20 kobol kernel: [ 198.352166] ata2.00: cmd
61/48:80:00:d8:95/05:00:07:00:00/40 tag 16 ncq 692224 out
Nov 14 17:46:20 kobol kernel: [ 198.352166] res
40/00:88:40:e1:95/00:00:07:00:00/40 Emask 0x60 (host bus error)
Nov 14 17:46:20 kobol kernel: [ 198.352196] ata2.00: status: { DRDY }
Nov 14 17:46:20 kobol kernel: [ 198.352204] ata2.00: failed command: WRITE
FPDMA QUEUED
Nov 14 17:46:20 kobol kernel: [ 198.352217] ata2.00: cmd
61/40:88:40:e1:95/00:00:07:00:00/40 tag 17 ncq 32768 out
Nov 14 17:46:20 kobol kernel: [ 198.352217] res
40/00:88:40:e1:95/00:00:07:00:00/40 Emask 0x60 (host bus error)
Nov 14 17:46:20 kobol kernel: [ 198.352246] ata2.00: status: { DRDY }
Nov 14 17:46:20 kobol kernel: [ 198.352254] ata2.00: failed command: WRITE
FPDMA QUEUED
Nov 14 17:46:20 kobol kernel: [ 198.352266] ata2.00: cmd
61/80:90:80:e1:95/00:00:07:00:00/40 tag 18 ncq 65536 out
Nov 14 17:46:20 kobol kernel: [ 198.352266] res
40/00:88:40:e1:95/00:00:07:00:00/40 Emask 0x60 (host bus error)
Nov 14 17:46:20 kobol kernel: [ 198.352295] ata2.00: status: { DRDY }
Nov 14 17:46:20 kobol kernel: [ 198.352304] ata2: hard resetting link
Nov 14 17:46:21 kobol kernel: [ 198.671678] ata2: SATA link up 6.0 Gbps
(SStatus 133 SControl 300)
Nov 14 17:46:21 kobol kernel: [ 198.673618] ata2.00: configured for UDMA/133
Nov 14 17:46:21 kobol kernel: [ 198.673628] ata2: EH complete
Nov 14 17:46:21 kobol kernel: [ 198.727651] ata1: SATA link up 6.0 Gbps
(SStatus 133 SControl 300)
Nov 14 17:46:21 kobol kernel: [ 198.735336] ata1.00: configured for UDMA/133
Nov 14 17:46:21 kobol kernel: [ 198.735343] ata1: EH complete
The error didn't show up before the update from kernel 4.2.0-16-generic.
Disabling NCQ with
echo 1 > /sys/block/sda/device/queue_depth
is a workaround.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516269
Title:
ata NCQ error with md, drbd and high load
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516269/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516269] Re: ata NCQ error with md, drbd and high load
After checking with kernel 4.2.0-16-generic again, I got the error too. I have another server (same hardware) still running with 4.2.0-16-generic (not updated yet) and the error doesn't show up, so I thought the update of the kernel brought the problem. The servers hardware was completely exchanged, but problem stays. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1516269 Title: ata NCQ error with md, drbd and high load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480440] Re: libvirt does not wait for guests to shut down
Actually it is a very acceptable workaround. I switched to upstart and it works fine. Boot and shutdown is even faster (which I don't really need in a server environment). The upstart way seems to be more stable and reliable than systemd. My two cents from a server administrator point of view: Avoid this complex systemd thing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480440 Title: libvirt does not wait for guests to shut down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1480440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480440] Re: libvirt does not wait for guests to shut down
I have the same problem with Vivid. Will there be a fix / backport available? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480440 Title: libvirt does not wait for guests to shut down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1480440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1388786] Re: TCP stale transfer with erroneous SACK information
This link may also be related, it tells about same problems, but without CISCO hardware: https://askubuntu.com/questions/475700/application- stuck-in-tcp-retransmit/563984 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1388786 Title: TCP stale transfer with erroneous SACK information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1388786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1388786] Re: TCP stale transfer with erroneous SACK information
I can confirm this bug with the 3.13 kernel shipped with Ubuntu 14.04. The 3.2 kernel shipped with Ubuntu 12.04 did not have the problem, all download were succeeding. The problem started after upgrade to 14.04. The problem also solved after downgrading the kernel to 3.2 by downloading the latest 12.04 (Linux 3.2) one from the PPA. Disabling TCP SACK also resolved the issue. I also tried newer PPA kernels, at least the next one for release with next Ubuntu Update (3.14) does not solve the problem yet. In our case the problems happens mostly with far-away or slower DSL connections, trying to download large files from our webserver. The download starts fine, but suddenly slows down to 0 bytes/sec. It then sometimes recovers, but fails again after a short while. The tcpdump showed, that the client is sending SACKs over and over, but the Ubuntu kernel does not understand them. In our case we also have Cisco hardware inbetween. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1388786 Title: TCP stale transfer with erroneous SACK information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1388786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported
same here: new gs70 with killer n1525 with ubuntu 14.10 and no wifi... is there a work around with compiling/installing something by hand? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309535] Re: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so
i've seen this error also, but because i was not able to login with lightdm anymore. i have an encrypted home and changed my password in the shel. so it seems like having different passwords for the system and the encryptedfs does not work. after changing back my system password i was able to log in again -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309535 Title: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1309535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1101883] Re: 14e4:16bc Sandisk Extreme 32GB Class 10 45MB/s not readable in Acer Aspire V3-571G-9686
I'm using Ubuntu 13.04 (64bit) on a MacBook Pro 13 (mid 2012) with the same adapter (bcm57765 for ethernet and card reader). This bug affects me, too. Same error messages in syslog, currently using kernel 3.8.0-21-generic. I've tried different sd card sizes and different classes. Size doesn't matter (what a joke), but my SanDisk Extreme Class 10 8GB is not recongized correctly. Another Transcend standard Class 10 32GB works fine. There is another bug report at https://bugs.launchpad.net/linaro- landing-team-freescale/+bug/910835 with a kernel patch, but I don't know how to use and test it. Regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1101883 Title: 14e4:16bc Sandisk Extreme 32GB Class 10 45MB/s not readable in Acer Aspire V3-571G-9686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1101883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
Well, I sent the laptop into suspend mode last evening and since today in the morning acpi is not working correctly anymore. So, overnight suspension could be the problem. Maybe minimalistic year 2000 problem ;) Is anybody from Canonical already involved in finding a solution? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
I just used the reset button on the laptop bottom and I can also confirm that it helps bringing back correct acpi function. Now plugging and unplugging the power supply is logged live. It's only some minutes ago, so I will place another comment when acpi falls back in malfunction again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
In addition to the previous post: closing the lid is also recongized correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
I can confirm you that if you push the reset button on bottom of the laptop with a needle (laptop unpowered, than use the power cord to start it otherwhise will not start) the next boot all the ACPI events are logged perfectly; all is run wanderfully untill some events that screw up again the ACPI/BIOS stuff. Is the installed OS affected by this workaround or only BIOS configuration? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
Regarding post #27: Marcello, how did you apply your patch to upowerd? Maybe it can help other users, too. Thanks in advance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
@Jon: Try this: http://www.samsung.com/uk/support/model/NP530U3C-A01UK- downloads?downloadName=UM -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971061] Re: acpi reports battery state incorrectly
I can confirm the same issue on my Samsung NP530U3C-A01DE with Ubuntu 12.04 x64 running Unity. It also appears using Xubuntu. BIOS update didn't change anything. It is annoying because a few days ago it already worked perfectly :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/971061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986149] Re: crash while booting MacBook Pro 6,2 from USB
I tried booting the image quantal-desktop-amd64+mac.iso (alpha 3) from USB on my MacBook Pro 6,2 but it did not work. The pendrive created with Startup Disk Creator was not recognized as bootable device by my MacBook. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986149 Title: crash while booting MacBook Pro 6,2 from USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/986149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986149] Re: crash while booting MacBook Pro 6,2 from USB
The following image is working: quantal-desktop-amd64.iso (alpha 3) Thank you so much to whoever fixed it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986149 Title: crash while booting MacBook Pro 6,2 from USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/986149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 856711] Re: 11.10 - Suspend fails on Asus 1215B
@sami Don't bother. I dont have a crypto disk set up and unfortunateliy I'm experiencing the exact same problems. Tried with /etc/pm/config.d/suspend_modules and /etc/pm/config.d/modules It crashed pretty hard each time I tried to wake it up. Worse than before. So there IS a change. But not the way I'd hoped. Hoping for a solution. Cheers, Stefan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/856711 Title: 11.10 - Suspend fails on Asus 1215B To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/856711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986149] [NEW] crash while booting MacBook Pro 6,2 from USB
Public bug reported: reproduce: 1. Create bootable USB flash drive with Startup Disk Creator from image ubuntu-12.04-beta2-desktop-amd64.iso 2. Boot MacBook Pro 6,2 from USB flash drive (hold Option while truning on, wait 30 seconds, select drive) 3. Select Try Ubuntu without Installing 4. Hit Enter: after a few seconds a distorted screen appears, some pixels are changing rhytmically beween red and green, then nothing happens anymore remark: I tried both a SanDisk Cruzer 2GB and Hama 8GB: same behavior ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986149 Title: crash while booting MacBook Pro 6,2 from USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/986149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986149] Re: crash while booting MacBook Pro 6,2 from USB
** Package changed: ubuntu = plymouth (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986149 Title: crash while booting MacBook Pro 6,2 from USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/986149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986149] Re: crash while booting MacBook Pro 6,2 from USB
It read GNU GRUB version 1.99-18ubuntu1. Today the crash slightly changed its timing: Instead of seeing a distorted screen I could see the Ubuntu logo with five dots below it. After a few seconds they stayed red. I waited some minutes but nothing happened. Still using the same image as yesterday (ubuntu-12.04-beta2-desktop-amd64.iso on SanDisk Cruzer 2GB). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986149 Title: crash while booting MacBook Pro 6,2 from USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/986149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 823765] [NEW] package nvidia-current 270.41.06-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build
Public bug reported: After installing Kernel 3.0.1 NVIDIA driver fails to build ProblemType: Package DistroRelease: Ubuntu 11.04 Package: nvidia-current 270.41.06-0ubuntu1 Uname: Linux 3.0.1-030001-generic x86_64 Architecture: amd64 Date: Wed Aug 10 09:29:45 2011 DistUpgraded: Fresh install DistroCodename: natty DistroVariant: ubuntu ErrorMessage: nvidia-current kernel module failed to build InstallationMedia: Xubuntu 11.04 Natty Narwhal - Release amd64 (20110427) PackageVersion: 270.41.06-0ubuntu1 SourcePackage: nvidia-graphics-drivers Title: package nvidia-current 270.41.06-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) version.compiz: compiz N/A version.ia32-libs: ia32-libs 20090808ubuntu13 version.libdrm2: libdrm2 2.4.23-1ubuntu6 version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2 version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7 ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package natty needs-reassignment regression-update ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/823765 Title: package nvidia-current 270.41.06-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/823765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 823765] Re: package nvidia-current 270.41.06-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/823765 Title: package nvidia-current 270.41.06-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/823765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 758581] [NEW] Scrollbar does not work with vinagre
Public bug reported: Binary package hint: overlay-scrollbar When connected to a vnc server, the scrollbar has a gray color and when the mouse moves over the scrollbars, they don't change to active color and are not useable. The handle also does not appear. So no scrollbars for vinagre. :( ** Affects: overlay-scrollbar (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/758581 Title: Scrollbar does not work with vinagre -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 758581] Re: Scrollbar does not work with vinagre
Added a image showing the problem ** Attachment added: Image showing the problem https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/758581/+attachment/2023302/+files/img.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/758581 Title: Scrollbar does not work with vinagre -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 728719] Re: Systray icons showing on top of everything
The bug is still present in unity 3.8.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/728719 Title: Systray icons showing on top of everything -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 758581] Re: Scrollbar does not work with vinagre
yes, i am absolutly sure, that they don't appear. The scrollbars don't move, they have no function. This only happens in vinagre when it is connected via vnc to another pc and scrollbars are displayed. It didn't happen in any other apps. It has nothing to do with fullscreen apps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/758581 Title: Scrollbar does not work with vinagre -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 758581] Re: Scrollbar does not work with vinagre
** Attachment added: video showing the problem https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/758581/+attachment/2023958/+files/vinagre_scrollbars.ogv -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/758581 Title: Scrollbar does not work with vinagre -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 640100] Re: Maverick fails to wake up on Samsung N150
Hi Step by step editing: 1.) Edit the grub config file #sudo nano /etc/default/grub 2.) Append intel_idle.max_cstate=0 to the line: GRUB_CMDLINE_LINUX_DEFAULT=quiet splash - GRUB_CMDLINE_LINUX_DEFAULT=quiet splash intel_idle.max_cstate=0 3.) Save grub config file Press Ctrl + X 4.) run update-grub #sudo update-grub 5.) Reboot #sudo reboot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/640100 Title: Maverick fails to wake up on Samsung N150 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 640100] Re: Maverick fails to wake up on Samsung N150
btw, it works also (at least for me) with just adding nolapic_timer to grub boot paramters instead of intel_idle.max_cstate=0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/640100 Title: Maverick fails to wake up on Samsung N150 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 640100] Re: Maverick fails to wake up on Samsung N150
I had the same problem with the NC10 Plus, appening intel_idle.max_cstate=0 to grub fixes the wakeup thing for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/640100 Title: Maverick fails to wake up on Samsung N150 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
