[Desktop-packages] [Bug 1721428] [NEW] Artful (17.10) Session logout after screen turned off
Public bug reported: Whenever I turn off my screen, the computer (a desktop PC) logs me out of my session. Here is a discussion thread with users of similar issue: https://ubuntuforums.org/showthread.php?t=2372388=13694312=1#post13694312 ** Affects: gnome-shell Importance: Undecided Status: New ** Tags: artful ** Summary changed: - Session logout after screen turned off + Artful (17.10) Session logout after screen turned off ** Tags added: artful ** Also affects: gnome-shell Importance: Undecided Status: New ** No longer affects: ubuntu-settings (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off Status in GNOME Shell: New Bug description: Whenever I turn off my screen, the computer (a desktop PC) logs me out of my session. Here is a discussion thread with users of similar issue: https://ubuntuforums.org/showthread.php?t=2372388=13694312=1#post13694312 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+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 1714855] [NEW] Stucked in Airplane mode after suspend
Public bug reported: I have updated to the latest version (as of 2017/9/4) of all my package in my Artful. Hardware Platform: HP Spectre X360 (2015) Software Version: 1.8.2-1ubuntu5 Steps to Reproduce on my Laptop: 1. Login to my account. 2. Connect to the wireless network as usual. 3. Suspend the machine by closing the lit. 4. Open up the lit and login again. Expected: The machine works normally. Actually got: The machine stucked at Airplane mode. I can neither disable the airplane mode by the top right menu nor by the network settings UI. The airplane mode stays on every time after I switch it off. I have to reboot to resume the network. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1714855 Title: Stucked in Airplane mode after suspend Status in network-manager package in Ubuntu: New Bug description: I have updated to the latest version (as of 2017/9/4) of all my package in my Artful. Hardware Platform: HP Spectre X360 (2015) Software Version: 1.8.2-1ubuntu5 Steps to Reproduce on my Laptop: 1. Login to my account. 2. Connect to the wireless network as usual. 3. Suspend the machine by closing the lit. 4. Open up the lit and login again. Expected: The machine works normally. Actually got: The machine stucked at Airplane mode. I can neither disable the airplane mode by the top right menu nor by the network settings UI. The airplane mode stays on every time after I switch it off. I have to reboot to resume the network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1714855/+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 1627290] Re: Firefox 49+ multiprocess windows feature (e10s) is disabled by ubufox
*** This bug is a duplicate of bug 1627808 *** https://bugs.launchpad.net/bugs/1627808 This issue cause problem with Firefox touch support (see my ticket here: https://bugzilla.mozilla.org/show_bug.cgi?id=1213342). Please take care of the issue. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubufox in Ubuntu. https://bugs.launchpad.net/bugs/1627290 Title: Firefox 49+ multiprocess windows feature (e10s) is disabled by ubufox Status in ubufox package in Ubuntu: Confirmed Bug description: Firefox 49+ enables e10s by default: https://wiki.mozilla.org/Electrolysis But Ubuntu's "Ubuntu Modifications 3.2" extension disables it. In about:support output it says: "Multiprocess Windows 0/1 (Disabled by add-ons)" If we manually disable "Ubuntu Modifications" extension, it works: "Multiprocess Windows 1/1 (Enabled by default)" I am using Xubuntu 16.04, firefox 49.0+build4-0ubuntu0.16.04.1, xul-ext-ubufox 3.2-0ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubufox/+bug/1627290/+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 1627808] Re: e10s support
I am using Firefox 49 and confirm to have this issue. The page "about:support" shows "Multiprocess Windows" as "0/1 (Disabled by add- ons)". This issue cause problem with Firefox touch support (see my ticket here: https://bugzilla.mozilla.org/show_bug.cgi?id=1213342). Please take care of the issue. Thanks. I'm using Ubuntu 16.10, ubufox 3.2 with Firefox 49. ** Bug watch added: Mozilla Bugzilla #1213342 https://bugzilla.mozilla.org/show_bug.cgi?id=1213342 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1627808 Title: e10s support Status in Ubufox Extension: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Would it be possible to determine whether this add-on is compatible with the e10s "electrolysis" feature of Firefox[1]? If it is, the manifest should say so: [2] This link may help when determining support: [3] Compatibility of this addon with e10s is required to enable the e10s feature, which brings many speedups and enhancements, on default configured ubuntu installations. Thank you! [1]: https://wiki.mozilla.org/Electrolysis [2]: https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#multiprocessCompatible [3]: https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubufox/+bug/1627808/+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 1627290] Re: Firefox 49+ multiprocess windows feature (e10s) is disabled by ubufox
*** This bug is a duplicate of bug 1627808 *** https://bugs.launchpad.net/bugs/1627808 I am using Firefox 49 and confirm to have this issue. The page "about:support" shows "Multiprocess Windows" as "0/1 (Disabled by add-ons)". ** Bug watch added: Mozilla Bugzilla #1213342 https://bugzilla.mozilla.org/show_bug.cgi?id=1213342 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubufox in Ubuntu. https://bugs.launchpad.net/bugs/1627290 Title: Firefox 49+ multiprocess windows feature (e10s) is disabled by ubufox Status in ubufox package in Ubuntu: Confirmed Bug description: Firefox 49+ enables e10s by default: https://wiki.mozilla.org/Electrolysis But Ubuntu's "Ubuntu Modifications 3.2" extension disables it. In about:support output it says: "Multiprocess Windows 0/1 (Disabled by add-ons)" If we manually disable "Ubuntu Modifications" extension, it works: "Multiprocess Windows 1/1 (Enabled by default)" I am using Xubuntu 16.04, firefox 49.0+build4-0ubuntu0.16.04.1, xul-ext-ubufox 3.2-0ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubufox/+bug/1627290/+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 1628039] Re: ubufox makes Electrolysis stopped.
*** This bug is a duplicate of bug 1627808 *** https://bugs.launchpad.net/bugs/1627808 ** This bug is no longer a duplicate of bug 1627290 Firefox 49+ multiprocess windows feature (e10s) is disabled by ubufox ** This bug has been marked a duplicate of bug 1627808 e10s support -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubufox in Ubuntu. https://bugs.launchpad.net/bugs/1628039 Title: ubufox makes Electrolysis stopped. Status in ubufox package in Ubuntu: New Bug description: Firefox has a new feature https://wiki.mozilla.org/Electrolysis. (abbr. e10s) ubufox makes e10s stopped. xul-ext-ubufox is installed by default so it affects all Ubuntu users. xul-ext-ubufox 3.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubufox/+bug/1628039/+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 1627290] Re: Firefox 49+ multiprocess windows feature (e10s) is disabled by ubufox
*** This bug is a duplicate of bug 1627808 *** https://bugs.launchpad.net/bugs/1627808 Forgot to mention: I'm using Ubuntu 16.10, ubufox 3.2 with Firefox 49. ** This bug has been marked a duplicate of bug 1627808 e10s support -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubufox in Ubuntu. https://bugs.launchpad.net/bugs/1627290 Title: Firefox 49+ multiprocess windows feature (e10s) is disabled by ubufox Status in ubufox package in Ubuntu: Confirmed Bug description: Firefox 49+ enables e10s by default: https://wiki.mozilla.org/Electrolysis But Ubuntu's "Ubuntu Modifications 3.2" extension disables it. In about:support output it says: "Multiprocess Windows 0/1 (Disabled by add-ons)" If we manually disable "Ubuntu Modifications" extension, it works: "Multiprocess Windows 1/1 (Enabled by default)" I am using Xubuntu 16.04, firefox 49.0+build4-0ubuntu0.16.04.1, xul-ext-ubufox 3.2-0ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubufox/+bug/1627290/+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
Re: [Desktop-packages] [Bug 1311443] Re: switching input method is not reliable
Tried using the proposed gnome-settings-daemon package for a few days. The input method switch problem didn't appear at all. I think it's safe to say that it fixed this bug. Hope I can see the proposed package on the main repository soon. Thanks. 樹雄 On Fri, Jun 27, 2014 at 10:19 PM, Mantas Kriaučiūnas man...@akl.lt wrote: ** Also affects: gnome-settings-daemon (Baltix) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1311443 Title: switching input method is not reliable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1311443/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1311443 Title: switching input method is not reliable Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “unity-settings-daemon” package in Ubuntu: Invalid Status in “gnome-settings-daemon” package in Baltix: New Bug description: [Impact] Under GNOME Shell, sometimes the input switcher popup (accessible via Super+Space by default) doesn't allow switching beyond the second input source. [Test Case] Under GNOME Shell, open gnome-control-center Region Language Input Sources + Add at least two input sources (I use us, ru, and gr). Then open gnome-control-center Keyboard Shortcuts Typing Switch to next source Set to Super+Space. Try pressing Super+Space to pop open the input switcher. Then press Super+Space again. The input switcher might not switch the second time. It happens unreliably, so if it works, restarting gnome- settings-daemon may allow reproducing the bug. [Regression Potential] The reason this is happening is because of an old patch that enables input switching for non-GNOME desktops (Unity, GNOME Flashback) by handling it in gnome-settings-daemon. But GNOME Shell handles it itself, so gnome-settings-daemon's shortcuts may be conflicting with GNOME Shell's sometimes. The fix is to remove it, which is ok because that code isn't used by those other non-GNOME desktops any more (they use unity-settings-daemon instead). For that reason, there should be low risk of regression. -- The behaviour of switching input method is strange. There are 2 ways to change input method. And both behave against expectation: 1. super-space: When hitting super-space, the system can only switch from English to Chinese. But not the other way round. 2. indicator: When switching language with the indicator, I can select both language. But the indicator is always showing en. OS: Ubuntu 14.04 Input Method: English (US), Chinese (Cangjie) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1311443/+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 1311443] Re: switching input method is not reliable
Thanks Mathew. I've just installed the proposed gnome-settings-daemon. The IM switching seems to be smoother. But since the problem came on- and-off randomly, it's hard to tell if it is really fixed unless I try it a few days. I'll get back to this a few days later. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1311443 Title: switching input method is not reliable Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “unity-settings-daemon” package in Ubuntu: Invalid Bug description: [Impact] Under GNOME Shell, sometimes the input switcher popup (accessible via Super+Space by default) doesn't allow switching beyond the second input source. [Test Case] Under GNOME Shell, open gnome-control-center Region Language Input Sources + Add at least two input sources (I use us, ru, and gr). Then open gnome-control-center Keyboard Shortcuts Typing Switch to next source Set to Super+Space. Try pressing Super+Space to pop open the input switcher. Then press Super+Space again. The input switcher might not switch the second time. It happens unreliably, so if it works, restarting gnome- settings-daemon may allow reproducing the bug. [Regression Potential] The reason this is happening is because of an old patch that enables input switching for non-GNOME desktops (Unity, GNOME Flashback) by handling it in gnome-settings-daemon. But GNOME Shell handles it itself, so gnome-settings-daemon's shortcuts may be conflicting with GNOME Shell's sometimes. The fix is to remove it, which is ok because that code isn't used by those other non-GNOME desktops any more (they use unity-settings-daemon instead). For that reason, there should be low risk of regression. -- The behaviour of switching input method is strange. There are 2 ways to change input method. And both behave against expectation: 1. super-space: When hitting super-space, the system can only switch from English to Chinese. But not the other way round. 2. indicator: When switching language with the indicator, I can select both language. But the indicator is always showing en. OS: Ubuntu 14.04 Input Method: English (US), Chinese (Cangjie) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1311443/+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 1311443] Re: Error switching input method
Situation can go back to normal it you logout and then log back in. The problem seems to relate to service start-up sequence. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1311443 Title: Error switching input method Status in “ibus” package in Ubuntu: Confirmed Bug description: The behaviour of switching input method is strange. There are 2 ways to change input method. And both behave against expectation: 1. super-space: When hitting super-space, the system can only switch from English to Chinese. But not the other way round. 2. indicator: When switching language with the indicator, I can select both language. But the indicator is always showing en. OS: Ubuntu 14.04 Input Method: English (US), Chinese (Cangjie) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1311443/+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 1311443] Re: Error switching input method
It appears again. The situation is unstable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1311443 Title: Error switching input method Status in “ibus” package in Ubuntu: New Bug description: The behaviour of switching input method is strange. There are 2 ways to change input method. And both behave against expectation: 1. super-space: When hitting super-space, the system can only switch from English to Chinese. But not the other way round. 2. indicator: When switching language with the indicator, I can select both language. But the indicator is always showing en. OS: Ubuntu 14.04 Input Method: English (US), Chinese (Cangjie) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1311443/+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 1311443] Re: Error switching input method
Here I made a screencast to illustrate what happen on my system: https://www.youtube.com/watch?v=YKhY5tF7TnMfeature=youtu.be What I did in the video: 1. Type normally in English mode. 2. Hit super-space once. Type in Chinese mode. 3. Hit super-space once again. Still type in Chinese. (I cannot switch to English as expected) 4. Switch to English mode by indicator menu. Types in English mode. 5. Switch to Chinese mode by indicator menu. Types in Chinese mode. Indicator still show en. OS: Ubuntu 14.04 DE: GNOME 3.10 Input method package used: ibus-cangjie -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1311443 Title: Error switching input method Status in “ibus” package in Ubuntu: New Bug description: The behaviour of switching input method is strange. There are 2 ways to change input method. And both behave against expectation: 1. super-space: When hitting super-space, the system can only switch from English to Chinese. But not the other way round. 2. indicator: When switching language with the indicator, I can select both language. But the indicator is always showing en. OS: Ubuntu 14.04 Input Method: English (US), Chinese (Cangjie) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1311443/+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 1311443] Re: Error switching input method
Not the other way around means I cannot switch from English to Chinese (Cangjie) with super-space hot key. My system was upgraded from Ubuntu 13.10. The problem is now fixed by manually open Configuration Language Support and install the package it suggested. Seems iBus + IME are not sufficient to work on their own. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1311443 Title: Error switching input method Status in “ibus” package in Ubuntu: New Bug description: The behaviour of switching input method is strange. There are 2 ways to change input method. And both behave against expectation: 1. super-space: When hitting super-space, the system can only switch from English to Chinese. But not the other way round. 2. indicator: When switching language with the indicator, I can select both language. But the indicator is always showing en. OS: Ubuntu 14.04 Input Method: English (US), Chinese (Cangjie) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1311443/+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 1311443] [NEW] Error switching input method
Public bug reported: The behaviour of switching input method is strange. There are 2 ways to change input method. And both behave against expectation: 1. super-space: When hitting super-space, the system can only switch from English to Chinese. But not the other way round. 2. indicator: When switching language with the indicator, I can select both language. But the indicator is always showing en. OS: Ubuntu 14.04 Input Method: English (US), Chinese (Cangjie) ** Affects: ibus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1311443 Title: Error switching input method Status in “ibus” package in Ubuntu: New Bug description: The behaviour of switching input method is strange. There are 2 ways to change input method. And both behave against expectation: 1. super-space: When hitting super-space, the system can only switch from English to Chinese. But not the other way round. 2. indicator: When switching language with the indicator, I can select both language. But the indicator is always showing en. OS: Ubuntu 14.04 Input Method: English (US), Chinese (Cangjie) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1311443/+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 1296020] Re: [Asus U36JC] Non-existent display detected in both intel driver and nvidia driver (Optimus Laptop) (ubuntu trusty 14.04)
I have a similar problem. `xrandr -q` gives me the below output: Screen 0: minimum 320 x 200, current 2390 x 768, maximum 32767 x 32767 LVDS1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm 1366x768 60.0*+ 1360x768 59.8 60.0 1024x768 60.0 800x60060.3 56.2 640x48059.9 VGA1 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) DP1 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) VGA-1-2 connected 1024x768+1366+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.0* 800x60060.3 56.2 848x48060.0 640x48059.9 1024x768 (0x43) 65.0MHz h: width 1024 start 1048 end 1184 total 1344 skew0 clock 48.4KHz v: height 768 start 771 end 777 total 806 clock 60.0Hz 800x600 (0x44) 40.0MHz h: width 800 start 840 end 968 total 1056 skew0 clock 37.9KHz v: height 600 start 601 end 605 total 628 clock 60.3Hz 800x600 (0x45) 36.0MHz h: width 800 start 824 end 896 total 1024 skew0 clock 35.2KHz v: height 600 start 601 end 603 total 625 clock 56.2Hz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1296020 Title: [Asus U36JC] Non-existent display detected in both intel driver and nvidia driver (Optimus Laptop) (ubuntu trusty 14.04) Status in “xorg” package in Ubuntu: Confirmed Bug description: There is a non existent display detected in both intel driver only and nvidia 331 driver installation. The non existent display is Unknown Display shown in gnome-control-center -- display and CRT-0 in nvidia-settings, and VGA-0 in xrandr -q output. It will cause gdm failed to start. gnome-shell has some crazy layouts. lightdm will only occupy 2/3 of monitor in top left corner. I tested this in intel driver only environment. and nvidia-331 installation environment. My laptop is Asus U36JC. My monitor correct resolution is 1366x768. The following is the output of xrandr -q in gnome-shell with nvidia-331 installed: $ xrandr -q Screen 0: minimum 8 x 8, current 1366 x 768, maximum 8192 x 8192 VGA-0 connected primary 680x384+0+0 (normal left inverted right x axis y axis) 0mm x 0mm panning 1366x768+0+0 680x384 60.0*+ 1366x768 60.0 1360x768 60.0 HDMI-0 disconnected (normal left inverted right x axis y axis) LVDS-1-0 connected 1366x768+0+0 (normal left inverted right x axis y axis) 293mm x 165mm 1366x768 60.0*+ 1360x768 59.8 60.0 1024x768 60.0 60.0 960x720 60.0 928x696 60.1 896x672 60.0 960x600 60.0 960x540 60.0 800x600 60.0 60.3 56.2 840x525 60.0 59.9 800x512 60.2 700x525 60.0 640x512 60.0 720x450 59.9 640x480 60.0 59.9 680x384 59.8 60.0 576x432 60.1 512x384 60.0 400x300 60.3 56.3 320x240 60.1 VGA-1-0 disconnected (normal left inverted right x axis y axis) HDMI-1-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1-0 disconnected (normal left inverted right x axis y axis) 1366x768 (0x46) 69.3MHz h: width 1366 start 1425 end 1464 total 1472 skew 0 clock 47.1KHz v: height 768 start 773 end 782 total 785 clock 60.0Hz 1360x768 (0x48) 72.0MHz h: width 1360 start 1408 end 1440 total 1520 skew 0 clock 47.4KHz v: height 768 start 771 end 781 total 790 clock 60.0Hz 680x384 (0x5c) 36.0MHz h: width 680 start 704 end 720 total 760 skew 0 clock 47.4KHz v: height 384 start 385 end 390 total 395 clock 60.0Hz The following is the output of xrandr -q in lxde with nvidia-331 installed: $ xrandr -q Screen 0: minimum 8 x 8, current 1366 x 768, maximum 8192 x 8192 VGA-0 connected primary 1024x768+31+0 (normal left inverted right x axis y axis) 0mm x 0mm panning 1366x768+0+0 680x38460.0 + 1366x768 60.0 1360x768 60.0 HDMI-0 disconnected (normal left inverted right x axis y axis) LVDS-1-0 connected 1366x768+0+0 (normal left inverted right x axis y axis) 293mm x 165mm 1366x768 60.0*+ 1360x768 59.8 60.0 1024x768 60.0 60.0 960x72060.0 928x69660.1 896x67260.0 960x60060.0 960x54060.0 800x60060.0 60.3 56.2 840x52560.0 59.9 800x51260.2 700x52560.0 640x51260.0 720x45059.9 640x48060.0 59.9 680x38459.8 60.0 576x43260.1 512x38460.0 400x30060.3 56.3 320x24060.1
[Desktop-packages] [Bug 1296020] Re: [Asus U36JC] Non-existent display detected in both intel driver and nvidia driver (Optimus Laptop) (ubuntu trusty 14.04)
VGA-1-2 was never there. When I plug in another monitor, it would be shown as the 3rd monitor. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1296020 Title: [Asus U36JC] Non-existent display detected in both intel driver and nvidia driver (Optimus Laptop) (ubuntu trusty 14.04) Status in “xorg” package in Ubuntu: Confirmed Bug description: There is a non existent display detected in both intel driver only and nvidia 331 driver installation. The non existent display is Unknown Display shown in gnome-control-center -- display and CRT-0 in nvidia-settings, and VGA-0 in xrandr -q output. It will cause gdm failed to start. gnome-shell has some crazy layouts. lightdm will only occupy 2/3 of monitor in top left corner. I tested this in intel driver only environment. and nvidia-331 installation environment. My laptop is Asus U36JC. My monitor correct resolution is 1366x768. The following is the output of xrandr -q in gnome-shell with nvidia-331 installed: $ xrandr -q Screen 0: minimum 8 x 8, current 1366 x 768, maximum 8192 x 8192 VGA-0 connected primary 680x384+0+0 (normal left inverted right x axis y axis) 0mm x 0mm panning 1366x768+0+0 680x384 60.0*+ 1366x768 60.0 1360x768 60.0 HDMI-0 disconnected (normal left inverted right x axis y axis) LVDS-1-0 connected 1366x768+0+0 (normal left inverted right x axis y axis) 293mm x 165mm 1366x768 60.0*+ 1360x768 59.8 60.0 1024x768 60.0 60.0 960x720 60.0 928x696 60.1 896x672 60.0 960x600 60.0 960x540 60.0 800x600 60.0 60.3 56.2 840x525 60.0 59.9 800x512 60.2 700x525 60.0 640x512 60.0 720x450 59.9 640x480 60.0 59.9 680x384 59.8 60.0 576x432 60.1 512x384 60.0 400x300 60.3 56.3 320x240 60.1 VGA-1-0 disconnected (normal left inverted right x axis y axis) HDMI-1-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1-0 disconnected (normal left inverted right x axis y axis) 1366x768 (0x46) 69.3MHz h: width 1366 start 1425 end 1464 total 1472 skew 0 clock 47.1KHz v: height 768 start 773 end 782 total 785 clock 60.0Hz 1360x768 (0x48) 72.0MHz h: width 1360 start 1408 end 1440 total 1520 skew 0 clock 47.4KHz v: height 768 start 771 end 781 total 790 clock 60.0Hz 680x384 (0x5c) 36.0MHz h: width 680 start 704 end 720 total 760 skew 0 clock 47.4KHz v: height 384 start 385 end 390 total 395 clock 60.0Hz The following is the output of xrandr -q in lxde with nvidia-331 installed: $ xrandr -q Screen 0: minimum 8 x 8, current 1366 x 768, maximum 8192 x 8192 VGA-0 connected primary 1024x768+31+0 (normal left inverted right x axis y axis) 0mm x 0mm panning 1366x768+0+0 680x38460.0 + 1366x768 60.0 1360x768 60.0 HDMI-0 disconnected (normal left inverted right x axis y axis) LVDS-1-0 connected 1366x768+0+0 (normal left inverted right x axis y axis) 293mm x 165mm 1366x768 60.0*+ 1360x768 59.8 60.0 1024x768 60.0 60.0 960x72060.0 928x69660.1 896x67260.0 960x60060.0 960x54060.0 800x60060.0 60.3 56.2 840x52560.0 59.9 800x51260.2 700x52560.0 640x51260.0 720x45059.9 640x48060.0 59.9 680x38459.8 60.0 576x43260.1 512x38460.0 400x30060.3 56.3 320x24060.1 VGA-1-0 disconnected (normal left inverted right x axis y axis) HDMI-1-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1-0 disconnected (normal left inverted right x axis y axis) 1366x768 (0x46) 69.3MHz h: width 1366 start 1425 end 1464 total 1472 skew0 clock 47.1KHz v: height 768 start 773 end 782 total 785 clock 60.0Hz 1360x768 (0x48) 72.0MHz h: width 1360 start 1408 end 1440 total 1520 skew0 clock 47.4KHz v: height 768 start 771 end 781 total 790 clock 60.0Hz 1024x768 (0x4a) 65.0MHz h: width 1024 start 1048 end 1184 total 1344 skew0 clock 48.4KHz v: height 768 start 771 end 777 total 806 clock 60.0Hz 680x384 (0x5c) 36.0MHz h: width 680 start 704 end 720 total 760 skew0 clock 47.4KHz v: height 384 start 385 end 390 total 395 clock 60.0Hz Note: this Unknown non-existent display happens in intel driver only environment TOO. If required, I can provide xrandr -q output with that environment. At present, I don't bother to remove/purge my nvidia-331 installation. Please let me know if anything else is required. Thank you very much!
[Desktop-packages] [Bug 410288] Re: Nautilus does not handle FTP timeouts well
I recently added a bug report on Gnome's bug tracker. Please help pumping that up so developer may notice: https://bugzilla.gnome.org/show_bug.cgi?id=707103 ** Bug watch added: GNOME Bug Tracker #707103 https://bugzilla.gnome.org/show_bug.cgi?id=707103 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/410288 Title: Nautilus does not handle FTP timeouts well Status in GVFS: New Status in Nautilus: New Status in “gvfs” package in Ubuntu: Triaged Bug description: Binary package hint: gvfs I connected to a FTP server via gvfs in Nautilus. After some time the FTP connection is closed automatically, as I observed with wireshark (421 No transfer timeout (300 seconds): closing control connection). After that, everytime I open a folder on the FTP server I get only an unexpected end of stream error. To access the FTP server again I have to disconnect and then connect again. Nautilus does not seem to know that the connection closed. A better behaviour IMHO would be to try and reconnect to the FTP server. ProblemType: Bug Architecture: i386 Date: Fri Aug 7 15:16:05 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/nautilus LiveMediaBuild: Ubuntu 9.10 Karmic Koala - Alpha i386 (20090722.2) Package: nautilus 1:2.27.4-0ubuntu4 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-5.24-generic SourcePackage: nautilus Uname: Linux 2.6.31-5-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/410288/+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 1120833] Re: Improve Traditional Chinese default input method list in Raring
We definitely want Quick to be installed by default. Cangjie and Quick is about 50-50 to all Chinese input market here. Others are nearly zero. We usually got asked how to install Quick here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1120833 Title: Improve Traditional Chinese default input method list in Raring Status in “language-selector” package in Ubuntu: In Progress Bug description: Let's review default Traditional Chinese input methods in other big OS first. https://live.gnome.org/InputCJK/MacOSX/Default https://live.gnome.org/InputCJK/Windows/Default Also note that Zhuyin = Phonetic, Jianyi = Quick. The common factor is indeed Phonetic, Cangjie, Quick. Then let's check our default list for Traditional Chinese, it is ibus-chewing and ibus-table-cangjie. http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/raring/language-selector/raring/view/head:/data/pkg_depends#L197 ibus-chewing is indeed a Phonetic input method, we are fine. ibus-table-cangjie is a virtual package for ibus-table-cangjie3, ibus-table-cangjie5, ibus-table-cangjie-big. Do we need three Cangjie input methods? I guess not. cangjie3 and cangjie5 represents two versions of Cangjie scheme, so we need them both at this moment. cangjie-big covers wider range of Chinese character; some of them are so rarely used that I've never seen in my life. So I guess it should be removed from default install since its audience is limited and some, if not many characters are cannot be rendered by our default Chinese fonts. We don't have a Quick input method. I guess ibus-quick-classic is the best candidate. It resemble Windows Quick input method most; you know, even OS X users may switch to a third-party input method to get Windows-like experience back. If the above is TL; DR, my suggestion is that we change the default list to ibus-chewing, ibus-table-cangjie3, ibus-table-cangjie5, ibus- table-quick-classic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1120833/+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
