[Kernel-packages] [Bug 1824642] Re: nvidia card disabled after upgrading to 5.0.0-11-generic
*** This bug is a duplicate of bug 1824677 *** https://bugs.launchpad.net/bugs/1824677 ** This bug has been marked a duplicate of bug 1824677 Display only has 640x480 -- 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/1824642 Title: nvidia card disabled after upgrading to 5.0.0-11-generic Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from 5.0.0.8-generic to 5.0.0.11-generic, the nvidia card suddenly became "disabled". I own a laptop with hybrid GPU stack, intel + nvidia; nvidia is in charge of display ports. On 5.0.0.8-generic I had only nvidia GPU enabled (discrete mode) and nouveau was able to properly control nvidia and send the signal to my monitor. In hybrid mode this worked as well properly. On 5.0.0.11-generic in discrete mode, linux booted to 640x480 resolution only. When I enabled hybrid mode back, the computer boots into 1920x1200 mode properly, however the display port ports don't work at all, and the "About" screen only lists the Intel GPU, not nvidia. lspci still lists nvidia though. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-11-generic 5.0.0-11.12 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mavi 2324 F pulseaudio /dev/snd/controlC1: mavi 2324 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 20:09:25 2019 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (950 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-11-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-11-generic N/A linux-backports-modules-5.0.0-11-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-03-12 (32 days ago) dmi.bios.date: 02/21/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET83W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824642/+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 1638780] Re: Linux 4.8.0-27-generic Eclipse fail
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- 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/1638780 Title: Linux 4.8.0-27-generic Eclipse fail Status in linux package in Ubuntu: Invalid Bug description: ubuntu-16.10 After updating system, on each launching of Eclipse, system freezed and i have one way - reboot PC. Mouse, keyboord no workin, clock stoped ect. When i booting using Linux 4.8.0-26-generic it OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638780/+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 1806223] Re: Black Screen 18.10 Kernel 4.19.1+
Similar report: bug 1803400 ** Package changed: light-locker (Ubuntu) => linux (Ubuntu) -- 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/1806223 Title: Black Screen 18.10 Kernel 4.19.1+ Status in linux package in Ubuntu: New Bug description: Ubuntu 18.10 Running on VM Fusion 11 latest updates to it, on Imac 2015 Mojave, any kernel past 4.19 example 4.19.1, 4.19.2 it locks to a black screen after boot up and there is nothing u can do. Kernel 4.19 and lower is fine, i went all the way to 4.20 RC4 and black screen no matter what? I googles this and it seems im not the only one with this issue lately? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806223/+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 1782177] Re: Screen sometimes jumps to full brightness on resume from suspend
** Bug watch added: freedesktop.org Bugzilla #108703 https://bugs.freedesktop.org/show_bug.cgi?id=108703 ** Also affects: linux via https://bugs.freedesktop.org/show_bug.cgi?id=108703 Importance: Unknown Status: Unknown -- 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/1782177 Title: Screen sometimes jumps to full brightness on resume from suspend Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Bug description: At night, I usually turn my brightness down as far as it will go using the brightness keys. This makes it dim, but visible and not off. When I walk away for a while, the screen goes to sleep, and when I come back and move the mouse, the screen jumps to full brightness, which is very unpleasant at night. Investigating, it seems that the brightness in intel_backlight is getting reset to 4437, but the one in acpi_video0 reads 0. $ for file in brightness max_brightness actual_brightness; > do > for directory in /sys/class/backlight/intel_backlight/ /sys/class/backlight/acpi_video0/ > do > echo $directory$file : $(cat $directory$file) > done > done /sys/class/backlight/intel_backlight/brightness : 4437 /sys/class/backlight/acpi_video0/brightness : 0 /sys/class/backlight/intel_backlight/max_brightness : 4437 /sys/class/backlight/acpi_video0/max_brightness : 15 /sys/class/backlight/intel_backlight/actual_brightness : 4437 /sys/class/backlight/acpi_video0/actual_brightness : 0 After I press the button to increase the brightness one notch, they are back in sync, and then I can turn it back down as well. $ for file in brightness max_brightness actual_brightness; > do >for directory in /sys/class/backlight/intel_backlight/ /sys/class/backlight/acpi_video0/ > do > echo $directory$file : $(cat $directory$file) > done > done /sys/class/backlight/intel_backlight/brightness : 53 /sys/class/backlight/acpi_video0/brightness : 1 /sys/class/backlight/intel_backlight/max_brightness : 4437 /sys/class/backlight/acpi_video0/max_brightness : 15 /sys/class/backlight/intel_backlight/actual_brightness : 53 /sys/class/backlight/acpi_video0/actual_brightness : 1 This is on a fresh install of xubuntu 18.04. Seems like a regression from 16.04, which I ran on the same laptop without this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1782177/+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 1803268] Re: Ubuntu 18.10 after Blank Screen System Will NOT Unblank
Possibly a duplicate of bug 1801609. -- 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/1803268 Title: Ubuntu 18.10 after Blank Screen System Will NOT Unblank Status in linux package in Ubuntu: Confirmed Bug description: Toshiba Satellite C650 (embedded Intel HD Graphics 3000) running Xubuntu 18.10. Once the Toshiba's Screen has Blanked, it will not unblank with normal Keystrokes or Mouse Events. My "Work around": Plugging an External Monitor into the Satellite C650's VGA Port, which will then unblank the Toshiba's Screen!!! version.log Ubuntu 4.18.0-10.11-generic 4.18.12 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: houston2335 F pulseaudio CurrentDesktop: XFCE Date: Tue Nov 13 22:42:09 2018 InstallationDate: Installed on 2018-11-01 (12 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: TOSHIBA Satellite C650 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=9d27207e-4cea-4a3f-9e73-35d175aa6a19 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 1.30 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.30:bd11/21/2011:svnTOSHIBA:pnSatelliteC650:pvrPSC2EC-07J001:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite C650 dmi.product.sku: PSC2EC-07J001 dmi.product.version: PSC2EC-07J001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803268/+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 1802712] Re: Doesn't work a touchpad on Lenovo 330-15IGM 81d1
** Package changed: xfce4-notifyd (Ubuntu) => linux (Ubuntu) -- 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/1802712 Title: Doesn't work a touchpad on Lenovo 330-15IGM 81d1 Status in linux package in Ubuntu: Incomplete Bug description: I think the touchpad doesn't work on linux kernel 4.18 and less, because it works fine with kernel 4.19.1. I'm using Ubuntu 18.10 now. My laptop: https://psref.lenovo.com/Detail/Lenovo_Laptops/ideapad_330_15_Intel?M=81D1003SRU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802712/+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 1782177] Re: Screen sometimes jumps to full brightness on resume from suspend
** Package changed: xfce4-power-manager (Ubuntu) => linux (Ubuntu) -- 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/1782177 Title: Screen sometimes jumps to full brightness on resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: At night, I usually turn my brightness down as far as it will go using the brightness keys. This makes it dim, but visible and not off. When I walk away for a while, the screen goes to sleep, and when I come back and move the mouse, the screen jumps to full brightness, which is very unpleasant at night. Investigating, it seems that the brightness in intel_backlight is getting reset to 4437, but the one in acpi_video0 reads 0. $ for file in brightness max_brightness actual_brightness; > do > for directory in /sys/class/backlight/intel_backlight/ /sys/class/backlight/acpi_video0/ > do > echo $directory$file : $(cat $directory$file) > done > done /sys/class/backlight/intel_backlight/brightness : 4437 /sys/class/backlight/acpi_video0/brightness : 0 /sys/class/backlight/intel_backlight/max_brightness : 4437 /sys/class/backlight/acpi_video0/max_brightness : 15 /sys/class/backlight/intel_backlight/actual_brightness : 4437 /sys/class/backlight/acpi_video0/actual_brightness : 0 After I press the button to increase the brightness one notch, they are back in sync, and then I can turn it back down as well. $ for file in brightness max_brightness actual_brightness; > do >for directory in /sys/class/backlight/intel_backlight/ /sys/class/backlight/acpi_video0/ > do > echo $directory$file : $(cat $directory$file) > done > done /sys/class/backlight/intel_backlight/brightness : 53 /sys/class/backlight/acpi_video0/brightness : 1 /sys/class/backlight/intel_backlight/max_brightness : 4437 /sys/class/backlight/acpi_video0/max_brightness : 15 /sys/class/backlight/intel_backlight/actual_brightness : 53 /sys/class/backlight/acpi_video0/actual_brightness : 1 This is on a fresh install of xubuntu 18.04. Seems like a regression from 16.04, which I ran on the same laptop without this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782177/+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 1798353] Re: When waking from suspend screen remains blank
Then this is not a bug in xfce4-power-manager which is only active after starting the Xfce session. What hardware is that exactly? ** Package changed: xfce4-power-manager (Ubuntu) => linux (Ubuntu) -- 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/1798353 Title: When waking from suspend screen remains blank Status in linux package in Ubuntu: New Bug description: After install of Xubuntu 18.04 When placing my laptop into suspend the screen remains blank when I try to wake it. I know that the laptop has woken because the power & cpu lights come on. I am also able to suspend the laptop by using the suspend hotkey. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798353/+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 451282] Re: display is fully dimmed after resume from suspend
Please open a new report if you still encounter this issue in any of the currently supported Ubuntu releases. ** Changed in: xfce4-power-manager (Ubuntu) Status: Confirmed => Invalid -- 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/451282 Title: display is fully dimmed after resume from suspend Status in linux package in Ubuntu: Won't Fix Status in xfce4-power-manager package in Ubuntu: Invalid Bug description: Binary package hint: gnome-power-manager When I resume from suspend (while on AC power), the laptop display brightness is set to it's lowest level, even when I had the brightness turned all the way up before. Interestingly enough, this only seems to happen on the first suspend after a reboot. Once I have turned up the display brightness again using the function keys, the next suspend/resume cycle will work normally (until the next reboot). Finally, when I use the function keys to increase the brightness after a suspend, I see that the brightness level in the notification bar indicates that the brightness is set to the maximum. Only after repeated adjustments with the function keys, the indicator 'resets' and reflects the true display brightness level. I'm using the proprietary nvidia display driver, but I've never had this problem before in Jaunty. Also, in case it makes a difference, I've set my laptop to suspend on lid closure since that's the way I generally suspend the laptop. ProblemType: Bug Architecture: amd64 CheckboxSubmission: 464ed6184a4fbf79d6e3084c58b13de8 CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Wed Oct 14 09:46:16 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: gnome-power-manager 2.28.0-0ubuntu6 ProcEnviron: PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.46-generic SourcePackage: gnome-power-manager Uname: Linux 2.6.31-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/451282/+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 1591043] Re: xubuntu 16.04 on the haswell platform random restart
Was this issue resolved? ** Package changed: xfdesktop4 (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1591043 Title: xubuntu 16.04 on the haswell platform random restart Status in linux package in Ubuntu: Incomplete Bug description: Recently，I am use the xubuntu 16.04 on the haswell platform.I found my haswell's device random restart,when log in the xubuntu about 10 minutes,but it doesn't happen every time. The random reboot is similar to use the watchdog(directly power off and then automatically power on ). Now,I can't find any message about this issue. Any help will be grateful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1591043/+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 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out
Looks like the next step would be to test with an older NVIDIA driver version from the Ubuntu repository, and maybe with the slightly newer version 390.77 from the NVIDIA website also. ** Changed in: xfce4 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1767711 Title: Nvidia+XFCE: Totem window is see-through during playback, colours washed out Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in totem package in Ubuntu: New Status in xfce4 package in Ubuntu: Invalid Bug description: Since the upgrade to Ubuntu 18.04, the Totem player will show everything behind it during playback, and the colours of the video are washed-out. https://i.imgur.com/0AwJMmf.jpg I did not find 'tranparency' nor 'opacity' setting in the program preferences, and the colour adjudgement settings are pinned to +/-0. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Apr 28 14:56:29 2018 InstallationDate: Installed on 2016-06-05 (692 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: totem UpgradeStatus: Upgraded to bionic on 2018-04-27 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1767711/+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 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out
I suggested to test with MATE's compositing window manager "marco" also. Any results? Another test case would be to use xfwm4 with disabled compositor plus "compton" (standalone compositing manager). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1767711 Title: Nvidia+XFCE: Totem window is see-through during playback, colours washed out Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in totem package in Ubuntu: New Status in xfce4 package in Ubuntu: Incomplete Bug description: Since the upgrade to Ubuntu 18.04, the Totem player will show everything behind it during playback, and the colours of the video are washed-out. https://i.imgur.com/0AwJMmf.jpg I did not find 'tranparency' nor 'opacity' setting in the program preferences, and the colour adjudgement settings are pinned to +/-0. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Apr 28 14:56:29 2018 InstallationDate: Installed on 2016-06-05 (692 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: totem UpgradeStatus: Upgraded to bionic on 2018-04-27 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1767711/+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 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out
What output do you get when opening the Totem player from a terminal window? The builtin compositor can be disabled via xfwm4-tweaks-settings, and that will most likely prevent the issue from occurring. Other than that, I suggest to test with a different window manager (e.g. "marco --replace", afterwards "xfwm4 --replace"). ** Changed in: xfce4 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1767711 Title: Nvidia+XFCE: Totem window is see-through during playback, colours washed out Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in totem package in Ubuntu: New Status in xfce4 package in Ubuntu: Incomplete Bug description: Since the upgrade to Ubuntu 18.04, the Totem player will show everything behind it during playback, and the colours of the video are washed-out. https://i.imgur.com/0AwJMmf.jpg I did not find 'tranparency' nor 'opacity' setting in the program preferences, and the colour adjudgement settings are pinned to +/-0. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Apr 28 14:56:29 2018 InstallationDate: Installed on 2016-06-05 (692 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: totem UpgradeStatus: Upgraded to bionic on 2018-04-27 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1767711/+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 1543418] Re: Closing lid causes system hang
Which hardware is that exactly? -- 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/1543418 Title: Closing lid causes system hang Status in linux package in Ubuntu: Incomplete Bug description: I have been having this problem for a past few weeks. I have been using this system for almost 1 year. I use with the power setting to suspend my system when I close the lid. In the past few weeks sometimes when I close the lid, the system doesn't gets suspended. Instead, it gets stuck. When i reopen the lid screen will be back and nothing can bring the system back. I have to restart the system by pressing the power key. No key is working during this state. I tried pressing num lock and no response. It happened rarely before. But for past few days, my system has been getting stuck like this more. Before this, I used to have system crash suddenly and lose all data without any reasons. I am fairly new to ubuntu I don't know how to diagnose these things. Please help me. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543418/+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 1543418] Re: Closing lid causes system hang
Is this problem still present in current Ubuntu releases? ** Package changed: xubuntu-default-settings (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1543418 Title: Closing lid causes system hang Status in linux package in Ubuntu: Incomplete Bug description: I have been having this problem for a past few weeks. I have been using this system for almost 1 year. I use with the power setting to suspend my system when I close the lid. In the past few weeks sometimes when I close the lid, the system doesn't gets suspended. Instead, it gets stuck. When i reopen the lid screen will be back and nothing can bring the system back. I have to restart the system by pressing the power key. No key is working during this state. I tried pressing num lock and no response. It happened rarely before. But for past few days, my system has been getting stuck like this more. Before this, I used to have system crash suddenly and lose all data without any reasons. I am fairly new to ubuntu I don't know how to diagnose these things. Please help me. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543418/+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 1687274] Re: Boot fails waiting for /dev/disk/by-uuid
Did a kernel update or the upgrade to a newer Ubuntu release resolve this problem? ** Package changed: xubuntu-meta (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1687274 Title: Boot fails waiting for /dev/disk/by-uuid Status in linux package in Ubuntu: Incomplete Bug description: The system is stuck waiting 90 seconds for the /dev/disk/by-uuid/* devices to show up. When dropping me to a shell, they do exist. Forcing the system to fsck (by removing power) makes no difference. After rebooting 1-5 times it suddenly completes booting. So it seems it might be a race condition. = Workaround = If I boot once in recovery mode, then the next boot will mostly complete just fine. OK as a workaround, but a horrible solution. I can even just run `systemctl reboot` from recovery mode - no need to boot fully. Running `reboot`, however, does not work. Attached: working$ cat ls-dev-disk-by-uuid working$ cat journalctl-xb failing$ cat ls-dev-disk-by-uuid failing$ cat journalctl-xb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687274/+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 1638780] Re: Linux 4.8.0-27-generic Eclipse fail
Was this issue resolved? ** Package changed: xubuntu-meta (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1638780 Title: Linux 4.8.0-27-generic Eclipse fail Status in linux package in Ubuntu: Incomplete Bug description: ubuntu-16.10 After updating system, on each launching of Eclipse, system freezed and i have one way - reboot PC. Mouse, keyboord no workin, clock stoped ect. When i booting using Linux 4.8.0-26-generic it OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638780/+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 1730321] Re: Ubuntu VM is not detecting the disks connected to Availa beach (LSI/Avago) in Pass Thru mode
** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: xubuntu-meta (Ubuntu) Status: Confirmed => Invalid -- 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/1730321 Title: Ubuntu VM is not detecting the disks connected to Availa beach (LSI/Avago) in Pass Thru mode Status in linux package in Ubuntu: Incomplete Status in xubuntu-meta package in Ubuntu: Invalid Bug description: Below is my setup details: C240 M4 24HDD server with AVB card (FW 24.12.1-0048) and Boot SSDs. Installed ESXi 6.0U1b in the boot SSD in AHCI mode. Updated the latest ESXi Native driver on this. (VMWare-Native-6.610.17.00) Created a VM and Installed Ubuntu 14.04.04. AVB card has one RAID1 VD, one JBOD and all other UG drives. Assigned the AVB controller as a Pass thorugh to ESXi host. Added AVB controller as a Pass through device to the Ubuntu VM. Updated the /etc/vmware/passthru.map file with the device ID and vendor ID of AVB card. Updated the Ubuntu VM with the latest MR driver 06.810 I want to run some IOs to the disks connected to the AVB card from Ubuntu VM. But I am unable to see the disks from the VM. I am seeing so many call traces in the console related to megaraid_sas and see the attached screenshots of the same. Avago is able to reproduce the issue in their lab and see the attached email thread on this discussion. Note : The same scenario is working fine with Ubuntu 12.x series VM's.This issue is occurring both Ubuntu 14.x.x and 16.x.x series guest operating systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730321/+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
