[Desktop-packages] [Bug 2035076] Re: Can't enter capital accented letters with Caps Lock on Wayland
@lastexile7gr The package doesn't come automatically with the updates, you have to pass "-t mantic-proposed" when using apt. This is the command I've used to update the mutter package in my system: sudo apt install mutter-common -t mantic-proposed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035076 Title: Can't enter capital accented letters with Caps Lock on Wayland Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: Fix Committed Status in mutter package in Fedora: Unknown Bug description: Impact -- Capital accented letters can't be entered using CAPS LOCK in the Wayland session Test Case - Open a terminal and install basic French support: sudo apt install language-pack-gnome-fr Open the Settings app. In the sidebar, click Keyboard Click +, choose French (France), then choose the French (AZERTY) keyboard Close the Settings app In the top right of the screen, click en and switch the keyboard layout to French (AZERTY) In the text editor, type é (this is the number 2 key on a US English keyboard). Now, press the Caps Lock key to enable Caps Lock. Press the same key. You should get É What Could Go Wrong --- This fix is included in mutter 45.2 so see the master bug for this upstream update: LP: #2043000 Original bug report --- Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. I've noticed that everything works fine using the Live session which still uses X11 session. It looks there's no problem with programs that use xwayland like Gimp and MarkText. WORKAROUND === In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2035076/+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 2035076] Re: Can't enter capital accented letters with Caps Lock on Wayland
OK, it works I've tried version 45.2-0ubuntu3 and can regularly type ÒÀÙÈÉÌ in the text editor, terminal, etc. ** Tags removed: verification-needed-mantic ** Tags added: verification-done-manti ** Tags removed: verification-done-manti ** Tags added: verification-done-mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035076 Title: Can't enter capital accented letters with Caps Lock on Wayland Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: Fix Committed Status in mutter package in Fedora: Unknown Bug description: Impact -- Capital accented letters can't be entered using CAPS LOCK in the Wayland session Test Case - Open a terminal and install basic French support: sudo apt install language-pack-gnome-fr Open the Settings app. In the sidebar, click Keyboard Click +, choose French (France), then choose the French (AZERTY) keyboard Close the Settings app In the top right of the screen, click en and switch the keyboard layout to French (AZERTY) In the text editor, type é (this is the number 2 key on a US English keyboard). Now, press the Caps Lock key to enable Caps Lock. Press the same key. You should get É What Could Go Wrong --- This fix is included in mutter 45.2 so see the master bug for this upstream update: LP: #2043000 Original bug report --- Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. I've noticed that everything works fine using the Live session which still uses X11 session. It looks there's no problem with programs that use xwayland like Gimp and MarkText. WORKAROUND === In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2035076/+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 2035076] Re: Can't enter capital accented letters with Caps Lock on Wayland
> Jeremie, you also have to pass "-t mantic-proposed" in the apt command line. Ok, I've updated the packages to version 45.2 and now I can enter capital accented letters ÒÀÙÈÉÌ as expected. Thank you very much, great job! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035076 Title: Can't enter capital accented letters with Caps Lock on Wayland Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: Fix Committed Status in mutter package in Fedora: Unknown Bug description: Impact -- Capital accented letters can't be entered using CAPS LOCK in the Wayland session Test Case - Open a terminal and install basic French support: sudo apt install language-pack-gnome-fr Open the Settings app. In the sidebar, click Keyboard Click +, choose French (France), then choose the French (AZERTY) keyboard Close the Settings app In the top right of the screen, click en and switch the keyboard layout to French (AZERTY) In the text editor, type é (this is the number 2 key on a US English keyboard). Now, press the Caps Lock key to enable Caps Lock. Press the same key. You should get É What Could Go Wrong --- This fix is included in mutter 45.2 so see the master bug for this upstream update: LP: #2043000 Original bug report --- Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. I've noticed that everything works fine using the Live session which still uses X11 session. It looks there's no problem with programs that use xwayland like Gimp and MarkText. WORKAROUND === In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2035076/+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 2035076] Re: Can't enter capital accented letters with Caps Lock on Wayland
I wanted to test the updated version of mutter so a couple of days ago I enabled the `proposed` repository, but I didn't receive any updates. I don't know if I did something wrong, however my sources.list has the line: deb http://archive.ubuntu.com/ubuntu mantic-proposed main multiverse restricted universe -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035076 Title: Can't enter capital accented letters with Caps Lock on Wayland Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Mantic: Fix Committed Status in mutter package in Fedora: Unknown Bug description: Impact -- Capital accented letters can't be entered using CAPS LOCK in the Wayland session Test Case - Open a terminal and install basic French support: sudo apt install language-pack-gnome-fr Open the Settings app. In the sidebar, click Keyboard Click +, choose French (France), then choose the French (AZERTY) keyboard Close the Settings app In the top right of the screen, click en and switch the keyboard layout to French (AZERTY) In the text editor, type é (this is the number 2 key on a US English keyboard). Now, press the Caps Lock key to enable Caps Lock. Press the same key. You should get É What Could Go Wrong --- This fix is included in mutter 45.2 so see the master bug for this upstream update: LP: #2043000 Original bug report --- Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. I've noticed that everything works fine using the Live session which still uses X11 session. It looks there's no problem with programs that use xwayland like Gimp and MarkText. WORKAROUND === In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2035076/+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 2035076] Re: Wayland - Capital accented letters not recognized
** Description changed: - Some programs (not only Gnome Text Editor... I had to choose at least one package to report the bug) don't recognize Italian accented capital letters. + Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. + I've noticed that everything works fine using the Live session which still uses X11 session. - This problem shows up with: - - Gnome Text Editor (deb) - - Libre Office (snap and deb) - - Firefox (snap) - - Sublime Text (snap) - - Gedit (snap) - - Gnome Terminal (deb) + It looks there's no problem with programs that use xwayland like Gimp + and MarkText. - No problems with the following software (all snap): - - Thunderbird - - MarkText - - Telegram + WORKAROUND === - WORKAROUND: - In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] - If I want É: + If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === - ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2035076 Title: Wayland - Capital accented letters not recognized Status in wayland package in Ubuntu: New Bug description: Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. I've noticed that everything works fine using the Live session which still uses X11 session. It looks there's no problem with programs that use xwayland like Gimp and MarkText. WORKAROUND === In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2035076/+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 2035076] Re: Wayland - Capital accented letters not recognized
changed from gnome-text-editor to wayland package ** Summary changed: - Capital accented letters not recognized + Wayland - Capital accented letters not recognized ** Package changed: gnome-text-editor (Ubuntu) => wayland (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2035076 Title: Wayland - Capital accented letters not recognized Status in wayland package in Ubuntu: New Bug description: Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. I've noticed that everything works fine using the Live session which still uses X11 session. It looks there's no problem with programs that use xwayland like Gimp and MarkText. WORKAROUND === In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2035076/+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 2035076] [NEW] Capital accented letters not recognized
Public bug reported: Some programs (not only Gnome Text Editor... I had to choose at least one package to report the bug) don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. This problem shows up with: - Gnome Text Editor (deb) - Libre Office (snap and deb) - Sublime Text (snap) - Gedit (snap) No problems with the following software (all snap): - Firefox - Thunderbird - MarkText - Telegram ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-text-editor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/2035076 Title: Capital accented letters not recognized Status in gnome-text-editor package in Ubuntu: New Bug description: Some programs (not only Gnome Text Editor... I had to choose at least one package to report the bug) don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. This problem shows up with: - Gnome Text Editor (deb) - Libre Office (snap and deb) - Sublime Text (snap) - Gedit (snap) No problems with the following software (all snap): - Firefox - Thunderbird - MarkText - Telegram ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/2035076/+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 1964541] Re: Cannot rearrange Firefox (snap) browser tabs in Wayland sessions
It looks like any kind of drag and drop doesn't work in the snap version of Firefox under Wayland session. First I've noticed that I couldn't personalize the toolbar, therefore I've open this bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1760449 Then I realized also tabs couldn't be moved. ** Bug watch added: Mozilla Bugzilla #1760449 https://bugzilla.mozilla.org/show_bug.cgi?id=1760449 -- 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/1964541 Title: Cannot rearrange Firefox (snap) browser tabs in Wayland sessions Status in firefox package in Ubuntu: Confirmed Bug description: Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2, attempting to re-arrange tabs in Firefox fails. Click and drag the tab and release, nothing changes. The next click to the tab is ignored. syslog has the following: Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. gnome-shell 42~beta-1ubuntu2 Firefox Snap 98.0-3 (1073) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964541/+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 1898462] Re: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell
@Timo Aaltonen The new package fix the problem. Good job! Here what I've done: 1. enabled the proposed repository 2. updated gnome-shell-extension-desktop-icons to version 20.04.0+git20200908-5~ubuntu20.10.0 3. Test case: created a file in the desktop and tried drag & drop inside an open folder. As expected drag & drop doesn't work, but now the shell doesn't freeze. ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1898462 Title: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome- shell Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons source package in Groovy: Fix Committed Status in gnome-shell-extension-desktop-icons source package in Hirsute: Fix Released Bug description: [Impact] Drag and drop files from Desktop to Nautilus freezes gnome-shell in Ubuntu 20.10. There is no way to recover without killing gnome-shell externally or rebooting. [Test Case] 1. Create a file in ~/Desktop 2. Open a nautilus (Files) window of a different directory. 3. Drag the new file from the desktop into the nautilus (Files) window. The shell should not become unresponsive. Also, the drag is expected to fail and snap back. That's a different issue (bug 1813441) not being fixed here. [Where problems could occur] An extension with syntax errors may fail to load leaving the user with reduced shell functionality. A more faulty extension might crash the entire shell after loading. [Other Info] Patch is in bug 1898005. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 4 12:19:26 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-03 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-10-03T01:41:41.633547 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1898462/+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 1865169] Re: volume and light not working in Gnome Shell 3.35
Just to confirm gjs version 1.63.92-1 fixes the problem. (P.S. focal-proposed activated) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1865169 Title: volume and light not working in Gnome Shell 3.35 Status in GNOME Shell: Unknown Status in gjs package in Ubuntu: Fix Committed Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading to GNOME shell 3.35, the speaker icon in top bar is missing and both volume and light sliders are set to 0. Changing volume and light from keyboard works, but has no effect in gnome shell dropdown. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-16.19-generic 5.4.22 Uname: Linux 5.4.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 18:57:54 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-01 (118 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1865169/+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 1733394] Re: Mines does not recognize a new high score has happened
Mines 3.26.0 - Ubuntu 17.10 I found a related upstream bug report: https://bugzilla.gnome.org/show_bug.cgi?id=789399 ** Bug watch added: GNOME Bug Tracker #789399 https://bugzilla.gnome.org/show_bug.cgi?id=789399 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-mines in Ubuntu. https://bugs.launchpad.net/bugs/1733394 Title: Mines does not recognize a new high score has happened Status in gnome-mines package in Ubuntu: Confirmed Bug description: When I finish a mines game successfully and the time is better than some of the other times in the scores list, the slower times are not replaced with the new, faster time that I just scored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mines/+bug/1733394/+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 1631750] Re: Language installation doesn't work in Ubuntu GNOME 16.10 Settings app
I found the same problem with the language setup on Ubuntu 17.10. This could be related to the new Gnome Settings (just let me know if you think I should open a new bug report). I was running Ubuntu 17.10 in Italian language, previously installed with the old Gnome Settings. I wanted to switch to English language but I couldn't because of this bug. Following the steps of the bug description, the only difference was the terminal warning: "Language it_IT not installed, trying to install it" ..which is a bit strange because the system was already set to Italian, I wanted to set the en_US.UTF-8. I've noticed that while trying to change the language settings, the strings in /etc/default/locale don't change at all. :: WORKAROUND 1- sudo nano /etc/default/locale 2- Comment or delete the existing strings end write the following: LANG="en_US.UTF-8" LANGUAGE="en" If I want to go back to the Italian setup I just need to write the following: LANG="it_IT.UTF-8" LANGUAGE="it:en" 3- Press [Ctrl]+O and [Enter] to save the file. Press then [Ctrl]+X to exit from Nano editor. 4- Log-out and log-in again or restart the system. After the log-in the system is asking if you would like to update the names of the folders into $HOME (Desktop, Music, Video, etc..). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1631750 Title: Language installation doesn't work in Ubuntu GNOME 16.10 Settings app Status in Ubuntu GNOME: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Bug description: What happens 1. From a terminal in Ubuntu GNOME, enter gnome-control-center region My locale is set to en_US so my terminal emits common-cc-panel-WARNING **: Language en_US.UTF-8 not installed, trying to install it 2. Click Language. 3. Click the 3-dot "more" button at the bottom of the popup. 4. Select French (France). Click Done. My terminal emits: common-cc-panel-WARNING **: Language fr_FR not installed, trying to install it French isn't actually installed. What should happen == PackageKit should install French. Language in the main window should change from English (United States) to French (France). Unfortunately because of how the system works, it would still require a log out and log in for the change to actually take effect. Other Info === Installation of audio/video codes appears to work just fine: 1. Uninstall the extra codecs (assuming you clicked the box in the installer to install third-party softwarel) sudo apt uninstall ubuntu-restricted-addons sudo apt autoremove Download this file https://archive.org/download/buckminsterfullereverythingiknow01/01001.rm It opens in Totem and session-installer prompts to install gstreamer1.0-plugins-ugly. Installation completed successfully and I was able to play the file. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-control-center 1:3.20.1-2ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 9 09:52:01 2016 InstallationDate: Installed on 2016-10-07 (1 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20161007) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1631750/+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 1716341] Re: Settings for external monitor are deleted after reboot, suspension, log out
** Summary changed: - Settings for external monitor are delete after reboot, suspension, log out + Settings for external monitor are deleted after reboot, suspension, log out -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1716341 Title: Settings for external monitor are deleted after reboot, suspension, log out Status in gnome-control-center package in Ubuntu: New Bug description: New Gnome Settings on Ubuntu 17.10 Settings for external monitor are working but after reboot/suspension /log-out log-in, the system will not remember the setup. Example: 1- open Gnome Settings and select "Devices → Displays" 2- set the external monitor as "Single Display" and click on "Apply" 3- log-out After log-in the laptop monitor will be set as default instead of the external monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1716341/+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 1714410] Re: Can't change display configuration, Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig
I have open a new bug related to the fact that gnome settings doesn't "remember" the setup for external monitors after log out, restart.. Please add comment here: https://bugs.launchpad.net/ubuntu/+source /gnome-control-center/+bug/1716341 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1714410 Title: Can't change display configuration, Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Since last night's updates, I can no longer change screen resolution or monitor alignment in gnome-control-center anymore (in gnome-shell running under Wayland). gnome-control-center fails silently in the GUI but reports this from the command line: (gnome-control-center:5887): display-cc-panel-WARNING **: Error applying configuration: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig All the available display modes are listed in gnome-control-center (you just can't select them). On the initial login, xrandr only showed two screen resolutions, one for screen XWAYLAND0 of 3840x2160 and another for XWAYLAND1 of 1920x1080, but after unplugging the external monitor and re-plugging it, now xrandr shows eDP-1 with all available modes and HDMI-1 with all available modes (you just can't select them from g-c-c). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.3-0ubuntu6 Uname: Linux 4.13.0-041300rc7-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 1 11:47:50 2017 InstallationDate: Installed on 2017-08-16 (15 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: gnome-control-center UpgradeStatus: Upgraded to artful on 2017-08-17 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1714410/+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 1716341] [NEW] Settings for external monitor are delete after reboot, suspension, log out
Public bug reported: New Gnome Settings on Ubuntu 17.10 Settings for external monitor are working but after reboot/suspension /log-out log-in, the system will not remember the setup. Example: 1- open Gnome Settings and select "Devices → Displays" 2- set the external monitor as "Single Display" and click on "Apply" 3- log-out After log-in the laptop monitor will be set as default instead of the external monitor. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: artful ** Tags added: artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1716341 Title: Settings for external monitor are delete after reboot, suspension, log out Status in gnome-control-center package in Ubuntu: New Bug description: New Gnome Settings on Ubuntu 17.10 Settings for external monitor are working but after reboot/suspension /log-out log-in, the system will not remember the setup. Example: 1- open Gnome Settings and select "Devices → Displays" 2- set the external monitor as "Single Display" and click on "Apply" 3- log-out After log-in the laptop monitor will be set as default instead of the external monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1716341/+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 1714410] Re: Can't change display configuration, Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig
After the latest updates with the new Gnome Settings I can change the setup for external monitors. The problem is that the system doesn't remember the settings, so after a log out (or restart or suspension, etc..) I need always to open again Gnome Settings and set the external monitor as "Single Display". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1714410 Title: Can't change display configuration, Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Since last night's updates, I can no longer change screen resolution or monitor alignment in gnome-control-center anymore (in gnome-shell running under Wayland). gnome-control-center fails silently in the GUI but reports this from the command line: (gnome-control-center:5887): display-cc-panel-WARNING **: Error applying configuration: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig All the available display modes are listed in gnome-control-center (you just can't select them). On the initial login, xrandr only showed two screen resolutions, one for screen XWAYLAND0 of 3840x2160 and another for XWAYLAND1 of 1920x1080, but after unplugging the external monitor and re-plugging it, now xrandr shows eDP-1 with all available modes and HDMI-1 with all available modes (you just can't select them from g-c-c). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.3-0ubuntu6 Uname: Linux 4.13.0-041300rc7-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 1 11:47:50 2017 InstallationDate: Installed on 2017-08-16 (15 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: gnome-control-center UpgradeStatus: Upgraded to artful on 2017-08-17 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1714410/+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 1715021] Re: Gnome settings for primary/secondary monitor are not working
*** This bug is a duplicate of bug 1714410 *** https://bugs.launchpad.net/bugs/1714410 @Peter Magnusson Thanks, I've marked the report as duplicated of Bug #1714410. Hopefully this bug will disappear once the new Gnome Settings will be updated to the new version https://bugs.launchpad.net/ubuntu/+source /gnome-control-center/+bug/1714410/comments/4 ** This bug has been marked a duplicate of bug 1714410 Can't change display configuration, Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1715021 Title: Gnome settings for primary/secondary monitor are not working Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Fresh install of Ubuntu 17.10 (laptop + external monitor). Running "Settings → Displays → Primary (or Secondary)", all the options: - Primary - Secondary Display - Mirror - Turn Off are not working. Also "Arrange Combined Displays" is not working. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 4 22:33:37 2017 InstallationDate: Installed on 2017-09-04 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1715021/+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 1715021] [NEW] Gnome settings for primary/secondary monitor are not working
Public bug reported: Fresh install of Ubuntu 17.10 (laptop + external monitor). Running "Settings → Displays → Primary (or Secondary)", all the options: - Primary - Secondary Display - Mirror - Turn Off are not working. Also "Arrange Combined Displays" is not working. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 4 22:33:37 2017 InstallationDate: Installed on 2017-09-04 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: artful gnome-17.10 ** Tags removed: amd64 apport-bug ** Tags added: gnome-17.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1715021 Title: Gnome settings for primary/secondary monitor are not working Status in gnome-control-center package in Ubuntu: New Bug description: Fresh install of Ubuntu 17.10 (laptop + external monitor). Running "Settings → Displays → Primary (or Secondary)", all the options: - Primary - Secondary Display - Mirror - Turn Off are not working. Also "Arrange Combined Displays" is not working. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 4 22:33:37 2017 InstallationDate: Installed on 2017-09-04 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1715021/+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 1376212] Re: BQ Aquaris E4.5 Android Phone not recognised by libmtp
Hi Brian, It works. I've just enabled the -proposed and installed the libmtp 1.1.6-20-g1b9f164-1ubuntu2.1 package. Then I've connected the BQ 4.5 via USB.cable. Nautilus starts automatically as expected. Thanks, well done! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1376212 Title: BQ Aquaris E4.5 Android Phone not recognised by libmtp Status in libmtp package in Ubuntu: Fix Released Status in libmtp source package in Trusty: Fix Committed Bug description: * Impact the device is not listed in the desktop interface * Test case somebody owning the device there should connect it to an ubuntu desktop and check that it's correctly list * Regression potential check that mtp devices keep working as they should (listed in nautilus, can copy files, etc) The bq Aquaris E4.5 phone is not recognised when in MTP file mode by Ubuntu. idVendor=2a47, idProduct=2012 Tested on a trusty/14.04 laptop with all recommended apt-get update's as of 5th Sep (sorry for long reporting delay). Reproduction Proceedure: - Plug a BQ Aquaris E4.5 Android phone into the Ubuntu desktop via a USB cable - Expect to see a natuilus window pop up, with the option to browse and copy files to the phone's file system - Actual result: no response from the Ubuntu host. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1376212/+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 1376212] Re: BQ Aquaris E4.5 Android Phone not recognised by libmtp
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1376212 Title: BQ Aquaris E4.5 Android Phone not recognised by libmtp Status in libmtp package in Ubuntu: Fix Released Status in libmtp source package in Trusty: Fix Committed Bug description: * Impact the device is not listed in the desktop interface * Test case somebody owning the device there should connect it to an ubuntu desktop and check that it's correctly list * Regression potential check that mtp devices keep working as they should (listed in nautilus, can copy files, etc) The bq Aquaris E4.5 phone is not recognised when in MTP file mode by Ubuntu. idVendor=2a47, idProduct=2012 Tested on a trusty/14.04 laptop with all recommended apt-get update's as of 5th Sep (sorry for long reporting delay). Reproduction Proceedure: - Plug a BQ Aquaris E4.5 Android phone into the Ubuntu desktop via a USB cable - Expect to see a natuilus window pop up, with the option to browse and copy files to the phone's file system - Actual result: no response from the Ubuntu host. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1376212/+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 1467649] [NEW] bq 4.5 not mounting on Ubuntu 14.04
Public bug reported: Ubuntu 14.04 doesn't mount the BQ Aquaris 4.5 once it is connected with usb cable. Everything works fine on Ubuntu 14.10 and 15.04. Workaround (found here http://ubuntuforums.org/showthread.php?t=2270325) Installing an updated version of libmtp from this repo https://launchpad.net/~phablet-team/+archive/ubuntu/tools: sudo add-apt-repository ppa:phablet-team/tools sudo apt-get update sudo apt-get upgrade libmtp-common, libmtp-runtime and libmtp9 will be updated. Once connected via usb, the smart phone will be browsable from the file manager and the icon will appear on the launcher. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libmtp-common 1.1.6-20-g1b9f164-1ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jun 22 21:09:18 2015 Dependencies: InstallationDate: Installed on 2015-03-15 (99 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) PackageArchitecture: all SourcePackage: libmtp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libmtp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1467649 Title: bq 4.5 not mounting on Ubuntu 14.04 Status in libmtp package in Ubuntu: New Bug description: Ubuntu 14.04 doesn't mount the BQ Aquaris 4.5 once it is connected with usb cable. Everything works fine on Ubuntu 14.10 and 15.04. Workaround (found here http://ubuntuforums.org/showthread.php?t=2270325) Installing an updated version of libmtp from this repo https://launchpad.net/~phablet-team/+archive/ubuntu/tools: sudo add-apt-repository ppa:phablet-team/tools sudo apt-get update sudo apt-get upgrade libmtp-common, libmtp-runtime and libmtp9 will be updated. Once connected via usb, the smart phone will be browsable from the file manager and the icon will appear on the launcher. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libmtp-common 1.1.6-20-g1b9f164-1ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jun 22 21:09:18 2015 Dependencies: InstallationDate: Installed on 2015-03-15 (99 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) PackageArchitecture: all SourcePackage: libmtp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1467649/+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 1294027] Re: [Fujitsu LIFEBOOK A512] Touchpad scrolling and middle click doesn't work
Touchpad works out of the box on Ubuntu 14.04 with linux 3.13.0-20-generic This was the xinput output with the old kernel 3.13.0-19-generic: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ PS/2 Generic Mouseid=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] and now with 3.13.0-20-generic: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS GlidePoint id=13 [slave pointer (2)] ⎜ ↳ ALPS PS/2 Device Great! -- 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/1294027 Title: [Fujitsu LIFEBOOK A512] Touchpad scrolling and middle click doesn't work Status in “xorg” package in Ubuntu: New Bug description: The scrolling and middle click left and right button pushed together doesn't work. WORKAROUND: 1- Downloaded drivers here http://www.dahetral.com/public-download/alps-psmouse-dlkm-for-3-2-and-3-5/view 2- Moved the folder psmouse-alps-1.3 into /usr/src/ 3- cd /usr/src 4- sudo dkms build psmouse/alps-1.3 5- sudo dkms install psmouse/alps-1.3 6- sudo rmmod psmouse sudo modprobe -v psmouse ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Mar 18 10:53:31 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: psmouse, alps-1.3, 3.11.0-18-generic, x86_64: installed psmouse, alps-1.3, 3.11.0-18-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:16c2] InstallationDate: Installed on 2014-03-17 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: FUJITSU LIFEBOOK A512 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic.efi.signed root=UUID=e71a3b11-0c9a-4e83-ade8-1a1090268bd1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.16 dmi.board.name: FJNBB29 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.16:bd10/23/2013:svnFUJITSU:pnLIFEBOOKA512:pvr:rvnFUJITSU:rnFJNBB29:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A512 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Tue Mar 18 10:43:53 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1427 vendor SAM xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1294027/+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 1041916] Re: Touchpad of Fujitsu LifeBook AH532 not recognized
Just to let you know that the touchpad is now working properly on Lifebook A512 with Ubuntu 14.04 and linux 3.13.0-20-generic. I hope it will be the same on Lifebook AH532. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1041916 Title: Touchpad of Fujitsu LifeBook AH532 not recognized Status in “xserver-xorg-input-synaptics” package in Ubuntu: Incomplete Bug description: Hi, on Ubuntu Precise 12.04.1 with kernel 3.2.0-29-generic the touchpad of the Fujitsu LifeBook AH532 (http://www.fujitsu.com/fts/products/computing/pc/notebooks-tablets/all-round/l is not recognized by the kernel. [Update: Same problem on Quantal as of 20120825] /proc/bus/input/device shows only a generic mouse: I: Bus=0011 Vendor=0002 Product=0001 Version= N: Name=PS/2 Generic Mouse Consequently, xinput shows Virtual core pointer id=2[master pointer ↳ Virtual core XTEST pointerid=4[slave pointer ↳ PS/2 Generic Mouseid=13 [slave pointer tpconfig --info reveals that it *is* a synaptic: Found Synaptics Touchpad. Firmware: 8.96 (multiple-byte mode). Sensor type: unknown (0). Geometry: rectangular/landscape/up. Packets: absolute, 80 packets per second. Corner taps disabled; no tap gestures. Edge motion: none. Z threshold: 6 of 7. 2 button mode; corner tap is right button click. Kernel: linux-image-3.2.0-29-generic 3.2.0-29.46 xorg: xserver-xorg-input-synaptics 1.6.2-1ubuntu1~precise1 Yours, Steffen ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-input-synaptics 1.6.2-1ubuntu1~precise1 [modified: usr/share/X11/xorg.conf.d/50-synaptics.conf] ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 Date: Sun Aug 26 20:43:59 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64+mac (20120822.4) MachineType: FUJITSU LIFEBOOK AH532 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-29-generic root=/dev/mapper/fujiama-precise ro persistent quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2012 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.09 dmi.board.name: FJNBB1C dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.09:bd05/22/2012:svnFUJITSU:pnLIFEBOOKAH532:pvr:rvnFUJITSU:rnFJNBB1C:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK AH532 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.7.8-0ubuntu1.4 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3+8.0.2-0ubuntu3.2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1041916/+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 1294027] [NEW] xorg - alps touchpad
Public bug reported: As suggested here: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1041916/comments/45 I run the ubuntu-bug xorg in orderd to get more infos related to bug Bug #1041916 about touchpad not working (scrolling and middle click left and right boutton pushed together) in Fujitsu LifeBook. The touchpad works properly after this workaround: 1- Downloaded drivers here http://www.dahetral.com/public-download/alps-psmouse-dlkm-for-3-2-and-3-5/view 2- Moved the folder psmouse-alps-1.3 into /usr/src/ 3- cd /usr/src 4- sudo dkms build psmouse/alps-1.3 5- sudo dkms install psmouse/alps-1.3 6- sudo rmmod psmouse sudo modprobe -v psmouse ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Mar 18 10:53:31 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: psmouse, alps-1.3, 3.11.0-18-generic, x86_64: installed psmouse, alps-1.3, 3.11.0-18-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:16c2] InstallationDate: Installed on 2014-03-17 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: FUJITSU LIFEBOOK A512 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic.efi.signed root=UUID=e71a3b11-0c9a-4e83-ade8-1a1090268bd1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.16 dmi.board.name: FJNBB29 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.16:bd10/23/2013:svnFUJITSU:pnLIFEBOOKA512:pvr:rvnFUJITSU:rnFJNBB29:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A512 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Tue Mar 18 10:43:53 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1427 vendor SAM xserver.version: 2:1.14.5-1ubuntu2~saucy1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 saucy ubuntu -- 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/1294027 Title: xorg - alps touchpad Status in “xorg” package in Ubuntu: New Bug description: As suggested here: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1041916/comments/45 I run the ubuntu-bug xorg in orderd to get more infos related to bug Bug #1041916 about touchpad not working (scrolling and middle click left and right boutton pushed together) in Fujitsu LifeBook. The touchpad works properly after this workaround: 1- Downloaded drivers here http://www.dahetral.com/public-download/alps-psmouse-dlkm-for-3-2-and-3-5/view 2- Moved the folder psmouse-alps-1.3 into /usr/src/ 3- cd /usr/src 4- sudo dkms build psmouse/alps-1.3 5- sudo dkms install psmouse/alps-1.3 6- sudo rmmod psmouse sudo modprobe -v psmouse ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true
[Desktop-packages] [Bug 1041916] Re: Touchpad of Fujitsu LifeBook AH532 not recognized
@Christopher M. Penalver (penalvch) Here we are: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1294027 Hope it's OK. Now I can describe the workaround, which might be helpful for other users: 1- Downloaded drivers here http://www.dahetral.com/public-download/alps-psmouse-dlkm-for-3-2-and-3-5/view 2- Moved the folder psmouse-alps-1.3 into /usr/src/ 3- cd /usr/src 4- sudo dkms build psmouse/alps-1.3 5- sudo dkms install psmouse/alps-1.3 6- sudo rmmod psmouse sudo modprobe -v psmouse -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1041916 Title: Touchpad of Fujitsu LifeBook AH532 not recognized Status in “xserver-xorg-input-synaptics” package in Ubuntu: Incomplete Bug description: Hi, on Ubuntu Precise 12.04.1 with kernel 3.2.0-29-generic the touchpad of the Fujitsu LifeBook AH532 (http://www.fujitsu.com/fts/products/computing/pc/notebooks-tablets/all-round/l is not recognized by the kernel. [Update: Same problem on Quantal as of 20120825] /proc/bus/input/device shows only a generic mouse: I: Bus=0011 Vendor=0002 Product=0001 Version= N: Name=PS/2 Generic Mouse Consequently, xinput shows Virtual core pointer id=2[master pointer ↳ Virtual core XTEST pointerid=4[slave pointer ↳ PS/2 Generic Mouseid=13 [slave pointer tpconfig --info reveals that it *is* a synaptic: Found Synaptics Touchpad. Firmware: 8.96 (multiple-byte mode). Sensor type: unknown (0). Geometry: rectangular/landscape/up. Packets: absolute, 80 packets per second. Corner taps disabled; no tap gestures. Edge motion: none. Z threshold: 6 of 7. 2 button mode; corner tap is right button click. Kernel: linux-image-3.2.0-29-generic 3.2.0-29.46 xorg: xserver-xorg-input-synaptics 1.6.2-1ubuntu1~precise1 Yours, Steffen ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-input-synaptics 1.6.2-1ubuntu1~precise1 [modified: usr/share/X11/xorg.conf.d/50-synaptics.conf] ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 Date: Sun Aug 26 20:43:59 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64+mac (20120822.4) MachineType: FUJITSU LIFEBOOK AH532 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-29-generic root=/dev/mapper/fujiama-precise ro persistent quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2012 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.09 dmi.board.name: FJNBB1C dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.09:bd05/22/2012:svnFUJITSU:pnLIFEBOOKAH532:pvr:rvnFUJITSU:rnFJNBB1C:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK AH532 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.7.8-0ubuntu1.4 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3+8.0.2-0ubuntu3.2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1041916/+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 1041916] Re: Touchpad of Fujitsu LifeBook AH532 not recognized
Had same problem on Lifebook A512 - Ubuntu 13.10 64bit and 14.04 Live version. The touchpad's scroll and mid-click (Left+Right button) were not working. I tried the commands suggested on #14 and this similar workaround http://nwoki.wordpress.com/2012/10/02/multitouch-fix-for-alps-touchpad Sorry, can't tell which one of the two methods worked, I'm totally noob with regard to kernel modules (made a lot of confiuson and receivde e few error messages)... anyway after a reboot I can tell that the touchpad is now working! This means that there must be something good into the psmouse-alps-1.3 driver (http://www.dahetral.com/public-download/alps-psmouse-dlkm- for-3-2-and-3-5/view) that could fix the problem. If there is any way to help to get more informations (run commands, post file settings...) just let me know. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1041916 Title: Touchpad of Fujitsu LifeBook AH532 not recognized Status in “xserver-xorg-input-synaptics” package in Ubuntu: Incomplete Bug description: Hi, on Ubuntu Precise 12.04.1 with kernel 3.2.0-29-generic the touchpad of the Fujitsu LifeBook AH532 (http://www.fujitsu.com/fts/products/computing/pc/notebooks-tablets/all-round/l is not recognized by the kernel. [Update: Same problem on Quantal as of 20120825] /proc/bus/input/device shows only a generic mouse: I: Bus=0011 Vendor=0002 Product=0001 Version= N: Name=PS/2 Generic Mouse Consequently, xinput shows Virtual core pointer id=2[master pointer ↳ Virtual core XTEST pointerid=4[slave pointer ↳ PS/2 Generic Mouseid=13 [slave pointer tpconfig --info reveals that it *is* a synaptic: Found Synaptics Touchpad. Firmware: 8.96 (multiple-byte mode). Sensor type: unknown (0). Geometry: rectangular/landscape/up. Packets: absolute, 80 packets per second. Corner taps disabled; no tap gestures. Edge motion: none. Z threshold: 6 of 7. 2 button mode; corner tap is right button click. Kernel: linux-image-3.2.0-29-generic 3.2.0-29.46 xorg: xserver-xorg-input-synaptics 1.6.2-1ubuntu1~precise1 Yours, Steffen ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-input-synaptics 1.6.2-1ubuntu1~precise1 [modified: usr/share/X11/xorg.conf.d/50-synaptics.conf] ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 Date: Sun Aug 26 20:43:59 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64+mac (20120822.4) MachineType: FUJITSU LIFEBOOK AH532 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-29-generic root=/dev/mapper/fujiama-precise ro persistent quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2012 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.09 dmi.board.name: FJNBB1C dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.09:bd05/22/2012:svnFUJITSU:pnLIFEBOOKAH532:pvr:rvnFUJITSU:rnFJNBB1C:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK AH532 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.7.8-0ubuntu1.4 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3+8.0.2-0ubuntu3.2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1041916/+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 1282264] [NEW] Middle-click on title bar doesn't work properly
Public bug reported: Middle-click on title bar should put a window behind all the others, but this happens only if a window is maximized. The mid-click on the title bar of a resized window, just doesn’t work. In dconf-editor the option Org → gnome → Desktop → wm → action-middle- click-titlebar is correctly set to 'lower'. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140218.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-10.30-generic 3.13.3 Uname: Linux 3.13.0-10-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 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: Wed Feb 19 21:45:48 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:150a] InstallationDate: Installed on 2014-02-17 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140217) MachineType: FUJITSU LIFEBOOK A530 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-10-generic root=UUID=81fbf282-a456-4198-ad53-9557e7f58d72 ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2010 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.17 dmi.board.name: FJNBB06 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd12/03/2010:svnFUJITSU:pnLIFEBOOKA530:pvr:rvnFUJITSU:rnFJNBB06:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A530 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Feb 19 21:32:28 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 620 vendor LGD xserver.version: 2:1.15.0-1ubuntu6 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 third-party-packages trusty ubuntu ** Description changed: Middle-click on title bar should put a window behind all the others, but this happens only if a window is maximized. The mid-click on the title bar of a resized window, just doesn’t work. In dconf-editor the option Org → gnome → Desktop → wm → action-middle- - click-titlebar is regularly set to 'lower'. + click-titlebar is correctly set to 'lower'. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140218.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-10.30-generic 3.13.3 Uname: Linux 3.13.0-10-generic i686 .tmp.unity.support.test.0: - + ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 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: Wed Feb 19 21:45:48 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: - Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) -Subsystem: Fujitsu Limited. Device [10cf:150a] + Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) + Subsystem: Fujitsu Limited. Device [10cf:150a] InstallationDate: Installed on 2014-02-17 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140217) MachineType: FUJITSU LIFEBOOK A530 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-10-generic root=UUID=81fbf282-a456-4198-ad53-9557e7f58d72 ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2010 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.17 dmi.board.name: FJNBB06 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias:
[Desktop-packages] [Bug 1063871] [NEW] Problems with Gedit and Compiz Grid plugin
Public bug reported: The grid plugin is working with Gedit only using shortcuts. Trying to drag the top bar against the edges (like this http://www.youtube.com/watch?v=5w5OapWK2Xo) doesn't work. And also, after the window have been resized to the top or bottom corners (shortcuts Ctrl + Alt + Num_1 /3/7/9), then it will not be possible to drag the window. To move it again I need first to use the combination Ctrl+Super+Left/Right Arrow, to make the window half size of the screen, then I will be able to move/drag the window again. Can't tell if the problem is Gedit or Compiz. Till now I didn't experienced this problem with other programs, it appends only with Gedit (this is why I thought it could be a problem with Gedit.. but I can be wrong). I had the same problem on an installation of Ubuntu 12.10 and on a 12.10 Live version downloaded today (8 October 2012). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gedit 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu1 Architecture: i386 Date: Mon Oct 8 16:55:35 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120918.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1063871 Title: Problems with Gedit and Compiz Grid plugin Status in “gedit” package in Ubuntu: New Bug description: The grid plugin is working with Gedit only using shortcuts. Trying to drag the top bar against the edges (like this http://www.youtube.com/watch?v=5w5OapWK2Xo) doesn't work. And also, after the window have been resized to the top or bottom corners (shortcuts Ctrl + Alt + Num_1 /3/7/9), then it will not be possible to drag the window. To move it again I need first to use the combination Ctrl+Super+Left/Right Arrow, to make the window half size of the screen, then I will be able to move/drag the window again. Can't tell if the problem is Gedit or Compiz. Till now I didn't experienced this problem with other programs, it appends only with Gedit (this is why I thought it could be a problem with Gedit.. but I can be wrong). I had the same problem on an installation of Ubuntu 12.10 and on a 12.10 Live version downloaded today (8 October 2012). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gedit 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu1 Architecture: i386 Date: Mon Oct 8 16:55:35 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120918.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1063871/+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 965895] Re: WiFi/NetworkManager menu doesn't show all items after booting into LiveCD environment
I have noticed the same situation on a installed and up to date version of Ubuntu 12.04 (32bit). Clicking the NetworkManager icon only four items were available. But after deactivating and then activating the Enable Wireless option, all the items were again available. I tried to log out and start a new session and also to reboot the system. Everything fine in both cases, the NetworkManager was still showing all the items. -- 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/965895 Title: WiFi/NetworkManager menu doesn't show all items after booting into LiveCD environment Status in “network-manager” package in Ubuntu: New Bug description: After I boot in to the LiveCD environment for Ubuntu 12.04, I click on the NetworkManager icon in the top-right of the screen and it's only showing four items: -- | ✓ Enable Networking | ✓ Enable Wireless | -- | | Connection Information | Edit Connections... -- If I then select the Enable Networking or Enable Wireless option to disable that interface and then re-enable it, then the NetworkManager populates with all the normal menu items (listing of all WiFi SSID, VPN connection, etc.). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CasperVersion: 1.312 Date: Tue Mar 27 03:23:48 2012 IfupdownConfig: auto lo iface lo inet loopback LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120325) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/965895/+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
