[Desktop-packages] [Bug 1245745] Re: Loading larger folders with images takes a lot of time
** Changed in: nautilus Importance: Critical = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1245745 Title: Loading larger folders with images takes a lot of time Status in Nautilus: New Status in “nautilus” package in Ubuntu: Triaged Bug description: I have lots of pictures on my computer and they are taken on digital camera. It makes them 1-6 MB each, and it is common to have 300-500 files in one folder. But using Nautilus to navigate there is a huge error, until I can do anything in that folder, it takes more than a minute. The file list does not appear instantly, but files appear as they get a thumbnail. See the attached screen recording, in my case it took more than 1 minute and 10 seconds to be able to do anything in that folder. It is a blocking bug. And thumbs do not have a standard size, like a square, they are shows upper/lower depending on the portrait/landscape type of picture. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Oct 29 05:52:43 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'840x550+49+189' InstallationDate: Installed on 2013-10-19 (10 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1245745/+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 1245315] Re: alacarte fails to write a proper Categories=; line to .desktop files
This issue finds its roots in a problem with the creation and deletion of Applications Menu (aka Main Menu) entries which is explained on: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1245300 Comment #2 there explains the motivation for the present submission in greater detail. It appears not related or limited just to Xfce. Specifically, the key issue of the present submission centres on giving the user GUI-based full control through alacarte to configure the desired allocation of individual menu entries (launchers) to the Application Menu categories. At present, this can only be fully achieved by manually editing .desktop configuration files. Note: Clearly, there is no intention (nor any need) to deviate from the standard menu specifications. It is merely a matter of fully enabling what goes where in the Applications Menu across (as opposed to within) the various menu categories under GUI-based user control. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1245315 Title: alacarte fails to write a proper Categories=; line to .desktop files Status in “alacarte” package in Ubuntu: New Bug description: When creating a new menu entry in the Applications Menu of Xubuntu using the Alacarte Menu Editor (alacarte 3.10.0-1) then alacarte does not enable the writing of a Categories=; attribute in the new .desktop file created in /home//local/share/applications/. Without a recognized and meaningful Categories=; attribute, the new menu entry is relegated by default to the non-specific Other menu category in the Applications Menu of Xubuntu. Moving the newly-created menu entry in question to a more meaningful Applications Menu category (such as, eg, Applications, Office, Systems, etc) by dragging and dropping then fails in alacarte due to the very absence of any Categories=; attribute in the .desktop file. Instead, First, when creating a new menu entry in, for example, Applications, then alacarte should write a corresponding Categories=; attribute line in the newly-made .desktop file. Second, when dragging and dropping the newly-created menu entry in alacarte from, for example, Applications to, for instance, System, then alacarte should amend the Categories=; attribute line in the .desktop file accordingly. Note 1: If alacarte cannot do these things automatically, then it should at least allow the user to choose the Application Menu category, say, from a drop-down list, when creating or editing a menu entry, and write this choice to the corresponding .desktop file in the form of a suitable Categories=; attribute line. Note 2: Resolving this issue by manually editing .desktop files, of course, wholly defeats the very raison d'être of Menu Editor programs such as alacarte. -- System: xubuntu 13.10 32-bit fully up-to-date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1245315/+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 1246597] [NEW] Backup failed
Public bug reported: Backup ends with the error Backup failed and the following message: Traceback (most recent call last): File /usr/bin/duplicity, line 1411, in module with_tempdir(main) File /usr/bin/duplicity, line 1404, in with_tempdir fn() File /usr/bin/duplicity, line 1338, in main restore(col_stats) File /usr/bin/duplicity, line 632, in restore restore_get_patched_rop_iter(col_stats)): File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 526, in Write_ROPaths for ropath in rop_iter: File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 499, in integrate_patch_iters final_ropath = patch_seq2ropath( normalize_ps( patch_seq ) ) File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 463, in patch_seq2ropath assert first.difftype != diff, patch_seq AssertionError: [(('README',) reg), (('README',) reg), (('README',) reg), (('README',) reg), (('README',) reg), (('README',) reg), (('README',) reg)] ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: deja-dup 27.3.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 31 09:53:50 2013 ExecutablePath: /usr/bin/deja-dup InstallationDate: Installed on 2013-04-30 (183 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: deja-dup UpgradeStatus: Upgraded to saucy on 2013-10-16 (14 days ago) ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1246597 Title: Backup failed Status in “deja-dup” package in Ubuntu: New Bug description: Backup ends with the error Backup failed and the following message: Traceback (most recent call last): File /usr/bin/duplicity, line 1411, in module with_tempdir(main) File /usr/bin/duplicity, line 1404, in with_tempdir fn() File /usr/bin/duplicity, line 1338, in main restore(col_stats) File /usr/bin/duplicity, line 632, in restore restore_get_patched_rop_iter(col_stats)): File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 526, in Write_ROPaths for ropath in rop_iter: File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 499, in integrate_patch_iters final_ropath = patch_seq2ropath( normalize_ps( patch_seq ) ) File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 463, in patch_seq2ropath assert first.difftype != diff, patch_seq AssertionError: [(('README',) reg), (('README',) reg), (('README',) reg), (('README',) reg), (('README',) reg), (('README',) reg), (('README',) reg)] ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: deja-dup 27.3.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 31 09:53:50 2013 ExecutablePath: /usr/bin/deja-dup InstallationDate: Installed on 2013-04-30 (183 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: deja-dup UpgradeStatus: Upgraded to saucy on 2013-10-16 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1246597/+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 946945] Re: Strange: dia-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome: package not found
That's because menu-data/dia-common:dia.desktop in app-install-data- ubuntu has this line: X-AppInstall-Package=dia-gnome-gnome-gnome-gnome Michael, can you please look at this? Looks like a bug somewhere in the update script. ** Also affects: app-install-data-ubuntu (Ubuntu) Importance: Undecided Status: New ** Changed in: app-install-data-ubuntu (Ubuntu) Status: New = Triaged ** Changed in: app-install-data-ubuntu (Ubuntu) Importance: Undecided = Medium ** Summary changed: - Strange: dia-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome: package not found + Strange: dia-gnome-gnome-gnome: package not found -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dia in Ubuntu. https://bugs.launchpad.net/bugs/946945 Title: Strange: dia-gnome-gnome-gnome: package not found Status in “app-install-data-ubuntu” package in Ubuntu: Triaged Status in “dia” package in Ubuntu: Confirmed Bug description: Description: Ubuntu precise (development branch) Release: 12.04 dia-gnome: Installato: (nessuno) Candidato: 0.97.2-5 Tabella versione: 0.97.2-5 0 500 http://archive.ubuntu.com/ubuntu/ precise/main i386 Packages When i upgrade the system i get this never seen message... Reading state information... Done dia-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome: package not found ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dia-gnome (not installed) ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9 Uname: Linux 3.2.0-18-generic-pae i686 ApportVersion: 1.94-0ubuntu1 Architecture: i386 Date: Mon Mar 5 10:05:47 2012 ProcEnviron: LANGUAGE=it:en TERM=xterm PATH=(custom, user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: dia UpgradeStatus: Upgraded to precise on 2012-02-17 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/app-install-data-ubuntu/+bug/946945/+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 894412] Re: Cannot install Dia in ubuntu 11.10 via Software Center
*** This bug is a duplicate of bug 946945 *** https://bugs.launchpad.net/bugs/946945 ** This bug is no longer a duplicate of bug 949890 Wrong package name for dia in app-install-data ** This bug has been marked a duplicate of bug 946945 Strange: dia-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome: package not found -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/894412 Title: Cannot install Dia in ubuntu 11.10 via Software Center Status in “software-center” package in Ubuntu: New Bug description: I cannot install Dia in ubuntu 11.10 via Software Center. It finds Dia by search box, but when I click the entry I got the message Cannot find package dia-gnome-gnome. Seems that the second -gnome in the package name is unnecessary. Installing it in the terminal by typing sudo apt-get install dia- gnome works perfectly, so it is propably only bug in the Software Center's database. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: dia-gnome (not installed) ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Thu Nov 24 16:02:42 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) SourcePackage: dia UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/894412/+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 896580] Re: Dia-gnome-gnome is false ubuntu software center directory.
*** This bug is a duplicate of bug 946945 *** https://bugs.launchpad.net/bugs/946945 ** This bug is no longer a duplicate of bug 949890 Wrong package name for dia in app-install-data ** This bug has been marked a duplicate of bug 946945 Strange: dia-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome: package not found -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/896580 Title: Dia-gnome-gnome is false ubuntu software center directory. Status in “software-center” package in Ubuntu: New Bug description: Dia-gnome-gnome is false ubuntu software center directory , (debug) true ubuntu software center directory is dia-gnome. picture http://img856.imageshack.us/img856/2504/screenshotat2026200.png Thanks You ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: software-center 5.0.2ubuntu0.1 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Sat Nov 26 20:09:00 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all SourcePackage: software-center UpgradeStatus: Upgraded to oneiric on 2011-10-21 (35 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/896580/+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 925255] Re: Reading state information... Done dia-gnome-gnome: package not found
*** This bug is a duplicate of bug 946945 *** https://bugs.launchpad.net/bugs/946945 ** This bug is no longer a duplicate of bug 949890 Wrong package name for dia in app-install-data ** This bug has been marked a duplicate of bug 946945 Strange: dia-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome: package not found -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dia in Ubuntu. https://bugs.launchpad.net/bugs/925255 Title: Reading state information... Done dia-gnome-gnome: package not found Status in “dia” package in Ubuntu: New Bug description: i guess the package dia-gnome is not the correct package to open this bug against. The latest dist-upgrade on 12.04 gives me Reading package lists... Done Building dependency tree Reading state information... Done dia-gnome-gnome: package not found these packages were affected by the latest dist-upgrade Die folgenden NEUEN Pakete werden installiert: (the following new packages will be installed) app-install-data linux-headers-3.2.0-12-generic-pae linux-headers-generic-pae lubuntu-software-center python-pysqlite2 Die folgenden Pakete werden aktualisiert (Upgrade): (the following packages will be upgraded) lubuntu-core lubuntu-desktop ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dia-gnome (not installed) ProcVersionSignature: Ubuntu 3.2.0-12.20-generic 3.2.2 Uname: Linux 3.2.0-12-generic i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Thu Feb 2 03:55:40 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426) ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: dia UpgradeStatus: Upgraded to precise on 2011-12-04 (59 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dia/+bug/925255/+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 889340] Re: duplicate data for 'dia' package in Oneiric
*** This bug is a duplicate of bug 946945 *** https://bugs.launchpad.net/bugs/946945 ** This bug is no longer a duplicate of bug 949890 Wrong package name for dia in app-install-data ** This bug has been marked a duplicate of bug 946945 Strange: dia-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome: package not found -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/889340 Title: duplicate data for 'dia' package in Oneiric Status in “software-center” package in Ubuntu: Confirmed Bug description: Searching for dia in the Software Center in Oneiric, the first two results are Diagram editor and Dia Diagram Editor. The first is installable, and has a normal set of info under More Info. The second has no Install button and gives me an error when I click More Info: -- Not found There isn't a software package called dia-gnome-gnome in your current software sources. -- Seems to be a data error, since they're both the same application, but I'm not sure where it's pulling the duplicate data from. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/889340/+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 926633] Re: Trying to install dia from dash results in error
*** This bug is a duplicate of bug 946945 *** https://bugs.launchpad.net/bugs/946945 ** This bug is no longer a duplicate of bug 949890 Wrong package name for dia in app-install-data ** This bug has been marked a duplicate of bug 946945 Strange: dia-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome-gnome: package not found -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/926633 Title: Trying to install dia from dash results in error Status in “software-center” package in Ubuntu: New Bug description: Steps to reproduce: 1) Click on the Dash button 2)Navigate to the Apps tab 3)Type dia in the search bar 4)Click on the Dia Diagram Editor from the Apps Available for Download section 5)software-center is executed but the message There isn't a software package called dia-gnome-gnome in your current software sources appears ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: software-center 5.0.4 ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13 Uname: Linux 3.0.0-15-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Sat Feb 4 14:14:43 2012 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-center UpgradeStatus: Upgraded to oneiric on 2011-10-20 (106 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/926633/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
Now i'ts possible to select (?) keys Shift, Alt, Ctrl and it's combination as a layout switchers. But language keep same. Neither Indicator nor real input be changed. Ctrl+Space works fine like before. -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Invalid Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” source package in Saucy: Fix Released Bug description: A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/1218322. There still remain issues regarding keyboard shortcuts though. To install: sudo add-apt-repository ppa:attente/1218322 sudo apt-get update sudo apt-get upgrade === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the next layout key entry - try entering a key combinaison (e.g ctrl-space) - the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - press and release ctrl+left shift - the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Separate bug reports for individual layout switching hotkey combinations: Super+Space and Shift+Super+Space, found in: * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245137); * Unity session (https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1245136); * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245138); * ubiquity installer (https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1242572). Alt+Shift * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245256) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245258) * Can't set keyboard layout change to Alt+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245926) Ctrl+Shift * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245270) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245268) * Can't set keyboard layout change to Ctrl+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245991) Shift+Shift * Can't set keyboard layout change to Shift+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245272) * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245278) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245280) Bugs which belong to keyboard layout switching: * Hotkeys not functional in non-latin keyboard layout in 13.10 (https://bugs.launchpad.net/unity/+bug/1226962) * Keyboard Layout Options window is missed in gnome-control-center keyboard (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245064) * Unable to set keyboard LED to show alternative layout in gnome-control-center keyboard in Saucy (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245188) * Unable to set Miscellaneous compatibility options in gnome-control-center keyboard in Saucy (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245199) * Keyboard shortcut for changing keyboard layout does not work on lock screen (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1244548) * [FFe] indicator-keyboard not working under greeter (https://bugs.launchpad.net/unity-greeter/+bug/1228207) * Lost ability to remap Caps Lock to Ctrl
[Desktop-packages] [Bug 1234400] Re: Cannot log in users if their Xauthority file is corrupt.
I've just experienced the same story as Mr. Bruno Nova (brunonova). I spent a whole day to shoot the trouble and identified that it's about .Xauthority. I tracked the /var/log/lightdm/lightdm.log and looked into my .Xauthority. I found it contained two entries: snow/unix:1 MIT-MAGIC-COOKIE-1 f8aa6a272ab2e68533175967a9e5d09d snow.mydomain.com.tw/unix:0 MIT-MAGIC-COOKIE-1 1e9a7aeba63b74bef069a3629fe3e80a Removing the 2nd entry, which should be 'snow' instead of 'snow.mydomain.com.tw', made my system recover and logs me in again. (Usually I am the only user of this machine. The :1 entry is created when I successfully login with a new test account, and switch to login my normal account.) I don't know when it was touched and by whom. I have tried to reconfigure postfix the other day. I have changed my /etc/hostname from snow to snow.mydomain.com.tw, but I changed it back later... I think short hostname is better for my administration. Such condition rarely happens. It looks .Xauthority is seldom updated except necessity. However it(the greeter?) could be more robust for such cases. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1234400 Title: Cannot log in users if their Xauthority file is corrupt. Status in Light Display Manager: Fix Released Status in Light Display Manager 1.6 series: Fix Released Status in Light Display Manager 1.7 series: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “lightdm” source package in Raring: Fix Released Status in “lightdm” source package in Saucy: Fix Released Bug description: Impact: If a users X authority file contains invalid data the user will not be able to log in with LightDM until the file is corrected or removed. The reason for the corruption has not been identified. To reproduce: 1. Stop lightdm $ sudo stop lightdm 2. Create an invalid X authority file in the home directory of a user, e.g. from a text VT: $ cp /etc/hostname ~/.Xauthority 3. Start lightdm $ sudo start lightdm 4. Log into the user account in the greeter Expected result: Logged into graphical session. Observed result: Returned to greeter, graphical session not shown. Regression potential: Change is small and was a regression in 1.6 due to accidental removal line resetting the error variable after reading the existing X authority file. Seems unlikely to cause any side-effects. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1234400/+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 1224732] Re: Custom keyboard shortcuts don't work
Yep. Also you can go back to iBus after that it will work. Needs to be done after any changes to shortcut. -- 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/1224732 Title: Custom keyboard shortcuts don't work Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Just noticed that adding custom keyboard shortcuts does not have any effect. If, for example, I add a custom keyboard shortcut for Evince and set it to Ctrl+Alt+E, pressing this key combination won't launch Evince. * What happens * When I add a custom keyboard shortcut (and bind it to some key combination), the shortcut does not run the associated command. * What I expect * After adding the custom shortcut, I expect that the shortcut launches the associated command. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 gnome-control-center: Installed: 1:3.6.3-0ubuntu36 Candidate: 1:3.6.3-0ubuntu36 Version table: *** 1:3.6.3-0ubuntu36 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Thu Sep 12 19:21:56 2013 InstallationDate: Installed on 2013-08-31 (12 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130830) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1224732/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
I found one more bug. When I try to set Alt+Space for switch layout Super+Space are shown. -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Invalid Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” source package in Saucy: Fix Released Bug description: A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/1218322. There still remain issues regarding keyboard shortcuts though. To install: sudo add-apt-repository ppa:attente/1218322 sudo apt-get update sudo apt-get upgrade === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the next layout key entry - try entering a key combinaison (e.g ctrl-space) - the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - press and release ctrl+left shift - the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Separate bug reports for individual layout switching hotkey combinations: Super+Space and Shift+Super+Space, found in: * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245137); * Unity session (https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1245136); * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245138); * ubiquity installer (https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1242572). Alt+Shift * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245256) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245258) * Can't set keyboard layout change to Alt+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245926) Ctrl+Shift * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245270) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245268) * Can't set keyboard layout change to Ctrl+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245991) Shift+Shift * Can't set keyboard layout change to Shift+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245272) * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245278) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245280) Bugs which belong to keyboard layout switching: * Hotkeys not functional in non-latin keyboard layout in 13.10 (https://bugs.launchpad.net/unity/+bug/1226962) * Keyboard Layout Options window is missed in gnome-control-center keyboard (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245064) * Unable to set keyboard LED to show alternative layout in gnome-control-center keyboard in Saucy (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245188) * Unable to set Miscellaneous compatibility options in gnome-control-center keyboard in Saucy (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245199) * Keyboard shortcut for changing keyboard layout does not work on lock screen (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1244548) * [FFe] indicator-keyboard not working under greeter (https://bugs.launchpad.net/unity-greeter/+bug/1228207) * Lost ability to remap Caps Lock to Ctrl (https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1215826/) * gnome-control-center keyboard no longer has way to
[Desktop-packages] [Bug 1192458] Re: [USB-Audio, playback] 4-channel mode don't work on E-MU 0204 USB
Full USB command specification: Switching to 2-channel mode: == Request Type: 0x21// CTRL_OUT | CTRL_TYPE_CLASS | CTRL_RECIPIENT_INTERFACE Request: 0x1 Value: 0x400 Interface Index: 0xE00 Data: 01 01 Data Length: 2 == Switching to 4-channel mode: == Request Type: 0x21// CTRL_OUT | CTRL_TYPE_CLASS | CTRL_RECIPIENT_INTERFACE Request: 0x1 Value: 0x400 Interface Index: 0xE00 Data: 01 02 Data Length: 2 == -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1192458 Title: [USB-Audio, playback] 4-channel mode don't work on E-MU 0204 USB Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: On E-MU 0204 USB only 2-channel mode worked. In this mode the second pair of channels just duplicates the output of the first pair. E-MU control panel under MS Windows allow to switch to 2-channel or 4-channel mode. I ran USB sniffer, and it shows switch commands that the system send to the device: == Host send 2 bytes to device: Request: 0x1 Value: 0x400 Data: 01 01//switching to 2-channel mode Data: 01 02//switching to 4-channel mode == Looks like in Ubuntu the card by default stay in 2-channel mode. Switching to 4-channel mode apparently can be added to quirks.c DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.9.6-030906-generic x86_64 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1192458/+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 1220764] Re: Rhythmbox does not add VBR headers when ripping CDs to MP3
XCFA seems to rip in the right way. Tracks length is correctly showed both with Rhythmbox and VLC if ripped with XCFA. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1220764 Title: Rhythmbox does not add VBR headers when ripping CDs to MP3 Status in “rhythmbox” package in Ubuntu: Confirmed Bug description: When ripping CDs to MP3 using Rhythmbox, by default they are VBR, because this is the default preset that is used in /usr/share/gstreamer-0.10/presets/GstLameMP3Enc.prs (cbr=false). The problem is that the VBR headers aren't added to the MP3 files, for example: $ mp3val 01\ -\ Gregory\ Alan\ Isakov\ -\ Dandelion\ Wine.mp3 Analyzing file 01 - Gregory Alan Isakov - Dandelion Wine.mp3... WARNING: /home/bmaupin/Desktop/Gregory Alan Isakov/This Empty Northern Hemisphere/01 - Gregory Alan Isakov - Dandelion Wine.mp3: VBR detected, but no VBR header is present. Seeking may not work properly. INFO: /home/bmaupin/Desktop/Gregory Alan Isakov/This Empty Northern Hemisphere/01 - Gregory Alan Isakov - Dandelion Wine.mp3: 9559 MPEG frames (MPEG 1 Layer III), +ID3v2, no VBR header Done! This causes most programs to report incorrect track lengths, including Rhythmbox itself and Ubuntu's default Nautilus file manager. This seems to be a huge oversight considering this is the default behavior using the default apps. I'm not sure when this started because I only use the LTS versions of Ubuntu, but I know it wasn't a problem in 10.04, because it was using a gstreamer pipeline with xingmux as opposed to gstreamer presets, which from what I understand don't support xingmux (which I believe adds the VBR headers). I currently have to fix any MP3s that I generate with Rhythmbox like so: sudo apt-get install vbrfix cd /path/to/mp3s find . -type f -iname '*.mp3' -exec vbrfix {} {} \; rm vbrfix.log vbrfix.tmp This bug is related to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/945987 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox-data 2.96-0ubuntu4.3 [modified: usr/share/gstreamer-0.10/presets/GstLameMP3Enc.prs usr/share/rhythmbox/rhythmbox.gep] ProcVersionSignature: Ubuntu 3.5.0-39.60~precise1-generic 3.5.7.17 Uname: Linux 3.5.0-39-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Wed Sep 4 09:54:54 2013 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1220764/+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 1244775] Re: huawei E1962 dongle to be plugged twice
Hi. I'm plugging the tongle in an usb 2 port. I checked the rules and everything is ok too: rules for device 1446 include many other devices among witch 1436 (huawei E1692). Well... In a certain way it works, but as I said I have to plug it twice. Quite a strange thing... Thank you! Il giorno 30/ott/2013 17:01, Mathieu Trudel-Lapierre mathieu...@gmail.com ha scritto: Indeed, seems more related to usb-modeswitch than anything else. That said, usb-modeswitch does end up working... Are you plugging this dongle in a USB 3.0 port by any chance? ** Package changed: plasma-nm (Ubuntu) = usb-modeswitch (Ubuntu) ** Changed in: usb-modeswitch (Ubuntu) Status: New = Confirmed ** Changed in: usb-modeswitch (Ubuntu) Importance: Undecided = High ** Changed in: usb-modeswitch (Ubuntu) Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl) -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1244775 Title: huawei E1962 dongle to be plugged twice Status in “usb-modeswitch” package in Ubuntu: Confirmed Bug description: I think the problem is in usb-modeswitch. If I plug the dongle (huawei E1692) the first time nothing happens: dmesg tells me that it is just mounted as storage device and I cannot see it in the network manager. So I unplug and then plug it a second time and everything is all right: the logs tell me that it is recognized as a modem and I can connect to the internet (I see it in the network manager). The same problem on kubuntu and on ubuntu 13.10 (fresh installation, no upgrade of previous release). No problem on the previous releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1244775/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1244775 Title: huawei E1962 dongle to be plugged twice Status in “usb-modeswitch” package in Ubuntu: Confirmed Bug description: I think the problem is in usb-modeswitch. If I plug the dongle (huawei E1692) the first time nothing happens: dmesg tells me that it is just mounted as storage device and I cannot see it in the network manager. So I unplug and then plug it a second time and everything is all right: the logs tell me that it is recognized as a modem and I can connect to the internet (I see it in the network manager). The same problem on kubuntu and on ubuntu 13.10 (fresh installation, no upgrade of previous release). No problem on the previous releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1244775/+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 1246608] [NEW] Daily crashing, X restarts, and Chrome tab lockups
Public bug reported: My system will freeze every few active hours, and I'm guessing it's a GPU issue due to the dmesg and Xorg log output below. I cannot reliably reproduce the issue. Attached are dmesg, Xorg, and lspci output. I'll also note that tabs and even entire windows of Chrome occasionally lock up. This may be unrelated, but I thought I'd note it as I've heard it may be related to Chrome's use of GPU acceleration and bugs in the driver. ** Affects: nvidia-graphics-drivers-319-updates (Ubuntu) Importance: Undecided Status: New ** Attachment added: gpu-error-report-20131030.tar.gz https://bugs.launchpad.net/bugs/1246608/+attachment/3896332/+files/gpu-error-report-20131030.tar.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-319-updates in Ubuntu. https://bugs.launchpad.net/bugs/1246608 Title: Daily crashing, X restarts, and Chrome tab lockups Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu: New Bug description: My system will freeze every few active hours, and I'm guessing it's a GPU issue due to the dmesg and Xorg log output below. I cannot reliably reproduce the issue. Attached are dmesg, Xorg, and lspci output. I'll also note that tabs and even entire windows of Chrome occasionally lock up. This may be unrelated, but I thought I'd note it as I've heard it may be related to Chrome's use of GPU acceleration and bugs in the driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319-updates/+bug/1246608/+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 1246203] BootLog.txt
apport information ** Attachment added: BootLog.txt https://bugs.launchpad.net/bugs/1246203/+attachment/3896335/+files/BootLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1246203 Title: Mouse point does not appear Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: It's a weird thing: I have an Apple magic mouse connected via bluetooth to my Dell XPS 13 laptop. When gnome shell starts, the mouse pointer is is not shown on the screen... however if a move the mouse, the pointer it is still not shown but it actually moves... if fact if I keep moving the mouse towards NW (that is where the top left corner of the screen is) the gnome shell overview mode is activated. In order to make my mouse pointer visible, I have to touch the touchpad. From that moment on, the mouse pointer will be visible. It's a minor thing but it can be annoying especially if you disable the touchpad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 30 07:53:25 2013 InstallationDate: Installed on 2013-05-27 (155 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. XPS L322X MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2013-10-17 (12 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:83:A7:0B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:76231 acl:3866 sco:0 events:283 errors:0 TX bytes:3411 acl:92 sco:0 commands:98 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2013-07-26T11:37:53.325690 mtime.conffile..etc.bluetooth.main.conf: 2013-07-25T15:50:55.459853 --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistUpgraded: 2013-10-17 21:42:13,870 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu InstallationDate: Installed on 2013-05-27 (156 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. XPS L322X MarkForUpload: True Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Tags: saucy ubuntu Uname: Linux 3.8.0-29-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (13 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 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.3-3ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 31 08:16:44 2013 xserver.configfile: default xserver.errors:
[Desktop-packages] [Bug 1246203] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1246203/+attachment/3896337/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1246203 Title: Mouse point does not appear Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: It's a weird thing: I have an Apple magic mouse connected via bluetooth to my Dell XPS 13 laptop. When gnome shell starts, the mouse pointer is is not shown on the screen... however if a move the mouse, the pointer it is still not shown but it actually moves... if fact if I keep moving the mouse towards NW (that is where the top left corner of the screen is) the gnome shell overview mode is activated. In order to make my mouse pointer visible, I have to touch the touchpad. From that moment on, the mouse pointer will be visible. It's a minor thing but it can be annoying especially if you disable the touchpad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 30 07:53:25 2013 InstallationDate: Installed on 2013-05-27 (155 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. XPS L322X MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2013-10-17 (12 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:83:A7:0B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:76231 acl:3866 sco:0 events:283 errors:0 TX bytes:3411 acl:92 sco:0 commands:98 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2013-07-26T11:37:53.325690 mtime.conffile..etc.bluetooth.main.conf: 2013-07-25T15:50:55.459853 --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistUpgraded: 2013-10-17 21:42:13,870 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu InstallationDate: Installed on 2013-05-27 (156 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. XPS L322X MarkForUpload: True Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Tags: saucy ubuntu Uname: Linux 3.8.0-29-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (13 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 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.3-3ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 31 08:16:44 2013 xserver.configfile: default xserver.errors:
[Desktop-packages] [Bug 1246203] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1246203/+attachment/3896336/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1246203 Title: Mouse point does not appear Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: It's a weird thing: I have an Apple magic mouse connected via bluetooth to my Dell XPS 13 laptop. When gnome shell starts, the mouse pointer is is not shown on the screen... however if a move the mouse, the pointer it is still not shown but it actually moves... if fact if I keep moving the mouse towards NW (that is where the top left corner of the screen is) the gnome shell overview mode is activated. In order to make my mouse pointer visible, I have to touch the touchpad. From that moment on, the mouse pointer will be visible. It's a minor thing but it can be annoying especially if you disable the touchpad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 30 07:53:25 2013 InstallationDate: Installed on 2013-05-27 (155 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. XPS L322X MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2013-10-17 (12 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:83:A7:0B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:76231 acl:3866 sco:0 events:283 errors:0 TX bytes:3411 acl:92 sco:0 commands:98 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2013-07-26T11:37:53.325690 mtime.conffile..etc.bluetooth.main.conf: 2013-07-25T15:50:55.459853 --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistUpgraded: 2013-10-17 21:42:13,870 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu InstallationDate: Installed on 2013-05-27 (156 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. XPS L322X MarkForUpload: True Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Tags: saucy ubuntu Uname: Linux 3.8.0-29-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (13 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 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.3-3ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 31 08:16:44 2013 xserver.configfile: default xserver.errors:
[Desktop-packages] [Bug 1246203] XorgLog.txt
apport information ** Attachment added: XorgLog.txt https://bugs.launchpad.net/bugs/1246203/+attachment/3896347/+files/XorgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1246203 Title: Mouse point does not appear Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: It's a weird thing: I have an Apple magic mouse connected via bluetooth to my Dell XPS 13 laptop. When gnome shell starts, the mouse pointer is is not shown on the screen... however if a move the mouse, the pointer it is still not shown but it actually moves... if fact if I keep moving the mouse towards NW (that is where the top left corner of the screen is) the gnome shell overview mode is activated. In order to make my mouse pointer visible, I have to touch the touchpad. From that moment on, the mouse pointer will be visible. It's a minor thing but it can be annoying especially if you disable the touchpad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 30 07:53:25 2013 InstallationDate: Installed on 2013-05-27 (155 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. XPS L322X MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2013-10-17 (12 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:83:A7:0B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:76231 acl:3866 sco:0 events:283 errors:0 TX bytes:3411 acl:92 sco:0 commands:98 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2013-07-26T11:37:53.325690 mtime.conffile..etc.bluetooth.main.conf: 2013-07-25T15:50:55.459853 --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistUpgraded: 2013-10-17 21:42:13,870 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu InstallationDate: Installed on 2013-05-27 (156 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. XPS L322X MarkForUpload: True Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Tags: saucy ubuntu Uname: Linux 3.8.0-29-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (13 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 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.3-3ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 31 08:16:44 2013 xserver.configfile: default xserver.errors:
[Desktop-packages] [Bug 1246203] xinput.txt
apport information ** Attachment added: xinput.txt https://bugs.launchpad.net/bugs/1246203/+attachment/3896350/+files/xinput.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1246203 Title: Mouse point does not appear Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: It's a weird thing: I have an Apple magic mouse connected via bluetooth to my Dell XPS 13 laptop. When gnome shell starts, the mouse pointer is is not shown on the screen... however if a move the mouse, the pointer it is still not shown but it actually moves... if fact if I keep moving the mouse towards NW (that is where the top left corner of the screen is) the gnome shell overview mode is activated. In order to make my mouse pointer visible, I have to touch the touchpad. From that moment on, the mouse pointer will be visible. It's a minor thing but it can be annoying especially if you disable the touchpad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 30 07:53:25 2013 InstallationDate: Installed on 2013-05-27 (155 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. XPS L322X MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2013-10-17 (12 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:83:A7:0B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:76231 acl:3866 sco:0 events:283 errors:0 TX bytes:3411 acl:92 sco:0 commands:98 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2013-07-26T11:37:53.325690 mtime.conffile..etc.bluetooth.main.conf: 2013-07-25T15:50:55.459853 --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistUpgraded: 2013-10-17 21:42:13,870 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu InstallationDate: Installed on 2013-05-27 (156 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. XPS L322X MarkForUpload: True Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Tags: saucy ubuntu Uname: Linux 3.8.0-29-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (13 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 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.3-3ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 31 08:16:44 2013 xserver.configfile: default xserver.errors:
[Desktop-packages] [Bug 1246203] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1246203/+attachment/3896346/+files/UdevLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1246203 Title: Mouse point does not appear Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: It's a weird thing: I have an Apple magic mouse connected via bluetooth to my Dell XPS 13 laptop. When gnome shell starts, the mouse pointer is is not shown on the screen... however if a move the mouse, the pointer it is still not shown but it actually moves... if fact if I keep moving the mouse towards NW (that is where the top left corner of the screen is) the gnome shell overview mode is activated. In order to make my mouse pointer visible, I have to touch the touchpad. From that moment on, the mouse pointer will be visible. It's a minor thing but it can be annoying especially if you disable the touchpad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 30 07:53:25 2013 InstallationDate: Installed on 2013-05-27 (155 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. XPS L322X MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2013-10-17 (12 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:83:A7:0B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:76231 acl:3866 sco:0 events:283 errors:0 TX bytes:3411 acl:92 sco:0 commands:98 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2013-07-26T11:37:53.325690 mtime.conffile..etc.bluetooth.main.conf: 2013-07-25T15:50:55.459853 --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistUpgraded: 2013-10-17 21:42:13,870 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu InstallationDate: Installed on 2013-05-27 (156 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. XPS L322X MarkForUpload: True Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Tags: saucy ubuntu Uname: Linux 3.8.0-29-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (13 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 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.3-3ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 31 08:16:44 2013 xserver.configfile: default xserver.errors:
[Desktop-packages] [Bug 1246203] peripherals.txt
apport information ** Attachment added: peripherals.txt https://bugs.launchpad.net/bugs/1246203/+attachment/3896349/+files/peripherals.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1246203 Title: Mouse point does not appear Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: It's a weird thing: I have an Apple magic mouse connected via bluetooth to my Dell XPS 13 laptop. When gnome shell starts, the mouse pointer is is not shown on the screen... however if a move the mouse, the pointer it is still not shown but it actually moves... if fact if I keep moving the mouse towards NW (that is where the top left corner of the screen is) the gnome shell overview mode is activated. In order to make my mouse pointer visible, I have to touch the touchpad. From that moment on, the mouse pointer will be visible. It's a minor thing but it can be annoying especially if you disable the touchpad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 30 07:53:25 2013 InstallationDate: Installed on 2013-05-27 (155 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. XPS L322X MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2013-10-17 (12 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:83:A7:0B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:76231 acl:3866 sco:0 events:283 errors:0 TX bytes:3411 acl:92 sco:0 commands:98 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2013-07-26T11:37:53.325690 mtime.conffile..etc.bluetooth.main.conf: 2013-07-25T15:50:55.459853 --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistUpgraded: 2013-10-17 21:42:13,870 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu InstallationDate: Installed on 2013-05-27 (156 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. XPS L322X MarkForUpload: True Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Tags: saucy ubuntu Uname: Linux 3.8.0-29-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (13 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 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.3-3ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 31 08:16:44 2013 xserver.configfile: default xserver.errors:
[Desktop-packages] [Bug 1246203] XorgLogOld.txt
apport information ** Attachment added: XorgLogOld.txt https://bugs.launchpad.net/bugs/1246203/+attachment/3896348/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1246203 Title: Mouse point does not appear Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: It's a weird thing: I have an Apple magic mouse connected via bluetooth to my Dell XPS 13 laptop. When gnome shell starts, the mouse pointer is is not shown on the screen... however if a move the mouse, the pointer it is still not shown but it actually moves... if fact if I keep moving the mouse towards NW (that is where the top left corner of the screen is) the gnome shell overview mode is activated. In order to make my mouse pointer visible, I have to touch the touchpad. From that moment on, the mouse pointer will be visible. It's a minor thing but it can be annoying especially if you disable the touchpad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 30 07:53:25 2013 InstallationDate: Installed on 2013-05-27 (155 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. XPS L322X MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2013-10-17 (12 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:83:A7:0B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:76231 acl:3866 sco:0 events:283 errors:0 TX bytes:3411 acl:92 sco:0 commands:98 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2013-07-26T11:37:53.325690 mtime.conffile..etc.bluetooth.main.conf: 2013-07-25T15:50:55.459853 --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistUpgraded: 2013-10-17 21:42:13,870 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu InstallationDate: Installed on 2013-05-27 (156 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. XPS L322X MarkForUpload: True Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Tags: saucy ubuntu Uname: Linux 3.8.0-29-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (13 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 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.3-3ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 31 08:16:44 2013 xserver.configfile: default xserver.errors:
[Desktop-packages] [Bug 1246203] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1246203/+attachment/3896344/+files/ProcModules.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1246203 Title: Mouse point does not appear Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: It's a weird thing: I have an Apple magic mouse connected via bluetooth to my Dell XPS 13 laptop. When gnome shell starts, the mouse pointer is is not shown on the screen... however if a move the mouse, the pointer it is still not shown but it actually moves... if fact if I keep moving the mouse towards NW (that is where the top left corner of the screen is) the gnome shell overview mode is activated. In order to make my mouse pointer visible, I have to touch the touchpad. From that moment on, the mouse pointer will be visible. It's a minor thing but it can be annoying especially if you disable the touchpad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 30 07:53:25 2013 InstallationDate: Installed on 2013-05-27 (155 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. XPS L322X MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2013-10-17 (12 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:83:A7:0B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:76231 acl:3866 sco:0 events:283 errors:0 TX bytes:3411 acl:92 sco:0 commands:98 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2013-07-26T11:37:53.325690 mtime.conffile..etc.bluetooth.main.conf: 2013-07-25T15:50:55.459853 --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistUpgraded: 2013-10-17 21:42:13,870 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu InstallationDate: Installed on 2013-05-27 (156 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. XPS L322X MarkForUpload: True Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Tags: saucy ubuntu Uname: Linux 3.8.0-29-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (13 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 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.3-3ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 31 08:16:44 2013 xserver.configfile: default xserver.errors:
[Desktop-packages] [Bug 1246203] xserver.devices.txt
apport information ** Attachment added: xserver.devices.txt https://bugs.launchpad.net/bugs/1246203/+attachment/3896351/+files/xserver.devices.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1246203 Title: Mouse point does not appear Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: It's a weird thing: I have an Apple magic mouse connected via bluetooth to my Dell XPS 13 laptop. When gnome shell starts, the mouse pointer is is not shown on the screen... however if a move the mouse, the pointer it is still not shown but it actually moves... if fact if I keep moving the mouse towards NW (that is where the top left corner of the screen is) the gnome shell overview mode is activated. In order to make my mouse pointer visible, I have to touch the touchpad. From that moment on, the mouse pointer will be visible. It's a minor thing but it can be annoying especially if you disable the touchpad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 30 07:53:25 2013 InstallationDate: Installed on 2013-05-27 (155 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. XPS L322X MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2013-10-17 (12 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:83:A7:0B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:76231 acl:3866 sco:0 events:283 errors:0 TX bytes:3411 acl:92 sco:0 commands:98 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2013-07-26T11:37:53.325690 mtime.conffile..etc.bluetooth.main.conf: 2013-07-25T15:50:55.459853 --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistUpgraded: 2013-10-17 21:42:13,870 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu InstallationDate: Installed on 2013-05-27 (156 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. XPS L322X MarkForUpload: True Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Tags: saucy ubuntu Uname: Linux 3.8.0-29-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (13 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 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.3-3ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 31 08:16:44 2013 xserver.configfile: default
[Desktop-packages] [Bug 1246203] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1246203/+attachment/3896345/+files/UdevDb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1246203 Title: Mouse point does not appear Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: It's a weird thing: I have an Apple magic mouse connected via bluetooth to my Dell XPS 13 laptop. When gnome shell starts, the mouse pointer is is not shown on the screen... however if a move the mouse, the pointer it is still not shown but it actually moves... if fact if I keep moving the mouse towards NW (that is where the top left corner of the screen is) the gnome shell overview mode is activated. In order to make my mouse pointer visible, I have to touch the touchpad. From that moment on, the mouse pointer will be visible. It's a minor thing but it can be annoying especially if you disable the touchpad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 30 07:53:25 2013 InstallationDate: Installed on 2013-05-27 (155 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. XPS L322X MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2013-10-17 (12 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:83:A7:0B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:76231 acl:3866 sco:0 events:283 errors:0 TX bytes:3411 acl:92 sco:0 commands:98 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2013-07-26T11:37:53.325690 mtime.conffile..etc.bluetooth.main.conf: 2013-07-25T15:50:55.459853 --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistUpgraded: 2013-10-17 21:42:13,870 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu InstallationDate: Installed on 2013-05-27 (156 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. XPS L322X MarkForUpload: True Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Tags: saucy ubuntu Uname: Linux 3.8.0-29-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (13 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 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.3-3ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 31 08:16:44 2013 xserver.configfile: default xserver.errors:
[Desktop-packages] [Bug 1246203] DpkgLog.txt
apport information ** Attachment added: DpkgLog.txt https://bugs.launchpad.net/bugs/1246203/+attachment/3896338/+files/DpkgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1246203 Title: Mouse point does not appear Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: It's a weird thing: I have an Apple magic mouse connected via bluetooth to my Dell XPS 13 laptop. When gnome shell starts, the mouse pointer is is not shown on the screen... however if a move the mouse, the pointer it is still not shown but it actually moves... if fact if I keep moving the mouse towards NW (that is where the top left corner of the screen is) the gnome shell overview mode is activated. In order to make my mouse pointer visible, I have to touch the touchpad. From that moment on, the mouse pointer will be visible. It's a minor thing but it can be annoying especially if you disable the touchpad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 30 07:53:25 2013 InstallationDate: Installed on 2013-05-27 (155 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. XPS L322X MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2013-10-17 (12 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:83:A7:0B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:76231 acl:3866 sco:0 events:283 errors:0 TX bytes:3411 acl:92 sco:0 commands:98 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2013-07-26T11:37:53.325690 mtime.conffile..etc.bluetooth.main.conf: 2013-07-25T15:50:55.459853 --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistUpgraded: 2013-10-17 21:42:13,870 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu InstallationDate: Installed on 2013-05-27 (156 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. XPS L322X MarkForUpload: True Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Tags: saucy ubuntu Uname: Linux 3.8.0-29-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (13 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 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.3-3ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 31 08:16:44 2013 xserver.configfile: default xserver.errors:
[Desktop-packages] [Bug 1246203] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1246203/+attachment/3896341/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1246203 Title: Mouse point does not appear Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: It's a weird thing: I have an Apple magic mouse connected via bluetooth to my Dell XPS 13 laptop. When gnome shell starts, the mouse pointer is is not shown on the screen... however if a move the mouse, the pointer it is still not shown but it actually moves... if fact if I keep moving the mouse towards NW (that is where the top left corner of the screen is) the gnome shell overview mode is activated. In order to make my mouse pointer visible, I have to touch the touchpad. From that moment on, the mouse pointer will be visible. It's a minor thing but it can be annoying especially if you disable the touchpad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 30 07:53:25 2013 InstallationDate: Installed on 2013-05-27 (155 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. XPS L322X MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2013-10-17 (12 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:83:A7:0B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:76231 acl:3866 sco:0 events:283 errors:0 TX bytes:3411 acl:92 sco:0 commands:98 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2013-07-26T11:37:53.325690 mtime.conffile..etc.bluetooth.main.conf: 2013-07-25T15:50:55.459853 --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistUpgraded: 2013-10-17 21:42:13,870 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu InstallationDate: Installed on 2013-05-27 (156 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. XPS L322X MarkForUpload: True Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Tags: saucy ubuntu Uname: Linux 3.8.0-29-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (13 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 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.3-3ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 31 08:16:44 2013 xserver.configfile: default xserver.errors:
[Desktop-packages] [Bug 1246203] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1246203/+attachment/3896340/+files/Lsusb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1246203 Title: Mouse point does not appear Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: It's a weird thing: I have an Apple magic mouse connected via bluetooth to my Dell XPS 13 laptop. When gnome shell starts, the mouse pointer is is not shown on the screen... however if a move the mouse, the pointer it is still not shown but it actually moves... if fact if I keep moving the mouse towards NW (that is where the top left corner of the screen is) the gnome shell overview mode is activated. In order to make my mouse pointer visible, I have to touch the touchpad. From that moment on, the mouse pointer will be visible. It's a minor thing but it can be annoying especially if you disable the touchpad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 30 07:53:25 2013 InstallationDate: Installed on 2013-05-27 (155 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. XPS L322X MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2013-10-17 (12 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:83:A7:0B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:76231 acl:3866 sco:0 events:283 errors:0 TX bytes:3411 acl:92 sco:0 commands:98 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2013-07-26T11:37:53.325690 mtime.conffile..etc.bluetooth.main.conf: 2013-07-25T15:50:55.459853 --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistUpgraded: 2013-10-17 21:42:13,870 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu InstallationDate: Installed on 2013-05-27 (156 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. XPS L322X MarkForUpload: True Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Tags: saucy ubuntu Uname: Linux 3.8.0-29-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (13 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 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.3-3ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 31 08:16:44 2013 xserver.configfile: default xserver.errors:
[Desktop-packages] [Bug 1246203] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1246203/+attachment/3896339/+files/Lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1246203 Title: Mouse point does not appear Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: It's a weird thing: I have an Apple magic mouse connected via bluetooth to my Dell XPS 13 laptop. When gnome shell starts, the mouse pointer is is not shown on the screen... however if a move the mouse, the pointer it is still not shown but it actually moves... if fact if I keep moving the mouse towards NW (that is where the top left corner of the screen is) the gnome shell overview mode is activated. In order to make my mouse pointer visible, I have to touch the touchpad. From that moment on, the mouse pointer will be visible. It's a minor thing but it can be annoying especially if you disable the touchpad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 30 07:53:25 2013 InstallationDate: Installed on 2013-05-27 (155 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. XPS L322X MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2013-10-17 (12 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:83:A7:0B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:76231 acl:3866 sco:0 events:283 errors:0 TX bytes:3411 acl:92 sco:0 commands:98 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2013-07-26T11:37:53.325690 mtime.conffile..etc.bluetooth.main.conf: 2013-07-25T15:50:55.459853 --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistUpgraded: 2013-10-17 21:42:13,870 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu InstallationDate: Installed on 2013-05-27 (156 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. XPS L322X MarkForUpload: True Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Tags: saucy ubuntu Uname: Linux 3.8.0-29-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (13 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 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.3-3ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 31 08:16:44 2013 xserver.configfile: default xserver.errors:
[Desktop-packages] [Bug 1246203] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1246203/+attachment/3896342/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1246203 Title: Mouse point does not appear Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: It's a weird thing: I have an Apple magic mouse connected via bluetooth to my Dell XPS 13 laptop. When gnome shell starts, the mouse pointer is is not shown on the screen... however if a move the mouse, the pointer it is still not shown but it actually moves... if fact if I keep moving the mouse towards NW (that is where the top left corner of the screen is) the gnome shell overview mode is activated. In order to make my mouse pointer visible, I have to touch the touchpad. From that moment on, the mouse pointer will be visible. It's a minor thing but it can be annoying especially if you disable the touchpad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 30 07:53:25 2013 InstallationDate: Installed on 2013-05-27 (155 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. XPS L322X MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2013-10-17 (12 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:83:A7:0B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:76231 acl:3866 sco:0 events:283 errors:0 TX bytes:3411 acl:92 sco:0 commands:98 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2013-07-26T11:37:53.325690 mtime.conffile..etc.bluetooth.main.conf: 2013-07-25T15:50:55.459853 --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistUpgraded: 2013-10-17 21:42:13,870 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu InstallationDate: Installed on 2013-05-27 (156 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. XPS L322X MarkForUpload: True Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Tags: saucy ubuntu Uname: Linux 3.8.0-29-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (13 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 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.3-3ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 31 08:16:44 2013 xserver.configfile: default
[Desktop-packages] [Bug 1246203] Re: Mouse point does not appear
apport information ** Tags added: apport-collected ubuntu ** Description changed: It's a weird thing: I have an Apple magic mouse connected via bluetooth to my Dell XPS 13 laptop. When gnome shell starts, the mouse pointer is is not shown on the screen... however if a move the mouse, the pointer it is still not shown but it actually moves... if fact if I keep moving the mouse towards NW (that is where the top left corner of the screen is) the gnome shell overview mode is activated. In order to make my mouse pointer visible, I have to touch the touchpad. From that moment on, the mouse pointer will be visible. It's a minor thing but it can be annoying especially if you disable the touchpad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 30 07:53:25 2013 InstallationDate: Installed on 2013-05-27 (155 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. XPS L322X MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2013-10-17 (12 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:83:A7:0B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:76231 acl:3866 sco:0 events:283 errors:0 TX bytes:3411 acl:92 sco:0 commands:98 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2013-07-26T11:37:53.325690 mtime.conffile..etc.bluetooth.main.conf: 2013-07-25T15:50:55.459853 + --- + ApportVersion: 2.12.5-0ubuntu2.1 + Architecture: amd64 + DistUpgraded: 2013-10-17 21:42:13,870 DEBUG enabling apt cron job + DistroCodename: saucy + DistroRelease: Ubuntu 13.10 + DistroVariant: ubuntu + InstallationDate: Installed on 2013-05-27 (156 days ago) + InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) + MachineType: Dell Inc. XPS L322X + MarkForUpload: True + Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=it_IT.UTF-8 + SHELL=/bin/bash + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 + Tags: saucy ubuntu + Uname: Linux 3.8.0-29-generic x86_64 + UpgradeStatus: Upgraded to saucy on 2013-10-17 (13 days ago) + UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo + dmi.bios.date: 08/28/2013 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A10 + dmi.board.name: 091F4Y + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.chassis.version: 0.1 + dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: + dmi.product.name: XPS L322X + dmi.sys.vendor: Dell Inc. + version.compiz: compiz N/A + version.ia32-libs: ia32-libs N/A + version.libdrm2: libdrm2 2.4.46-1 + 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.3-3ubuntu2 + 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 + version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 + xserver.bootTime: Thu Oct 31 08:16:44 2013 + xserver.configfile: default + xserver.errors: + + xserver.logfile: /var/log/Xorg.0.log + xserver.outputs: + product id4920 + vendor CMN + xserver.version: 2:1.14.3-3ubuntu2 ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1246203/+attachment/3896334/+files/BootDmesg.txt -- You received this bug notification because
[Desktop-packages] [Bug 1180881] Re: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch
This bug was fixed in the package linux - 3.12.0-1.3 --- linux (3.12.0-1.3) trusty; urgency=low [ Andy Whitcroft ] * [Config] arm64 -- add arch to the configuration handlers * [Config] arm64 -- add generic flavour * [Config] arm64 -- default config * [Config] arm64 -- fix up various FTBFS config options * SAUCE: arm64: export __copy_in_user to modules * [Config] arm64 -- disable ABI/module checks * [Config] arm64 -- enforcer -- add arm64 to the enforcer * [Config] arm64 -- enable udebs for arm64 [ Colin Watson ] * [Config] Clean up various udeb Provides [ Paolo Pisati ] * [Config] AHCI_IMX=y * [Config] build imx*-wandboard dtbs [ Serge Hallyn ] * SAUCE: device_cgroup: remove can_attach [ Tim Gardner ] * rebase to v3.12-rc7 * SAUCE: KVM: Fix modprobe failure for kvm_intel/kvm_amd * Release tracker - LP: #1245932 [ Upstream Kernel Changes ] * rebase to v3.12-rc7 - LP: #1180881 - LP: #1180881 - LP: #1217957 linux (3.12.0-0.2) trusty; urgency=low [ Andy Whitcroft ] * Revert SAUCE: (no-up) scsi: hyper-v storage -- mark as preferring READ CAPACITY (16) at SPC-2 * Revert SAUCE: (no-up) scsi: hyper-v storage -- mark as VPD capable at SPC-2 * Revert SAUCE: (no-up) scsi: add scsi device flag to request READ CAPACITY (16) be preferred * Revert SAUCE: (no-up) scsi: add scsi device flag to request VPD pages be used at SPC-2 * Revert overlayfs: Update to v19 * Revert ubuntu: overlayfs v18 -- -- overlayfs: implement show_options * Revert ubuntu: overlayfs v18 -- -- overlayfs: add statfs support * Revert ubuntu: overlayfs v18 -- -- overlay filesystem * Revert ubuntu: overlayfs v18 -- -- vfs: introduce clone_private_mount() * Revert ubuntu: overlayfs v18 -- -- vfs: export do_splice_direct() to modules * Revert ubuntu: overlayfs v18 -- -- overlay: overlay filesystem documentation * ubuntu: overlayfs v20 -- overlayfs: add statfs support * [Config] fix linux-libc-dev generation for arm64 * [Config] fix linux-libc-dev generation for x32 * [Config] add linux-libc-dev generation for ppc64el [ Erez Zadok ] * ubuntu: overlayfs v20 -- overlayfs: implement show_options [ Miklos Szeredi ] * ubuntu: overlayfs v20 -- vfs: add i_op-dentry_open() * ubuntu: overlayfs v20 -- vfs: export do_splice_direct() to modules * ubuntu: overlayfs v20 -- vfs: export __inode_permission() to modules * ubuntu: overlayfs v20 -- vfs: introduce clone_private_mount() * ubuntu: overlayfs v20 -- overlay filesystem * ubuntu: overlayfs v20 -- fs: limit filesystem stacking depth [ Neil Brown ] * ubuntu: overlayfs v20 -- overlay: overlay filesystem documentation [ Paolo Pisati ] * [Config] arm: VIRTIO_[BLK|NET|MMIO]=y [ Seth Forshee ] * SAUCE: (no-up) ACPI: Disable Windows 8 compatibility for some Lenovo ThinkPads - LP: #1183856 [ Tim Gardner ] * [Config] CONFIG_CRYPTO_CRCT10DIF=y, CONFIG_CRYPTO_CRCT10DIF_PCLMUL=m * rebase to v3.12-rc2 * updateconfigs * [Config] disable CONFIG_FB_VESA enforcer check * [Config] Disable lttng for FTBS * rebase to v3.12-rc3 * rebase to v3.12-rc4 * [Config] CONFIG_ANDROID=n - LP: #1235161 * [Config] CONFIG_L2TP_V3=y - LP: #1235914 * [Config] CONFIG_USB_OTG=n for all arches * Release tracker - LP: #1242811 [ Upstream Kernel Changes ] * scsi: hyper-v storsvc switch up to SPC-3 * rebase to v3.12-rc6 - LP: #1235977 - LP: #1235523 - LP: #1239392 - LP: #1227491 * rebase to v3.12-rc3 - LP: #1231931 * rebase to v3.12-rc2 - LP: #1213820 - LP: #1213055 - LP: #1198030 -- Tim Gardner tim.gard...@canonical.com Sun, 27 Oct 2013 22:08:55 -0600 ** Changed in: linux (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1180881 Title: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch Status in HWE Next Project: Confirmed Status in HWE Next saucy series: Confirmed Status in HWE Next trusty series: Confirmed Status in “linux” package in Ubuntu: Fix Released Status in “xserver-xorg-input-evdev” package in Ubuntu: Invalid Bug description: Touchscreen is unresponsive on fresh 13.04 Ubuntu installation. All other devices work. Touchscreen shows as working and 'states' are correct for any xinput --list off of a cold boot. However, if I (at any point) Suspend the system, then awaken it, the Touchscreen immediately functions properly. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1180881/+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 1210785] Re: wpa_supplicant crashed with SIGSEGV
It happens on Asus P50IJ too, sometimes after only one wake up since the last restart, sometimes after 2 or 3 wake ups. Is it possible posting more trace? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1210785 Title: wpa_supplicant crashed with SIGSEGV Status in “wpa” package in Ubuntu: Triaged Bug description: wpa_supplicant crashed with SIGSEGV ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: wpasupplicant 1.0-3ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4 Uname: Linux 3.11.0-1-generic i686 ApportVersion: 2.12-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sat Aug 10 16:58:28 2013 ExecutablePath: /sbin/wpa_supplicant InstallationDate: Installed on 2013-08-06 (4 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Alpha i386 (20130730) MarkForUpload: True ProcCmdline: /sbin/wpa_supplicant -B -P /run/sendsigs.omit.d/wpasupplicant.pid -u -s -O /var/run/wpa_supplicant ProcEnviron: SegvAnalysis: Segfault happened at: 0x81028d0: mov0x4(%esi),%edx PC (0x081028d0) ok source 0x4(%esi) (0x012d) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: wpa StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: wpa_supplicant crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1210785/+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 1245678] Re: Simple Scan hangs repeatedly on Ubuntu 13.10
Also, simple-scan can't see my scanner without sudo after upgrade from 13.04 to 13.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1245678 Title: Simple Scan hangs repeatedly on Ubuntu 13.10 Status in “simple-scan” package in Ubuntu: Confirmed Bug description: Since I upgraded to ubuntu 13.10, Simple Scan has been rendered unusable. It hangs for about half a minute every now and then for now obvious reason. First of all, it always hangs when I try to crop a scanned page and sometimes when a Page has finished scanning. To conclude, it also hangs upon exit for even more time (about 2-3 minutes). The whole window goes dark and it accepts no input. I noticed that, during those hangs, the Hard Disk is also being used - apart from the Processor. I am using Ubuntu 13.10 with the latest updates as of today (28.10.2013) and Simple Scan 3.10.0 on an HP Deskjet 2050A Printer/Scanner... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1245678/+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 1241929] Re: Lightdm Ubuntu 13.10 fails to start intermittently after cold boot or from shutdown/reboot.
Sry Adam, thx for informing I wasn't familiar with what to run. Apologies for my mistakes then.. Hope you resolve the issue soon. On Wed, Oct 30, 2013 at 3:58 PM, Adam Niedling 1241...@bugs.launchpad.netwrote: I also get a blank screen instead of the login screen in a freshly installed 13.10. You should have ran the ubuntu-bug lightdm command to report this problem. Now you need to run apport-collect 1241929 to include the necessary information to this bug report. Any why did you add the tag no to this bug? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1241929 Title: Lightdm Ubuntu 13.10 fails to start intermittently after cold boot or from shutdown/reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1241929/+subscriptions -- Entia non sunt multiplicanda praeter necessitatem -- (William of Ockham) -- Pluralitas non est ponenda sine neccesitate. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1241929 Title: Lightdm Ubuntu 13.10 fails to start intermittently after cold boot or from shutdown/reboot. Status in “lightdm” package in Ubuntu: Confirmed Bug description: Ubuntu 13.10 official release. After a clean install of Ubuntu 13.10 I shut down for the night. Upon boot the next morning I found a blank screen with no greeter. I rebooted. This time I saw a wallpaper but no menu's. I did sudo service lightdm restart and it worked. But now after each shutdown or even a reboot I have to manually restart lightdm or might get lucky with lightdm greeter... I have added sleep 2 to the lightdm.conf. Additional info running on a hybrid disc with btrfs /, /home ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1241929/+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 1224098] Re: xserver wont start after nvidia-prime installation
** 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 nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1224098 Title: xserver wont start after nvidia-prime installation Status in “nvidia-prime” package in Ubuntu: Fix Released Status in “nvidia-prime” source package in Precise: Fix Committed Status in “nvidia-prime” source package in Saucy: Fix Committed Bug description: SRU request: [Impact] * As a result of this bug, the lightdm configuration file will always been overwritten. This is not desirabled or expected and causes serious problems on any *buntu system other than Ubuntu. [Test Case] * Enable the precise-proposed or the saucy-proposed repository and install nvidia-prime (0.4.2~hybrid0.0.1 in precise or 0.4.2~hybrid0.1 in saucy). * If the package doesn't overwrite the lightdm greeter in the lightdm.conf file, then the fix is correct. [Regression Potential] * The regression potential here should be zero, as we only replace two conditions ( test -f and test ! -s) that can never be true at the same time, with the test -s condition which does exactly what we need - it checks that the file exists and has a size greater than zero - and reuse the existing file if this condition is satisfied. I have done a fresh install of saucy, before the installation of nvidia-prime lightdm-gtk-greeter was set in lightdm.conf. During the installation of nvidia-prime the greeter ist changed to unity-greeter which causes a crash and no display after a reboot. When changing the greeter back to lightdm-gtk-greeter everything works fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nvidia-prime 0.4 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Wed Sep 11 22:11:06 2013 InstallationDate: Installed on 2013-09-11 (0 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Alpha amd64 (20130902.1) MarkForUpload: True PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1224098/+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 1219650] Re: Failed to install on 12.04.3 , /var/lib/dpkg/info/nvidia-prime.postinst: 36: printf: 08: not completely converted
** 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 nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1219650 Title: Failed to install on 12.04.3 , /var/lib/dpkg/info/nvidia- prime.postinst: 36: printf: 08: not completely converted Status in “nvidia-prime” package in Ubuntu: Fix Released Status in “nvidia-prime” source package in Precise: Fix Committed Status in “nvidia-prime” source package in Saucy: Fix Committed Bug description: SRU request: [Impact] * As a result of this bug, systems whose card has a bus id containing numbers such as 08 or 09 numbers will trigger an error in printf where it treats these string values with leading zeros as octal. This causes the postinst script to fail. [Test Case] * Enable the precise-proposed or the saucy-proposed repository and install nvidia-prime (0.4.2~hybrid0.0.1 in precise or 0.4.2~hybrid0.1 in saucy). * If the package can be installed without errors, then the fix is correct. * Alternatively, you can launch the attached script (see comment #8) as follows, you'll be able to reproduce the issue: sh printf_test.sh reproduce You can then test the fix by running the attached script without any arguments: sh printf_test.sh [Regression Potential] * The regression potential here is zero. As the attached script demonstrates. -- Encountered this problem during install nvidia driver by using jockey, then verified using apt-get install nvidia-prime, received following messages: $ sudo apt-get install nvidia-prime Reading package lists... Done Building dependency tree Reading state information... Done nvidia-prime is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue [Y/n]? y Setting up nvidia-prime (0.3~hybrid0.0.1) ... /var/lib/dpkg/info/nvidia-prime.postinst: 36: printf: 08: not completely converted dpkg: error processing nvidia-prime (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: nvidia-prime E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-prime 0.3~hybrid0.0.1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Mon Sep 2 14:07:37 2013 InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1219650/+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 1220645] Re: Webcam capture plays green screen through xv on Haswell platform
verify package xserver-xorg-video-intel-lts- raring(2:2.21.6-0ubuntu4.3~precise1) on CID 201305-13636 * check update source: proposed * apt-get update * apt-get install xserver-xorg-video-intel-lts-raring * reboot * verify by /usr/share/checkbox/scripts/camera_test display -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1220645 Title: Webcam capture plays green screen through xv on Haswell platform Status in “xserver-xorg-video-intel” package in Ubuntu: Invalid Status in “xserver-xorg-video-intel-lts-raring” package in Ubuntu: Invalid Status in “xserver-xorg-video-intel-lts-raring” source package in Precise: Fix Committed Status in “xserver-xorg-video-intel” source package in Raring: Fix Released Bug description: xv driver is having playback issue with webcam capture, it plays green screen. It was firstly found when using stock 12.04.3 image, during on installing step of Choose a Picture, the webcam view only playback with green screen, but it still can capture correctly if you hit the button. After completely installed 12.04.3 system or upgrade your X driver stack to lts-raring, on system with haswell chipset, webcam capture will playback with green screen. To reproduced this problem we could use: guvcview luvcview mplayer tv:///dev/video0 -vo xv vlc v4l2:/ //dev/video0 -V xv On the same hardware system, To validate that webcam works fine with other output drivers: luvcview -w mplayer tv:///dev/video0 -vo x11 vlc v4l2:/ //dev/video0 -V glx By downgrade to xserver-xorg-lts-quantal also fixes this issue, its also verified on 12.04.2 stock image with the same webcam. Affected webcams: 1bcf:289e Sunplus 1bcf:2985 Sunplus 0c45:64af Microdia 0c45:64ad Microdia 064e:812c Suyin ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-lts-raring 1:7.7+1ubuntu4~precise1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Wed Sep 4 06:59:59 2013 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 1: PCH [HDA Intel PCH], device 0: ALC283 Analog [ALC283 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1311 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf7e14000 irq 62' Mixer name : 'Intel Haswell HDMI' Components : 'HDA:80862807,80860101,0010' Controls : 6 Simple ctrls : 1 Card0.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [off] Card1.Amixer.info: Card hw:1 'PCH'/'HDA Intel PCH at 0xf7e1 irq 62' Mixer name : 'Realtek ALC283' Components : 'HDA:10ec0283,102805f3,0013' Controls : 14 Simple ctrls : 7 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=65f73994-7b9b-40b6-a815-0beafb8c94ef InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Inspiron 3437 MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-39-generic root=UUID=6bde1692-22e7-4822-95b8-59fd86f63632 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.5.0-39.60~precise1-generic 3.5.7.17 RelatedPackageVersions: linux-restricted-modules-3.5.0-39-generic N/A linux-backports-modules-3.5.0-39-generic N/A linux-firmware1.79.6 RfKill: Tags: precise running-unity Uname: Linux 3.5.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 06/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: X19 dmi.board.vendor: Dell Inc. dmi.board.version: X19 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias:
[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
Unfortunately, for [at least] Caps Lock as layout switching key current state definitely not Fix Released. Just some workaround available. So... After update to 3.8.5-0ubuntu11.1 from saucy-updates/main (environment restart required): What is OK: * Caps Lock could be set as next/previous layout switching key via System Settings-Text Entry * When Caps Lock is set as layout switching key original Caps Lock function could be achieved via Shift+Caps Lock, Caps Lock LED for Caps Lock function works OK What is broken: * Caps Lock could not be set as next/previous layout switching key via System Settings-Keyboard-Shortcuts-Typing * Each layout switch with Caps Lock key resets original Caps Lock function state to off, so there's no more Caps Lock function, just some kind of sticky Shift * No ability to use Caps Lock LED for current layout indication (already reported as separate bug: https://bugs.launchpad.net/ubuntu-gnome/+bug/1245188 ) And last but not least... Specials thanks to William Hua for saving this Ubuntu release. -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Invalid Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” source package in Saucy: Fix Released Bug description: A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/1218322. There still remain issues regarding keyboard shortcuts though. To install: sudo add-apt-repository ppa:attente/1218322 sudo apt-get update sudo apt-get upgrade === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the next layout key entry - try entering a key combinaison (e.g ctrl-space) - the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - press and release ctrl+left shift - the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Separate bug reports for individual layout switching hotkey combinations: Super+Space and Shift+Super+Space, found in: * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245137); * Unity session (https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1245136); * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245138); * ubiquity installer (https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1242572). Alt+Shift * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245256) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245258) * Can't set keyboard layout change to Alt+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245926) Ctrl+Shift * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245270) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245268) * Can't set keyboard layout change to Ctrl+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245991) Shift+Shift * Can't set keyboard layout change to Shift+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245272) * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245278) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245280) Bugs which belong to keyboard layout switching: * Hotkeys not functional in non-latin keyboard layout in 13.10 (https://bugs.launchpad.net/unity/+bug/1226962) * Keyboard Layout Options window is
[Desktop-packages] [Bug 1224098] Re: xserver wont start after nvidia-prime installation
Doesn't work for me on Lenovo G580 (nVidia 610m) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1224098 Title: xserver wont start after nvidia-prime installation Status in “nvidia-prime” package in Ubuntu: Fix Released Status in “nvidia-prime” source package in Precise: Fix Committed Status in “nvidia-prime” source package in Saucy: Fix Committed Bug description: SRU request: [Impact] * As a result of this bug, the lightdm configuration file will always been overwritten. This is not desirabled or expected and causes serious problems on any *buntu system other than Ubuntu. [Test Case] * Enable the precise-proposed or the saucy-proposed repository and install nvidia-prime (0.4.2~hybrid0.0.1 in precise or 0.4.2~hybrid0.1 in saucy). * If the package doesn't overwrite the lightdm greeter in the lightdm.conf file, then the fix is correct. [Regression Potential] * The regression potential here should be zero, as we only replace two conditions ( test -f and test ! -s) that can never be true at the same time, with the test -s condition which does exactly what we need - it checks that the file exists and has a size greater than zero - and reuse the existing file if this condition is satisfied. I have done a fresh install of saucy, before the installation of nvidia-prime lightdm-gtk-greeter was set in lightdm.conf. During the installation of nvidia-prime the greeter ist changed to unity-greeter which causes a crash and no display after a reboot. When changing the greeter back to lightdm-gtk-greeter everything works fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nvidia-prime 0.4 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Wed Sep 11 22:11:06 2013 InstallationDate: Installed on 2013-09-11 (0 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Alpha amd64 (20130902.1) MarkForUpload: True PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1224098/+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 1246624] [NEW] Reminders from Google are displayed as “This is an event reminder”
Public bug reported: When Evolution syncs from Google Calendar, event reminders are displayed at the right time, but the title of the popup is “This is an event reminder” instead of the correct text. Discussion here: http://ubuntuforums.org/showthread.php?t=2182365p=12822808#post12822808 Release: 13.10 evolution: Installed: 3.8.4-0ubuntu1 ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1246624 Title: Reminders from Google are displayed as “This is an event reminder” Status in “evolution” package in Ubuntu: New Bug description: When Evolution syncs from Google Calendar, event reminders are displayed at the right time, but the title of the popup is “This is an event reminder” instead of the correct text. Discussion here: http://ubuntuforums.org/showthread.php?t=2182365p=12822808#post12822808 Release: 13.10 evolution: Installed: 3.8.4-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1246624/+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 1246583] Re: All hotkeys of LibreOffice don't work in non-English keyboard layout [ubuntu 13.10]
** Summary changed: - All hotkeys of LibreOffice don't work in non-English keyboard layout + All hotkeys of LibreOffice don't work in non-English keyboard layout [ubuntu 13.10] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1246583 Title: All hotkeys of LibreOffice don't work in non-English keyboard layout [ubuntu 13.10] Status in “libreoffice” package in Ubuntu: Confirmed Bug description: Hotkeys (Ctrl+b, Ctrl+s etc) in LibreOffice are language dependent and work in English language only. While writing in any other language i.e. any Cyrillic, it's impossible to use hotkeys, they just don't do anything. Switching to English input language enable hotkeys once again. This is very frustrating as user needs to switch language to save document, to make it bold, or italic, etc. This was not experienced in Ubuntu 13.04. Steps to reproduce: 1. System Settings Text Entry. 2. Add another keyboard layout beside English [In my case it is Bengali (Probhat)] 3. Now launch Writer. 4. Switch the keyboard layout from English (US) to Bengali (Probhat) by pressing Ctrl+Space. 5. Press Ctrl+B to change font weight to bold. Error: Font weight does not get changed. Expected: Font weight should change to bold. Note: none other system hotkeys work as expected. I.e. Ctrl+s to save, or Ctrl+b to subscript, or Ctrl+i to italic etc. Workaround: The only way is to - 1. change the keyboard layout to English 2. then press desired hotkey 3. then switch keyboard layout back to Bengali. The issue is critical, as it make writer very slow for keyboard-only typing. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libreoffice-core 1:4.1.2~rc3-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 31 10:11:53 2013 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2013-05-13 (170 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: Upgraded to saucy on 2013-10-26 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1246583/+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 1196668] Re: VNC crashes on startup on Raring
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: vino (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1196668 Title: VNC crashes on startup on Raring Status in GNOME Remote Desktop: Unknown Status in “vino” package in Ubuntu: Confirmed Bug description: Vino-server is what is impacted. I believe what triggers this is related to customizing via vino-preferences. Afterwards, vino will not launch the server. A similar bug was reported on Oneiric and older, but I believe the bug report was marked as invalid due to it not having nearly enough info. The notification area icon will not stay. It will appear after startup, and quickly disappear. VNC is COMPLETELY UNUSABLE in every FOSS application I've tried on Ubuntu 13.04. From the GNOME Remote Desktop Client to Remnima, nothing works. Worse yet, none of the proprietary clients/servers such as Splashtop work either. The only remote desktop tool working is Teamviewer, and that runs under WINE. So remote desktop is borked on both my desktop and laptop. I will copy and paste some debug below: /usr/lib/vino/vino-server --sm-disable (vino-server:27458): EggSMClient-CRITICAL **: egg_sm_client_set_mode: assertion `global_client == NULL || global_client_mode == EGG_SM_CLIENT_MODE_DISABLED' failed 01/07/2013 03:01:26 PM Autoprobing TCP port in (all) network interface 01/07/2013 03:01:26 PM Listening IPv6://[::]:5900 01/07/2013 03:01:26 PM Listening IPv4://0.0.0.0:5900 01/07/2013 03:01:26 PM Autoprobing selected port 5900 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface 01/07/2013 03:01:26 PM Listening IPv6://[::]:5900 01/07/2013 03:01:26 PM Listening IPv4://0.0.0.0:5900 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Advertising authentication type: 'No Authentication' (1) 01/07/2013 03:01:26 PM Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface 01/07/2013 03:01:26 PM Listening IPv6://[::]:5900 01/07/2013 03:01:26 PM Listening IPv4://0.0.0.0:5900 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Clearing authTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Advertising authentication type: 'VNC Authentication' (2) 01/07/2013 03:01:26 PM Clearing securityTypes 01/07/2013 03:01:26 PM Clearing authTypes 01/07/2013 03:01:26 PM Advertising security type: 'TLS' (18) 01/07/2013 03:01:26 PM Advertising authentication type: 'VNC Authentication' (2) 01/07/2013 03:01:26 PM Advertising security type: 'VNC Authentication' (2) (vino-server:27458): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. *** Error in `/usr/lib/vino/vino-server': free(): invalid pointer: 0x7fdfefbf5798 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x80a46)[0x7fdfef8b4a46] /usr/lib/libminiupnpc.so.8(FreeUPNPUrls+0x11)[0x7fdff2494add] /usr/lib/vino/vino-server[0x4165e5] /usr/lib/vino/vino-server[0x41666d] /usr/lib/vino/vino-server[0x416c00] /usr/lib/vino/vino-server[0x416dae] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49b1b)[0x7fdfefc45b1b] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x135)[0x7fdfefc44f05] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49248)[0x7fdfefc45248] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0x6a)[0x7fdfefc456ba] /usr/lib/vino/vino-server[0x40bdb2] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fdfef855ea5] /usr/lib/vino/vino-server[0x40be99] === Memory map: 0040-00446000 r-xp 08:06 9420 /usr/lib/vino/vino-server 00646000-00647000 r--p 00046000 08:06 9420 /usr/lib/vino/vino-server 00647000-00649000 rw-p 00047000 08:06 9420 /usr/lib/vino/vino-server 00649000-00656000 rw-p 00:00 0 01c67000-01e19000 rw-p 00:00 0 [heap] 7fdfd400-7fdfd4022000 rw-p 00:00 0 7fdfd4022000-7fdfd800 ---p 00:00 0 7fdfd800-7fdfd8022000 rw-p 00:00 0 7fdfd8022000-7fdfdc00 ---p 00:00 0 7fdfdedc-7fdfdedc5000 r-xp 08:06 131713 /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/menuproxies/libappmenu.so 7fdfdedc5000-7fdfdefc4000 ---p 5000 08:06 131713 /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/menuproxies/libappmenu.so
[Desktop-packages] [Bug 1224098] Re: xserver wont start after nvidia-prime installation
@Michał: what happens exactly and what Ubuntu flavour are you using? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1224098 Title: xserver wont start after nvidia-prime installation Status in “nvidia-prime” package in Ubuntu: Fix Released Status in “nvidia-prime” source package in Precise: Fix Committed Status in “nvidia-prime” source package in Saucy: Fix Committed Bug description: SRU request: [Impact] * As a result of this bug, the lightdm configuration file will always been overwritten. This is not desirabled or expected and causes serious problems on any *buntu system other than Ubuntu. [Test Case] * Enable the precise-proposed or the saucy-proposed repository and install nvidia-prime (0.4.2~hybrid0.0.1 in precise or 0.4.2~hybrid0.1 in saucy). * If the package doesn't overwrite the lightdm greeter in the lightdm.conf file, then the fix is correct. [Regression Potential] * The regression potential here should be zero, as we only replace two conditions ( test -f and test ! -s) that can never be true at the same time, with the test -s condition which does exactly what we need - it checks that the file exists and has a size greater than zero - and reuse the existing file if this condition is satisfied. I have done a fresh install of saucy, before the installation of nvidia-prime lightdm-gtk-greeter was set in lightdm.conf. During the installation of nvidia-prime the greeter ist changed to unity-greeter which causes a crash and no display after a reboot. When changing the greeter back to lightdm-gtk-greeter everything works fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nvidia-prime 0.4 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Wed Sep 11 22:11:06 2013 InstallationDate: Installed on 2013-09-11 (0 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Alpha amd64 (20130902.1) MarkForUpload: True PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1224098/+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 818852] Re: X cursor often not shown
Looks that this one is fixed indeed. ** Changed in: lightdm-gtk-greeter Status: Triaged = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/818852 Title: X cursor often not shown Status in LightDM GTK+ Greeter: Fix Released Status in “lightdm” package in Ubuntu: Triaged Status in “lightdm” package in Arch Linux: New Status in “lightdm” package in Debian: Fix Released Bug description: It seems that, since 0.9.2, cursor is often not shown in GTK+ greeter. This is a regression from 0.9.0, afaict, but it might be a GTK+ 3.0 issue too. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/818852/+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 1245226] Re: HDMI: audio-video playback too fast
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/log/sound/pci/hda/patch_hdmi.c for intel hdmi codec, the audio driver get the monitor model , channel map , format , rate and channels from the graphic driver when graphic driver pass ELD to audio driver https://bugzilla.kernel.org/attachment.cgi?id=109821 [ 73.965229] HDMI: detected monitor DELL U2410 at connection type HDMI [ 73.965230] HDMI: available speakers: FL/FR [ 73.965232] HDMI: supports coding type LPCM: channels = 2, rates = 32000 44100 48000, bits = 16 20 24 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1245226 Title: HDMI: audio-video playback too fast Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: After upgrading to Ubuntu 13.10, selecting HDMI as audio output device is broken. Audio is played back at high speed. When playing back video clips, the video frames are also too fast. This is similar to an old bug I reported some time ago, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/897008 . In that case, adding radeon.audio=1 to the kernel command line solved. Now, the configuration is unchanged since when Ubuntu 13.04 was running $cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=10b9da6b-d735-48a7-bc45-2c1fc81183dd ro quiet splash radeon.audio=1 vt.handoff=7 yet audio is broken. Note that, when selecting headphone as audio output device, everything works. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu44 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Oct 27 18:00:53 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2010-11-07 (1085 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: Upgraded to saucy on 2013-10-22 (5 days ago) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1245226/+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 1239130] Re: Saucy Beta 2 Gedit Warning Messages
it looks like that #4 should be right for me... -- 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/1239130 Title: Saucy Beta 2 Gedit Warning Messages Status in “gedit” package in Ubuntu: Fix Committed Bug description: Warning messages when running gedit with Saucy Beta 2: ** (gedit:2505): WARNING **: Could not load Gedit repository: Typelib file for namespace 'GtkSource', version '3.0' not found (gedit:2505): Gtk-WARNING **: Attempting to read the recently used resources file at `/home/jerry/.local/share/recently-used.xbel', but the parser failed: Failed to open file '/home/jerry/.local/share /recently-used.xbel': Permission denied. What's wrong with gnome and/or gedit and how do I fix these warnings? Thanks, Jerry ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gedit 3.8.3-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Sat Oct 12 09:19:20 2013 InstallationDate: Installed on 2013-09-28 (13 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) MarkForUpload: True 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/1239130/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
This bug has been partially fixed for me. I used left shift + caps lock to change language in 13.04 and it know works in 13.10. I haven’t used the control panel application to set those keys, they are kept from the upgrade to 13.10. However, the indicator (US, SV etc) never changes between languages unless I mouse click, even when the keyboard layout changes. -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Invalid Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” source package in Saucy: Fix Released Bug description: A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/1218322. There still remain issues regarding keyboard shortcuts though. To install: sudo add-apt-repository ppa:attente/1218322 sudo apt-get update sudo apt-get upgrade === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the next layout key entry - try entering a key combinaison (e.g ctrl-space) - the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - press and release ctrl+left shift - the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Separate bug reports for individual layout switching hotkey combinations: Super+Space and Shift+Super+Space, found in: * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245137); * Unity session (https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1245136); * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245138); * ubiquity installer (https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1242572). Alt+Shift * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245256) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245258) * Can't set keyboard layout change to Alt+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245926) Ctrl+Shift * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245270) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245268) * Can't set keyboard layout change to Ctrl+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245991) Shift+Shift * Can't set keyboard layout change to Shift+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245272) * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245278) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245280) Bugs which belong to keyboard layout switching: * Hotkeys not functional in non-latin keyboard layout in 13.10 (https://bugs.launchpad.net/unity/+bug/1226962) * Keyboard Layout Options window is missed in gnome-control-center keyboard (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245064) * Unable to set keyboard LED to show alternative layout in gnome-control-center keyboard in Saucy (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245188) * Unable to set Miscellaneous compatibility options in gnome-control-center keyboard in Saucy (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245199) * Keyboard shortcut for changing keyboard layout does not work on lock screen (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1244548) * [FFe] indicator-keyboard
[Desktop-packages] [Bug 1236881] Re: Google Account Plugin fails to authenticate
I've the same error message ... since the update from 13.04 to 13.10 ... Error: invalid_request Invalid response_type: codeaccess_type=offline Learn more Request Details response_type=codeaccess_type=offline scope=https://docs.google.com/feeds/ https://www.googleapis.com/auth/googletalk https://www.googleapis.com/auth/userinfo.email https://www.googleapis.com/auth/userinfo.profile https://picasaweb.google.com/data/ redirect_uri=https://wiki.ubuntu.com/ client_id=759250720802-4sii0me9963n9fdqdmi7cepn6ub8luoh.apps.googleusercontent.com type=web_server ** Changed in: account-plugins (Ubuntu) Assignee: (unassigned) = tino227 (tino-mbucher) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1236881 Title: Google Account Plugin fails to authenticate Status in “account-plugins” package in Ubuntu: Confirmed Bug description: For the past few days on my saucy system I haven't been able to re- authorize my Google account. Attempts to do so result in an error page with the following content: Error: invalid_request Invalid response_type: codeaccess_type=offline Learn more Request Details response_type=codeaccess_type=offline scope=https://www.googleapis.com/auth/userinfo.email https://mail.google.com/ https://www.google.com/m8/feeds/ https://www.googleapis.com/auth/calendar redirect_uri=https://live.gnome.org/Evolution client_id=796629365126.apps.googleusercontent.com type=web_server ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: account-plugin-google 0.11+13.10.20130802-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Tue Oct 8 10:17:06 2013 InstallationDate: Installed on 2011-07-08 (823 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MarkForUpload: True PackageArchitecture: all SourcePackage: account-plugins UpgradeStatus: Upgraded to saucy on 2013-06-14 (116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1236881/+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 1245226] Re: HDMI: audio-video playback too fast
( 26.847| 0.000) D: [alsa-sink-HDMI 0] sink.c: Found underrun 2840 bytes ago (612 bytes ahead in playback buffer) this message seem related to this patch http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=e87eb85474e0d357d82a9a38097144b607e1ef57 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1245226 Title: HDMI: audio-video playback too fast Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: After upgrading to Ubuntu 13.10, selecting HDMI as audio output device is broken. Audio is played back at high speed. When playing back video clips, the video frames are also too fast. This is similar to an old bug I reported some time ago, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/897008 . In that case, adding radeon.audio=1 to the kernel command line solved. Now, the configuration is unchanged since when Ubuntu 13.04 was running $cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=10b9da6b-d735-48a7-bc45-2c1fc81183dd ro quiet splash radeon.audio=1 vt.handoff=7 yet audio is broken. Note that, when selecting headphone as audio output device, everything works. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu44 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Oct 27 18:00:53 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2010-11-07 (1085 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: Upgraded to saucy on 2013-10-22 (5 days ago) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1245226/+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 1246643] [NEW] Alt+Tab window switching is broken in GNOME session flashback in Saucy
Public bug reported: After recent updates gnome-control-center – 1:3.6.3-0ubuntu45 gnome-settings-daemon – 3.8.5-0ubuntu11.1 window switching with Alt+Tab is broken in GNOME Session FlashBack. But Alt+Tab works normally in Unity and GNOME Session FlashBack (no effects). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu45 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Thu Oct 31 13:19:28 2013 InstallationDate: Installed on 2013-10-20 (10 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131023.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 saucy -- 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/1246643 Title: Alt+Tab window switching is broken in GNOME session flashback in Saucy Status in “gnome-control-center” package in Ubuntu: New Bug description: After recent updates gnome-control-center – 1:3.6.3-0ubuntu45 gnome-settings-daemon – 3.8.5-0ubuntu11.1 window switching with Alt+Tab is broken in GNOME Session FlashBack. But Alt+Tab works normally in Unity and GNOME Session FlashBack (no effects). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu45 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Thu Oct 31 13:19:28 2013 InstallationDate: Installed on 2013-10-20 (10 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131023.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1246643/+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 1246645] [NEW] PCI/internal sound card not detected
Public bug reported: My original problem was that i had no HDMI Sound so i figure i upgrade ALSA to 1.0.24 and I recieved an error emul.c seq_midi_emul.c seq_virmidi.c .depend /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. seq_clientmgr.c:27:28: fatal error: linux/smp_lock.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. make[3]: *** [fastdep] Error 1 make[3]: Leaving directory `/opt/Alsa-1.0.24/alsa-driver-1.0.24/acore/seq' make[2]: *** [_sfdep_seq] Error 2 make[2]: Leaving directory `/opt/Alsa-1.0.24/alsa-driver-1.0.24/acore' make[1]: *** [dep] Error 1 make[1]: Leaving directory `/opt/Alsa-1.0.24/alsa-driver-1.0.24' make: *** [include/sndversions.h] Error 2 *** * alsa-driver-1.0.24 make failed Here is my Specifications !! !!ALSA Information Script v 0.4.62 !! !!Script ran on: Thu Oct 31 09:24:38 UTC 2013 !!Linux Distribution !!-- Ubuntu 12.04.2 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION=Ubuntu 12.04.2 LTS NAME=Ubuntu ID=ubuntu ID_LIKE=debian PRETTY_NAME=Ubuntu precise (12.04.2 LTS) !!DMI Information !!--- Manufacturer: Dell Inc. Product Name: Inspiron 1525 Product Version: Firmware Version: A17 !!Kernel Information !!-- Kernel release:3.5.0-23-generic Operating System: GNU/Linux Architecture: i686 Processor: i686 SMP Enabled: Yes !!ALSA Version !! Driver version: Library version:1.0.25 Utilities version: 1.0.25 !!Loaded ALSA modules !!--- !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- !!PCI
[Desktop-packages] [Bug 1246645] Re: PCI/internal sound card not detected
Not a bug. User borked his/her configuration by trying to install custom kernel modules. ** Changed in: alsa-driver (Ubuntu) Status: New = Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/238404 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1246645 Title: PCI/internal sound card not detected Status in “alsa-driver” package in Ubuntu: Invalid Bug description: My original problem was that i had no HDMI Sound so i figure i upgrade ALSA to 1.0.24 and I recieved an error emul.c seq_midi_emul.c seq_virmidi.c .depend /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. seq_clientmgr.c:27:28: fatal error: linux/smp_lock.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. /usr/src/linux-headers-3.5.0-23-generic/arch/x86/include/asm/unistd.h:17:29: fatal error: asm/unistd_32.h: No such file or directory compilation terminated. make[3]: *** [fastdep] Error 1 make[3]: Leaving directory `/opt/Alsa-1.0.24/alsa-driver-1.0.24/acore/seq' make[2]: *** [_sfdep_seq] Error 2 make[2]: Leaving directory `/opt/Alsa-1.0.24/alsa-driver-1.0.24/acore' make[1]: *** [dep] Error 1 make[1]: Leaving directory `/opt/Alsa-1.0.24/alsa-driver-1.0.24' make: *** [include/sndversions.h] Error 2 *** * alsa-driver-1.0.24 make failed Here is my Specifications !! !!ALSA Information Script v 0.4.62 !! !!Script ran on: Thu Oct 31 09:24:38 UTC 2013 !!Linux Distribution !!-- Ubuntu 12.04.2 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION=Ubuntu 12.04.2 LTS NAME=Ubuntu ID=ubuntu ID_LIKE=debian PRETTY_NAME=Ubuntu precise (12.04.2 LTS) !!DMI Information !!---
[Desktop-packages] [Bug 1243806] Re: Folder names in Location area keeps the width (13.10)
How come this issue could be Low? Do we need to handle files/folder blindly? We should advertise Even blind people can use ubuntu as well as other people can! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1243806 Title: Folder names in Location area keeps the width (13.10) Status in “nautilus” package in Ubuntu: Confirmed Bug description: Folder names in Location area keeps the width even though when I go back to upper folder. First of all this new downgraded nautilus folder section holds its width and I cannot even change the width at all. Then when I go deep down lower folders or open folder with long name, it would squeeze down the Name part and I cannot even see names anymore. Then when I go up to upper folder or root, I cannot see the names anymore becaue location column takes up all the space. Once I click one of the unseen folder, I may see the names again. This is one of too many problems of 13.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1243806/+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 1246656] [NEW] If keyboard layout switching hotkey is set to Ctrl+Shift, Ctrl+Shift+C/V are not working in gnome-terminal
Public bug reported: I have installed recent updates: gnome-control-center – 1:3.6.3-0ubuntu45 gnome-settings-daemon – 3.8.5-0ubuntu11.1 In 12.04.3 I was able to use Ctrl+Shift+C and Ctrl+Shift+V for copying and pasting text in gnome-terminal even if my keyboard layout change hotkey is set to Ctrl+Shift. In Saucy I can't use these shortcuts in gnome-terminal. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu45 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Thu Oct 31 13:59:44 2013 InstallationDate: Installed on 2013-10-20 (10 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131023.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 saucy -- 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/1246656 Title: If keyboard layout switching hotkey is set to Ctrl+Shift, Ctrl+Shift+C/V are not working in gnome-terminal Status in “gnome-control-center” package in Ubuntu: New Bug description: I have installed recent updates: gnome-control-center – 1:3.6.3-0ubuntu45 gnome-settings-daemon – 3.8.5-0ubuntu11.1 In 12.04.3 I was able to use Ctrl+Shift+C and Ctrl+Shift+V for copying and pasting text in gnome-terminal even if my keyboard layout change hotkey is set to Ctrl+Shift. In Saucy I can't use these shortcuts in gnome-terminal. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu45 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Thu Oct 31 13:59:44 2013 InstallationDate: Installed on 2013-10-20 (10 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131023.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1246656/+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 957589] Re: Localized LibreOffice Help files ignored when help for en-US is installed
** Changed in: ubuntu-translations Status: Triaged = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/957589 Title: Localized LibreOffice Help files ignored when help for en-US is installed Status in LibreOffice Productivity Suite: Invalid Status in Ubuntu Italian ISO defaults package: Invalid Status in Ubuntu Translations: Fix Released Status in “libreoffice” package in Ubuntu: Fix Released Status in “libreoffice” package in Debian: Confirmed Bug description: WORKAROUND == uninstall the english help package (libreoffice-help-en-us) Revised bug description === Ubuntu's language packs don't install the LibreOffice help language packs. For instance language-pack-en should install libreoffice-help-en-us or libreoffice-help-en-gb; language-pack-de should install libreoffice-help-de and so on. libreoffice-help-en-us is currently special-cased and installed by ubuntu-desktop. Ubuntu flavors that don't ship LibreOffice are then forced to either install that several MB package or users will get redirected to webhelp when they click Help buttons in LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/957589/+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 1246452] Re: Calendar no longer working after upgrade from 13.04 to 13.10
*** This bug is a duplicate of bug 1244619 *** https://bugs.launchpad.net/bugs/1244619 ** This bug has been marked a duplicate of bug 1244619 Thunderbird must be upgraded to Thunderbird 24.0.1 for lightning 2.6.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1246452 Title: Calendar no longer working after upgrade from 13.04 to 13.10 Status in “thunderbird” package in Ubuntu: New Bug description: Thunderbird no longer reminds of recurring events, and can't see any events scheduled, as if the calendar entirely disappeared. Cannot schedule new events. In edit...preferences...calendar, it appears to be unaware of the time-zone. The button to press to specify the nearest city in the timezone is only 1/16 inch high, and doesn't function. Expected behavior is that after upgrade, the same calendar I was using on 13.04 would be used an 13.10, or at a bare minimum, I would be able to specify a new calendar (which I cannot). I need to have the calendar feature work again. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: thunderbird 1:24.0+build1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 AddonCompatCheckDisabled: False ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aere 2352 F pulseaudio BuildID: 20130917155400 CRDA: Error: [Errno 2] No such file or directory: 'iw' Channel: Unavailable Date: Wed Oct 30 13:37:08 2013 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-05-18 (165 days ago) InstallationMedia: Lubuntu 13.04 Raring Ringtail - Release i386 (20130423.1) IpRoute: default via 192.168.0.1 dev eth2 proto static 192.168.0.0/24 dev eth2 proto kernel scope link src 192.168.0.13 metric 1 IwConfig: lono wireless extensions. eth2 no wireless extensions. MarkForUpload: True PrefSources: prefs.js [Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js Profiles: Profile0 (Default) - LastVersion=24.0/20130917155400 (In use) RelatedPackageVersions: gecko-mediaplayer 1.0.8-4ubuntu1 RfKill: RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to saucy on 2013-10-20 (10 days ago) dmi.bios.date: 11/21/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0GDG8Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 00 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd11/21/2011:svnDellInc.:pnInspiron620:pvr00:rvnDellInc.:rn0GDG8Y:rvrA00:cvnDellInc.:ct3:cvr00: dmi.product.name: Inspiron 620 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1246452/+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 529946] Re: Temporary file created in source directory for 7z compression
Not sure when this was fixed, but file-roller in saucy correctly creates the temporary file inside the target folder. ** Changed in: file-roller (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/529946 Title: Temporary file created in source directory for 7z compression Status in “file-roller” package in Ubuntu: Fix Released Bug description: Binary package hint: file-roller When creating a 7z archive using file-roller, the temporary .7z.tmp file is created in the source directory, instead of the target directory as with other formats like .tar.gz. This is problematic when the source and target directories are on different partitions. The source may not have enough free space and in any case this results in extra copying. I imagine it would be even more annoying with a network share. 7z/7za from the command line does not have this problem. ProblemType: Bug Architecture: amd64 CheckboxSubmission: 6c48a5ef458e70786da929ddf440a66f CheckboxSystem: fd6c484c0b5d20a2f1cd036ef0f63975 Date: Mon Mar 1 12:13:29 2010 DistroRelease: Ubuntu 9.10 Package: file-roller 2.28.1-0ubuntu1 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-20.57-generic SourcePackage: file-roller Uname: Linux 2.6.31-20-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/529946/+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 1246659] [NEW] Problem with brightness control on multi-monitor system
Public bug reported: This problem only happens when I'm working with two monitors. If I press the keyboard button Brightness down, the screen resolution of one of my monitors changes. If I press it again, the laptop's screen turns off. I can restore my original configuration by going to 'System settings' - 'Displays' This problem doesn't happen when pressing Brightness up button. If I change the resolution by going to 'System setting' - 'Brightness lock', I don't get any problems. It seems to happen only when: * Pressing the keyboard button * Decreasing brightness * Having multiple monitors I have attached a video showing the problem. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 319.32 Wed Jun 19 15:51:20 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.1 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: Thu Oct 31 10:34:39 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-319, 319.32, 3.11.0-12-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 320M] [10de:0a2d] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:036d] InstallationDate: Installed on 2013-10-27 (3 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Packard Bell EasyNote TM85 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic root=UUID=392386e0-8d2e-400d-b4bf-4ce5ae57d3a0 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2011 dmi.bios.vendor: Packard Bell dmi.bios.version: V1.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: EasyNote TM85 dmi.board.vendor: Packard Bell dmi.board.version: V1.23 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: V1.23 dmi.modalias: dmi:bvnPackardBell:bvrV1.23:bd04/25/2011:svnPackardBell:pnEasyNoteTM85:pvrV1.23:rvnPackardBell:rnEasyNoteTM85:rvrV1.23:cvnPackardBell:ct10:cvrV1.23: dmi.product.name: EasyNote TM85 dmi.product.version: V1.23 dmi.sys.vendor: Packard Bell version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 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.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 31 10:17:18 2013 xserver.configfile: default xserver.errors: Failed to load /usr/lib/xorg/modules/libglamoregl.so: /usr/lib/xorg/modules/libglamoregl.so: undefined symbol: _glapi_tls_Context Failed to load module glamoregl (loader failed, 7) open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.14.3-3ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 resolution saucy ubuntu ** Attachment added: Video demonstrating the problem https://bugs.launchpad.net/bugs/1246659/+attachment/3896481/+files/Brightness%20problem.mp4 -- 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/1246659 Title: Problem with brightness control on multi-monitor system Status in “xorg” package in Ubuntu: New Bug description: This problem only happens when I'm working with two monitors. If I press the keyboard button Brightness down, the screen resolution of one of my monitors changes. If I press it again, the laptop's screen turns off. I can restore my original configuration by going to 'System settings' - 'Displays' This problem doesn't happen when pressing Brightness up button. If I change the resolution by going to 'System setting' - 'Brightness lock', I don't get any
[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
The fix didn't work for me. I still can't set Control-Shift to switch between layouts. I can use Alt-X or Control-X, but not Control-Shift. It stays Disabled. -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Invalid Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” source package in Saucy: Fix Released Bug description: A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/1218322. There still remain issues regarding keyboard shortcuts though. To install: sudo add-apt-repository ppa:attente/1218322 sudo apt-get update sudo apt-get upgrade === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the next layout key entry - try entering a key combinaison (e.g ctrl-space) - the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - press and release ctrl+left shift - the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Separate bug reports for individual layout switching hotkey combinations: Super+Space and Shift+Super+Space, found in: * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245137); * Unity session (https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1245136); * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245138); * ubiquity installer (https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1242572). Alt+Shift * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245256) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245258) * Can't set keyboard layout change to Alt+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245926) Ctrl+Shift * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245270) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245268) * Can't set keyboard layout change to Ctrl+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245991) Shift+Shift * Can't set keyboard layout change to Shift+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245272) * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245278) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245280) Bugs which belong to keyboard layout switching: * Hotkeys not functional in non-latin keyboard layout in 13.10 (https://bugs.launchpad.net/unity/+bug/1226962) * Keyboard Layout Options window is missed in gnome-control-center keyboard (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245064) * Unable to set keyboard LED to show alternative layout in gnome-control-center keyboard in Saucy (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245188) * Unable to set Miscellaneous compatibility options in gnome-control-center keyboard in Saucy (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245199) * Keyboard shortcut for changing keyboard layout does not work on lock screen (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1244548) * [FFe] indicator-keyboard not working under greeter (https://bugs.launchpad.net/unity-greeter/+bug/1228207) * Lost ability to remap Caps Lock to Ctrl
[Desktop-packages] [Bug 1246662] [NEW] Gnome Shell won't lock and ask for password when sssd auth is used
Public bug reported: I use sssd to authenticate users, and due to a change introduced in accountsservice on unlock, the desktop is shown immediately wqith no password entry. Upstream has a patch here: https://bugzilla.gnome.org/show_bug.cgi?id=708997 Please apply ASAP. I tested the patch with a dpkg-buildpackage local install. It works. ** Affects: accountsservice Importance: Unknown Status: Unknown ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Bug watch added: GNOME Bug Tracker #708997 https://bugzilla.gnome.org/show_bug.cgi?id=708997 ** Also affects: accountsservice via https://bugzilla.gnome.org/show_bug.cgi?id=708997 Importance: Unknown Status: Unknown ** Summary changed: - Gnme Shell won't lock and ask for password when sssd auth is used + Gnome Shell won't lock and ask for password when sssd auth is used -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1246662 Title: Gnome Shell won't lock and ask for password when sssd auth is used Status in D-Bus interfaces for querying and manipulating user account information: Unknown Status in “accountsservice” package in Ubuntu: New Bug description: I use sssd to authenticate users, and due to a change introduced in accountsservice on unlock, the desktop is shown immediately wqith no password entry. Upstream has a patch here: https://bugzilla.gnome.org/show_bug.cgi?id=708997 Please apply ASAP. I tested the patch with a dpkg-buildpackage local install. It works. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1246662/+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 1243484] Re: Incorrect handling of orientation when printing PDF files
Stephane, thanks, I have fixed this duplex issue upstream now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1243484 Title: Incorrect handling of orientation when printing PDF files Status in “cups-filters” package in Ubuntu: New Bug description: There seems to be some problems in the CUPS filters handling PDF files, which can be shown without having an actual printer hooked up (this seems to be independent of the driver in use). This happens on the latest Ubuntu 13.10 but I believe the real culprit is in the cups-filters 1.0.40 package. This happens when trying to print a PDF file (such as the CUPS test page in /usr/share/cups/data/default.pdf) and trying to change its orientation with the 'landscape' option, as such : lp -d queue -o landscape /usr/share/cups/data/default.pdf The result right now would be that the job is upside down, instead of being in a landscape orientation. This happens regardless of the driver. The same behavior doesn't happen for documents such as PostScript files, which works as expected, at least with a PS printer. The easiest way to test this is to set up queues that print to file (enable FileDevice in the CUPS config first) and look at the resulting files with a document viewer such as evince : - Create a new Generic Postscript queue using the default drivers, set it to print to a URI such as file:///tmp/test.ps - Send a PDF job to the queue with the landscape option - Look at the output in evince or Ghostview I strongly suspect something is amiss with the pdftopdf filter's handling of these options, especially in v1.0.40. Fedora 19 didn't exhibit the same problem until the cups-filters package was brought up to the same version just today. I also suspect that more than the orientation options are affected, we have had reports from customers having trouble with options handled through the Collate PPD options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1243484/+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 1222586] Re: Gnome Online Accounts and Empathy don't connect to Facebook
** Bug watch added: GNOME Bug Tracker #707747 https://bugzilla.gnome.org/show_bug.cgi?id=707747 ** Also affects: gnome-online-accounts via https://bugzilla.gnome.org/show_bug.cgi?id=707747 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1222586 Title: Gnome Online Accounts and Empathy don't connect to Facebook Status in GNOME Online Accounts: Unknown Status in “gnome-online-accounts” package in Ubuntu: Confirmed Bug description: I have been experiencing this bug for a few months now in Ubuntu Gnome 12.10 and Ubuntu 12.04 (via Ubuntu Online Accounts) where when I add a FB account, it looks okay UNTIL I try and connect to it with, well, anything even the GOA itself, I tried 13.10 (like I usually do with alpha/beta releases) and this bug is still present, what's more is this bug is present in OTHER distros (I'm filing a bug on the Gnome bugzilla as I type), reason I'm filing this here is I'm making sure it's not something in Ubuntu that isn't playing nice (doubtful since Arch doesn't inherit the patches from Ubuntu) What I expected to happen: Facebook to work with GOA and Empathy, What actually happened: GOA looked like it tried to connect to FB, but gets an authorization error, I double and triple checked the details I entered, even resorted to copy/paste. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-online-accounts 3.8.2-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sun Sep 8 16:21:35 2013 InstallationDate: Installed on 2013-09-08 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130903) MarkForUpload: True SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1222586/+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 1165104] Re: oneconf is only showing the pc you are on in raring and isn't sharing to other machines
...and now the same with saucy... 3.11.0-12 generic kernel, if it matters. On two computers I have tried, both are unable to sync the same way as described above. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to oneconf in Ubuntu. https://bugs.launchpad.net/bugs/1165104 Title: oneconf is only showing the pc you are on in raring and isn't sharing to other machines Status in One Hundred Papercuts: Triaged Status in “oneconf” package in Ubuntu: Triaged Bug description: In Raring I see only the machince I'm on. In the precise box beside it I see a couple of boxes but not this one. Please see the screenshots attached. I have a feeling that some how the sync has broken but I'm not sure what technology it is use on the backend. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: oneconf 0.3.3 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Fri Apr 5 18:18:24 2013 InstallationDate: Installed on 2013-04-02 (3 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130402) MarkForUpload: True PackageArchitecture: all SourcePackage: oneconf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1165104/+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 1243235] Re: Please demote libav to universe
We used to have libav in main also because of KDE. What happened to kdemultimedia, do they also have been demoted to universe? Besides, what are the implications of this demotion regarding updates and care by the ubuntu security team? Libav, as a codec library, is by nature a pretty sensitive piece of software that frequently receives point releases with security updates. Would demoting it make it more or less likely that such point release updates land in ubuntu? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1243235 Title: Please demote libav to universe Status in “alsa-plugins” package in Ubuntu: Fix Released Status in “libav” package in Ubuntu: New Status in “strigi” package in Ubuntu: Fix Released Bug description: libav demotion: I would like libav to be demoted to universe in Trusty. It is a package that takes considerable resources to maintain security updates for, resulting in it being vulnerable in Debian and Ubuntu. Not only does anything in main currently depend on it, but having it in main results in split packaging (libav and libav-extras) which puts an extra burden on maintenance. It is currently being seeded in supported-desktop-extra. $ reverse-depends -c main src:libav No reverse dependencies found $ reverse-depends -b -c main src:libav Reverse-Build-Depends = * alsa-plugins (for libavcodec-dev) * alsa-plugins (for libavutil-dev) * strigi(for libpostproc-dev) * strigi(for libswscale-dev) strigi: --- I don't believe strigi actually needs libpostproc-dev and libswscale-dev. Here is the current build log with them: -- checking for module 'libavcodec' -- package 'libavcodec' not found -- checking for module 'libavformat' -- package 'libavformat' not found -- checking for module 'libavdevice' -- package 'libavdevice' not found -- checking for module 'libavutil' -- found libavutil, version 51.22.1 -- checking for module 'libswscale' -- found libswscale, version 2.1.0 -- checking for module 'libpostproc' -- found libpostproc, version 52.0.0 -- Could NOT find FFmpeg (missing: AVCODEC_LIBRARIES AVCODEC_INCLUDE_DIRS AVFORMAT_LIBRARIES AVFORMAT_INCLUDE_DIRS) ** FFmpeg not found. Support for indexing FFMPEG is disabled Here is the build log after they have been removed: -- checking for module 'libavcodec' -- package 'libavcodec' not found -- checking for module 'libavformat' -- package 'libavformat' not found -- checking for module 'libavdevice' -- package 'libavdevice' not found -- checking for module 'libavutil' -- package 'libavutil' not found -- checking for module 'libswscale' -- package 'libswscale' not found -- checking for module 'libpostproc' -- package 'libpostproc' not found -- Could NOT find FFmpeg (missing: FFMPEG_LIBRARIES FFMPEG_INCLUDE_DIRS AVCODEC_LIBRARIES AVCODEC_INCLUDE_DIRS AVFORMAT_LIBRARIES AVFORMAT_INCLUDE_DIRS AVUTIL_LIBRARIES AVUTIL_INCLUDE_DIRS SWSCALE_LIBRARIES SWSCALE_INCLUDE_DIRS) ** FFmpeg not found. Support for indexing FFMPEG is disabled alsa-plugins: - alsa-plugins needs libavcodec-dev and libavutil-dev for the libasound2-plugins-extra package in universe. We have three options: 1- Stop building libasound2-plugins-extra $ reverse-depends -s libasound2-plugins-extra No reverse dependencies found 2- Leave libavcodec-dev and libavutil-dev in main (not ideal) 3- Add an alsa-plugins-extras source package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1243235/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
** Description changed: A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/1218322. There still remain issues regarding keyboard shortcuts though. To install: sudo add-apt-repository ppa:attente/1218322 sudo apt-get update sudo apt-get upgrade === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the next layout key entry - try entering a key combinaison (e.g ctrl-space) - the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - press and release ctrl+left shift - the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Separate bug reports for individual layout switching hotkey combinations: Super+Space and Shift+Super+Space, found in: * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245137); * Unity session (https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1245136); * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245138); * ubiquity installer (https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1242572). Alt+Shift * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245256) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245258) * Can't set keyboard layout change to Alt+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245926) Ctrl+Shift * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245270) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245268) - * Can't set keyboard layout change to Ctrl+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245991) + * Can't set keyboard layout change to Ctrl+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245991) + * If keyboard layout switching hotkey is set to Ctrl+Shift, Ctrl+Shift+C/V are not working in gnome-terminal (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1246656) Shift+Shift * Can't set keyboard layout change to Shift+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245272) * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245278) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245280) Bugs which belong to keyboard layout switching: * Hotkeys not functional in non-latin keyboard layout in 13.10 (https://bugs.launchpad.net/unity/+bug/1226962) * Keyboard Layout Options window is missed in gnome-control-center keyboard (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245064) * Unable to set keyboard LED to show alternative layout in gnome-control-center keyboard in Saucy (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245188) * Unable to set Miscellaneous compatibility options in gnome-control-center keyboard in Saucy (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245199) * Keyboard shortcut for changing keyboard layout does not work on lock screen (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1244548) * [FFe] indicator-keyboard not working under greeter (https://bugs.launchpad.net/unity-greeter/+bug/1228207) * Lost ability to remap Caps Lock to Ctrl (https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1215826/) * gnome-control-center keyboard no longer has way to modify caps lock key behavior (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1224575) * Pressing Caps Lock toggles LED even when mapped to another key (https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1221403)
[Desktop-packages] [Bug 1246669] [NEW] nvidia-319-updates 319.60-0ubuntu1: nvidia-319-updates kernel module failed to build
Public bug reported: crashed while manually updating ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-319-updates 319.60-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.12.0-1-generic Date: Thu Oct 31 06:53:24 2013 DuplicateSignature: dkms:nvidia-319-updates:319.60-0ubuntu1:/var/lib/dkms/nvidia-319-updates/319.60/build/nv-drm.c:204:9: error: void value not ignored as it ought to be InstallationDate: Installed on 2013-10-28 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20131021.1) MarkForUpload: True PackageVersion: 319.60-0ubuntu1 SourcePackage: nvidia-graphics-drivers-319-updates Title: nvidia-319-updates 319.60-0ubuntu1: nvidia-319-updates kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-319-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-319-updates in Ubuntu. https://bugs.launchpad.net/bugs/1246669 Title: nvidia-319-updates 319.60-0ubuntu1: nvidia-319-updates kernel module failed to build Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu: New Bug description: crashed while manually updating ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-319-updates 319.60-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.12.0-1-generic Date: Thu Oct 31 06:53:24 2013 DuplicateSignature: dkms:nvidia-319-updates:319.60-0ubuntu1:/var/lib/dkms/nvidia-319-updates/319.60/build/nv-drm.c:204:9: error: void value not ignored as it ought to be InstallationDate: Installed on 2013-10-28 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20131021.1) MarkForUpload: True PackageVersion: 319.60-0ubuntu1 SourcePackage: nvidia-graphics-drivers-319-updates Title: nvidia-319-updates 319.60-0ubuntu1: nvidia-319-updates kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319-updates/+bug/1246669/+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 1246659] Re: Problem with brightness control on multi-monitor system
** Description changed: This problem only happens when I'm working with two monitors. If I press the keyboard button Brightness down, the screen resolution of one of my monitors changes. If I press it again, the laptop's screen turns off. I can restore my original configuration by going to 'System settings' - 'Displays' This problem doesn't happen when pressing Brightness up button. If I change the resolution by going to 'System setting' - 'Brightness lock', I don't get any problems. It seems to happen only when: * Pressing the keyboard button * Decreasing brightness * Having multiple monitors + I have tried both nvidia closed source drivers and nouveau open source drivers, and it happens with both of them. I have attached a video showing the problem. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 319.32 Wed Jun 19 15:51:20 PDT 2013 - GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 319.32 Wed Jun 19 15:51:20 PDT 2013 + GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) .tmp.unity.support.test.0: - + ApportVersion: 2.12.5-0ubuntu2.1 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: Thu Oct 31 10:34:39 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-319, 319.32, 3.11.0-12-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: - NVIDIA Corporation GT216M [GeForce GT 320M] [10de:0a2d] (rev a2) (prog-if 00 [VGA controller]) -Subsystem: Acer Incorporated [ALI] Device [1025:036d] + NVIDIA Corporation GT216M [GeForce GT 320M] [10de:0a2d] (rev a2) (prog-if 00 [VGA controller]) + Subsystem: Acer Incorporated [ALI] Device [1025:036d] InstallationDate: Installed on 2013-10-27 (3 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Packard Bell EasyNote TM85 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic root=UUID=392386e0-8d2e-400d-b4bf-4ce5ae57d3a0 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2011 dmi.bios.vendor: Packard Bell dmi.bios.version: V1.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: EasyNote TM85 dmi.board.vendor: Packard Bell dmi.board.version: V1.23 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: V1.23 dmi.modalias: dmi:bvnPackardBell:bvrV1.23:bd04/25/2011:svnPackardBell:pnEasyNoteTM85:pvrV1.23:rvnPackardBell:rnEasyNoteTM85:rvrV1.23:cvnPackardBell:ct10:cvrV1.23: dmi.product.name: EasyNote TM85 dmi.product.version: V1.23 dmi.sys.vendor: Packard Bell version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 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.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 31 10:17:18 2013 xserver.configfile: default xserver.errors: - Failed to load /usr/lib/xorg/modules/libglamoregl.so: /usr/lib/xorg/modules/libglamoregl.so: undefined symbol: _glapi_tls_Context - Failed to load module glamoregl (loader failed, 7) - open /dev/fb0: No such file or directory + Failed to load /usr/lib/xorg/modules/libglamoregl.so: /usr/lib/xorg/modules/libglamoregl.so: undefined symbol: _glapi_tls_Context + Failed to load module glamoregl (loader failed, 7) + open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: - + xserver.version: 2:1.14.3-3ubuntu2 ** Description changed: This problem only happens when I'm working with two monitors. If I press the keyboard button Brightness down, the screen resolution of one of my monitors changes. If I press it
[Desktop-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10
What is interesting - non-latin shortcuts (for example Ctrl+Alt+T) work in GNOME Session FlashBack (with effects), but do not work in Unity and GNOME Session FlashBack (without effects). -- 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/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10 Status in IBus: New Status in Indicator keyboard: Fix Committed Status in Unity: Invalid Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Fix Released Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters-keyboard-hotkeys-windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1226962/+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 1246669] Re: nvidia-319-updates 319.60-0ubuntu1: nvidia-319-updates kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-319-updates in Ubuntu. https://bugs.launchpad.net/bugs/1246669 Title: nvidia-319-updates 319.60-0ubuntu1: nvidia-319-updates kernel module failed to build Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu: New Bug description: crashed while manually updating ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-319-updates 319.60-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.12.0-1-generic Date: Thu Oct 31 06:53:24 2013 DuplicateSignature: dkms:nvidia-319-updates:319.60-0ubuntu1:/var/lib/dkms/nvidia-319-updates/319.60/build/nv-drm.c:204:9: error: void value not ignored as it ought to be InstallationDate: Installed on 2013-10-28 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20131021.1) MarkForUpload: True PackageVersion: 319.60-0ubuntu1 SourcePackage: nvidia-graphics-drivers-319-updates Title: nvidia-319-updates 319.60-0ubuntu1: nvidia-319-updates kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319-updates/+bug/1246669/+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 1192458] Re: [USB-Audio, playback] 4-channel mode don't work on E-MU 0204 USB
I made a patch for quirks.c , please check it. ** Attachment added: patch https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1192458/+attachment/3896522/+files/patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1192458 Title: [USB-Audio, playback] 4-channel mode don't work on E-MU 0204 USB Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: On E-MU 0204 USB only 2-channel mode worked. In this mode the second pair of channels just duplicates the output of the first pair. E-MU control panel under MS Windows allow to switch to 2-channel or 4-channel mode. I ran USB sniffer, and it shows switch commands that the system send to the device: == Host send 2 bytes to device: Request: 0x1 Value: 0x400 Data: 01 01//switching to 2-channel mode Data: 01 02//switching to 4-channel mode == Looks like in Ubuntu the card by default stay in 2-channel mode. Switching to 4-channel mode apparently can be added to quirks.c DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.9.6-030906-generic x86_64 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1192458/+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 1169694] Re: evolution crashes with GSlice: assertion failed: sinfo-n_allocated 0
after removing evolution-indicator, it seems evolution is not crashing anymore. I'm using xubuntu 13.04, evolution 3.8.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1169694 Title: evolution crashes with GSlice: assertion failed: sinfo-n_allocated 0 Status in “evolution” package in Ubuntu: Confirmed Bug description: This happens within a few minutes, but not really sure what triggers it. I'm using 2 IMAP+ connections (to gmail and to mail.office365.com). ***MEMORY-ERROR***: evolution[27334]: GSlice: assertion failed: sinfo-n_allocated 0 Program received signal SIGABRT, Aborted. [Switching to Thread 0x7fffb3baf700 (LWP 27473)] 0x73c81037 in raise () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x73c81037 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x73c84698 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x742496b0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7429247b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x742927be in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x742928f2 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x74019d92 in __nptl_deallocate_tsd () from /lib/x86_64-linux-gnu/libpthread.so.0 #7 0x74019f9c in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x73d43e1d in clone () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) info thr Id Target Id Frame 86 Thread 0x7fffb13aa700 (LWP 27475) pool 0x7401e05e in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 85 Thread 0x7fff37dd8700 (LWP 27474) pool 0x7402082c in __lll_lock_wait () from /lib/x86_64-linux-gnu/libpthread.so.0 * 84 Thread 0x7fffb3baf700 (LWP 27473) pool 0x73c81037 in raise () from /lib/x86_64-linux-gnu/libc.so.6 83 Thread 0x7fffb2bad700 (LWP 27472) pool 0x7401e05e in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 81 Thread 0x7fff36dd6700 (LWP 27470) pool 0x7401e05e in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 59 Thread 0x7fffb33ae700 (LWP 27447) pool 0x7401dca4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 55 Thread 0x7fff375d7700 (LWP 27443) pool 0x73d373cd in poll () from /lib/x86_64-linux-gnu/libc.so.6 25 Thread 0x7fffb23ac700 (LWP 27408) evolution 0x73d373cd in poll () from /lib/x86_64-linux-gnu/libc.so.6 24 Thread 0x7fffb43b0700 (LWP 27407) pool 0x7401dca4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 19 Thread 0x7fff45b55700 (LWP 27402) pool 0x73d373cd in poll () from /lib/x86_64-linux-gnu/libc.so.6 18 Thread 0x7fff46756700 (LWP 27401) evolution 0x7401e05e in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 16 Thread 0x7fff9bfff700 (LWP 27389) evolution 0x7401dca4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 15 Thread 0x7fffb0ba9700 (LWP 27388) evolution 0x7401dca4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 5Thread 0x7fffda9e6700 (LWP 27373) evolution 0x73d373cd in poll () from /lib/x86_64-linux-gnu/libc.so.6 4Thread 0x7fffdb3ed700 (LWP 27372) gmain 0x73d373cd in poll () from /lib/x86_64-linux-gnu/libc.so.6 3Thread 0x7fffdbbee700 (LWP 27371) dconf worker 0x73d373cd in poll () from /lib/x86_64-linux-gnu/libc.so.6 2Thread 0x7fffe092f700 (LWP 27370) gdbus 0x73d373cd in poll () from /lib/x86_64-linux-gnu/libc.so.6 1Thread 0x77f99a00 (LWP 27334) evolution 0x73d373cd in poll () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) thread 1 [Switching to thread 1 (Thread 0x77f99a00 (LWP 27334))] #0 0x73d373cd in poll () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x73d373cd in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x742781dc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x742786ba in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x74c624a5 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #4 0x7299 in main (argc=1, argv=0x7fffe568) at main.c:711 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: evolution 3.6.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Tue Apr 16 12:04:30 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-02-04 (437 days ago) InstallationMedia:
[Desktop-packages] [Bug 1246656] Re: If keyboard layout switching hotkey is set to Ctrl+Shift, Ctrl+Shift+C/V are not working in gnome-terminal
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New = Confirmed -- 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/1246656 Title: If keyboard layout switching hotkey is set to Ctrl+Shift, Ctrl+Shift+C/V are not working in gnome-terminal Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: I have installed recent updates: gnome-control-center – 1:3.6.3-0ubuntu45 gnome-settings-daemon – 3.8.5-0ubuntu11.1 In 12.04.3 I was able to use Ctrl+Shift+C and Ctrl+Shift+V for copying and pasting text in gnome-terminal even if my keyboard layout change hotkey is set to Ctrl+Shift. In Saucy I can't use these shortcuts in gnome-terminal. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu45 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Thu Oct 31 13:59:44 2013 InstallationDate: Installed on 2013-10-20 (10 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131023.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1246656/+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 1192458] Re: [USB-Audio, playback] 4-channel mode don't work on E-MU 0204 USB
I made a patch for quirks.c , please check it. Unfortunately I do not know how to add switching to alsamixer. ** Patch added: alsa_emu0204.patch https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1192458/+attachment/3896525/+files/alsa_emu0204.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1192458 Title: [USB-Audio, playback] 4-channel mode don't work on E-MU 0204 USB Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: On E-MU 0204 USB only 2-channel mode worked. In this mode the second pair of channels just duplicates the output of the first pair. E-MU control panel under MS Windows allow to switch to 2-channel or 4-channel mode. I ran USB sniffer, and it shows switch commands that the system send to the device: == Host send 2 bytes to device: Request: 0x1 Value: 0x400 Data: 01 01//switching to 2-channel mode Data: 01 02//switching to 4-channel mode == Looks like in Ubuntu the card by default stay in 2-channel mode. Switching to 4-channel mode apparently can be added to quirks.c DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.9.6-030906-generic x86_64 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1192458/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
Hello! Thank you for update, William! I did some tests. I have enabled proposed-updates in my clean Ubuntu 13.10 installation. So I use latest packages: gnome-control-center1:3.6.3-0ubuntu45 gnome-settings-daemon 3.8.5-0ubuntu11.1. I made tests on clean user profile at each hotkey assign. I prepared a table in Google Docs (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVEusp=sharing). My test results are: 1. The default hotkey - Super+Space and Shift+Super+Space do not work in Unity session, but work in GNOME session flashback (with or without effects). We have separate bug for it (bug 1245136). 2. Alt+Shift works. 3. Ctrl+Shift works, but breaks all shortcuts, which start from Ctrl+Shift+ (for example, copy and paste in gnome-terminal is broken - see bug 1246656). Current behaviour of Ctrl+Shift disallows to select words by Ctrl+Shift+arrows. I unable to enter Firefox private session (because of Ctrl+Shift+P is broken too). So Ctrl+Shift is almost fully broken. 4. Shift+Shift works, but I can't set this shortcut from gnome-control-center in Unity (it tells only Shift R), I set it from GNOME Session FlashBack gnome-control-center (it reports Shift+Shift R). In GNOME FlashBack (with effects) Alt+Tab is broken (bug 1246643). I don't know is it connected with layout-switching bugs. Ctrl+Alt+T (launch terminal) still does not work in non-latin layout (it is bug 1226962) in Unity and GNOME Session FlashBack (without effects), but works in GNOME Session FlashBack (with effects) . So the bug is partially fixed. The aforementioned Google Docs table may be editable by anyone with link. If you want to test other hotkeys for keyboard layout change or test them under Ubuntu-GNOME - you can do it and add lines to the table. -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Invalid Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” source package in Saucy: Fix Released Bug description: A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/1218322. There still remain issues regarding keyboard shortcuts though. To install: sudo add-apt-repository ppa:attente/1218322 sudo apt-get update sudo apt-get upgrade === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the next layout key entry - try entering a key combinaison (e.g ctrl-space) - the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - press and release ctrl+left shift - the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Separate bug reports for individual layout switching hotkey combinations: Super+Space and Shift+Super+Space, found in: * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245137); * Unity session (https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1245136); * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245138); * ubiquity installer (https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1242572). Alt+Shift * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245256) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245258) * Can't set keyboard layout change to Alt+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245926) Ctrl+Shift * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245270) * Unity greeter
[Desktop-packages] [Bug 1246662] Re: Gnome Shell won't lock and ask for password when sssd auth is used
** Changed in: accountsservice Status: Unknown = New ** Changed in: accountsservice Importance: Unknown = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1246662 Title: Gnome Shell won't lock and ask for password when sssd auth is used Status in D-Bus interfaces for querying and manipulating user account information: New Status in “accountsservice” package in Ubuntu: New Bug description: I use sssd to authenticate users, and due to a change introduced in accountsservice on unlock, the desktop is shown immediately wqith no password entry. Upstream has a patch here: https://bugzilla.gnome.org/show_bug.cgi?id=708997 Please apply ASAP. I tested the patch with a dpkg-buildpackage local install. It works. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1246662/+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 1222586] Re: Gnome Online Accounts and Empathy don't connect to Facebook
** Changed in: gnome-online-accounts Status: Unknown = New ** Changed in: gnome-online-accounts Importance: Unknown = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1222586 Title: Gnome Online Accounts and Empathy don't connect to Facebook Status in GNOME Online Accounts: New Status in “gnome-online-accounts” package in Ubuntu: Confirmed Bug description: I have been experiencing this bug for a few months now in Ubuntu Gnome 12.10 and Ubuntu 12.04 (via Ubuntu Online Accounts) where when I add a FB account, it looks okay UNTIL I try and connect to it with, well, anything even the GOA itself, I tried 13.10 (like I usually do with alpha/beta releases) and this bug is still present, what's more is this bug is present in OTHER distros (I'm filing a bug on the Gnome bugzilla as I type), reason I'm filing this here is I'm making sure it's not something in Ubuntu that isn't playing nice (doubtful since Arch doesn't inherit the patches from Ubuntu) What I expected to happen: Facebook to work with GOA and Empathy, What actually happened: GOA looked like it tried to connect to FB, but gets an authorization error, I double and triple checked the details I entered, even resorted to copy/paste. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-online-accounts 3.8.2-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sun Sep 8 16:21:35 2013 InstallationDate: Installed on 2013-09-08 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130903) MarkForUpload: True SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1222586/+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 1245064] Re: Keyboard Layout Options window is missed in gnome-control-center keyboard
I have problems controlling numlock on my macbook, and I did hope to find those options to prevent Numlock turning on after Unity starts (which did happened sometimes and was impossible to change) -- 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/1245064 Title: Keyboard Layout Options window is missed in gnome-control-center keyboard Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: In next six month 14.04 will be prepared and arrived. It's LTS. So users of Ubuntu 12.04 LTS may want to update to it. What they have now (in Ubuntu 12.04.3)? They have very wide choose of available hotkeys for layout change. Let's see. In Ubuntu 12.04.3, under gnome-control-center keyboard we have (select tab Typing, click on link Layout Settings in left bottom corner of window, press the Options button in the bottom right corner of window, window Keyboard Layout Options is opened). This window allows user to set many options. It allows to set the following: Adding currency signs to certain keys Adding Esperanto circumflexes (supersigno) Alt/Win key behavior Caps Lock key behavior Compose key position Ctrl key position Japanese keyboard options Key sequence to kill the X server Key(s) to change layout Key to choose 3rd level Key to choose 5th level Miscellaneous compatibility options Numeric keypad delete key behavior Numeric keypad layout selection Use keyboard LED to show alternative layout Using space key to input non-breakable space character In Ubuntu 13.10 this setup window is missing. So user will be unable to adjust many layout switching parameters. For example, under Key(s) to change layout this window has: Alt+Caps Lock Alt+Ctrl Alt+Shift Alt+Space Any Win key (while pressed) Both Alt keys together Both Ctrl keys together Both Shift keys together Caps Lock Caps Lock (to first layout), Shift+Caps Lock (to last layout) Caps Lock (while pressed), Alt+Caps Lock does the original capslock action Ctrl+Shift Left Alt Left Alt+Left Shift Left Alt (while pressed) Left Ctrl Left Ctrl+Left Shift Left Ctrl+LeftWin (to first layout), RightCtrl+Menu (to second layout) Left Ctrl (to first layout), Right Ctrl (to last layout) Left Shift Left Win Left Win (to first layout), Right Win/Menu (to last layout) Left Win (while pressed) Menu Right Alt Rigth Alt (while pressed) Right Ctrl Right Ctrl+Right Shift Right Ctrl (while pressed) Right Shift Right Win Right Win (while pressed) Scroll Lock Shift+Caps Lock This list is very long but universal. Defined hotkeys are full-functional. For example if I set Ctrl+Shift for layout changing I can copy and paste in gnome-terminal with Ctrl+Shift+C / V. I do not want to post other Keyboard Layout Options features, that missed in 13.10. But they are of course missed. What we have now in 13.10 (ppa:attente/1218322 or proposed)? We have simple shortcuts (for example Alt+Shift and Ctrl+Shift) and do not have other. This bug report will be a table of contents of all issues, that are called from this window and are broken/missed in Ubuntu 13.10. For example, we can detect and report separate bugreports for each hotkey which does not work correctly in 13.10: Separate bug reports for individual layout switching hotkey combinations: Super+Space and Shift+Super+Space, found in: * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245137); * Unity session (https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1245136); * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245138); * ubiquity installer (https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1242572). Alt+Shift * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245256) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245258) * Can't set keyboard layout change to Alt+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245926) Ctrl+Shift * lock screen - gnome-screensaver (https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1245270) * Unity greeter (https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1245268) * Can't set keyboard layout change to Ctrl+Shift (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1245991) Shift+Shift * Can't set keyboard layout change to Shift+Shift
[Desktop-packages] [Bug 1192458] Re: [USB-Audio, playback] 4-channel mode don't work on E-MU 0204 USB
** Patch removed: patch https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1192458/+attachment/3896522/+files/patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1192458 Title: [USB-Audio, playback] 4-channel mode don't work on E-MU 0204 USB Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: On E-MU 0204 USB only 2-channel mode worked. In this mode the second pair of channels just duplicates the output of the first pair. E-MU control panel under MS Windows allow to switch to 2-channel or 4-channel mode. I ran USB sniffer, and it shows switch commands that the system send to the device: == Host send 2 bytes to device: Request: 0x1 Value: 0x400 Data: 01 01//switching to 2-channel mode Data: 01 02//switching to 4-channel mode == Looks like in Ubuntu the card by default stay in 2-channel mode. Switching to 4-channel mode apparently can be added to quirks.c DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.9.6-030906-generic x86_64 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1192458/+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 1241409] Re: Shows corrupt screen - Freezed Latop
I did the normal Ubuntu updates today and now both gnome3 and unity is crashing 3 to 4 times per hour. -- 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/1241409 Title: Shows corrupt screen - Freezed Latop Status in “xorg” package in Ubuntu: New Bug description: I have a Lenovo B590 laptop that crashed occationally with a scrambled screen on 13.04 but since I upgraded to 13.10 it crashes a couple of times a day and needs to be hard reset or left for a while to reboot on its own. This error occurs periodically in various application and until now I could not see a pattern, but I recently started using teamspeak3 and with that application I get at least 3 crashes per hour, a lot of times a lot more. (As far as I can see the bios is up to date, I downloaded the latest bios update from the lenovo website and when I run it it actually warns me that it would downlevel the bios if I run the update program so I assume that means the version on the laptop is newer.) The only proprietry driver used on the laptop is the Broadcom Wireless driver. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 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: Fri Oct 18 09:41:32 2013 DistUpgraded: 2013-09-27 09:33:17,480 DEBUG failed to SystemUnLock() (E:Not locked) DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.11.0-12-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.11.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5011] InstallationDate: Installed on 2013-03-13 (218 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130313) MachineType: LENOVO 20206 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=cd5b0845-6fe3-45d9-ba72-b3e3af7b051f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to saucy on 2013-09-27 (21 days ago) dmi.bios.date: 10/23/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H9ET67WW (1.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 20206 dmi.board.vendor: LENOVO dmi.board.version: Win8 STD EM DPK IPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH9ET67WW(1.04):bd10/23/2012:svnLENOVO:pn20206:pvrLenovoB590:rvnLENOVO:rn20206:rvrWin8STDEMDPKIPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20206 dmi.product.version: Lenovo B590 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 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.3-3ubuntu1 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 17 19:27:47 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputDP-0 HDMI-0 VGA-0 xserver.version: 2:1.14.3-3ubuntu1 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1241409/+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 1245745] Re: Loading larger folders with images takes a lot of time
As someone said on Gnome Bugzilla, if the above link does not work, this should do the trick: http://www.youtube.com/watch?v=zrbNCg4ijtU (both work for me). I have created another bug report on Gnome Bugzilla (https://bugzilla.gnome.org/show_bug.cgi?id=711201) because Nautilus does not check the file size before creating thumbnails. I have set it to only show thumbs for files less than 500 KB, but I get thumbs for files larger than 5-6 MB. See attachment. Should I create another bug report on Launchpad, too, or is it enough to have it here? ** Bug watch added: GNOME Bug Tracker #711201 https://bugzilla.gnome.org/show_bug.cgi?id=711201 ** Attachment added: Workspace 1_290.jpg https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1245745/+attachment/3896528/+files/Workspace%201_290.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1245745 Title: Loading larger folders with images takes a lot of time Status in Nautilus: New Status in “nautilus” package in Ubuntu: Triaged Bug description: I have lots of pictures on my computer and they are taken on digital camera. It makes them 1-6 MB each, and it is common to have 300-500 files in one folder. But using Nautilus to navigate there is a huge error, until I can do anything in that folder, it takes more than a minute. The file list does not appear instantly, but files appear as they get a thumbnail. See the attached screen recording, in my case it took more than 1 minute and 10 seconds to be able to do anything in that folder. It is a blocking bug. And thumbs do not have a standard size, like a square, they are shows upper/lower depending on the portrait/landscape type of picture. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Oct 29 05:52:43 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'840x550+49+189' InstallationDate: Installed on 2013-10-19 (10 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1245745/+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 1088244] Re: No Full-Disk Encryption unlock screen on some boots
This is also happening in Ubuntu 13.10. ** Tags added: raring saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1088244 Title: No Full-Disk Encryption unlock screen on some boots Status in “lightdm” package in Ubuntu: Confirmed Bug description: I use Full-Disk Encryption on 12.10. All seems to work fine sometimes - the pretty screen asks for my disk unlock password and then takes me to the login screen when I enter it correctly. Other times, it shows a completely blank black screen. I can type the password in the dark and hit enter and it goes to the login screen, but it obviously isn't very good from a usability point of view. Let me know how I can help. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Dec 9 20:15:36 2012 EcryptfsInUse: Yes InstallationDate: Installed on 2012-12-09 (0 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1088244/+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 1246669] Re: nvidia-319-updates 319.60-0ubuntu1: nvidia-319-updates kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-319-updates (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-319-updates in Ubuntu. https://bugs.launchpad.net/bugs/1246669 Title: nvidia-319-updates 319.60-0ubuntu1: nvidia-319-updates kernel module failed to build Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu: Confirmed Bug description: crashed while manually updating ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-319-updates 319.60-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.12.0-1-generic Date: Thu Oct 31 06:53:24 2013 DuplicateSignature: dkms:nvidia-319-updates:319.60-0ubuntu1:/var/lib/dkms/nvidia-319-updates/319.60/build/nv-drm.c:204:9: error: void value not ignored as it ought to be InstallationDate: Installed on 2013-10-28 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20131021.1) MarkForUpload: True PackageVersion: 319.60-0ubuntu1 SourcePackage: nvidia-graphics-drivers-319-updates Title: nvidia-319-updates 319.60-0ubuntu1: nvidia-319-updates kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319-updates/+bug/1246669/+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 1246683] [NEW] Middle button does not work for scrolling
Public bug reported: With the new Lenovo Trackpad/Trackpoint found in the **40 series laptops (tested on a T440s) scrolling does not work when pressing middle button + moving the Trackpoint. evdev seems to be set correctly ( http://paste.ubuntuusers.de/416732/ ). Middle button itself works fine for middle clicks just no scrolling. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 Uname: Linux 3.12.0-031200rc7-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 31 12:36:14 2013 InstallationDate: Installed on 2013-10-17 (13 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) MarkForUpload: True SourcePackage: xserver-xorg-input-evdev UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xserver-xorg-input-evdev (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1246683 Title: Middle button does not work for scrolling Status in “xserver-xorg-input-evdev” package in Ubuntu: New Bug description: With the new Lenovo Trackpad/Trackpoint found in the **40 series laptops (tested on a T440s) scrolling does not work when pressing middle button + moving the Trackpoint. evdev seems to be set correctly ( http://paste.ubuntuusers.de/416732/ ). Middle button itself works fine for middle clicks just no scrolling. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 Uname: Linux 3.12.0-031200rc7-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 31 12:36:14 2013 InstallationDate: Installed on 2013-10-17 (13 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) MarkForUpload: True SourcePackage: xserver-xorg-input-evdev UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1246683/+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 1245155] Re: Menus are very slow to load
No crashes/freezes, thanks to 8 GBytes of RAM most likely, but I have the exact same issue and the menus take forever to load and about an entire second to render. I also checked if it makes a difference if I'm editing a huge file or something blank. It doesn't seem that way. This also appeared with 13.10 - I'm on 64bit too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1245155 Title: Menus are very slow to load Status in “gimp” package in Ubuntu: Confirmed Bug description: When trying to use menu (File - Edit - Select - etc) it takes at time over 10 sec to appear and further 3-5sec to load the drop down menus. Often when switching from another program the previous program is still there. This does not happen in other programs. This happens with one small file and with many big files open in Gimp. Gimp used to be nice and fast, even in 13.10. Not sure which update caused it to slow down, been running 13.10 beta for a while. Shortcuts work just fine, I just can't remember them all and therefore has to use the menu. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gimp 2.8.6-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Oct 27 10:29:30 2013 ExecutablePath: /usr/bin/gimp-2.8 InstallationDate: Installed on 2013-08-04 (83 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gimp UpgradeStatus: Upgraded to saucy on 2013-08-19 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1245155/+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 1239182] Re: Crashes in nouveau CACHE_ERROR
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1239182 Title: Crashes in nouveau CACHE_ERROR Status in “xserver-xorg-video-nouveau” package in Ubuntu: Confirmed Bug description: Have been running Kubuntu 13.10 beta2 for 1 day now and have had 3 similar crashes that totally hang the machine. Oct 12 07:00:03 linux1 kernel: [50255.577404] nouveau E[ PFIFO][:01:00.0] CACHE_ERROR - ch 4 [kwin[2218]] subc 3 mthd 0x1b00 data 0x Oct 12 07:01:20 linux1 kernel: [50333.062989] nouveau E[Xorg[1486]] failed to idle channel 0x [Xorg[1486]] Have not had any previous problems running 13.04. Machine is an AMD64 Description:Ubuntu Saucy Salamander (development branch) Release:13.10 Was not doing anything special, and in fact one crash happened while the machine was idle overnight. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1239182/+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 1246692] [NEW] Eclipse crashes on closing search dialogue
Public bug reported: I upgraded from 13.04 to Xubuntu 13.10 and then I changed to kde-desktop with kde-full Now my Eclipse 3.8 with PHPEclipse crashes when I start a search with Ctrl+F in a PHP-file exactly at the moment when I close the search dialogue. with this message: # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fd7e138a528, pid=9151, tid=140565398136576 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgobject-2.0.so.0+0x19528] g_object_get_qdata+0x18 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try ulimit -c unlimited before starting Java again # # An error report file with more information is saved as: # /home/ruben/hs_err_pid9151.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. ** Affects: eclipse (Ubuntu) Importance: Undecided Status: New ** Affects: openjdk-7 (Ubuntu) Importance: Undecided Status: New ** Attachment added: hs_err_pid9151.log https://bugs.launchpad.net/bugs/1246692/+attachment/3896564/+files/hs_err_pid9151.log ** Also affects: eclipse (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eclipse in Ubuntu. https://bugs.launchpad.net/bugs/1246692 Title: Eclipse crashes on closing search dialogue Status in “eclipse” package in Ubuntu: New Status in “openjdk-7” package in Ubuntu: New Bug description: I upgraded from 13.04 to Xubuntu 13.10 and then I changed to kde- desktop with kde-full Now my Eclipse 3.8 with PHPEclipse crashes when I start a search with Ctrl+F in a PHP-file exactly at the moment when I close the search dialogue. with this message: # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fd7e138a528, pid=9151, tid=140565398136576 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgobject-2.0.so.0+0x19528] g_object_get_qdata+0x18 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try ulimit -c unlimited before starting Java again # # An error report file with more information is saved as: # /home/ruben/hs_err_pid9151.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1246692/+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 1232454] Re: Often automatic suspend dialog when I unlock
Three times in a row, after resuming from suspend I unlock the computer. Then immediately after unlock the screen goes black and then the login window again, forcing me to login yet another time. Related or separate bug? I think that it is a clash between action on suspend (Settings - Power) and action when inactive (Settings - Brightness Lock). I had suspend after 5 minutes and turning off screen after 5 minutes. I believe that this was causing duplicated unlock -- 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/1232454 Title: Often automatic suspend dialog when I unlock Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: After upgrading to 13.10 today, every time I unlock my computer after leaving it for a long time I get this prompt: -- Power Automatic suspend Computer will suspend very soon because of inactivity. -- However, the computer doesn't actually suspend. And even if I do this manually (which works) and then resume, the prompt is still there (and in that case, not true at all). This is ugly and seems broken! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubuntu-desktop 1.304 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 Date: Sat Sep 28 15:32:42 2013 InstallationDate: Installed on 2012-08-03 (420 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to saucy on 2013-09-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1232454/+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 1246698] [NEW] /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: PyOS_InputHook is not available for interactive use of PyGTK
Public bug reported: Its a fresh Saucy i386 installation, with default packages installed. Having some issues with the scaning/printing device (all in one hp model), i've first found this logged: ** hplip_config_usb_printer.log error: hp-systray must be running. Run 'hp-systray ' in a terminal. so i've installed hplip-gui which provide hp-systray; and got that output: oem@ubuncur32:~$ hp-systray [1] 15775 oem@ubuncur32:~$ HP Linux Imaging and Printing System (ver. 3.13.9) System Tray Status Service ver. 2.0 Copyright (c) 2001-13 Hewlett-Packard Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: PyOS_InputHook is not available for interactive use of PyGTK set_interactive(1) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: hplip-gui 3.13.9-1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 CupsErrorLog: E [31/Oct/2013:12:50:34 +0100] Unable to bind socket for address [v1.::1]:631 - Address already in use. E [31/Oct/2013:12:50:34 +0100] Unable to bind socket for address 127.0.0.1:631 - Address already in use. Date: Thu Oct 31 13:03:21 2013 Lpstat: device for Photosmart_C4500: hp:/usb/Photosmart_C4500_series?serial=CN87JD4109057K Lsusb: Bus 001 Device 003: ID 03f0:6b11 Hewlett-Packard Photosmart C4500 series Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe MarkForUpload: True PackageArchitecture: all Papersize: a4 PpdFiles: Photosmart_C4500: HP Photosmart c4500 Series, hpcups 3.13.9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=cc94b9dd-3c33-491b-bc40-e4a131dc9b13 ro SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC ** Affects: hplip (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1246698 Title: /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: PyOS_InputHook is not available for interactive use of PyGTK Status in “hplip” package in Ubuntu: New Bug description: Its a fresh Saucy i386 installation, with default packages installed. Having some issues with the scaning/printing device (all in one hp model), i've first found this logged: ** hplip_config_usb_printer.log error: hp-systray must be running. Run 'hp-systray ' in a terminal. so i've installed hplip-gui which provide hp-systray; and got that output: oem@ubuncur32:~$ hp-systray [1] 15775 oem@ubuncur32:~$ HP Linux Imaging and Printing System (ver. 3.13.9) System Tray Status Service ver. 2.0 Copyright (c) 2001-13 Hewlett-Packard Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: PyOS_InputHook is not available for interactive use of PyGTK set_interactive(1) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: hplip-gui 3.13.9-1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 CupsErrorLog: E [31/Oct/2013:12:50:34 +0100] Unable to bind socket for address [v1.::1]:631 - Address already in use. E [31/Oct/2013:12:50:34 +0100] Unable to bind socket for address 127.0.0.1:631 - Address already in use. Date: Thu Oct 31 13:03:21 2013 Lpstat: device for Photosmart_C4500: hp:/usb/Photosmart_C4500_series?serial=CN87JD4109057K Lsusb: Bus 001 Device 003: ID 03f0:6b11 Hewlett-Packard Photosmart C4500 series
[Desktop-packages] [Bug 1192458] Re: [USB-Audio, playback] 4-channel mode don't work on E-MU 0204 USB
The attachment alsa_emu0204.patch seems to be a patch. If it isn't, please remove the patch flag from the attachment, remove the patch tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1192458 Title: [USB-Audio, playback] 4-channel mode don't work on E-MU 0204 USB Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: On E-MU 0204 USB only 2-channel mode worked. In this mode the second pair of channels just duplicates the output of the first pair. E-MU control panel under MS Windows allow to switch to 2-channel or 4-channel mode. I ran USB sniffer, and it shows switch commands that the system send to the device: == Host send 2 bytes to device: Request: 0x1 Value: 0x400 Data: 01 01//switching to 2-channel mode Data: 01 02//switching to 4-channel mode == Looks like in Ubuntu the card by default stay in 2-channel mode. Switching to 4-channel mode apparently can be added to quirks.c DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.9.6-030906-generic x86_64 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1192458/+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 1245422] Re: Update to 24.1
This bug was fixed in the package thunderbird - 1:24.1.0+build1-0ubuntu0.12.04.1 --- thunderbird (1:24.1.0+build1-0ubuntu0.12.04.1) precise-security; urgency=low * New upstream stable release (THUNDERBIRD_24_1_0_BUILD1) - see LP: #1245422 for USN information -- Chris Coulson chris.coul...@canonical.com Mon, 28 Oct 2013 11:07:03 + ** Changed in: thunderbird (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1245422 Title: Update to 24.1 Status in “thunderbird” package in Ubuntu: Fix Released Bug description: ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1245422/+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 1245422] Re: Update to 24.1
This bug was fixed in the package thunderbird - 1:24.1.0+build1-0ubuntu0.12.10.1 --- thunderbird (1:24.1.0+build1-0ubuntu0.12.10.1) quantal-security; urgency=low * New upstream stable release (THUNDERBIRD_24_1_0_BUILD1) - see LP: #1245422 for USN information -- Chris Coulson chris.coul...@canonical.com Mon, 28 Oct 2013 11:05:11 + ** Changed in: thunderbird (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1245422 Title: Update to 24.1 Status in “thunderbird” package in Ubuntu: Fix Released Bug description: ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1245422/+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 1245422] Re: Update to 24.1
This bug was fixed in the package thunderbird - 1:24.1.0+build1-0ubuntu0.13.04.1 --- thunderbird (1:24.1.0+build1-0ubuntu0.13.04.1) raring-security; urgency=low * New upstream stable release (THUNDERBIRD_24_1_0_BUILD1) - see LP: #1245422 for USN information -- Chris Coulson chris.coul...@canonical.com Mon, 28 Oct 2013 11:04:11 + -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1245422 Title: Update to 24.1 Status in “thunderbird” package in Ubuntu: Fix Released Bug description: ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1245422/+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 1245422] Re: Update to 24.1
This bug was fixed in the package thunderbird - 1:24.1.0+build1-0ubuntu0.13.10.1 --- thunderbird (1:24.1.0+build1-0ubuntu0.13.10.1) saucy-security; urgency=low * New upstream stable release (THUNDERBIRD_24_1_0_BUILD1) - see LP: #1245422 for USN information -- Chris Coulson chris.coul...@canonical.com Mon, 28 Oct 2013 10:47:16 + ** Changed in: thunderbird (Ubuntu) Status: Confirmed = Fix Released ** Changed in: thunderbird (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1245422 Title: Update to 24.1 Status in “thunderbird” package in Ubuntu: Fix Released Bug description: ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1245422/+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 1195481] Re: [power]: gnome-control-center crashes if indicator-power is not installed in Unity
** Changed in: hundredpapercuts Status: In Progress = Fix Released ** Changed in: hundredpapercuts Importance: Low = High -- 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/1195481 Title: [power]: gnome-control-center crashes if indicator-power is not installed in Unity Status in One Hundred Papercuts: Fix Released Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-control-center” source package in Saucy: Fix Released Bug description: [ Description ] gnome-control-center's power panel crashes when indicator-power isn't installed. [ Test case ] 1. Uninstall indicator-power 2. Open System Settings and click Power 3. System Settings crashes At 3 it shouldn't crash. If you have indicator-power installed, you should see the option to configure whether it shows. [ Regression potential ] This adds some new code to check if the GSettings schema is installed, since that's a reliable way to check for indicator-power's presence, and is what the code modifies. It also makes the option appear in DEs other than Unity. There's a chance that the GSettings schema-detection work could be wrong. It also wouldn't hurt to check non-Unity environments such as a gnome-panel session. [ Original report ] I see that unity recommends indicator-power; let's make it a depends instead. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu29 ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 NonfreeKernelModules: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 overlayfs nls_utf8 isofs pci_stub vboxpci vboxnetadp vboxnetflt vboxdrv parport_pc ppdev rfcomm bnep dm_crypt intel_powerclamp coretemp kvm_intel kvm joydev crc32_pclmul ghash_clmulni_intel arc4 cryptd ath9k dm_multipath scsi_dh ath9k_common ath9k_hw uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core ath snd_hda_codec_hdmi snd_hda_codec_conexant mac80211 snd_hda_intel videodev ath3k btusb snd_hda_codec bluetooth cfg80211 snd_hwdep snd_pcm psmouse microcode toshiba_acpi toshiba_bluetooth serio_raw sparse_keymap snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd mei soundcore lpc_ich mac_hid lp parport btrfs xor zlib_deflate raid6_pq libcrc32c dm_mirror dm_region_hash dm_log ums_realtek usb_storage i915 i2c_algo_bit drm_kms_helper drm atl1c ahci libahci wmi video ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 Date: Thu Jun 27 17:42:04 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-06-14 (13 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130613) MarkForUpload: True ProcCmdline: gnome-control-center Signal: 5 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/control-center-1/panels/libpower.so Title: [power]: gnome-control-center crashed with signal 5 in g_object_new_valist() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.5-0ubuntu1 deja-dup27.3.1-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130625-0ubuntu1 gnome-control-center-unity 1.3daily13.06.14.1-0ubuntu1 indicator-datetime 12.10.3daily13.06.19-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1195481/+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 1245155] Re: Menus are very slow to load
Same situation here. I have a rather powerful PC: QuadCore 3.2 GHz, 8GB Ram, Nvidia 1024 MB, 64bit system as well. The range goes from 3 second delay to 20 seconds and longer while showing fragments of other windows' menus. The whole problem seems to only inflict GIMP and I don't notice any influence on the rest of the system. Also I get the impression that it gets worse the longer GIMP is opened, no matter how big the file is that GIMP has to handle. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1245155 Title: Menus are very slow to load Status in “gimp” package in Ubuntu: Confirmed Bug description: When trying to use menu (File - Edit - Select - etc) it takes at time over 10 sec to appear and further 3-5sec to load the drop down menus. Often when switching from another program the previous program is still there. This does not happen in other programs. This happens with one small file and with many big files open in Gimp. Gimp used to be nice and fast, even in 13.10. Not sure which update caused it to slow down, been running 13.10 beta for a while. Shortcuts work just fine, I just can't remember them all and therefore has to use the menu. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gimp 2.8.6-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Oct 27 10:29:30 2013 ExecutablePath: /usr/bin/gimp-2.8 InstallationDate: Installed on 2013-08-04 (83 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gimp UpgradeStatus: Upgraded to saucy on 2013-08-19 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1245155/+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 1189165] Re: [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
*** This bug is a duplicate of bug 1041790 *** https://bugs.launchpad.net/bugs/1041790 Also crahses on fresh install of Linux mint 15 (based on Ubuntu 13.04) when the cinnamon screensaver activates. Attached the syslog (the last part of it is intrested), also the i915_error_state. ** Attachment added: reports.zip https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1189165/+attachment/3896586/+files/reports.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1189165 Title: [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung Status in “xserver-xorg-video-intel” package in Ubuntu: Incomplete Bug description: Release of Ubuntu:13.10 Package Version: Installed: 2:2.21.9-0ubuntu1 Expected Results: Actual Results: System not particularry loaded at the time of the crash, no video player in action, I was browsing with nautilus from CurrentDmesg: 16845.827652] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [16845.827658] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state [16847.827129] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [16847.827388] [drm:i915_reset] *ERROR* GPU hanging too fast, declaring wedged! [16847.827391] [drm:i915_reset] *ERROR* Failed to reset chip. from LightdmDisplay.log: Loading extension GLX (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x7f29fdab844d] (EE) 1: /usr/bin/X (mieqEnqueue+0x22b) [0x7f29fda9a4fb] (EE) 2: /usr/bin/X (QueuePointerEvents+0x52) [0x7f29fd9814f2] (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f29f7a28000+0x5f44) [0x7f29f7a2df44] (EE) 4: /usr/bin/X (0x7f29fd913000+0x94a48) [0x7f29fd9a7a48] (EE) 5: /usr/bin/X (0x7f29fd913000+0xbd2d0) [0x7f29fd9d02d0] (EE) 6: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f29fca13000+0xfbd0) [0x7f29fca22bd0] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x7) [0x7f29fb72f747] (EE) 8: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x34) [0x7f29fc80a344] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f29f9f6d000+0x391b0) [0x7f29f9fa61b0] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f29f9f6d000+0x3a0ef) [0x7f29f9fa70ef] (EE) 11: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f29f9f6d000+0x60a2b) [0x7f29f9fcda2b] (EE) 12: /usr/bin/X (BlockHandler+0x44) [0x7f29fd96ef94] (EE) 13: /usr/bin/X (WaitForSomething+0x124) [0x7f29fdab5974] (EE) 14: /usr/bin/X (0x7f29fd913000+0x57c71) [0x7f29fd96ac71] (EE) 15: /usr/bin/X (0x7f29fd913000+0x4758a) [0x7f29fd95a58a] (EE) 16: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7f29fb65fea5] (EE) 17: /usr/bin/X (0x7f29fd913000+0x478d1) [0x7f29fd95a8d1] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. (EE) [mi] EQ overflow continuing. 100 events have been dropped. ProblemType: BugDistroRelease: Ubuntu 13.10 Package: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None Date: Sun Jun 9 17:01:01 2013 DistUpgraded: 2013-05-01 20:34:06,287 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: open-vm-tools, 2013.04.16, 3.9.0-3-generic, x86_64: installed open-vm-tools, 2013.04.16, 3.9.0-4-generic, x86_64: installed vboxhost, 4.2.12, 3.9.0-2-generic, x86_64: installed vboxhost, 4.2.12, 3.9.0-3-generic, x86_64: installed vboxhost, 4.2.12, 3.9.0-4-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2012-10-12 (239 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20121011) MachineType: Gigabyte Technology Co., Ltd. H55M-S2H MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-13-generic root=UUID=874a505d-d121-4029-b543-ef8ce5fb9498 ro quiet splash vt.handoff=7SourcePackage: compiz UpgradeStatus: Upgraded to saucy on 2013-05-01 (38 days ago) dmi.bios.date: 08/20/2010 dmi.bios.vendor: Award Software International, Inc.