[Touch-packages] [Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore
Networked fails to set the IP address between leases if IP address changes on Ubuntu Core. The network fails to renew a lease, specifically, it fails to change IPv4. If anyone is searching a good job click here https://careerjobs360.in/ ** Attachment added: "job-vs-career-og.png" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721223/+attachment/5241750/+files/job-vs-career-og.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1721223 Title: Networkd fail to set ip address between leases if ip address changes on UbuntuCore Status in Snappy: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Zesty: Won't Fix Status in systemd source package in Artful: Fix Released Bug description: [Impact] * networkd fails to renew a lease, specifically it fails to change IPv4 address via DHCP renew/rebind. * networkd relies on a kernel feature to promote secondary IPv4 address to primary, upon primary address lease expiry. * this sysctl tunable was not enabled by default in systemd. [Test Case] Add a device, and assign two IPv4 addresses. First one, with a short lease time. Second one, with a different ip and a longer lease time. Second one should be treated as secondary ip address, and upon expiry of the first one, should be promoted and become primary ip address. The below scripted instructions simulate this: sudo ip link add name testleases type dummy sudo ip address add 192.0.2.10/27 dev testleases \ valid_lft 5 preferred_lft 5 sudo ip address add 192.0.2.11/27 dev testleases \ valid_lft 11 preferred_lft 11 ip address list dev testleases | \ grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \ && echo ok || echo not ok ip address list dev testleases | \ grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \ && echo ok || echo not ok sleep 6 ip address list dev testleases | \ grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \ && echo ok || echo not ok sudo ip link del dev testleases [Regression Potential] * This changes the default kernel behaviour, previously upon expiry of the primary address, secondary addresses were removed as well. Which is imho silly. * comparing networkd renewal with isc-dhcp renewal the semantics are quite different. Upon acquiring new ip address, isc-dhcp would instantly flush existing ip address, and add a new one. Networkd add the new address as secondary, and waits for old one to expire first before promoting / switching to using the new ip address. IMHO kernel should have an API to promote secondary ip address to a primary one. * This update also applies other safe-looking options, which are currently also already applied via sysctls shipped in other packages # Source route verification net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.all.rp_filter = 1 # Do not accept source routing net.ipv4.conf.default.accept_source_route = 0 net.ipv4.conf.all.accept_source_route = 0 # Enable hard and soft link protection fs.protected_hardlinks = 1 fs.protected_symlinks = 1 * This update also applies the following upstream/bufferbloat.net recommended setting # Fair Queue CoDel packet scheduler to fight bufferbloat net.core.default_qdisc = fq_codel * [~racb] There are complex network setups out there, such as HA with corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this fix were SRU'd, will all of these things in the wild cope with this sysctl change? [Other Info] * Original bug report Hi there, we found a replicable issue that involves the Ubuntu Core networking and causes complete loss of connectivity. We run a custom board with ubuntu core: the architecure is amrhf. We replicated this issue with an official Ubuntu Core image on a Raspberry Pi: other platform was been tested. It shows that it is a snap core problem which interests networkd: we use the default network stack based on networkd + netplan. Below steps to replicate the issue. 1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes). 2)Boot the board and wait for get an ip from dhcp server 3)Before the lease expires, set a reservation for a different ip address Depending on lease duration before the lease expires( for 10 minute we have 2 minutes before ), networkd configure the new address in addition to the previous one. When the lease expire both ip address ( the prevoius and the new one ) disappear from the interested network interface. Depending on lease duration before the second lease expires ( for 10 minure we have 2 minutes before ) networkd configure only the new ip address on the network interface and the ping
[Touch-packages] [Bug 902535] Re: Unable to print with Lexmark S400 series since upgrade to 11.10
when my Lexmark printer printing blank pages, I solve this issue in this way Press the More button until you find Print Menus. Look under the Paper Menu section for the settings mentioned - Separator Sheets should be set to None, and Blank Pages should be set to Do not Print. If these settings are not correct, change them as follows: Press the button next to Menus on your printer screen. If anyone faces any router issue just click on this www.belkinroutersupportnumber.com/blog/steps-to-fix-belkin-router- error-651/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/902535 Title: Unable to print with Lexmark S400 series since upgrade to 11.10 Status in cups package in Ubuntu: Confirmed Status in cups source package in Precise: Incomplete Bug description: Following the upgrade from 11.04 to 11.10 my Lexmark S405 now is unable to print. After removing all previous drivers (i.e. from a clean install of the printer), I have two options to proceed: If I connect the printer via USB and wait for "auto-detection", the system is able to determine that a Lexmark S405 has been added (and adds the printer as a "S300-S400-Series". However at the same time I get the following error message: "Not supported by this backend. The action is not supported by this backend. Please report a bug as this should not have happened. Provided postscript-driver not supported" The printer is added and does show up in CUPS. The device URI is given as: "://Lexmark/S300-S400%20Series?serial=90T409817388744=1". Previously two packages were also added via the Software Centre ( "lexmark-legacy-wsu (1.0-1)" and "lexmark-inkjet-legacy-wjre (1.0-1)" but my most recent attempt to rectify this fault was following updates to fix bug 897309. On this occasion (following the updated ghostscript) no software was added via the Software Centre. I also have the drivers from Lexmark (the second install option). These drivers will install (but if they detect either of the above mentioned packages then installation will fail) but, once you are prompted to connect the printer via USB the error message highlighted above also appears. The results from this approach is that two printers are installed...but neither of them work. Either method of installing the printer results in the same scenario - the printer is listed as "installed", but items in the print queue remain there without no response from the printer. A Test Page shows the printer as "Processing page 1" before eventually throwing an error. Incidentally it is possible to scan from the printer (it's an all-in- one printer) into Ubuntu, but it seems to be impossible to print out from Ubuntu. Also previous work suggested that this may be connected to bug 883585. Also, despite CUPS referring to itself as 1.5, the intro screen says "what's new in CUPS 1.4". The printer does show up in CUPS, but it seems to be impossible to carry out any maintenance on the printer within CUPS (but this may be my "newbie-ness" showing though). My first bug report so hope I've included everything! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/902535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 902535] Re: Unable to print with Lexmark S400 series since upgrade to 11.10
when my Lexmark printer printing blank pages, I solve this issue in this way Press the More button until you find Print Menus. Look under the Paper Menu section for the settings mentioned - Separator Sheets should be set to None, and Blank Pages should be set to Do not Print. If these settings are not correct, change them as follows: Press the button next to Menus on your printer screen. If anyone faces any router issue just click on this https://www.belkinroutersupportnumber.com/blog/steps-to-fix-belkin- router-error-651/ ** Attachment added: "rou.png" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/902535/+attachment/5204779/+files/rou.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/902535 Title: Unable to print with Lexmark S400 series since upgrade to 11.10 Status in cups package in Ubuntu: Confirmed Status in cups source package in Precise: Incomplete Bug description: Following the upgrade from 11.04 to 11.10 my Lexmark S405 now is unable to print. After removing all previous drivers (i.e. from a clean install of the printer), I have two options to proceed: If I connect the printer via USB and wait for "auto-detection", the system is able to determine that a Lexmark S405 has been added (and adds the printer as a "S300-S400-Series". However at the same time I get the following error message: "Not supported by this backend. The action is not supported by this backend. Please report a bug as this should not have happened. Provided postscript-driver not supported" The printer is added and does show up in CUPS. The device URI is given as: "://Lexmark/S300-S400%20Series?serial=90T409817388744=1". Previously two packages were also added via the Software Centre ( "lexmark-legacy-wsu (1.0-1)" and "lexmark-inkjet-legacy-wjre (1.0-1)" but my most recent attempt to rectify this fault was following updates to fix bug 897309. On this occasion (following the updated ghostscript) no software was added via the Software Centre. I also have the drivers from Lexmark (the second install option). These drivers will install (but if they detect either of the above mentioned packages then installation will fail) but, once you are prompted to connect the printer via USB the error message highlighted above also appears. The results from this approach is that two printers are installed...but neither of them work. Either method of installing the printer results in the same scenario - the printer is listed as "installed", but items in the print queue remain there without no response from the printer. A Test Page shows the printer as "Processing page 1" before eventually throwing an error. Incidentally it is possible to scan from the printer (it's an all-in- one printer) into Ubuntu, but it seems to be impossible to print out from Ubuntu. Also previous work suggested that this may be connected to bug 883585. Also, despite CUPS referring to itself as 1.5, the intro screen says "what's new in CUPS 1.4". The printer does show up in CUPS, but it seems to be impossible to carry out any maintenance on the printer within CUPS (but this may be my "newbie-ness" showing though). My first bug report so hope I've included everything! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/902535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1153488] Re: Treats bluetooth input device batteries as batteries
Bluetooth is one of the best technology to share a data, image, song, picture to one device with another device. if anyone faces Microsoft Outlook click here https://www.outlooktechnicalsupportnumbers.com/blog/microsoft-outlook- not-implemented/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1153488 Title: Treats bluetooth input device batteries as batteries Status in gnome-power-manager package in Ubuntu: Invalid Status in upower package in Ubuntu: Fix Released Status in gnome-power-manager source package in Precise: Invalid Status in upower source package in Precise: Fix Released Status in gnome-power-manager source package in Quantal: Invalid Status in upower source package in Quantal: Won't Fix Status in gnome-power-manager source package in Raring: Invalid Status in upower source package in Raring: Fix Released Status in gnome-power-manager source package in Saucy: Invalid Status in upower source package in Saucy: Fix Released Bug description: [Impact] * There are many Bluetooth devices with battery information inside. When they are treated as system battery, it will make the system poweroff/suspend/hibernate when some Bluetooth device has critical low battery. It is a very annoying behavior for the users. Originally, there is no such Bluetooth battery information until Ubuntu 12.04 brings linux-quantal-lts and linux-raring-lts, so those linux kernels also bring this issue. [Test Case] * Pair some Bluetooth devices, such as Apple Wireless Mouse or Apple Wireless Keyboard. * Click the power indicator and you can find Apple Wireless Mouse is listed as system battery, and there is no Apple Wireless Keyboard. If you open gnome-power-statistics, you can find the 'Supply' field of Apple Wireless Mouse is 'Yes' but it should not be. [Regression Potential] * There is no obvious regression as I know. [Other Info] * Most patches are from upstream, modified to fix the conflicts, and made by the same developer (i.e. fourdollars). * We need another patch from https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d0a934b764c67b4bf626f5b7cf725a6e3066afd2 to make Apple Wireless Keyboard showing. [Original Bug Description] This is a weird one... the system is an HP Pavilion 23 All In One and is powered by a large power supply brick. I currently have an Apple Magic Mouse connected via Bluetooth. As soon as the mouse is connected, the Battery indicator shows up and clicking on that shows that the system is reading my mouse as a battery! See the attached screen shot for what I see in the Power status. Looking at hcitool: ubuntu@201206-11396:~$ hcitool dev Devices: hci0 9C:B7:0D:80:71:DB To make matters even more weird, I actually observed the battery indicator go from full to "Critically Low" and the system suspended itself. Keep in mind, again, that this system has NO battery, it's reading my bluetooth mouse as a battery device. I disconnected the magic mouse and the battery indicator went to Empty Red outline and status showed Battery Disconnected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1 ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 NonfreeKernelModules: wl fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: List of PLAYBACK Hardware Devices card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1726 F pulseaudio Card0.Amixer.info: Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb4 irq 16' Mixer name : 'Realtek ALC269VC' Components : 'HDA:10ec0269,103c2aee,00100202' Controls : 21 Simple ctrls : 10 Date: Mon Mar 11 03:54:36 2013 HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MachineType: Hewlett-Packard a654 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=e2a5f4ae-dfa2-40be-a6c5-3ddb85dcf68e ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-23-generic N/A
[Touch-packages] [Bug 1620054] Re: Google reCaptcha does not work in browser
*** This bug is a duplicate of bug 1599146 *** https://bugs.launchpad.net/bugs/1599146 yes, I m also facing this Google reCaptcha issue, How can I solved this issue. click here https://www.outlooktechnicalsupportnumbers.com/ if anyone faces an outlook issue. ** Attachment added: "out.png" https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1620054/+attachment/5198514/+files/out.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1620054 Title: Google reCaptcha does not work in browser Status in webbrowser-app package in Ubuntu: Confirmed Bug description: I was not able to post a reply on xda developers forum. Recaptcha told me that the browser does not support the widget. It seemed strange since this is a commonly used captcha framework. However, testing with the following test page https://patrickhlauke.github.io/recaptcha/ revealed that reCaptcha is not working at ll in the Ubuntu Browser. Since this is an important verification method these days I would assume someone needs to talk to Google to either allow our User-Agent, or we must fake once again the UA string in some way. This is really a bad thing I know. But what does it help? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1620054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351939] Re: Sending USSD message does not work
I wonder if I could be of any help with this? Could I contribute any error message? Could I be of help in testing? I'd like to see a solution to this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1351939 Title: Sending USSD message does not work Status in Modem Manager Gui: Invalid Status in ModemManager: New Status in modem-manager-gui package in Ubuntu: Invalid Status in modemmanager package in Ubuntu: Confirmed Bug description: The error message says: "Error sending USSD" "GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.freedesktop.ModemManager1.Modem.Modem3gpp.Ussd' on object at path /org/freedesktop/ModemManager1/Modem/5" This is reported upstream here: http://linuxonly.ru/cms/e107_plugins/bug_tracker/bugs.php?0.item.3.22.0 To manage notifications about this bug go to: https://bugs.launchpad.net/modem-manager-gui/+bug/1351939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351939] Re: Sending USSD message does not work
I use a ZTE K3565-Z from Vodafone. In Linuxmint 17 I managed to get this running with patched version from Alex by PPA. In Linuxmint 18 I'm lost - USSD still not working, to balance and no top up from abroad possible. The old PPA version does not work - no modem found. Is there a chance to find a patched Xenial Version in PPA again? Would be great -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1351939 Title: Sending USSD message does not work Status in Modem Manager Gui: Invalid Status in ModemManager: New Status in modem-manager-gui package in Ubuntu: Invalid Status in modemmanager package in Ubuntu: Confirmed Bug description: The error message says: "Error sending USSD" "GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.freedesktop.ModemManager1.Modem.Modem3gpp.Ussd' on object at path /org/freedesktop/ModemManager1/Modem/5" This is reported upstream here: http://linuxonly.ru/cms/e107_plugins/bug_tracker/bugs.php?0.item.3.22.0 To manage notifications about this bug go to: https://bugs.launchpad.net/modem-manager-gui/+bug/1351939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576228] Re: Black borders around all windows
(Switching back to proprietary nVidia driver) results in (graphic corruption after resume from suspend) However it seems there might be some issue related to how shadows are rendered. Using nouveau, there are no shadows, and windows have borders instead of being borderless with shadows. I'm not familiar with: how the shadows are rendered, but there might be some bug with shadow rendering path. ** Attachment added: "Graphic corruption around windows" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576228/+attachment/4685624/+files/Screenshot%20from%202016-06-17%2018-33-08.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1576228 Title: Black borders around all windows Status in xorg package in Ubuntu: New Bug description: There seems to be a bug somewhere in [ kernel OR xorg OR nvidia proprietary driver ] in the display stack. After the laptop ( dell XPS L501X ) resumes from suspend there are wide black borders around all windows with close/minimize/maximize buttons blacked out. [ image attached: black border on all windows ] It occurs inconsistently, as it doesn't happen every time the computer resumes. ( Slight possibility that it usually occurs after long suspend, i.e. resuming after long time ). = Also there seems to be certain amount of performance degradation as if the graphics driver was running at half-strength ( and I don't mean software-only rendering, neither do I mean switch over to nouveau open source driver ) The "nVidia X Server Settings" app suggests its in maximum performance mode. == Adhoc Workaround: switch display layout ( I have an external monitor/TV attached to HDMI port ) changing anything such as arrangement or resolution of the displays, etcetera... corrects the black border issue ( and also possibly performance issue ) This bug has been present in Ubuntu 14.04, 15.04, 15.10 and now in 16.04 as well. ( It was probably present before that as well ) == p.s. this is only partial duplicate of black border issue as the black borders appear on every window, not just windows with new header bars or client side decoration... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 28 18:43:37 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF108M [GeForce GT 435M] [10de:0df2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 435M] [1028:046e] InstallationDate: Installed on 2016-04-23 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. XPS L501X ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-21-generic root=UUID=f657e606-ac2a-49cd-9f3e-fca6a315338d ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0J1VR3 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc.
[Touch-packages] [Bug 1576228] Re: Black borders around all windows
It seems the problem might have something to do with how shadows are rendered, AFAIK using nouveau has disabled shadows (possibly due to lower performance of graphics card on nouveau) however the shadows are enabled using the proprietary Nvidia driver 361.42... I'm just guessing the shadows are disabled as windows are not borderless even using default theme Ambiance/Radiance -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1576228 Title: Black borders around all windows Status in xorg package in Ubuntu: New Bug description: There seems to be a bug somewhere in [ kernel OR xorg OR nvidia proprietary driver ] in the display stack. After the laptop ( dell XPS L501X ) resumes from suspend there are wide black borders around all windows with close/minimize/maximize buttons blacked out. [ image attached: black border on all windows ] It occurs inconsistently, as it doesn't happen every time the computer resumes. ( Slight possibility that it usually occurs after long suspend, i.e. resuming after long time ). = Also there seems to be certain amount of performance degradation as if the graphics driver was running at half-strength ( and I don't mean software-only rendering, neither do I mean switch over to nouveau open source driver ) The "nVidia X Server Settings" app suggests its in maximum performance mode. == Adhoc Workaround: switch display layout ( I have an external monitor/TV attached to HDMI port ) changing anything such as arrangement or resolution of the displays, etcetera... corrects the black border issue ( and also possibly performance issue ) This bug has been present in Ubuntu 14.04, 15.04, 15.10 and now in 16.04 as well. ( It was probably present before that as well ) == p.s. this is only partial duplicate of black border issue as the black borders appear on every window, not just windows with new header bars or client side decoration... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 28 18:43:37 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF108M [GeForce GT 435M] [10de:0df2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 435M] [1028:046e] InstallationDate: Installed on 2016-04-23 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. XPS L501X ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-21-generic root=UUID=f657e606-ac2a-49cd-9f3e-fca6a315338d ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0J1VR3 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/26/2011:svnDellInc.:pnXPSL501X:pvrA08:rvnDellInc.:rn0J1VR3:rvrA08:cvnDellInc.:ct8:cvrA08: dmi.product.name: XPS L501X dmi.product.version: A08
[Touch-packages] [Bug 1576228] Re: Black borders around all windows
Hey penalvch, After almost a day of using nouveau, there doesn't seem to be any black border after resume from suspend, however this might be because of low suspend-resume cycle count. I'll post update if the issue occurs on nouveau. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1576228 Title: Black borders around all windows Status in xorg package in Ubuntu: New Bug description: There seems to be a bug somewhere in [ kernel OR xorg OR nvidia proprietary driver ] in the display stack. After the laptop ( dell XPS L501X ) resumes from suspend there are wide black borders around all windows with close/minimize/maximize buttons blacked out. [ image attached: black border on all windows ] It occurs inconsistently, as it doesn't happen every time the computer resumes. ( Slight possibility that it usually occurs after long suspend, i.e. resuming after long time ). = Also there seems to be certain amount of performance degradation as if the graphics driver was running at half-strength ( and I don't mean software-only rendering, neither do I mean switch over to nouveau open source driver ) The "nVidia X Server Settings" app suggests its in maximum performance mode. == Adhoc Workaround: switch display layout ( I have an external monitor/TV attached to HDMI port ) changing anything such as arrangement or resolution of the displays, etcetera... corrects the black border issue ( and also possibly performance issue ) This bug has been present in Ubuntu 14.04, 15.04, 15.10 and now in 16.04 as well. ( It was probably present before that as well ) == p.s. this is only partial duplicate of black border issue as the black borders appear on every window, not just windows with new header bars or client side decoration... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 28 18:43:37 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF108M [GeForce GT 435M] [10de:0df2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 435M] [1028:046e] InstallationDate: Installed on 2016-04-23 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. XPS L501X ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-21-generic root=UUID=f657e606-ac2a-49cd-9f3e-fca6a315338d ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0J1VR3 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/26/2011:svnDellInc.:pnXPSL501X:pvrA08:rvnDellInc.:rn0J1VR3:rvrA08:cvnDellInc.:ct8:cvrA08: dmi.product.name: XPS L501X dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2
Re: [Touch-packages] [Bug 1576228] Re: Black borders around all windows
Hey Christopher, Always a pleasure to contribute. I have switched over to nouveau, but since the issue occurs INconsistently I cannot immediately reproduce the bug condition. I'll most likely have to wait and watch for suspend-resume cycles to check if the bug gets reproduced . Meanwhile there seems to be bug: title bar appearing transparent with nouveau as I have posted on bug tracker On Mon, Jun 13, 2016, 10:05 AM Christopher M. Penalver < christopher.m.penal...@gmail.com> wrote: > John Smith, thank you for reporting this and helping make Ubuntu better. > > To clarify, if you remove the nvidia drivers is this still reproducible? > > ** Tags added: latest-bios-a08 > > ** Changed in: xorg (Ubuntu) >Importance: Undecided => Medium > > ** Changed in: xorg (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1576228 > > Title: > Black borders around all windows > > Status in xorg package in Ubuntu: > Incomplete > > Bug description: > There seems to be a bug somewhere in [ kernel OR xorg OR nvidia > proprietary driver ] in the display stack. > After the laptop ( dell XPS L501X ) resumes from suspend there are wide > black borders around all windows with close/minimize/maximize buttons > blacked out. > > [ image attached: black border on all windows ] > > It occurs inconsistently, as it doesn't happen every time the computer > resumes. > ( Slight possibility that it usually occurs after long suspend, i.e. > resuming after long time ). > > = > > Also there seems to be certain amount of performance degradation as if > the graphics driver was running at half-strength ( and I don't mean > software-only rendering, neither do I mean switch over to nouveau open > source driver ) > > The "nVidia X Server Settings" app suggests its in maximum performance > mode. > > > == > > Adhoc Workaround: switch display layout ( I have an external > monitor/TV attached to HDMI port ) changing anything such as > arrangement or resolution of the displays, etcetera... corrects the > black border issue ( and also possibly performance issue ) > > This bug has been present in Ubuntu 14.04, 15.04, 15.10 and now in > 16.04 as well. ( It was probably present before that as well ) > > > == > > p.s. this is only partial duplicate of black border issue as the black > borders appear on every window, not just windows with new header bars > or client side decoration... > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: xorg 1:7.7+13ubuntu3 > ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 > Uname: Linux 4.4.0-21-generic x86_64 > NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia > .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: > '/proc/driver/nvidia/gpus/:02:00.0' > .proc.driver.nvidia.registry: Binary: "" > .proc.driver.nvidia.version: >NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 > 18:10:58 PDT 2016 >GCC version: gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) > .proc.driver.nvidia.warnings.fbdev: >Your system is not currently configured to drive a VGA console >on the primary VGA device. The NVIDIA Linux graphics driver >requires the use of a text-mode VGA console. Use of other console >drivers including, but not limited to, vesafb, may result in >corruption and stability problems, and is not supported. > .tmp.unity_support_test.0: > > ApportVersion: 2.20.1-0ubuntu2 > Architecture: amd64 > BootLog: [ [0;32m OK [0m] Started LSB: Speech Dispatcher. > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: compiz > CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' > CompositorUnredirectFSW: true > CurrentDesktop: Unity > Date: Thu Apr 28 18:43:37 2016 > DistUpgraded: Fresh install > DistroCodename: xenial > DistroVariant: ubuntu > DkmsStatus: >bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed >nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >NVIDIA Corporation GF108M [GeForce GT 435M] [10de:0df2] (rev a1) > (prog-if 00 [VGA controller]) > Subsystem: Dell GF108M [GeForce GT
[Touch-packages] [Bug 1576228] Re: Black borders around all windows
I sorted out the suspend issue (turns out I had inserted a faulty memory card in the laptop and as it was unable to get data 'sync' to it hence systemd was assuming that suspend transaction would be destructive :D ) I'll try to use nouveau for a few days, see if black border issue persists or comes up. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1576228 Title: Black borders around all windows Status in xorg package in Ubuntu: Incomplete Bug description: There seems to be a bug somewhere in [ kernel OR xorg OR nvidia proprietary driver ] in the display stack. After the laptop ( dell XPS L501X ) resumes from suspend there are wide black borders around all windows with close/minimize/maximize buttons blacked out. [ image attached: black border on all windows ] It occurs inconsistently, as it doesn't happen every time the computer resumes. ( Slight possibility that it usually occurs after long suspend, i.e. resuming after long time ). = Also there seems to be certain amount of performance degradation as if the graphics driver was running at half-strength ( and I don't mean software-only rendering, neither do I mean switch over to nouveau open source driver ) The "nVidia X Server Settings" app suggests its in maximum performance mode. == Adhoc Workaround: switch display layout ( I have an external monitor/TV attached to HDMI port ) changing anything such as arrangement or resolution of the displays, etcetera... corrects the black border issue ( and also possibly performance issue ) This bug has been present in Ubuntu 14.04, 15.04, 15.10 and now in 16.04 as well. ( It was probably present before that as well ) == p.s. this is only partial duplicate of black border issue as the black borders appear on every window, not just windows with new header bars or client side decoration... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 28 18:43:37 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF108M [GeForce GT 435M] [10de:0df2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 435M] [1028:046e] InstallationDate: Installed on 2016-04-23 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. XPS L501X ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-21-generic root=UUID=f657e606-ac2a-49cd-9f3e-fca6a315338d ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0J1VR3 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/26/2011:svnDellInc.:pnXPSL501X:pvrA08:rvnDellInc.:rn0J1VR3:rvrA08:cvnDellInc.:ct8:cvrA08: dmi.product.name: XPS L501X dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz
[Touch-packages] [Bug 1576228] Re: Black borders around all windows
Another thing that might help in triage is as per the workaround specified, Changing screen position (in a 2 monitor setup: laptop + HD TV(via HDMI) ) corrects the problem, Important thing to note is that you can use [ nvidia-x-server-settings ] or [ gnome program: Displays] to do it, in either case as soon as I click 'apply' the black border issue is corrected. i.e. [ 'change position of either screen' -> 'click apply' -> screens blackout -> screens re-appear -> revert to previous configuration (or not) -> black borders gone ] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1576228 Title: Black borders around all windows Status in xorg package in Ubuntu: Incomplete Bug description: There seems to be a bug somewhere in [ kernel OR xorg OR nvidia proprietary driver ] in the display stack. After the laptop ( dell XPS L501X ) resumes from suspend there are wide black borders around all windows with close/minimize/maximize buttons blacked out. [ image attached: black border on all windows ] It occurs inconsistently, as it doesn't happen every time the computer resumes. ( Slight possibility that it usually occurs after long suspend, i.e. resuming after long time ). = Also there seems to be certain amount of performance degradation as if the graphics driver was running at half-strength ( and I don't mean software-only rendering, neither do I mean switch over to nouveau open source driver ) The "nVidia X Server Settings" app suggests its in maximum performance mode. == Adhoc Workaround: switch display layout ( I have an external monitor/TV attached to HDMI port ) changing anything such as arrangement or resolution of the displays, etcetera... corrects the black border issue ( and also possibly performance issue ) This bug has been present in Ubuntu 14.04, 15.04, 15.10 and now in 16.04 as well. ( It was probably present before that as well ) == p.s. this is only partial duplicate of black border issue as the black borders appear on every window, not just windows with new header bars or client side decoration... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 28 18:43:37 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF108M [GeForce GT 435M] [10de:0df2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 435M] [1028:046e] InstallationDate: Installed on 2016-04-23 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. XPS L501X ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-21-generic root=UUID=f657e606-ac2a-49cd-9f3e-fca6a315338d ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0J1VR3 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias:
[Touch-packages] [Bug 1576228] Re: Black borders around all windows
1. The black border issue is inconsistent so cannot verify whether using nouveau fixed it or not. 2. My HDD seems to be giving-up as the read-error-rate is at: 6033 ->Which seems to result in btrfs errors/panic in syslog -> -> Also which seems to prevent `suspend` at the moment 3. There's a different issue with nouveau driver -> The title bar of 'currently-selected' window becomes almost transparent, the issue was not present with proprietary driver. [ image attached: 2 'Files/Nautilus' windows with one selected (title bar transparent) ] 4. One last thing, with proprietary driver, Google Chrome GPU process used to crash intermittently, and WebGL used to crash every-time on visiting maps.google.com, but it doesn't crash with nouveau. ( p.s. I know it's a chromium bug, but it might help in finding the problem in display stack. ** Attachment added: "An image of window displaying vidual glitch" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576228/+attachment/4683181/+files/Screenshot%20from%202016-06-14%2001-54-18.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1576228 Title: Black borders around all windows Status in xorg package in Ubuntu: Incomplete Bug description: There seems to be a bug somewhere in [ kernel OR xorg OR nvidia proprietary driver ] in the display stack. After the laptop ( dell XPS L501X ) resumes from suspend there are wide black borders around all windows with close/minimize/maximize buttons blacked out. [ image attached: black border on all windows ] It occurs inconsistently, as it doesn't happen every time the computer resumes. ( Slight possibility that it usually occurs after long suspend, i.e. resuming after long time ). = Also there seems to be certain amount of performance degradation as if the graphics driver was running at half-strength ( and I don't mean software-only rendering, neither do I mean switch over to nouveau open source driver ) The "nVidia X Server Settings" app suggests its in maximum performance mode. == Adhoc Workaround: switch display layout ( I have an external monitor/TV attached to HDMI port ) changing anything such as arrangement or resolution of the displays, etcetera... corrects the black border issue ( and also possibly performance issue ) This bug has been present in Ubuntu 14.04, 15.04, 15.10 and now in 16.04 as well. ( It was probably present before that as well ) == p.s. this is only partial duplicate of black border issue as the black borders appear on every window, not just windows with new header bars or client side decoration... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 28 18:43:37 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF108M [GeForce GT 435M] [10de:0df2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 435M] [1028:046e] InstallationDate: Installed on 2016-04-23 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. XPS L501X
[Touch-packages] [Bug 1576228] [NEW] Black borders around all windows
Public bug reported: There seems to be a bug somewhere in [ kernel OR xorg OR nvidia proprietary driver ] in the display stack. After the laptop ( dell XPS L501X ) resumes from suspend there are wide black borders around all windows with close/minimize/maximize buttons blacked out. [ image attached: black border on all windows ] It occurs inconsistently, as it doesn't happen every time the computer resumes. ( Slight possibility that it usually occurs after long suspend, i.e. resuming after long time ). = Also there seems to be certain amount of performance degradation as if the graphics driver was running at half-strength ( and I don't mean software-only rendering, neither do I mean switch over to nouveau open source driver ) The "nVidia X Server Settings" app suggests its in maximum performance mode. == Adhoc Workaround: switch display layout ( I have an external monitor/TV attached to HDMI port ) changing anything such as arrangement or resolution of the displays, etcetera... corrects the black border issue ( and also possibly performance issue ) This bug has been present in Ubuntu 14.04, 15.04, 15.10 and now in 16.04 as well. ( It was probably present before that as well ) == p.s. this is only partial duplicate of black border issue as the black borders appear on every window, not just windows with new header bars or client side decoration... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 28 18:43:37 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF108M [GeForce GT 435M] [10de:0df2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 435M] [1028:046e] InstallationDate: Installed on 2016-04-23 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. XPS L501X ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-21-generic root=UUID=f657e606-ac2a-49cd-9f3e-fca6a315338d ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0J1VR3 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/26/2011:svnDellInc.:pnXPSL501X:pvrA08:rvnDellInc.:rn0J1VR3:rvrA08:cvnDellInc.:ct8:cvrA08: dmi.product.name: XPS L501X dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Apr 28 17:09:49
