[Desktop-packages] [Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS
Just upgraded to 18.04.03 and thought I'd check if there was any action on this, but alas, no change. I see you were asking for a journalctl dump. Here's mine from today attached. H/W & driver details are:- *-display UNCLAIMED description: VGA compatible controller product: GP106M [GeForce GTX 1060 Mobile] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list configuration: latency=0 resources: memory:a300-a3ff memory:9000-9fff memory:a000-a1ff ioport:4000(size=128) memory:a400-a407 *-display description: VGA compatible controller product: Intel Corporation vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:28 memory:a200-a2ff memory:8000-8fff ioport:5000(size=64) memory:c-d Hopefully this is what you are after. Regards ** Attachment added: "jnlctl.hdmi" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1771185/+attachment/5284421/+files/jnlctl.hdmi -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1771185 Title: Secondary monitor not connecting in 18.04 LTS Status in xorg-server package in Ubuntu: Confirmed Bug description: I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M (nvidia driver v390) and a Benq W1070 projector. I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects for a split second and then gets disconnected. In Ubuntu 16.04 projector was working fine as a mirror display and extended desktop. Here's what I already tried: - enable the nouveau driver instead of the nvidia driver -> no result - enable the on-board intel board with sudo prime-select intel -> no result - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> no result - disable nouveau driver, disable nvidia driver from the repository and install nvidia driver from nvidia website (both 390 and 396) -> no result - installed CCSM (CompizConfig Settings Manager) and disabled display auto-detection -> no result - played around with the refresh rate (some forums say that the two outputs have to be in sync -> no result - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still the same issue - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 1920x1920 -> nothing - under settings -> devices -> displays I don't see a secondary display (just the main one) I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to day) Here is the output of xrandr the very second when I connect the projector (then HDMI-1-2 goes disconnected and no modes are displayed): ~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 345mm x 194mm 1920x1080 60.02*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.
[Desktop-packages] [Bug 1816032] Re: gtk_widget_destroy reports error
The original package noted was a mistake. The nearest I can guess at for this problem is as above. I couldn't find anything that was obvious for a problem Gtk+3.0 development ** Package changed: ubuntu => libcanberra (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1816032 Title: gtk_widget_destroy reports error Status in libcanberra package in Ubuntu: Incomplete Bug description: I have recently installed Ubuntu 18.04 on a new computer and have a Gtk+3.0 program that reports an error:- Gtk-CRITICAL gtk_widget_is_drawable: assertion 'GTK_IS_WIDGET (widget)' failed The same program runs without error on another computer with 16.04. The problem occurs when a ComboBoxText widget in a container (grid) is destroyed using gtk_widget_destroy. Other widgets may be affected but the problem does not occur for GtkScale widgets. The widget does actually get destroyed, but the message is produced in the process. I have also found that using gtk_container_remove avoids the error, but the docs indicate that this is inefficient and not preferred. I have attached a test program to reproduce the error. It also includes a few other things that I tried to see if they made any difference but to no avail. 'Destroy cbox' is the essential test to reproduce. System details: Description:Ubuntu 18.04.1 LTS Release:18.04 libwxgtk3.0-dev: Installed: (none) Candidate: 3.0.4+dfsg-3 Version table: 3.0.4+dfsg-3 500 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/1816032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816032] Re: gtk_widget_destroy reports error
** Package changed: network-manager-applet (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1816032 Title: gtk_widget_destroy reports error Status in libcanberra package in Ubuntu: Incomplete Bug description: I have recently installed Ubuntu 18.04 on a new computer and have a Gtk+3.0 program that reports an error:- Gtk-CRITICAL gtk_widget_is_drawable: assertion 'GTK_IS_WIDGET (widget)' failed The same program runs without error on another computer with 16.04. The problem occurs when a ComboBoxText widget in a container (grid) is destroyed using gtk_widget_destroy. Other widgets may be affected but the problem does not occur for GtkScale widgets. The widget does actually get destroyed, but the message is produced in the process. I have also found that using gtk_container_remove avoids the error, but the docs indicate that this is inefficient and not preferred. I have attached a test program to reproduce the error. It also includes a few other things that I tried to see if they made any difference but to no avail. 'Destroy cbox' is the essential test to reproduce. System details: Description:Ubuntu 18.04.1 LTS Release:18.04 libwxgtk3.0-dev: Installed: (none) Candidate: 3.0.4+dfsg-3 Version table: 3.0.4+dfsg-3 500 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/1816032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816032] Re: gtk_widget_destroy reports error
Apologies for the mess up. I was looking at a similar bug listed for the network applet. I thought I had changed it, but the first time I tried to save I had a timeout and had to re-enter the details all over. Somehow the network applet must have been set when I re-entered. It was meant to a problem with Gtk+3.0 Dev. Sample code to reproduced is attached. ** Attachment added: "test_cbox_destroy.c" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1816032/+attachment/5239013/+files/test_cbox_destroy.c -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1816032 Title: gtk_widget_destroy reports error Status in Ubuntu: Incomplete Bug description: I have recently installed Ubuntu 18.04 on a new computer and have a Gtk+3.0 program that reports an error:- Gtk-CRITICAL gtk_widget_is_drawable: assertion 'GTK_IS_WIDGET (widget)' failed The same program runs without error on another computer with 16.04. The problem occurs when a ComboBoxText widget in a container (grid) is destroyed using gtk_widget_destroy. Other widgets may be affected but the problem does not occur for GtkScale widgets. The widget does actually get destroyed, but the message is produced in the process. I have also found that using gtk_container_remove avoids the error, but the docs indicate that this is inefficient and not preferred. I have attached a test program to reproduce the error. It also includes a few other things that I tried to see if they made any difference but to no avail. 'Destroy cbox' is the essential test to reproduce. System details: Description:Ubuntu 18.04.1 LTS Release:18.04 libwxgtk3.0-dev: Installed: (none) Candidate: 3.0.4+dfsg-3 Version table: 3.0.4+dfsg-3 500 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1816032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816032] [NEW] gtk_widget_destroy reports error
Public bug reported: I have recently installed Ubuntu 18.04 on a new computer and have a Gtk+3.0 program that reports an error:- Gtk-CRITICAL gtk_widget_is_drawable: assertion 'GTK_IS_WIDGET (widget)' failed The same program runs without error on another computer with 16.04. The problem occurs when a ComboBoxText widget in a container (grid) is destroyed using gtk_widget_destroy. Other widgets may be affected but the problem does not occur for GtkScale widgets. The widget does actually get destroyed, but the message is produced in the process. I have also found that using gtk_container_remove avoids the error, but the docs indicate that this is inefficient and not preferred. I have attached a test program to reproduce the error. It also includes a few other things that I tried to see if they made any difference but to no avail. 'Destroy cbox' is the essential test to reproduce. System details: Description:Ubuntu 18.04.1 LTS Release:18.04 libwxgtk3.0-dev: Installed: (none) Candidate: 3.0.4+dfsg-3 Version table: 3.0.4+dfsg-3 500 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: destroy gtk widget -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1816032 Title: gtk_widget_destroy reports error Status in network-manager-applet package in Ubuntu: New Bug description: I have recently installed Ubuntu 18.04 on a new computer and have a Gtk+3.0 program that reports an error:- Gtk-CRITICAL gtk_widget_is_drawable: assertion 'GTK_IS_WIDGET (widget)' failed The same program runs without error on another computer with 16.04. The problem occurs when a ComboBoxText widget in a container (grid) is destroyed using gtk_widget_destroy. Other widgets may be affected but the problem does not occur for GtkScale widgets. The widget does actually get destroyed, but the message is produced in the process. I have also found that using gtk_container_remove avoids the error, but the docs indicate that this is inefficient and not preferred. I have attached a test program to reproduce the error. It also includes a few other things that I tried to see if they made any difference but to no avail. 'Destroy cbox' is the essential test to reproduce. System details: Description:Ubuntu 18.04.1 LTS Release:18.04 libwxgtk3.0-dev: Installed: (none) Candidate: 3.0.4+dfsg-3 Version table: 3.0.4+dfsg-3 500 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1816032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS
Thought I'd add my 2 cents worth. I only just tried adding a second monitor in addition to my laptop a few days ago and had this problem. Tried many of the suggested solutions - none worked. Works OK in windows 10. Also works OK in 16.04. Tried using a HDMI to digital adapter at the monitor - did not work. OK in windows 10. Alas cannot try the adapter at the computer as no digital or dvi plug. xrandr pretty as in others shown above - HDMI-1 disconnected. Hopefully this will be fixed before too long. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1771185 Title: Secondary monitor not connecting in 18.04 LTS Status in xorg-server package in Ubuntu: Incomplete Bug description: I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M (nvidia driver v390) and a Benq W1070 projector. I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects for a split second and then gets disconnected. In Ubuntu 16.04 projector was working fine as a mirror display and extended desktop. Here's what I already tried: - enable the nouveau driver instead of the nvidia driver -> no result - enable the on-board intel board with sudo prime-select intel -> no result - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> no result - disable nouveau driver, disable nvidia driver from the repository and install nvidia driver from nvidia website (both 390 and 396) -> no result - installed CCSM (CompizConfig Settings Manager) and disabled display auto-detection -> no result - played around with the refresh rate (some forums say that the two outputs have to be in sync -> no result - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still the same issue - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 1920x1920 -> nothing - under settings -> devices -> displays I don't see a secondary display (just the main one) I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to day) Here is the output of xrandr the very second when I connect the projector (then HDMI-1-2 goes disconnected and no modes are displayed): ~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 345mm x 194mm 1920x1080 60.02*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-2 disconnected (normal left inverted right x axis y axis) 1920x1080 (0x258) 148.500MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz 1920x1080 (0x259) 148.500MHz +HSync +VSync h: width 1920 start 2448 end 2492 total 2640 skew0 clock 56.25KHz v: height 1080 start 1084 end 1089 total 1125 clock 50.00Hz 1920x1080 (0x25a) 148.352MHz +HSy
[Desktop-packages] [Bug 1577137] Re: saned.service masked and cannot be unmasked
I'm also having the same or similar problem with my Epson WF-3520. Worked find at 15.10, nothing after 16.04 upgrade. I was a little confused about which set up some of the comments described here. Mine is a printer / scanner directly connected to the router and accessed wirelessly. So in theory needing to set up a backend is not required(?). I have also bugged this separately at #1613027. I've also tested a few mainline kernels to see where the problem starts (it appears to be all the 4.4... series). Reverting to an earlier kernel allows scanning to work which may be a temporary work-around. In any case I've tried the solutions raised here, but did not succeed. Tony -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1577137 Title: saned.service masked and cannot be unmasked Status in sane-backends package in Ubuntu: Confirmed Bug description: After upgrading to 16.04 (from 14.04) I noticed the sane daemon (sane- utils 1.0.25+git20150528-1ubuntu2) was no longer running. Attempting to manually start it results in systems complaining that the service is masked: kjetil at lucien in ~> sudo systemctl start saned Failed to start saned.service: Unit saned.service is masked. Unmasking it does not work: kjetil at lucien in ~> sudo systemctl unmask saned kjetil at lucien in ~> sudo systemctl start saned Failed to start saned.service: Unit saned.service is masked. kjetil at lucien in ~> ps u -C saned USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND kjetil at lucien in ~> ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: sane-utils 1.0.25+git20150528-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 1 13:10:31 2016 InstallationDate: Installed on 2012-08-01 (1368 days ago) InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1) SourcePackage: sane-backends UpgradeStatus: Upgraded to xenial on 2016-04-24 (6 days ago) mtime.conffile..etc.default.saned: 2016-05-01T12:51:02.879807 mtime.conffile..etc.sane.d.saned.conf: 2016-01-10T13:57:20.785810 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1577137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
