[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Well, if you're a LVM user i recommend to leave ubuntu/debian. I know this sounds somewhat hard, but this nasty bug inside the ramdisk mouning script exist now more or less since a year! I can't accept a 30 seconds delay on boot for nothing and moved on to other distros. Yes you can fix it inside the script which will be copied, but with a new package the file will be overwritten without any warning or save/new file. Time to untrack this bug now. Good luck! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802050] [NEW] Kernel module crash 4.18.0-10 after upgrade from 18.04 to 18.10
Public bug reported: [ 56.996976] [ cut here ] [ 56.996978] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)! [ 56.996985] WARNING: CPU: 3 PID: 2547 at mm/usercopy.c:81 usercopy_warn+0x81/0xa0 [ 56.996985] Modules linked in: ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter devlink bpfilter pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) nvidia_uvm(POE) eeepc_wmi asus_wmi snd_hda_codec_hdmi mxm_wmi wmi_bmof sparse_keymap nvidia_drm(POE) nvidia_modeset(POE) snd_hda_codec_realtek intel_rapl nvidia(POE) snd_hda_codec_generic x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_intel kvm_intel kvm snd_hda_codec joydev snd_hda_core snd_usb_audio snd_usbmidi_lib irqbypass snd_hwdep input_leds crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_pcm pcbc aesni_intel snd_seq_midi snd_seq_midi_event aes_x86_64 snd_rawmidi crypto_simd cryptd snd_seq glue_helper drm_kms_helper intel_cstate drm ipmi_devintf ipmi_msghandler intel_rapl_perf snd_seq_device snd_timer fb_sys_fops [ 56.997003] syscopyarea sysfillrect sysimgblt snd mac_hid soundcore wmi video mei_me mei acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 raid10 multipath linear raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 libcrc32c raid1 hid_generic usbhid hid gpio_ich r8169 i2c_i801 mii lpc_ich ahci libahci [ 56.997016] CPU: 3 PID: 2547 Comm: Xorg Tainted: P OE 4.18.0-10-generic #11-Ubuntu [ 56.997017] Hardware name: ASUS All Series/Z97-K, BIOS 2902 03/31/2016 [ 56.997018] RIP: 0010:usercopy_warn+0x81/0xa0 [ 56.997018] Code: b0 aa 41 51 4d 89 d8 48 c7 c0 89 8d af aa 49 89 f1 48 89 f9 48 0f 45 c2 48 c7 c7 f0 a1 b0 aa 4c 89 d2 48 89 c6 e8 f1 cf df ff <0f> 0b 48 83 c4 18 c9 c3 48 c7 c6 b2 8a b2 aa 49 89 f1 49 89 f3 eb [ 56.997030] RSP: 0018:b9550248bb08 EFLAGS: 00010286 [ 56.997031] RAX: RBX: 90fdc8535cb0 RCX: 0006 [ 56.997032] RDX: 0007 RSI: 0096 RDI: 90fdded964b0 [ 56.997032] RBP: b9550248bb20 R08: 0001 R09: 038f [ 56.997032] R10: 0004 R11: R12: 0003 [ 56.997033] R13: 0001 R14: 90fdc8535cb3 R15: 90fdc8535cf8 [ 56.997033] FS: 7f854792ba80() GS:90fdded8() knlGS: [ 56.997034] CS: 0010 DS: ES: CR0: 80050033 [ 56.997034] CR2: 7f8543fd2110 CR3: 000406668006 CR4: 001606e0 [ 56.997035] Call Trace: [ 56.997038] __check_heap_object+0xc2/0x110 [ 56.997039] __check_object_size+0x14c/0x178 [ 56.997148] os_memcpy_to_user+0x26/0x50 [nvidia] [ 56.997254] _nv009384rm+0xbf/0xe0 [nvidia] [ 56.997255] WARNING: kernel stack frame pointer at 8fe294b8 in Xorg:2547 has bad value 5fea09aa [ 56.997256] unwind stack type:0 next_sp: (null) mask:0x2 graph_idx:0 [ 56.997257] 1bbff756: b9550248bb30 (0xb9550248bb30) [ 56.997258] 21ffd201: a9c69a82 (__check_heap_object+0xc2/0x110) [ 56.997258] 2ec89026: b9550248bb60 (0xb9550248bb60) [ 56.997259] 297b0120: a9c91abc (__check_object_size+0x14c/0x178) [ 56.997259] 8569feab: 0003 (0x3) [ 56.997260] b2feea66: 90fdc8535cb0 (0x90fdc8535cb0) [ 56.997260] a5345c20: 55924226a63e (0x55924226a63e) [ 56.997260] 798de38a: ... [ 56.997261] 871cf253: b9550248bb88 (0xb9550248bb88) [ 56.997311] 5645fcd2: c0b305b6 (os_memcpy_to_user+0x26/0x50 [nvidia]) [ 56.997311] 929e7969: 0003 (0x3) [ 56.997312] cbb9721c: 55924226a63e (0x55924226a63e) [ 56.997312] cf624d15: 90fdc8535cb0 (0x90fdc8535cb0) [ 56.997312] 8fe294b8: 90fdc8535ca8 (0x90fdc8535ca8) [ 56.997417] 7dbcdd8d: c110087f (_nv009384rm+0xbf/0xe0 [nvidia]) [ 56.997418] c0dd2ba2: 90fdc8535c88 (0x90fdc8535c88) [ 56.997418] a931d446: ... [ 56.997418] 28151017: 90fda8ed62e8 (0x90fda8ed62e8) [ 56.997419] f1c853ed: 90fdc8535db8 (0x90fdc8535db8) [ 56.997419] 761fa9f3: 7ffe66b4aa10 (0x7ffe66b4aa10) [ 56.997505] 9e2ac77b: c0cfa259 (_nv028097rm+0x79/0x90 [nvidia]) [ 56.997505] cc78d7b8: 0001 (0x1) [ 56.997590] 859e80f8: c0cfa235 (_nv028097rm+0x55/0x90 [nvidia]) [ 56.997591] a092cc62: ... [ 56.997591] 0a1cc0bb: 90fdc8535db8 (0x90fdc8535db8) [ 56.997591] 5dd40a26: 90fdc416e008 (0x90fdc416e008) [ 56.997671] cb4ddc09: c0cb9a6e (_nv013699rm+0xee/0x100 [nvidia]) [
[Bug 1802050] Re: Kernel module crash 4.18.0-10 after upgrade from 18.04 to 18.10
Kernel module crash after dist-upgrade from 18.04 to 18.10. This happens after every boot. I rebuild dkms modules twice. Everything else runs smoothly :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802050 Title: Kernel module crash 4.18.0-10 after upgrade from 18.04 to 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1802050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752251] Re: Missing mcelog userspace package in bionic - or maybe linux kernel config should disable mcelog_legacy
I have a real mce hardware problem and can't view it without such tools! Is there an alternate to mcelog ? Here are my paints (just to show users need tools: root@Homer-Mobil:/var/log# cp kern.log.* /tmp root@Homer-Mobil:/var/log# cd /tmp root@Homer-Mobil:/tmp# ls -l insgesamt 1400 -rw--- 1 daniel daniel 0 Jul 18 11:53 config-err-427YPT -rw--- 1 daniel daniel579 Jul 18 11:53 dropbox-antifreeze-FaG7tD -rw-r- 1 root root 819353 Jul 18 12:08 kern.log.1 -rw-r- 1 root root71976 Jul 18 12:08 kern.log.2.gz -rw-r- 1 root root 290598 Jul 18 12:08 kern.log.3.gz -rw-r- 1 root root 218573 Jul 18 12:08 kern.log.4.gz drwx-- 2 daniel daniel 4096 Jul 18 11:53 ssh-MVmb1aXusomC drwx-- 3 root root 4096 Jul 18 11:53 systemd-private-a3571b085332405690c697a16b97a0f2-colord.service-ko1OdP drwx-- 3 root root 4096 Jul 18 11:53 systemd-private-a3571b085332405690c697a16b97a0f2-rtkit-daemon.service-KZ8HzU drwx-- 3 root root 4096 Jul 18 11:52 systemd-private-a3571b085332405690c697a16b97a0f2-systemd-resolved.service-mlRf3S drwx-- 3 root root 4096 Jul 18 11:52 systemd-private-a3571b085332405690c697a16b97a0f2-systemd-timesyncd.service-KQWbRG root@Homer-Mobil:/tmp# gunzip *.gz root@Homer-Mobil:/tmp# grep -i "machine check" kern.log.* kern.log.1:Jul 12 17:06:44 Homer-Mobil kernel: [0.028169] mce: [Hardware Error]: Machine check events logged kern.log.1:Jul 12 17:06:44 Homer-Mobil kernel: [0.028174] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ae23110a kern.log.3:Jun 26 13:54:36 Homer-Mobil kernel: [0.028167] mce: [Hardware Error]: Machine check events logged kern.log.3:Jun 26 13:54:36 Homer-Mobil kernel: [0.028171] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ae23110a kern.log.3:Jun 27 14:11:31 Homer-Mobil kernel: [0.028168] mce: [Hardware Error]: Machine check events logged kern.log.3:Jun 27 14:11:31 Homer-Mobil kernel: [0.028173] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ae23110a kern.log.3:Jun 28 18:09:32 Homer-Mobil kernel: [0.028166] mce: [Hardware Error]: Machine check events logged kern.log.3:Jun 28 18:09:32 Homer-Mobil kernel: [0.028171] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ae23110a kern.log.3:Jun 29 13:38:20 Homer-Mobil kernel: [0.032167] mce: [Hardware Error]: Machine check events logged kern.log.3:Jun 29 13:38:20 Homer-Mobil kernel: [0.032172] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ae23110a kern.log.4:Jun 19 08:48:10 Homer-Mobil kernel: [0.028167] mce: [Hardware Error]: Machine check events logged kern.log.4:Jun 19 08:48:10 Homer-Mobil kernel: [0.028172] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ae23110a kern.log.4:Jun 19 09:09:22 Homer-Mobil kernel: [0.032167] mce: [Hardware Error]: Machine check events logged kern.log.4:Jun 19 09:09:22 Homer-Mobil kernel: [0.032172] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ae23110a kern.log.4:Jun 22 11:30:49 Homer-Mobil kernel: [0.032171] mce: [Hardware Error]: Machine check events logged kern.log.4:Jun 22 11:30:49 Homer-Mobil kernel: [0.032176] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ae23110a root@Homer-Mobil:/tmp# mcelog mcelog: Befehl nicht gefunden. root@Homer-Mobil:/tmp# sudo apt-get install mcelog Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig E: Paket mcelog kann nicht gefunden werden. root@Homer-Mobil:/tmp# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752251 Title: Missing mcelog userspace package in bionic - or maybe linux kernel config should disable mcelog_legacy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
@Steve I'm using another LVM setup, which i created manual while using Ubunuts live system ;-) I wrote this in my first comment already. But basicly i was the same problem with the "30 seconds" problem and my system falls back twice to scanning devices :-(. But to be honest, yes, i don't in this case and you can ignore me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Thanks! Now tested with versuion 3.2 and the bug is still there. :-( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Ooops, i was testing with version 3.1! Where can i get version 3.2? It's still not in the update channel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I can confirm that the bug is still there with version 3.2! :-( I did "update-initramfs -u". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Fresh install on my Laptop 18.04 and using lvm with ext4 filesystem. Boot is slowdown about 30 seconds while display the error message in bug desscription. I'm using a manual created lvm setup druing installation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452943] Re: Scroll Position Jumps To Marked Item
I can confirm this bug with thunar 1.6.6 xfce-412 ppa (Xubuntu 14.04.2) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452943 Title: Scroll Position Jumps To Marked Item To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1452943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440651] [NEW] Dfc display error with LVM
Public bug reported: It shows +dev/mapper/system-backup instead of /dev/... I'm using LVM setup: Trigger für man-db (2.6.7.1-1ubuntu1) werden verarbeitet ... dfc (2.5.0-1) wird eingerichtet ... daniel@Homer:/var/log$ dfc FILESYSTEM (=) USED FREE (-) %USED AVAILABLE TOTAL MOUNTED ON /dev/mapper/system-root [=---] 23% 3.0G 3.8G / none []0% 4.0K 4.0K /sys/fs/cgroup udev [=---]0% 3.9G 3.9G /dev tmpfs[=---]0%797.0M798.5M /run none []0% 5.0M 5.0M /run/lock none [=---]0% 3.9G 3.9G /run/shm none [=---]0%100.0M100.0M /run/user /dev/sdb1[=---] 24%371.5M487.9M /boot /dev/mapper/system-usr [===-] 52% 7.5G 15.6G /usr +ev/mapper/system-backup [==--] 66%128.8G377.8G /backup /dev/mapper/system-var [===-] 14% 13.4G 15.6G /var /dev/mapper/system-tmp [==--]6% 3.6G 3.8G /tmp /dev/mapper/system-opt [=---] 22% 3.0G 3.8G /opt /dev/mapper/system-home [=---] 83% 42.8G251.9G /home /dev/mapper/system-vm[==--] 87% 34.3G255.9G /var/local/vm daniel@Homer:/var/log$ which dfc /usr/bin/dfc daniel@Homer:/var/log$ file /usr/bin/dfc /usr/bin/dfc: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=caee3df73cd0e02cf3c3166a822f9b362dc893ef, stripped daniel@Homer:/var/log$ which dfc /usr/bin/dfc daniel@Homer:/var/log$ dfc FILESYSTEM (=) USED FREE (-) %USED AVAILABLE TOTAL MOUNTED ON /dev/mapper/system-root [=---] 23% 3.0G 3.8G / none []0% 4.0K 4.0K /sys/fs/cgroup udev [=---]0% 3.9G 3.9G /dev tmpfs[=---]0%797.0M798.5M /run none []0% 5.0M 5.0M /run/lock none [=---]0% 3.9G 3.9G /run/shm none [=---]0%100.0M100.0M /run/user /dev/sdb1[=---] 24%371.5M487.9M /boot /dev/mapper/system-usr [===-] 52% 7.5G 15.6G /usr +ev/mapper/system-backup [==--] 66%128.8G377.8G /backup /dev/mapper/system-var [===-] 14% 13.4G 15.6G /var /dev/mapper/system-tmp [==--]6% 3.6G 3.8G /tmp /dev/mapper/system-opt [=---] 22% 3.0G 3.8G /opt /dev/mapper/system-home [=---] 83% 42.8G251.9G /home /dev/mapper/system-vm[==--] 87% 34.3G255.9G /var/local/vm daniel@Homer:/var/log$ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: dfc 2.5.0-1 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 6 09:17:49 2015 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.6 InstallationDate: Installed on 2014-12-08 (118 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) SourcePackage: dfc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dfc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Summary changed: - Display error with LVM + Dfc display error with LVM ** Description changed: - It shows +devmapper/system-backup instead of /dev/... I'm using + It shows +dev/mapper/system-backup instead of /dev/... I'm using LVM setup: Trigger für man-db (2.6.7.1-1ubuntu1) werden verarbeitet ... dfc (2.5.0-1) wird eingerichtet ... daniel@Homer:/var/log$ dfc - FILESYSTEM (=) USED FREE (-) %USED AVAILABLE TOTAL MOUNTED ON + FILESYSTEM (=) USED FREE (-) %USED AVAILABLE TOTAL MOUNTED ON /dev/mapper/system-root [=---] 23% 3.0G 3.8G / none []0% 4.0K 4.0K /sys/fs/cgroup udev [=---]0% 3.9G 3.9G /dev tmpfs[=---]0%797.0M798.5M /run none []0% 5.0M 5.0M /run/lock none
[Bug 1440651] Re: Dfc display error with LVM
** Attachment added: Screenshot https://bugs.launchpad.net/ubuntu/+source/dfc/+bug/1440651/+attachment/4367251/+files/dfc_error.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1440651 Title: Dfc display error with LVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dfc/+bug/1440651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1425047] Re: Install (manual partitioning) in Xubuntu Desktop i386 for Vivid Daily doesn't finish installation
In my case the installation runs in an timeout while step_before = StepUserInfo (screenshot: http://de.zimagez.com/zimage/screenshot-24022015-212516.php). Something was killed (window output) and after that the installation continue up to this screen (screenshot: http://de.zimagez.com/zimage/screenshot-24022015-213132.php) So, there was no window anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425047 Title: Install (manual partitioning) in Xubuntu Desktop i386 for Vivid Daily doesn't finish installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1425047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1424774] Re: Unable to expand directories in the tree pane and remain in the current directory
Well, i'm not sure that this should be called a bug. It's more or less a matter of taste. It's up to the developers what they like or want. Personal i prefer this new tree handling. However, it good way would be to add an UI option, that users can choose what they want. Maybe the default setting should be the old way. Just my thoughts :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1424774 Title: Unable to expand directories in the tree pane and remain in the current directory To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1424774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1424774] Re: Unable to expand directories in the tree pane and remain in the current directory
Well, i'm not sure that this should be called a bug. It's more or less a matter of taste. It's up to the developers what they like or want. Personal i prefer this new tree handling. However, it good way would be to add an UI option, that users can choose what they want. Maybe the default setting should be the old way. Just my thoughts :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1424774 Title: Unable to expand directories in the tree pane and remain in the current directory To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1424774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1425047] Re: Install (manual partitioning) in Xubuntu Desktop i386 for Vivid Daily doesn't finish installation
Add kernel log ** Attachment added: Kernel log https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1425047/+attachment/4326652/+files/dmesg.log ** Tags added: installer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425047 Title: Install (manual partitioning) in Xubuntu Desktop i386 for Vivid Daily doesn't finish installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1425047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1425047] Re: Install (manual partitioning) in Xubuntu Desktop i386 for Vivid Daily doesn't finish installation
I can confirm this bug. 64-Bit Installation was done with VMware Player 6.0.5. I'll add installer data and kernel log. ** Attachment added: /var/log/installer archiv https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1425047/+attachment/4326651/+files/installer.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425047 Title: Install (manual partitioning) in Xubuntu Desktop i386 for Vivid Daily doesn't finish installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1425047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1348431] Re: -O inline_data not supported by Ubuntu e2fsprogs
** Branch linked: lp:~daniel-mehrmann/e2fsprogs/master -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1348431 Title: -O inline_data not supported by Ubuntu e2fsprogs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1348431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1348431] Re: -O inline_data not supported by Ubuntu e2fsprogs
My e2fsprogs ppa got an update :-) * New upstream snapshot from master branch (23-02-2015) - libext2fs: fix potential buffer overflow in closefs() - e2fsck: salvage under-sized dirents by removing them - e2fsck: improve the inline directory detector - e2fsck: inspect inline dir data as two directory blocks - e2fsck: decrement bad count _after_ remapping a duplicate block - e2fsck: handle multiple *ind block collisions with critical metadata - e2fsck: fix message when the journal is deleted and regenerated - e2fsck: on read error, don't rewrite blocks past the end of the fs - e2fsck: clear i_block[] when there are too many bad mappings on a special inode - tune2fs: direct user to resize2fs for 64bit conversion - tune2fs: abort when trying to enable/disable metadata_csum on mounted fs - tune2fs: disable csum verification before resizing inode - resize2fs: fix regression test to not depend on ext4.ko being loaded - libext2fs: fix tdb.c mmap leak - libext2fs: strengthen i_extra_isize checks when reading/writing xattrs - libext2fs: avoid pointless EA block allocation - libext2fs: initialize i_extra_isize when writing EAs - debugfs: fix crash in ea_set argument handling - debugfs: document new commands - misc: fix minor testcase problems - Reserve the codepoints for the new INCOMPAT feature ENCRYPT - buildsystem: use 'chmod a-w' instead of 'chmod -w' - e2fsck: fix corruption of Hurd filesystems - e2fuzz: fix clang warning - Fix clang warning and a resource leak - e2fsck: close the progress_fd in the logfile child process - libext2fs: add sanity check for an invalid itable_used value in inode scan code New bzr branch is: https://code.launchpad.net/~daniel- mehrmann/e2fsprogs/master -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1348431 Title: -O inline_data not supported by Ubuntu e2fsprogs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1348431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1069350] Re: suspicious /.rpmdb root directory
I can confirm that trusty 14.04.2 LTS is affected. I have this problem on my xubuntu 14.04.2. Latest avaialable rpm package version is 4.11.1-3ubuntu0.1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069350 Title: suspicious /.rpmdb root directory To manage notifications about this bug go to: https://bugs.launchpad.net/rpm/+bug/1069350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1419372] Re: After install completes, Xubuntu 14.04.2 hangs on reboot
Well, with the latest iso version (20150218.1) the problem is gone and everything runs smoothy now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1419372 Title: After install completes, Xubuntu 14.04.2 hangs on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1419372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1419372] Re: After install completes, Xubuntu 14.04.2 hangs on reboot
I can repeat this bug with different machines, but on the other hand it's just a virtual software and there is no warranty that this could be a VMware Player bug. So long no other people reporting a VMware problem, we can close this ticket so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1419372 Title: After install completes, Xubuntu 14.04.2 hangs on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1419372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1419372] Re: After install completes, Xubuntu 14.04.2 hangs on reboot
** Attachment added: Xubuntu-14.04.2-test-64-bit.vmx https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1419372/+attachment/4316728/+files/Xubuntu-14.04.2-test-64-bit.vmx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1419372 Title: After install completes, Xubuntu 14.04.2 hangs on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1419372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1419372] Re: After install completes, Xubuntu 14.04.2 hangs on reboot
BTW: VMware Player runs stable and after a hard reset with Virtual machine-Power-reset guest, the system comes up in a clean state. :-) I'll attach log and configuration files. ** Attachment added: vmware.log https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1419372/+attachment/4316727/+files/vmware.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1419372 Title: After install completes, Xubuntu 14.04.2 hangs on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1419372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1306362] Re: AccountsService conflicts with configured logon background
Very nice :-) I've created a trusty backport here: https://launchpad.net/~daniel- mehrmann/+archive/ubuntu/test/+sourcepub/4766609/+listing-archive-extra ** Branch linked: lp:~daniel-mehrmann/lightdm-gtk-greeter/master -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1306362 Title: AccountsService conflicts with configured logon background To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1306362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418377] Re: A whole bunch of unwanted stuff installed
I'm getting the same basic problem (ibus and gnome panel) with a german installation. I did a screenshot. ** Attachment added: 14.04.2-after-install.png https://bugs.launchpad.net/ubuntu/+source/xubuntu-default-settings/+bug/1418377/+attachment/4314890/+files/14.04.2-after-install.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1418377 Title: A whole bunch of unwanted stuff installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xubuntu-default-settings/+bug/1418377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1419372] Re: After install completes, Xubuntu 14.04.2 hangs on reboot
I'm getting the same problem with a Installation under VMware Player 6.0.5. After a successful installation (installing packages and updates over the internet) the installer hangs on the reboot. ** Attachment added: Screenshot - 08.02.2015 - 18:28:42.png https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1419372/+attachment/4314923/+files/Screenshot%20-%2008.02.2015%20-%2018%3A28%3A42.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1419372 Title: After install completes, Xubuntu 14.04.2 hangs on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1419372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1419372] Re: After install completes, Xubuntu 14.04.2 hangs on reboot
I added /var/log/installer in a tar archiv ** Attachment added: installer.tar.gz https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1419372/+attachment/4314924/+files/installer.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1419372 Title: After install completes, Xubuntu 14.04.2 hangs on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1419372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1417450] Re: Kernel modul mac8021 ieee80211 iwlwifi crashed
** Summary changed: - Kernel modul mac80211 crashed + Kernel modul mac8021 ieee80211 iwlwifi crashed ** Tags added: ieee80211 mac8021 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1417450 Title: Kernel modul mac8021 ieee80211 iwlwifi crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1417450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1417450] [NEW] Kernel modul iwlwifi crashed
Public bug reported: From time to time my kernel wlan modul iwlwifi is crashing. I'm using my laptop daily and once in a month this happen. I can't force this bug. I only can say that it happens mostly during big data transfer (sftp/backup). /var/log/boot.log.1: [ cut here ] Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106187] WARNING: CPU: 3 PID: 76 at /build/buildd/linux-lts-utopic-3.16.0/net/mac80211/util.c:1565 ieee80211_reconfig+0x4b1/0x1500 [mac80211]() Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106194] Hardware became unavailable during restart. Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106219] Modules linked in: vmw_vsock_vmci_transport vsock vmw_vmci bnep rfcomm binfmt_misc xfs libcrc32c uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media arc4 iwldvm mac80211 intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm i915 snd_hda_codec_hdmi btusb iwlwifi crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek bluetooth rtsx_pci_ms drm_kms_helper snd_hda_codec_generic joydev cfg80211 serio_raw ghash_clmulni_intel 6lowpan_iphc snd_hda_intel cryptd drm mei_me snd_hda_controller snd_hda_codec snd_hwdep i2c_algo_bit thinkpad_acpi wmi memstick mei snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq nvram lpc_ich snd_seq_device snd_timer snd video mac_hid soundcore parport_pc ppdev coretemp lp parport hid_generic usbhid hid rtsx_pci_sdmmc psmouse r8169 ahci libahci mii rtsx_pci Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106268] CPU: 3 PID: 76 Comm: kworker/3:1 Not tainted 3.16.0-30-generic #40~14.04.1-Ubuntu Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106269] Hardware name: LENOVO 3354APG/3354APG, BIOS H3ET72WW(1.09) 02/25/2013 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106277] Workqueue: events ieee80211_restart_work [mac80211] Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106279] 0009 880210edbce8 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106282] ieee80211 phy0: Hardware restart was requested Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106283] 81762590 880210edbd30 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106285] 880210edbd20 8106dd2d fffb 880212710680 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106287] 880212711738 880212710680 880210edbd80 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106290] Call Trace: Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106295] [81762590] dump_stack+0x45/0x56 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106307] [8106dd2d] warn_slowpath_common+0x7d/0xa0 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106317] [8106dd9c] warn_slowpath_fmt+0x4c/0x50 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106322] [810889cf] ? flush_workqueue+0x17f/0x5a0 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106333] [c06b1f81] ieee80211_reconfig+0x4b1/0x1500 [mac80211] Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106344] [c06841b2] ieee80211_restart_work+0x42/0x70 [mac80211] Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106346] [81089ef2] process_one_work+0x182/0x450 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106348] [8108a663] worker_thread+0x123/0x5a0 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106351] [8108a540] ? rescuer_thread+0x380/0x380 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106354] [810912c2] kthread+0xd2/0xf0 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106357] [810911f0] ? kthread_create_on_node+0x1c0/0x1c0 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106361] [8176ac3c] ret_from_fork+0x7c/0xb0 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106363] [810911f0] ? kthread_create_on_node+0x1c0/0x1c0 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106365] ---[ end trace cf4f868f9d3defa0 ]--- Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106417] [ cut here ] Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106428] WARNING: CPU: 3 PID: 76 at /build/buildd/linux-lts-utopic-3.16.0/net/mac80211/driver-ops.h:12 ieee80211_do_stop+0x88a/0x8f0 [mac80211]() Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106430] wlan0: Failed check-sdata-in-driver check, flags: 0x0 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106431] Modules linked in: vmw_vsock_vmci_transport vsock vmw_vmci bnep rfcomm binfmt_misc xfs libcrc32c uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media arc4 iwldvm mac80211 intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm i915 snd_hda_codec_hdmi btusb iwlwifi crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek bluetooth rtsx_pci_ms drm_kms_helper snd_hda_codec_generic joydev cfg80211 serio_raw ghash_clmulni_intel 6lowpan_iphc snd_hda_intel cryptd drm mei_me snd_hda_controller snd_hda_codec snd_hwdep i2c_algo_bit thinkpad_acpi wmi memstick mei snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq nvram lpc_ich snd_seq_device snd_timer snd video
[Bug 1417450] Re: Kernel modul mac80211 crashed
** Summary changed: - Kernel modul iwlwifi crashed + Kernel modul mac80211 crashed ** Description changed: - From time to time my kernel wlan modul iwlwifi is crashing. I'm using + From time to time my kernel wlan modul mac80211 is crashing. I'm using my laptop daily and once in a month this happen. I can't force this bug. I only can say that it happens mostly during big data transfer (sftp/backup). - /var/log/boot.log.1: [ cut here ] Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106187] WARNING: CPU: 3 PID: 76 at /build/buildd/linux-lts-utopic-3.16.0/net/mac80211/util.c:1565 ieee80211_reconfig+0x4b1/0x1500 [mac80211]() Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106194] Hardware became unavailable during restart. Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106219] Modules linked in: vmw_vsock_vmci_transport vsock vmw_vmci bnep rfcomm binfmt_misc xfs libcrc32c uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media arc4 iwldvm mac80211 intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm i915 snd_hda_codec_hdmi btusb iwlwifi crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek bluetooth rtsx_pci_ms drm_kms_helper snd_hda_codec_generic joydev cfg80211 serio_raw ghash_clmulni_intel 6lowpan_iphc snd_hda_intel cryptd drm mei_me snd_hda_controller snd_hda_codec snd_hwdep i2c_algo_bit thinkpad_acpi wmi memstick mei snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq nvram lpc_ich snd_seq_device snd_timer snd video mac_hid soundcore parport_pc ppdev coretemp lp parport hid_generic usbhid hid rtsx_pci_sdmmc psmouse r8169 ahci libahci mii rtsx_pci Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106268] CPU: 3 PID: 76 Comm: kworker/3:1 Not tainted 3.16.0-30-generic #40~14.04.1-Ubuntu Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106269] Hardware name: LENOVO 3354APG/3354APG, BIOS H3ET72WW(1.09) 02/25/2013 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106277] Workqueue: events ieee80211_restart_work [mac80211] Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106279] 0009 880210edbce8 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106282] ieee80211 phy0: Hardware restart was requested Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106283] 81762590 880210edbd30 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106285] 880210edbd20 8106dd2d fffb 880212710680 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106287] 880212711738 880212710680 880210edbd80 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106290] Call Trace: Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106295] [81762590] dump_stack+0x45/0x56 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106307] [8106dd2d] warn_slowpath_common+0x7d/0xa0 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106317] [8106dd9c] warn_slowpath_fmt+0x4c/0x50 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106322] [810889cf] ? flush_workqueue+0x17f/0x5a0 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106333] [c06b1f81] ieee80211_reconfig+0x4b1/0x1500 [mac80211] Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106344] [c06841b2] ieee80211_restart_work+0x42/0x70 [mac80211] Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106346] [81089ef2] process_one_work+0x182/0x450 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106348] [8108a663] worker_thread+0x123/0x5a0 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106351] [8108a540] ? rescuer_thread+0x380/0x380 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106354] [810912c2] kthread+0xd2/0xf0 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106357] [810911f0] ? kthread_create_on_node+0x1c0/0x1c0 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106361] [8176ac3c] ret_from_fork+0x7c/0xb0 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106363] [810911f0] ? kthread_create_on_node+0x1c0/0x1c0 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106365] ---[ end trace cf4f868f9d3defa0 ]--- Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106417] [ cut here ] Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106428] WARNING: CPU: 3 PID: 76 at /build/buildd/linux-lts-utopic-3.16.0/net/mac80211/driver-ops.h:12 ieee80211_do_stop+0x88a/0x8f0 [mac80211]() Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106430] wlan0: Failed check-sdata-in-driver check, flags: 0x0 Feb 1 10:49:20 Homer-Mobil kernel: [ 18.106431] Modules linked in: vmw_vsock_vmci_transport vsock vmw_vmci bnep rfcomm binfmt_misc xfs libcrc32c uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media arc4 iwldvm mac80211 intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm i915 snd_hda_codec_hdmi btusb iwlwifi crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek bluetooth rtsx_pci_ms drm_kms_helper snd_hda_codec_generic joydev cfg80211 serio_raw ghash_clmulni_intel
[Bug 1417450] Re: Kernel modul iwlwifi crashed
Add version.log ** Attachment added: version.log https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1417450/+attachment/4311032/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1417450 Title: Kernel modul iwlwifi crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1417450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1417450] Re: Kernel modul iwlwifi crashed
Add uname.log ** Attachment added: uname-a.log https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1417450/+attachment/4311031/+files/uname-a.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1417450 Title: Kernel modul iwlwifi crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1417450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1417450] Re: Kernel modul iwlwifi crashed
Add dmesg.log ** Attachment added: dmesg.log https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1417450/+attachment/4311034/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1417450 Title: Kernel modul iwlwifi crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1417450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1348431] Re: -O inline_data not supported by Ubuntu e2fsprogs
Clarification: I used branch 'master' for my packages and bzr branch as well. First i thought it would be a good idea to use the branch 'maint'. But later on i decided to use the branch 'master'. After uploading the bzr branch to lp i notice that i used the wrong label (naming) in lp and it was to late for a correction , because i announced it already. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1348431 Title: -O inline_data not supported by Ubuntu e2fsprogs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1348431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1365874] Re: Ubuntu 14.04 does not support ext4 metadata checksumming
** Branch linked: lp:~daniel-mehrmann/e2fsprogs/maint -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1365874 Title: Ubuntu 14.04 does not support ext4 metadata checksumming To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1365874] Re: Ubuntu 14.04 does not support ext4 metadata checksumming
I build a personal Ubuntu PPA for this tools collection (e2fsprogs). I did a snapshot of git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git and used the master trunk maint. I will update my personal PPA monthly or if tytso tells me it's time to do so. :-) I build deb packages for trusty, utopic and vivet and/or you can use my bzr branch for these packages. You can add my PPA to your Ubuntu system with: sudo add-apt-repository ppa:daniel-mehrmann/admin sudo apt-get update sudo apt-get upgrade Happy testing!! (And don't forget to report bugs to linux-ext4 and help developers to get this feature more stable) Links: PPA: https://launchpad.net/~daniel-mehrmann/+archive/ubuntu/admin BZR branch: https://code.launchpad.net/~daniel-mehrmann/e2fsprogs/maint -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1365874 Title: Ubuntu 14.04 does not support ext4 metadata checksumming To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1365874] Re: Ubuntu 14.04 does not support ext4 metadata checksumming
** Changed in: e2fsprogs (Ubuntu) Assignee: (unassigned) = Daniel Mehrmann (daniel-mehrmann) ** Changed in: e2fsprogs (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1365874 Title: Ubuntu 14.04 does not support ext4 metadata checksumming To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1348431] Re: -O inline_data not supported by Ubuntu e2fsprogs
I build a personal Ubuntu PPA for this tools collection (e2fsprogs). I did a snapshot of git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git and used the master trunk maint. I will update my personal PPA monthly or if tytso tells me it's time to do so. :-) I build deb packages for trusty, utopic and vivet and/or you can use my bzr branch for these packages. You can add my PPA to your Ubuntu system with: sudo add-apt-repository ppa:daniel-mehrmann/admin sudo apt-get update sudo apt-get upgrade Happy testing!! (And don't forget to report bugs to linux-ext4 and help developers to get this feature more stable) Links: PPA: https://launchpad.net/~daniel-mehrmann/+archive/ubuntu/admin BZR branch: https://code.launchpad.net/~daniel-mehrmann/e2fsprogs/maint ** Branch linked: lp:~daniel-mehrmann/e2fsprogs/maint -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1348431 Title: -O inline_data not supported by Ubuntu e2fsprogs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1348431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393477] Re: Trusty update to v3.13.11.11 stable release
** Branch linked: lp:~daniel-mehrmann/e2fsprogs/maint -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393477 Title: Trusty update to v3.13.11.11 stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1393477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393477] Re: Trusty update to v3.13.11.11 stable release
Probably there is a problem with the ext4: enable journal checksum when metadata checksum feature enabled patch. Tytso wrote in bug LP: #1365874 that with Linux kernel 3.18 the metadata checksum feature got some format changes. Is this patch compatible with these changes? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393477 Title: Trusty update to v3.13.11.11 stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1393477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1365874] Re: Ubuntu 14.04 does not support ext4 metadata checksumming
Well, Ubuntu based on Debian (mostly testing stage). If i'm looking here https://packages.qa.debian.org/e/e2fsprogs.html, we can see that Debian has no support for extended etx4 features yet and it looks like that take a while. Probably it was a little bit optimistic to add such features to the release notes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1365874 Title: Ubuntu 14.04 does not support ext4 metadata checksumming To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996484] [NEW] xfce4-terminal create a zombie
Public bug reported: Hello, I'm running Xubuntu 12.04 and every time i'm open a xfce4 terminal window it creates a zombie process as well: daniel@Homer-Mobil:~$ ps -ely |grep -i terminal S 1000 2909 1 0 80 0 14188 14593 poll_s ?00:00:02 xfce4-terminal Z 1000 2910 2909 0 80 0 0 0 exit ?00:00:00 xfce4-terminal defunct It happens only with the first terminal and the zombie process says good bye if the window get closed. Well, it has no impact about the terminal and everything run smoothly, but it shouldn't happens. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xfce4-terminal 0.4.8-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic i686 ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Tue May 8 13:12:37 2012 InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xfce4-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise xfce4-terminal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996484 Title: xfce4-terminal create a zombie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-terminal/+bug/996484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996484] Re: xfce4-terminal create a zombie
** Tags added: xfce4-terminal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996484 Title: xfce4-terminal create a zombie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-terminal/+bug/996484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994414] Re: SD-Card slot empty but Kernel think it's attached
I'm using this kernel right now: daniel@Homer-Mobil:~$ uname -a Linux Homer-Mobil 3.4.0-030400rc6-generic #201205061835 SMP Sun May 6 22:42:47 UTC 2012 i686 i686 i386 GNU/Linux and the bug is still there :-( I've attached new log - and install files. I hope this might help you. :-) ** Attachment added: full dmesg output https://bugs.launchpad.net/ubuntu/+source/linux/+bug/994414/+attachment/3134723/+files/boot.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994414 Title: SD-Card slot empty but Kernel think it's attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/994414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994414] Re: SD-Card slot empty but Kernel think it's attached
** Attachment added: New kernel install log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/994414/+attachment/3134725/+files/kernel.install.log ** Tags removed: needs-upstream-testing ** Tags added: kernel-bug-exists-upstream ** 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/994414 Title: SD-Card slot empty but Kernel think it's attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/994414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994414] Re: SD-Card slot empty but Kernel think it's attached
*** This bug is a duplicate of bug 925760 *** https://bugs.launchpad.net/bugs/925760 Oops, i think my bugreport seems duplicate of 925760. Sorry for that. ** This bug has been marked a duplicate of bug 925760 Constant warnings from the kernel: Test WP failed, assume Write Enabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994414 Title: SD-Card slot empty but Kernel think it's attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/994414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 925760] Re: Constant warnings from the kernel: Test WP failed, assume Write Enabled
Well, i have the same problem with my SD-Card reader and I can confirm that this bug is still there with Ubuntu 12.04. I tested the latestest upstream kernel (3.4.0-030400rc6-generic #201205061835 SMP Sun May 6 22:42:47 UTC 2012 i686 i686 i386 GNU/Linux) and i have no good news for you. :-( Sorry, I overlooked this report and marked my one #994414 as duplicated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925760 Title: Constant warnings from the kernel: Test WP failed, assume Write Enabled To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/925760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 925760] Re: Constant warnings from the kernel: Test WP failed, assume Write Enabled
** Attachment added: full dmesg output https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925760/+attachment/3135072/+files/boot.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925760 Title: Constant warnings from the kernel: Test WP failed, assume Write Enabled To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/925760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994414] Re: SD-Card slot empty but Kernel think it's attached
Ok, I'll do that on monday next week (07.05.2012), because i don't have my system at home right now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994414 Title: SD-Card slot empty but Kernel think it's attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/994414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994414] [NEW] SD-Card slot empty but Kernel think it's attached
Public bug reported: Well, my Netbook has a normal harddisk and a SD-Card slot reader. My main disk runs fine: [1.450126] ata1.00: ATA-8: SAMSUNG HM400LI, 2TF00_00, max UDMA7 [1.450160] ata1.00: 781422768 sectors, multi 16: LBA48 NCQ (depth 0/32) [1.466126] ata1.00: configured for UDMA/133 [1.466581] scsi 0:0:0:0: Direct-Access ATA SAMSUNG HM400LI 2TF0 PQ: 0 ANSI: 5 [1.466990] sd 0:0:0:0: [sda] 781422768 512-byte logical blocks: (400 GB/372 GiB) [1.467089] sd 0:0:0:0: Attached scsi generic sg0 type 0 [1.467252] sd 0:0:0:0: [sda] Write Protect is off [1.467272] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [1.467392] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [1.503545] sda: sda1 sda2 sda3 [1.504727] sd 0:0:0:0: [sda] Attached SCSI disk But my SD-Card reader slot is always empty and i never used a card before. Every time my system starts the kernel found it and attach a device, which might be wrong because its empty: [7.870635] scsi 2:0:0:0: Direct-Access Generic- Multi-Card 1.00 PQ: 0 ANSI: 0 CCS [7.873147] sd 2:0:0:0: Attached scsi generic sg1 type 0 [7.81] sd 2:0:0:0: [sdb] Attached SCSI removable disk Well, now the kernel tries to find out some technical data about the device which doesn't work of course. So my kernel log get spamed time of time: [ 3162.653370] sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled [ 3162.655854] sd 2:0:0:0: [sdb] Asking for cache data failed [ 3162.655871] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 3214.365502] sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled [ 3214.367989] sd 2:0:0:0: [sdb] Asking for cache data failed [ 3214.368075] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 3266.081262] sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled [ 3266.083747] sd 2:0:0:0: [sdb] Asking for cache data failed [ 3266.083762] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 3317.789397] sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled [ 3317.791884] sd 2:0:0:0: [sdb] Asking for cache data failed [ 3317.791902] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 3369.505377] sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled [ 3369.507895] sd 2:0:0:0: [sdb] Asking for cache data failed [ 3369.507907] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 3421.273894] sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled [ 3421.276593] sd 2:0:0:0: [sdb] Asking for cache data failed [ 3421.276618] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 3472.925298] sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled [ 3472.927689] sd 2:0:0:0: [sdb] Asking for cache data failed [ 3472.927701] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 3524.733456] sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled [ 3524.736477] sd 2:0:0:0: [sdb] Asking for cache data failed [ 3524.736492] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 3576.349309] sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled [ 3576.351723] sd 2:0:0:0: [sdb] Asking for cache data failed [ 3576.351742] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 3628.069311] sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled [ 3628.071883] sd 2:0:0:0: [sdb] Asking for cache data failed [ 3628.071897] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 3679.817327] sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled [ 3679.819567] sd 2:0:0:0: [sdb] Asking for cache data failed [ 3679.819581] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 3731.481617] sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled [ 3731.483965] sd 2:0:0:0: [sdb] Asking for cache data failed [ 3731.483980] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 3783.197740] sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled [ 3783.200521] sd 2:0:0:0: [sdb] Asking for cache data failed [ 3783.200546] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 3834.914066] sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled [ 3834.916535] sd 2:0:0:0: [sdb] Asking for cache data failed [ 3834.916559] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 3886.622010] sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled [ 3886.624539] sd 2:0:0:0: [sdb] Asking for cache data failed [ 3886.624563] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 3938.329534] sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled [ 3938.332172] sd 2:0:0:0: [sdb] Asking for cache data failed [ 3938.332193] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 3990.045405] sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled [ 3990.047906] sd 2:0:0:0: [sdb] Asking for cache data failed [ 3990.047923] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 4041.757695] sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled [ 4041.760435] sd 2:0:0:0: [sdb] Asking for cache data failed [ 4041.760462] sd 2:0:0:0: [sdb] Assuming
[Bug 994414] Re: SD-Card slot empty but Kernel think it's attached
** Attachment added: Boot log by dmesg comand https://bugs.launchpad.net/bugs/994414/+attachment/3129417/+files/boot.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994414 Title: SD-Card slot empty but Kernel think it's attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/994414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994414] Re: SD-Card slot empty but Kernel think it's attached
** Tags added: kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994414 Title: SD-Card slot empty but Kernel think it's attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/994414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
