[Kernel-packages] [Bug 1822913] Re: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at 0000000000000000
@Maurizio, could you test a newer Kernel? 5.1 for example to see if it's already solved, it is in my case. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822913 Title: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: New Bug description: With Kernel 5.0.0-8 I have strange behaivour. I have no wifi and no sound, typing sudo doesn't work. kern.log attached, include a boot with kernel 5 and one with 4.19 (which works ok) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821564] Re: b44 Ethernet driver null pointer during initialization
@Boris please test kernel 5.1.0-050100rc3-generic (or above) at least #1822913 was solved with this kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821564 Title: b44 Ethernet driver null pointer during initialization Status in linux package in Ubuntu: Confirmed Bug description: This problem started after upgrading to Ubuntu 19.04. It was not present with 4.18.0-16-generic kernel and is present in the 4.18.0-15-generic kernel. Ever time during boot there is a null pointer dereference in the b44 driver for the on-board Ethernet on this Dell Inspiron 6400. After that I can log in but networking related commands hang and the computer eventually locks up. Blacklisting the b44 module so it doesn't load works as a workaround, though of course the on board Ethernet can't be used that way. The b43 WiFi still works then. The following is pasted from the log of one crash: 6.483003] BUG: unable to handle kernel NULL pointer dereference at 6.483052] #PF error: [normal kernel read fault] 6.483093] PGD 0 P4D 0 6.483133] Oops: [#1] SMP PTI 6.483175] CPU: 0 PID: 725 Comm: NetworkManager Tainted: GW 5.0.0-7-generic #8-Ubuntu 6.483217] Hardware name: Dell Inc. MM061 /0XD720, BIOS A17 06/13/2007 6.483267] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310 6.483310] Code: 4c 8b 45 a8 4c 8b 1d 0f b2 a9 01 89 d3 45 31 d2 44 8b 4d a4 44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c a3 0f 83 cb 00 00 00 42 8d 04 33 48 89 c3 48 39 c1 41 0f 6.483368] RSP: 0018:bc7040c7f3c0 EFLAGS: 00010016 6.483416] RAX: 0001 RBX: RCX: 6.483467] RDX: RSI: 001f RDI: 0001 6.483521] RBP: bc7040c7f420 R08: 0001 R09: 0001 6.483572] R10: R11: R12: 6.483621] R13: R14: 0001 R15: 0020 6.483670] FS: 7f2cb49ccbc0() GS:9d8a4c40() knlGS: 6.483726] CS: 0010 DS: ES: CR0: 80050033 6.483773] CR2: CR3: c72ce000 CR4: 06f0 6.483820] Call Trace: 6.483869] swiotlb_map+0x6c/0x1c0 6.483915] dma_direct_map_page+0xc5/0x160 6.483965] b44_alloc_rx_skb+0x18e/0x3f0 [b44] 6.484013] b44_init_rings+0xbe/0x1b0 [b44] 6.484060] b44_open+0xfc/0x3f0 [b44] 6.484107] __dev_open+0xd4/0x170 6.484153] __dev_change_flags+0x18f/0x200 6.484199] dev_change_flags+0x27/0x60 6.484246] do_setlink+0x31c/0xe30 6.484292] ? __nla_parse+0xf1/0x120 6.484340] ? cpumask_next+0x1b/0x20 6.484388] ? __snmp6_fill_stats64.isra.57+0xf6/0x120 6.484439] ? __nla_parse+0x38/0x120 6.484488] __rtnl_newlink+0x531/0x910 6.484535] ? __nla_put+0x20/0x30 6.484586] ? __kmalloc_node_track_caller+0x1e6/0x2b0 6.484636] ? pskb_expand_head+0x70/0x2e0 6.484693] ? __kmalloc_reserve.isra.53+0x31/0x90 6.484751] ? apparmor_inet_conn_request+0x40/0x40 6.484822] ? security_sock_rcv_skb+0x2f/0x50 6.484879] ? skb_queue_tail+0x43/0x50 6.484934] ? __netlink_sendskb+0x53/0x70 6.484992] ? syscall_return_via_sysret+0xf/0x7f 6.485043] ? __switch_to_asm+0x40/0x70 6.485097] ? syscall_return_via_sysret+0xf/0x7f 6.485153] ? _cond_resched+0x19/0x30 6.485204] ? kmem_cache_alloc_trace+0x153/0x1d0 6.485253] rtnl_newlink+0x48/0x70 6.485301] rtnetlink_rcv_msg+0x213/0x300 6.485348] ? __d_lookup+0x126/0x140 6.485393] ? rtnl_calcit.isra.31+0x100/0x100 6.485440] netlink_rcv_skb+0x4f/0x120 6.485485] rtnetlink_rcv+0x15/0x20 6.485518] netlink_unicast+0x1a1/0x260 6.485518] netlink_sendmsg+0x20d/0x3c0 6.485518] sock_sendmsg+0x3e/0x50 6.485518] ___sys_sendmsg+0x295/0x2f0 6.485518] ? rtnl_unlock+0xe/0x10 6.485518] ? addrconf_sysctl_forward+0x114/0x280 6.485518] ? dev_forward_change+0x140/0x140 6.485518] ? __fget_light+0x54/0x60 6.485518] __sys_sendmsg+0x5c/0xa0 6.485518] __x64_sys_sendmsg+0x1f/0x30 6.485518] do_syscall_64+0x5a/0x110 6.485518] entry_SYSCALL_64_after_hwframe+0x44/0xa9 6.485518] RIP: 0033:0x7f2cb6153cb7 6.485518] Code: 44 00 00 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 3b ed ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 74 ed ff ff 48 6.485518] RSP: 002b:7ffe93a35c80 EFLAGS: 0293 ORIG_RAX: 002e 6.485518] RAX: ffda RBX: 0008 RCX: 7f2cb6153cb7 6.485518] RDX: RSI: 7ffe93a35cd0 RDI: 0008 6.485518] RBP: 7ffe93a35cd0 R08: R09: 6.485518] R10: 7f2cb6139ca0 R11: 0293 R12: 6.485518] R13: 5598b029e880 R14:
[Kernel-packages] [Bug 1822913] Re: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at 0000000000000000
problem is solved in kernel 5.1.0-050100rc3-generic Is it necessary the bisect? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822913 Title: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at Status in linux package in Ubuntu: Confirmed Bug description: With Kernel 5.0.0-8 I have strange behaivour. I have no wifi and no sound, typing sudo doesn't work. kern.log attached, include a boot with kernel 5 and one with 4.19 (which works ok) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821564] Re: b44 Ethernet driver null pointer during initialization
I just tested Kernel 4.20.17 an it is good. I will do the bisect but I don't have much time at this moment -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821564 Title: b44 Ethernet driver null pointer during initialization Status in linux package in Ubuntu: Confirmed Bug description: This problem started after upgrading to Ubuntu 19.04. It was not present with 4.18.0-16-generic kernel and is present in the 4.18.0-15-generic kernel. Ever time during boot there is a null pointer dereference in the b44 driver for the on-board Ethernet on this Dell Inspiron 6400. After that I can log in but networking related commands hang and the computer eventually locks up. Blacklisting the b44 module so it doesn't load works as a workaround, though of course the on board Ethernet can't be used that way. The b43 WiFi still works then. The following is pasted from the log of one crash: 6.483003] BUG: unable to handle kernel NULL pointer dereference at 6.483052] #PF error: [normal kernel read fault] 6.483093] PGD 0 P4D 0 6.483133] Oops: [#1] SMP PTI 6.483175] CPU: 0 PID: 725 Comm: NetworkManager Tainted: GW 5.0.0-7-generic #8-Ubuntu 6.483217] Hardware name: Dell Inc. MM061 /0XD720, BIOS A17 06/13/2007 6.483267] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310 6.483310] Code: 4c 8b 45 a8 4c 8b 1d 0f b2 a9 01 89 d3 45 31 d2 44 8b 4d a4 44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c a3 0f 83 cb 00 00 00 42 8d 04 33 48 89 c3 48 39 c1 41 0f 6.483368] RSP: 0018:bc7040c7f3c0 EFLAGS: 00010016 6.483416] RAX: 0001 RBX: RCX: 6.483467] RDX: RSI: 001f RDI: 0001 6.483521] RBP: bc7040c7f420 R08: 0001 R09: 0001 6.483572] R10: R11: R12: 6.483621] R13: R14: 0001 R15: 0020 6.483670] FS: 7f2cb49ccbc0() GS:9d8a4c40() knlGS: 6.483726] CS: 0010 DS: ES: CR0: 80050033 6.483773] CR2: CR3: c72ce000 CR4: 06f0 6.483820] Call Trace: 6.483869] swiotlb_map+0x6c/0x1c0 6.483915] dma_direct_map_page+0xc5/0x160 6.483965] b44_alloc_rx_skb+0x18e/0x3f0 [b44] 6.484013] b44_init_rings+0xbe/0x1b0 [b44] 6.484060] b44_open+0xfc/0x3f0 [b44] 6.484107] __dev_open+0xd4/0x170 6.484153] __dev_change_flags+0x18f/0x200 6.484199] dev_change_flags+0x27/0x60 6.484246] do_setlink+0x31c/0xe30 6.484292] ? __nla_parse+0xf1/0x120 6.484340] ? cpumask_next+0x1b/0x20 6.484388] ? __snmp6_fill_stats64.isra.57+0xf6/0x120 6.484439] ? __nla_parse+0x38/0x120 6.484488] __rtnl_newlink+0x531/0x910 6.484535] ? __nla_put+0x20/0x30 6.484586] ? __kmalloc_node_track_caller+0x1e6/0x2b0 6.484636] ? pskb_expand_head+0x70/0x2e0 6.484693] ? __kmalloc_reserve.isra.53+0x31/0x90 6.484751] ? apparmor_inet_conn_request+0x40/0x40 6.484822] ? security_sock_rcv_skb+0x2f/0x50 6.484879] ? skb_queue_tail+0x43/0x50 6.484934] ? __netlink_sendskb+0x53/0x70 6.484992] ? syscall_return_via_sysret+0xf/0x7f 6.485043] ? __switch_to_asm+0x40/0x70 6.485097] ? syscall_return_via_sysret+0xf/0x7f 6.485153] ? _cond_resched+0x19/0x30 6.485204] ? kmem_cache_alloc_trace+0x153/0x1d0 6.485253] rtnl_newlink+0x48/0x70 6.485301] rtnetlink_rcv_msg+0x213/0x300 6.485348] ? __d_lookup+0x126/0x140 6.485393] ? rtnl_calcit.isra.31+0x100/0x100 6.485440] netlink_rcv_skb+0x4f/0x120 6.485485] rtnetlink_rcv+0x15/0x20 6.485518] netlink_unicast+0x1a1/0x260 6.485518] netlink_sendmsg+0x20d/0x3c0 6.485518] sock_sendmsg+0x3e/0x50 6.485518] ___sys_sendmsg+0x295/0x2f0 6.485518] ? rtnl_unlock+0xe/0x10 6.485518] ? addrconf_sysctl_forward+0x114/0x280 6.485518] ? dev_forward_change+0x140/0x140 6.485518] ? __fget_light+0x54/0x60 6.485518] __sys_sendmsg+0x5c/0xa0 6.485518] __x64_sys_sendmsg+0x1f/0x30 6.485518] do_syscall_64+0x5a/0x110 6.485518] entry_SYSCALL_64_after_hwframe+0x44/0xa9 6.485518] RIP: 0033:0x7f2cb6153cb7 6.485518] Code: 44 00 00 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 3b ed ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 74 ed ff ff 48 6.485518] RSP: 002b:7ffe93a35c80 EFLAGS: 0293 ORIG_RAX: 002e 6.485518] RAX: ffda RBX: 0008 RCX: 7f2cb6153cb7 6.485518] RDX: RSI: 7ffe93a35cd0 RDI: 0008 6.485518] RBP: 7ffe93a35cd0 R08: R09: 6.485518] R10: 7f2cb6139ca0 R11: 0293 R12: 6.485518] R13: 5598b029e880 R14:
[Kernel-packages] [Bug 1822913] Re: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at 0000000000000000
I saw in the comments that #1821564 was with kernel 5 it might be a dupe of it then. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822913 Title: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at Status in linux package in Ubuntu: Confirmed Bug description: With Kernel 5.0.0-8 I have strange behaivour. I have no wifi and no sound, typing sudo doesn't work. kern.log attached, include a boot with kernel 5 and one with 4.19 (which works ok) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822913] Re: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at 0000000000000000
I cannot run apport-collect because when I have this issue I don't have wifi connectiom. I will try to connect via cable an do apport-collect, but It will take some time. Giving that 19.04 with Kernel 5 is almost ready to be delivered, I will change to confirm anyway. I'm not sure is a dupe of #1821564 because it's a different Kernel (5) and in 4.19 it works ok, symptoms are very similar though. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822913 Title: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at Status in linux package in Ubuntu: Confirmed Bug description: With Kernel 5.0.0-8 I have strange behaivour. I have no wifi and no sound, typing sudo doesn't work. kern.log attached, include a boot with kernel 5 and one with 4.19 (which works ok) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822913] Re: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at 0000000000000000
forgot to add info about the audio and wifi: *-multimedia description: Audio device product: NM10/ICH7 Family High Definition Audio Controller vendor: Intel Corporation physical id: 1b bus info: pci@:00:1b.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:25 memory:efebc000-efeb *-network description: Wireless interface product: PRO/Wireless 3945ABG [Golan] Network Connection vendor: Intel Corporation physical id: 0 bus info: pci@:0c:00.0 logical name: wlp12s0 version: 02 serial: 00:18:de:8a:64:ec width: 32 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwl3945 driverversion=4.19.0-13-generic firmware=15.32.2.9 ip=192.168.0.18 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:24 memory:efdff000-efdf -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822913 Title: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at Status in linux package in Ubuntu: New Bug description: With Kernel 5.0.0-8 I have strange behaivour. I have no wifi and no sound, typing sudo doesn't work. kern.log attached, include a boot with kernel 5 and one with 4.19 (which works ok) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822913] [NEW] Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at 0000000000000000
Public bug reported: With Kernel 5.0.0-8 I have strange behaivour. I have no wifi and no sound, typing sudo doesn't work. kern.log attached, include a boot with kernel 5 and one with 4.19 (which works ok) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel kernel-bug ** Attachment added: "kern.log" https://bugs.launchpad.net/bugs/1822913/+attachment/5252319/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822913 Title: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at Status in linux package in Ubuntu: New Bug description: With Kernel 5.0.0-8 I have strange behaivour. I have no wifi and no sound, typing sudo doesn't work. kern.log attached, include a boot with kernel 5 and one with 4.19 (which works ok) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773718] Re: mouse pointer disappear after screen off
I haven't tried with other DE, since it is an old computer I have only tried lxde. I could easily try with openbox alone, installing another DE could be a little longer. Is there one better to test with? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773718 Title: mouse pointer disappear after screen off Status in linux package in Ubuntu: Confirmed Bug description: With nouveau driver (doesn't happened with propietary nvidia) after screen switch off because of power management, the mouse pointer disappear. Mouse still works, you can hover, select, click, but the pointer is invisible. In a dual monitor configuration, this only happened in the screen where the mouse was when it turned off. If It firs happened in one monitor and tehn I left the mouse in the other and it also turn off, mouse end up disappearing in both. My video card is an nvidia GeForce Go6150 (NV4E C51). Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773718] Re: mouse pointer disappear after screen off
I just realize that it only happen after login (lxde, lubuntu) in lightdm this does not happen. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773718 Title: mouse pointer disappear after screen off Status in linux package in Ubuntu: Confirmed Bug description: With nouveau driver (doesn't happened with propietary nvidia) after screen switch off because of power management, the mouse pointer disappear. Mouse still works, you can hover, select, click, but the pointer is invisible. In a dual monitor configuration, this only happened in the screen where the mouse was when it turned off. If It firs happened in one monitor and tehn I left the mouse in the other and it also turn off, mouse end up disappearing in both. My video card is an nvidia GeForce Go6150 (NV4E C51). Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773718] Re: mouse ponter disappear after screen off
Hi, I've seen this problem since I install linux in this computer (2 years ago), but my workaround was to use the nvidia propietary driver. Now that nvidia stop developing the 304 driver, I will have to use nouveau. I installed 4.17.0-041700rc7-generic and the problem still is there. It might be that I had to wait a couple of minutes more oafter the screen switch off or suspended, but the problem is still there. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream ** Summary changed: - mouse ponter disappear after screen off + mouse pointer disappear after screen off -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773718 Title: mouse pointer disappear after screen off Status in linux package in Ubuntu: Confirmed Bug description: With nouveau driver (doesn't happened with propietary nvidia) after screen switch off because of power management, the mouse pointer disappear. Mouse still works, you can hover, select, click, but the pointer is invisible. In a dual monitor configuration, this only happened in the screen where the mouse was when it turned off. If It firs happened in one monitor and tehn I left the mouse in the other and it also turn off, mouse end up disappearing in both. My video card is an nvidia GeForce Go6150 (NV4E C51). Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773718] Re: mouse ponter disappear after screen off
I didn't knew which log to attach. Already done what you asked for. I'm also attaching lspci -vnvn log ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Attachment added: "lspci -vnv" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773718/+attachment/5145369/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773718 Title: mouse ponter disappear after screen off Status in linux package in Ubuntu: Confirmed Bug description: With nouveau driver (doesn't happened with propietary nvidia) after screen switch off because of power management, the mouse pointer disappear. Mouse still works, you can hover, select, click, but the pointer is invisible. In a dual monitor configuration, this only happened in the screen where the mouse was when it turned off. If It firs happened in one monitor and tehn I left the mouse in the other and it also turn off, mouse end up disappearing in both. My video card is an nvidia GeForce Go6150 (NV4E C51). Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773718] [NEW] mouse ponter disappear after screen off
Public bug reported: With nouveau driver (doesn't happened with propietary nvidia) after screen switch off because of power management, the mouse pointer disappear. Mouse still works, you can hover, select, click, but the pointer is invisible. In a dual monitor configuration, this only happened in the screen where the mouse was when it turned off. If It firs happened in one monitor and tehn I left the mouse in the other and it also turn off, mouse end up disappearing in both. My video card is an nvidia GeForce Go6150 (NV4E C51). Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: disappear mouse nouveau nvidia pointer ** Description changed: With nouveau driver (doesn't happened with propietary nvidia) after screen switch off because of power management, the mouse pointer disappear. Mouse still works, you can hover, select, click, but the pointer is invisible. In a dual monitor configuration, this only happened in the screen where the mouse was when it turned off. If It firs happened in one monitor and tehn I left the mouse in the other and it also turn off, mouse end up disappearing in both. My video card is an nvidia GeForce Go6150 (NV4E C51). + + Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773718 Title: mouse ponter disappear after screen off Status in linux package in Ubuntu: New Bug description: With nouveau driver (doesn't happened with propietary nvidia) after screen switch off because of power management, the mouse pointer disappear. Mouse still works, you can hover, select, click, but the pointer is invisible. In a dual monitor configuration, this only happened in the screen where the mouse was when it turned off. If It firs happened in one monitor and tehn I left the mouse in the other and it also turn off, mouse end up disappearing in both. My video card is an nvidia GeForce Go6150 (NV4E C51). Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
