[Touch-packages] [Bug 1400230] [NEW] Recommends on firefox-locale-de dropped in trusty-updates
Public bug reported: The initial package of language-pack-de-base had a Recommends on firefox-locale-de: http://packages.ubuntu.com/de/trusty/all/language-pack-de-base In trusty-updates this Recommends was dropped: http://packages.ubuntu.com/de/trusty-updates/all/language-pack-de-base The changelog for the language packs doesn't contain the package history (only Initial Release), so I can't tell whether this was intentional or a bug. To me it looks like a bug and the behaviour shouldn't change in a LTS release: Anyone who installed firefox-locale-de through the language pack will have the firefox-locale-de package suggested for auto-removal. Cheers, Moritz ** Affects: language-pack-de-base (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-de-base in Ubuntu. https://bugs.launchpad.net/bugs/1400230 Title: Recommends on firefox-locale-de dropped in trusty-updates Status in language-pack-de-base package in Ubuntu: New Bug description: The initial package of language-pack-de-base had a Recommends on firefox-locale-de: http://packages.ubuntu.com/de/trusty/all/language-pack-de-base In trusty-updates this Recommends was dropped: http://packages.ubuntu.com/de/trusty-updates/all/language-pack-de-base The changelog for the language packs doesn't contain the package history (only Initial Release), so I can't tell whether this was intentional or a bug. To me it looks like a bug and the behaviour shouldn't change in a LTS release: Anyone who installed firefox-locale-de through the language pack will have the firefox-locale-de package suggested for auto- removal. Cheers, Moritz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-de-base/+bug/1400230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394155] Re: Crash of unity8-dash possible through Today scope
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1394155 Title: Crash of unity8-dash possible through Today scope Status in the base for Ubuntu mobile products: New Status in unity-scopes-shell package in Ubuntu: In Progress Bug description: On krillin r165: 1) Go to the Today scope 2) Scroll to the bottom 3) Tap Tell me more... 4) Scroll to the bottom again 5) Tap Finished Crash! To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1394155/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 445333] Re: remember password on printing to windows printers does not work
Hello, I upgraded from trusty-proposed: - libgail-3-0:amd64 3.10.8-0ubuntu1.3 - libgtk-3-0:amd64 3.10.8-0ubuntu1.3 Here is my test scenario (using gedit): Nothing in gnome keyring Print text1 A dialog asked for credentials (I fill and check remember) job is printed credentials appear in gnome keyring Print text2 no dialog appear, job is printed Print text3 no dialog appear, job is printed Then I deleted the credentials in gnome keyring Print text4 A dialog asked again for credentials. The new packages looks perfect to me! :) ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/445333 Title: remember password on printing to windows printers does not work Status in GTK+ GUI Toolkit: Fix Released Status in gtk+2.0 package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+2.0 source package in Trusty: Triaged Status in gtk+3.0 source package in Trusty: Fix Committed Bug description: [Impact] * Passwords for printers are not stored and the users are required to retype it with every print job for password protected printers [Test Case] * Configure a remote (shared via SMB), password-protected printer. * Request a print job. * Each subsequent job will require retyping the password. [Regression Potential] * Cherry-pick from upstream (present in Gtk+3.13.8). * Minor conflict resolution needed (line numbers changed) [Other Info] * Original bug description: i am printing from my ubuntu karmic to a windows box. everytime i print i get asked to input username and password to windows box, then the document gets printed. there is a remember password checkbox, but it keeps asking me when printing the next document. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/445333/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399948] Re: Commands on found if both ./bin and ~/bin in PATH
I suspect that it is some cache which is not properly getting reset. Your assumption is somewhat correct. Bash does cache the locations of executables it located. The keyword to look for would be hashing. At first sight that behaviour doesn't seem to have changed for quite a long time, it can be influenced via a configuration option though. Could you please try to set the 'checkhash' option, and check if it still behaves the way you described? The command to do this would be: shopt -s checkhash you can check if the option was set successfully as follows: shopt checkhash wich sould return: checkhash on The effect of enabling this option should be that when a command is processed not just the hashed file is executed, but beforehand it will be checked if the file does actually exists and otherwise the executable will be rehashed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1399948 Title: Commands on found if both ./bin and ~/bin in PATH Status in bash package in Ubuntu: New Bug description: I use (and have been using for 20 years or so) a path variable that looks like PATH=.;./bin;~/bin;$PATH; export PATH This PATH should execute in priority: project specific commands (in the working directory, or the bin subdirectory of the working directory), my personal commands (in my $HOME/bin folder) and then system commands. The problem seems to be that when I start a shell in my home directory, it will cache the location of commands in ~/bin as if they were in ./bin and then will be unable to find them if I cd out of my home directory. For example, I have a personal command called SlideShow: Here is a short example: ralmond@Limu:~$ file ~/bin/SlideShow /home/ralmond/bin/SlideShow: POSIX shell script, ASCII text executable ralmond@Limu:~$ # Works fine if I execute it from home directory ralmond@Limu:~$ SlideShow Pictures/ ^C [Working as expected] ralmond@Limu:~$ cd Pictures/ ralmond@Limu:~/Pictures$ #But if I change directory it does not work. ralmond@Limu:~/Pictures$ SlideShow Pics bash: ./bin/SlideShow: No such file or directory ralmond@Limu:~/Pictures$ #If I start the shell in a directory other than home it works ralmond@Limu:~/Pictures$ bash ralmond@Limu:~/Pictures$ SlideShow Pics ^C [Working as expected] I suspect that it is some cache which is not properly getting reset. Here are my system details: ralmond@Limu:~/Pictures$ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 ralmond@Limu:~/Pictures$ apt-cache policy bash bash: Installed: 4.3-7ubuntu1.5 Candidate: 4.3-7ubuntu1.5 Version table: *** 4.3-7ubuntu1.5 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 4.3-6ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ralmond@Limu:~/Pictures$ ^C ralmond@Limu:~/Pictures$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1399948/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400205] Re: network-manager may start before libsystemd-logind
The attachment network-manager-logind.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 Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1400205 Title: network-manager may start before libsystemd-logind Status in network-manager package in Ubuntu: Confirmed Bug description: When NetworkManager starts, it requests systemd login-monitor notifications through the libsystemd-login sd_login_monitor_new(3) API. This API will fail if the systemd-logind service has not been started, since it directly accesses directories in /run/systemd. As far as I can tell, systemd-logind in Utopic is started on-demand (through DBUS service activation). So, there's no guarantee that it has been started at the point during boot when NetworkMonitor is started. I attached a patch to upstart .conf file with one way to fix it -- it contacts the DBUS logind API within pre-start to ensure it has been started. NOTE: you will not see the error in syslog -- NetworkManager logs it to stderr which is /dev/null. If you enable --no-daemon on NetworkManager, the error (sd_login_monitor_new failed) should get logged to /var/log/upstart/network-manager.log. NOTE: even with this fix, I saw that sd_login_monitor_new failed -- I believe that's a bug in Utopic's systemd (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400203). I had to patch both to resolve a suspend/resume issue for me. Seen on: Ubuntu 14.10 NetworkManager 0.9.8.8-0ubuntu28 libsystemd-login0 208-8ubuntu8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1400205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400235] [NEW] [Dell M4800] Screen does not wake up after sleep
Public bug reported: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu vivid ** Description changed: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. + The problem is is present in todays (2014-12-8) Vivid daily image + (booted with nomodeset, but not done any configuration of the screen). + ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: - + ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: - NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Dell Device [1028:05cc] + NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no
[Touch-packages] [Bug 1268151] Re: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep
I opened a new bug report #1400235 for my particular hardware. Also, the problem is is present in todays Vivid daily image (booted with nomodeset). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1268151 Title: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep Status in xorg package in Ubuntu: Incomplete Bug description: With my Dell Precision M4800, GK106GLM [Quadro K2100M], QHD+ display, and either nvidia-graphics-drivers-331 or nvidia-graphics-drivers-319 once the display shuts off, it will not wake up anymore, and the screen stays dark. A cycle of the following will leave the display dark: xset dpms force off; sleep 30; xset dpms force on WORKAROUND: A restart of the Xserver will bring back the display. WORKAROUND: Don't allow DPMS to switch off the display: xset dpms 0 0 0 xset -q -d :0.0 Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 20 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 0cycle: 0 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Sat Jan 11 12:06:30 2014 InstallationDate: Installed on 2014-01-07 (3 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1268151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399953] Re: Google contacts authentication problem with U-O-A (Trusty, Unity7)
I can reproduce this as well. I'll try to figure out what's happening.
** Changed in: account-plugins (Ubuntu)
Status: New = Confirmed
** Also affects: evolution-data-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to account-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1399953
Title:
Google contacts authentication problem with U-O-A (Trusty, Unity7)
Status in account-plugins package in Ubuntu:
Confirmed
Status in evolution-data-server package in Ubuntu:
New
Bug description:
I simply can not access Google-Contacts with Ubuntu Online Accounts.
After I enabled EDS contacts, If I open evolution click on the
address-book list, it shows following error:
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._e_2dclient_2derror_2dquark.Code5:
Authentication required.
I tried to revoke access for UOA from google accounts, re-authorize
it. But it did not help. However google-calendar integration is
working fine. And if log into gnome-shell add my Google account in
Gnome-Online-Accounts(G-O-A), contacts works as well. The problem only
appearing for google-contacts in UOA. And I couldn't find anything
significant in syslog.
I have multiple google accounts enabled in UOA.
Here is some more information:
khurshid@mypc:~$ ag-tool list-enabled 11
--
Type Service Name
IM google-im
contacts google-contacts
documents google-drive
khurshid@mypc:~$ account-console show 11 | grep Cred
--
CredentialsId: 14 (class 'int')
khurshid@mypc:~$ strings ~/.cache/signon-ui/cookies/14.jar
---
GALX=IZLpIn1Fakc; secure; domain=accounts.google.com; path=/
GAPS=1:9VjmZnLpxD0TzDbRqMElmGKRyLMg:qrKFg6yRv_4g6hT; secure; HttpOnly;
expires=Tue, 29-Nov-2016 13:35:15 GMT; domain=accounts.google.com; path=/
NID=67=goKtbf0sx5dy_HuXXCG5EEfPfrTKyL_7iIDBf5aNjaA843PF1lAu3pbDjY5jvH5s-FcY81k_a-0gQpI7RymkAq_apdelo_lpkPrnVW_q7N6h8_a59sN3iNKhGJ5G_dsgYf56FT;
HttpOnly; expires=Mon, 01-Jun-2015 13:35:15 GMT; domain=.google.com; path=/
SID=DQAAAPEAAACXK66HAgH7SV83LSOjKN_ZQPiR7qCeL7Yk9p98HlYTGNET_CH2lTTWvj2jPhQasPf78TcT0cc_lRNO7wU-TuXQl2JPj28PJXaxxbX1NZBYrt-qdhtTwrRk2qiewRN1QPH2AuYtaJTsbX5PNsy-o-uxiFGCTD5u0QTYOTdGvCu1UD9lZs5fUdtLbq;
expires=Tue, 29-Nov-2016 13:35:15 GMT; domain=.google.com; path=/
LSID=lso|s.IN:DQAAAPAAAMxO_ttZTWoynoEsoHEt_zDEgk7pXkbqdQ9bnogq4HcnCNOAM8nxRsnqBWLmTF5AkgWc0XY-qjU_SI_K9JX_pBpaIAtq0o1hBZD0sbQB_Lw81Twwqewnj4J68K3aS0OcVnEm_S0G_MBtzbV-T26lcxwHGheh8mhtUpIDdUnvpjdFbQTe-fLwd4UsTku7s;
secure; HttpOnly; expires=Tue, 29-Nov-2016 13:35:15 GMT;
domain=accounts.google.com; path=/
cHSID=AYLDuiTZv-sSOmfy; HttpOnly; expires=Tue, 29-Nov-2016 13:35:15 GMT;
domain=.google.com; path=/
kSSID=AqfiEDXUGfWBBl9; secure; HttpOnly; expires=Tue, 29-Nov-2016 13:35:15
GMT; domain=.google.com; path=/
lAPISID=Q0uvxSM2ZHgNs8L4/AR76LUN_S_xqCq2; expires=Tue, 29-Nov-2016 13:35:15
GMT; domain=.google.com; path=/
uSAPISID=bcf2oH6xaV8r1-/AIol-KZlQU551Z0uT; secure; expires=Tue, 29-Nov-2016
13:35:15 GMT; domain=.google.com; path=/
ACCOUNT_CHOOSER=AFx_qI6UxIzXMxLi2j9QUAAymv8WTOJR; secure; HttpOnly;
expires=Tue, 29-Nov-2016 13:35:15 GMT; domain=accounts.google.com; path=/
NID=67=I2DxXlt4TwixPqUzJOOKAUifcVobnGLasEaA31uwxPwfORegpkxpdcdUK-upq-8V2ZB5FDFGJEb3K4T5rZVyI7cBN2ZpGZwLQrwBLggtz1KBJTK_eA;
HttpOnly; expires=Mon, 01-Jun-2015 13:35:18 GMT; domain=.google.co.in; path=/
SID=DQAAAPCXK66HAgH7SV83MLSOjKN_ZQPiR7qCeL7Yk9p98HYTGNET_CH2lTTWvj2jPhQasPf78TcT0cc_lRNOGRjTjTmV2maEhHLzTqJFQ-TMDyKueBLR_-4fcC2gUW-0lALMCuGaaTY0DX7wU-TuXQl2JPj28PJXaxxbX1NZBYrt-qdhtTwrRk2qieuSYguA2bKAdnvxtmKfD9ElQoSc;
expires=Tue, 29-Nov-2016 13:35:18 GMT; domain=.google.co.in; path=/
eHSID=Au4nSmb8XraQ99XrQ; HttpOnly; expires=Tue, 29-Nov-2016 13:35:18 GMT;
domain=.google.co.in; path=/
mSSID=ACnCCS4X8GYIqpMrF; secure; HttpOnly; expires=Tue, 29-Nov-2016 13:35:18
GMT; domain=.google.co.in; path=/
nAPISID=Q0uvxSM2ZHgNs4/AR76LUN_S_XVxqCq2; expires=Tue, 29-Nov-2016 13:35:18
GMT; domain=.google.co.in; path=/
wSAPISID=bcf2oH6YWx8r1-/AIol-KZlQU551Z0uT; secure; expires=Tue, 29-Nov-2016
13:35:18 GMT; domain=.google.co.in; path=/
LSOSID=DQAAAPnyGDiPN1Xi8giBFN-FOwwjVkTtCvqAaxuOg4mLjKW1k_NqKdZh; secure;
HttpOnly; expires=Tue, 29-Nov-2016 13:35:19 GMT; domain=accounts.google.com;
path=/o
version:
libaccount-plugin-google: 0.11+14.04.20140409.1-0ubuntu1
evolution-data-server: 3.10.4-0ubuntu1.5
To manage
[Touch-packages] [Bug 1394155] Re: Crash of unity8-dash possible through Today scope
** Changed in: unity-scopes-shell (Ubuntu) Milestone: None = ubuntu-14.09 ** Changed in: unity-scopes-shell (Ubuntu) Milestone: ubuntu-14.09 = ubuntu-14.10 ** Changed in: unity-scopes-shell (Ubuntu) Milestone: ubuntu-14.10 = ubuntu-15.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1394155 Title: Crash of unity8-dash possible through Today scope Status in the base for Ubuntu mobile products: New Status in unity-scopes-shell package in Ubuntu: In Progress Bug description: On krillin r165: 1) Go to the Today scope 2) Scroll to the bottom 3) Tap Tell me more... 4) Scroll to the bottom again 5) Tap Finished Crash! To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1394155/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
I cannot imagine how a missing password input field in the lock screen could be related to an LDAP configuration issue on our side. If the authentication would fail after entering the password, then yes, of course this could be such a problem. But a password field should always be shown by the unlock screen, regardless of the authentication backend. Also our LDAP configuration is working for several years now without problems. Only since the upgrade to Ubuntu 14.04 this problem with the lock screen has started appearing. All other applications, including the login screen (lightdm) are working fine. By the way, we have a dual monitor setup, too. Our home file systems are on an NFS fileserver, mounted using automount and with root_squash enabled (this means that root does not have full access to my home directory, but only the same rights as all other accounts). If there is a root process trying to access files in my home this would fail. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 502642] Re: .ts files always get recognized as application/x-linguist and never as video/mp2t (mpeg transport stream)
I hate to say it, but as part of a small paid open source development team with a very active community bug tracker for our own product, which is not supposed to prevent us from working on the features we need to implement (for the paying customers who make the open product possible) I can very well understand why this is still an issue after four, five or whatever years. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/502642 Title: .ts files always get recognized as application/x-linguist and never as video/mp2t (mpeg transport stream) Status in shared MIME database: Fix Released Status in shared-mime-info package in Ubuntu: Fix Released Status in Baltix GNU/Linux: New Bug description: Binary package hint: shared-mime-info I checked Hardy, Jaunty and Karmic: *.ts files are always mapped to application/x-linguist by /usr/share/mime/packages/freedesktop.org.xml. But there are several Linux-based settop boxes that record videos in *.ts-files. So if application/x-linguist is obsolete then it should simply be replaced by video/mpeg. Otherwise the mime framework has to distinguish such files by inspecting their headers. If someone knows more about x-linguist files, please add a comment! The problem has already been reported upstream two month ago (see freedesktop.org above). But for 10.04 LTS we should fix it by a patch, if it is not fixed upstream by then. As a workaround copy the attached file to ~/.local/share/mime/packages/mpeg-ts.xml and update your mime-database with: $ update-mime-database ~/.local/share/mime To trigger the regeneration of failed thumbnails just delete them: $ rm ~/.thumbnails/fail/gnome-thumbnail-factory/*.png ProblemType: Bug Architecture: i386 Date: Sun Jan 3 17:47:29 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) Package: shared-mime-info 0.70-0ubuntu1 ProcEnviron: PATH=(custom, user) LANG=de_CH.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-16.53-generic SourcePackage: shared-mime-info Uname: Linux 2.6.31-16-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/502642/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399953] Re: Google contacts authentication problem with U-O-A (Trusty, Unity7)
** Attachment added: Logs from evolution-addressbook-factory
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1399953/+attachment/4276009/+files/eds.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to account-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1399953
Title:
Google contacts authentication problem with U-O-A (Trusty, Unity7)
Status in account-plugins package in Ubuntu:
Confirmed
Status in evolution-data-server package in Ubuntu:
New
Bug description:
I simply can not access Google-Contacts with Ubuntu Online Accounts.
After I enabled EDS contacts, If I open evolution click on the
address-book list, it shows following error:
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._e_2dclient_2derror_2dquark.Code5:
Authentication required.
I tried to revoke access for UOA from google accounts, re-authorize
it. But it did not help. However google-calendar integration is
working fine. And if log into gnome-shell add my Google account in
Gnome-Online-Accounts(G-O-A), contacts works as well. The problem only
appearing for google-contacts in UOA. And I couldn't find anything
significant in syslog.
I have multiple google accounts enabled in UOA.
Here is some more information:
khurshid@mypc:~$ ag-tool list-enabled 11
--
Type Service Name
IM google-im
contacts google-contacts
documents google-drive
khurshid@mypc:~$ account-console show 11 | grep Cred
--
CredentialsId: 14 (class 'int')
khurshid@mypc:~$ strings ~/.cache/signon-ui/cookies/14.jar
---
GALX=IZLpIn1Fakc; secure; domain=accounts.google.com; path=/
GAPS=1:9VjmZnLpxD0TzDbRqMElmGKRyLMg:qrKFg6yRv_4g6hT; secure; HttpOnly;
expires=Tue, 29-Nov-2016 13:35:15 GMT; domain=accounts.google.com; path=/
NID=67=goKtbf0sx5dy_HuXXCG5EEfPfrTKyL_7iIDBf5aNjaA843PF1lAu3pbDjY5jvH5s-FcY81k_a-0gQpI7RymkAq_apdelo_lpkPrnVW_q7N6h8_a59sN3iNKhGJ5G_dsgYf56FT;
HttpOnly; expires=Mon, 01-Jun-2015 13:35:15 GMT; domain=.google.com; path=/
SID=DQAAAPEAAACXK66HAgH7SV83LSOjKN_ZQPiR7qCeL7Yk9p98HlYTGNET_CH2lTTWvj2jPhQasPf78TcT0cc_lRNO7wU-TuXQl2JPj28PJXaxxbX1NZBYrt-qdhtTwrRk2qiewRN1QPH2AuYtaJTsbX5PNsy-o-uxiFGCTD5u0QTYOTdGvCu1UD9lZs5fUdtLbq;
expires=Tue, 29-Nov-2016 13:35:15 GMT; domain=.google.com; path=/
LSID=lso|s.IN:DQAAAPAAAMxO_ttZTWoynoEsoHEt_zDEgk7pXkbqdQ9bnogq4HcnCNOAM8nxRsnqBWLmTF5AkgWc0XY-qjU_SI_K9JX_pBpaIAtq0o1hBZD0sbQB_Lw81Twwqewnj4J68K3aS0OcVnEm_S0G_MBtzbV-T26lcxwHGheh8mhtUpIDdUnvpjdFbQTe-fLwd4UsTku7s;
secure; HttpOnly; expires=Tue, 29-Nov-2016 13:35:15 GMT;
domain=accounts.google.com; path=/
cHSID=AYLDuiTZv-sSOmfy; HttpOnly; expires=Tue, 29-Nov-2016 13:35:15 GMT;
domain=.google.com; path=/
kSSID=AqfiEDXUGfWBBl9; secure; HttpOnly; expires=Tue, 29-Nov-2016 13:35:15
GMT; domain=.google.com; path=/
lAPISID=Q0uvxSM2ZHgNs8L4/AR76LUN_S_xqCq2; expires=Tue, 29-Nov-2016 13:35:15
GMT; domain=.google.com; path=/
uSAPISID=bcf2oH6xaV8r1-/AIol-KZlQU551Z0uT; secure; expires=Tue, 29-Nov-2016
13:35:15 GMT; domain=.google.com; path=/
ACCOUNT_CHOOSER=AFx_qI6UxIzXMxLi2j9QUAAymv8WTOJR; secure; HttpOnly;
expires=Tue, 29-Nov-2016 13:35:15 GMT; domain=accounts.google.com; path=/
NID=67=I2DxXlt4TwixPqUzJOOKAUifcVobnGLasEaA31uwxPwfORegpkxpdcdUK-upq-8V2ZB5FDFGJEb3K4T5rZVyI7cBN2ZpGZwLQrwBLggtz1KBJTK_eA;
HttpOnly; expires=Mon, 01-Jun-2015 13:35:18 GMT; domain=.google.co.in; path=/
SID=DQAAAPCXK66HAgH7SV83MLSOjKN_ZQPiR7qCeL7Yk9p98HYTGNET_CH2lTTWvj2jPhQasPf78TcT0cc_lRNOGRjTjTmV2maEhHLzTqJFQ-TMDyKueBLR_-4fcC2gUW-0lALMCuGaaTY0DX7wU-TuXQl2JPj28PJXaxxbX1NZBYrt-qdhtTwrRk2qieuSYguA2bKAdnvxtmKfD9ElQoSc;
expires=Tue, 29-Nov-2016 13:35:18 GMT; domain=.google.co.in; path=/
eHSID=Au4nSmb8XraQ99XrQ; HttpOnly; expires=Tue, 29-Nov-2016 13:35:18 GMT;
domain=.google.co.in; path=/
mSSID=ACnCCS4X8GYIqpMrF; secure; HttpOnly; expires=Tue, 29-Nov-2016 13:35:18
GMT; domain=.google.co.in; path=/
nAPISID=Q0uvxSM2ZHgNs4/AR76LUN_S_XVxqCq2; expires=Tue, 29-Nov-2016 13:35:18
GMT; domain=.google.co.in; path=/
wSAPISID=bcf2oH6YWx8r1-/AIol-KZlQU551Z0uT; secure; expires=Tue, 29-Nov-2016
13:35:18 GMT; domain=.google.co.in; path=/
LSOSID=DQAAAPnyGDiPN1Xi8giBFN-FOwwjVkTtCvqAaxuOg4mLjKW1k_NqKdZh; secure;
HttpOnly; expires=Tue, 29-Nov-2016 13:35:19 GMT; domain=accounts.google.com;
path=/o
version:
libaccount-plugin-google: 0.11+14.04.20140409.1-0ubuntu1
evolution-data-server: 3.10.4-0ubuntu1.5
To manage notifications about this bug go to:
[Touch-packages] [Bug 1400235] Re: [Dell M4800] Screen does not wake up after sleep
** Tags added: latest-bios-a09 trusty ** Summary changed: - [Dell M4800] Screen does not wake up after sleep + 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset --
[Touch-packages] [Bug 1400235] Re: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep
** Also affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Renderer: Software Tags: vivid ubuntu
[Touch-packages] [Bug 1400235] Re: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep
Marius B. Kotsbak, thank you for reporting this and helping make Ubuntu better. Could you please advise on which NVIDIA driver version you tested specifically, and from what source (Ubuntu repository or nvidia.com)? ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8
[Touch-packages] [Bug 1400235] Re: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep
apport information ** Tags added: apport-collected reproducible ** Description changed: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 + --- + .tmp.unity.support.test.1: + + ApportVersion: 2.14.7-0ubuntu10 + Architecture: amd64 + CasperVersion: 1.346 + CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' + CompositorRunning: compiz + CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' + CompositorUnredirectFSW: true + CurrentDesktop: Unity + DistUpgraded: Fresh install + DistroCodename: vivid + DistroRelease: Ubuntu 15.04 + DistroVariant: ubuntu + DkmsStatus: + bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed + nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed + nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed + ExtraDebuggingInterest: Yes, including running git bisection searches + GraphicsCard: + NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) +Subsystem: Dell Device [1028:05cc] + LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) + MachineType: Dell Inc. Precision M4800 + Package: xorg 1:7.7+7ubuntu2 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- + ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 + Renderer: Software + Tags: vivid ubuntu reproducible compiz-0.9 + Uname: Linux 3.16.0-25-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 06/26/2014 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A09 + dmi.board.name: 077KCT +
[Touch-packages] [Bug 1400235] BootLog.txt
apport information ** Attachment added: BootLog.txt https://bugs.launchpad.net/bugs/1400235/+attachment/4276029/+files/BootLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
[Touch-packages] [Bug 1400235] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1400235/+attachment/4276030/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- ProcVersionSignature: Ubuntu 3.16.0-25.33-generic
[Touch-packages] [Bug 1400235] DpkgLog.txt
apport information ** Attachment added: DpkgLog.txt https://bugs.launchpad.net/bugs/1400235/+attachment/4276032/+files/DpkgLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
[Touch-packages] [Bug 1400235] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1400235/+attachment/4276031/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- ProcVersionSignature: Ubuntu 3.16.0-25.33-generic
[Touch-packages] [Bug 1400235] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1400235/+attachment/4276042/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
[Touch-packages] [Bug 1400235] xdpyinfo.txt
apport information ** Attachment added: xdpyinfo.txt https://bugs.launchpad.net/bugs/1400235/+attachment/4276048/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
[Touch-packages] [Bug 1400235] UnitySupportTest.txt
apport information ** Attachment added: UnitySupportTest.txt https://bugs.launchpad.net/bugs/1400235/+attachment/4276043/+files/UnitySupportTest.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- ProcVersionSignature: Ubuntu
[Touch-packages] [Bug 1400235] Xrandr.txt
apport information ** Attachment added: Xrandr.txt https://bugs.launchpad.net/bugs/1400235/+attachment/4276047/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Renderer:
[Touch-packages] [Bug 1400235] XorgLog.txt
apport information ** Attachment added: XorgLog.txt https://bugs.launchpad.net/bugs/1400235/+attachment/4276046/+files/XorgLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
[Touch-packages] [Bug 1400235] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1400235/+attachment/4276040/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
[Touch-packages] [Bug 1400235] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1400235/+attachment/4276036/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Renderer:
[Touch-packages] [Bug 1400235] LightdmLog.txt
apport information ** Attachment added: LightdmLog.txt https://bugs.launchpad.net/bugs/1400235/+attachment/4276035/+files/LightdmLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
[Touch-packages] [Bug 1400235] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1400235/+attachment/4276041/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Renderer:
[Touch-packages] [Bug 1400235] Re: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep
Marius B. Kotsbak, please do not add any additional bug tasks. If the root cause is found, the package will be reassigned accordingly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
[Touch-packages] [Bug 1400235] Re: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep
** No longer affects: nvidia-graphics-drivers-331 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Renderer: Software Tags: vivid ubuntu reproducible compiz-0.9 Uname: Linux
[Touch-packages] [Bug 1400235] Re: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep
I am testing with nvidia-331 version 331.89-0ubuntu6 from Vivid now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Renderer: Software Tags: vivid ubuntu reproducible compiz-0.9 Uname:
[Touch-packages] [Bug 1400235] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1400235/+attachment/4276039/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- ProcVersionSignature: Ubuntu 3.16.0-25.33-generic
[Touch-packages] [Bug 1400235] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1400235/+attachment/4276037/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Renderer:
[Touch-packages] [Bug 1400235] xserver.errors.txt
apport information ** Attachment added: xserver.errors.txt https://bugs.launchpad.net/bugs/1400235/+attachment/4276050/+files/xserver.errors.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- ProcVersionSignature: Ubuntu 3.16.0-25.33-generic
[Touch-packages] [Bug 1400235] LightdmDisplayLog.txt
apport information ** Attachment added: LightdmDisplayLog.txt https://bugs.launchpad.net/bugs/1400235/+attachment/4276034/+files/LightdmDisplayLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- ProcVersionSignature: Ubuntu
[Touch-packages] [Bug 1400235] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1400235/+attachment/4276038/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 --- .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
[Touch-packages] [Bug 1400244] [NEW] Qtbase 5.4.0 fails to build on powerpc
Public bug reported: Build log at https://launchpadlibrarian.net/192081247/buildlog_ubuntu- vivid-powerpc.qtbase-opensource-src_5.4.0~rc- 0ubuntu1~vivid1~test3_FAILEDTOBUILD.txt.gz g++ -c -include .pch/Qt5Network -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -O2 -fvisibility=hidden -fvisibility-inlines-hidden -std=c++0x -fno-exceptions -Wall -W -D_REENTRANT -fPIC -DQT_NO_USING_NAMESPACE -DQT_BUILD_NETWORK_LIB -DQT_BUILDING_QT -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_BEFORE=0x05 -DQT_NO_EXCEPTIONS -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_CORE_LIB -I../../mkspecs/linux-g++ -I. -I../../include -I../../include/QtNetwork -I../../include/QtNetwork/5.4.0 -I../../include/QtNetwork/5.4.0/QtNetwork -Ikernel -I../../include/QtCore/5.4.0 -I../../include/QtCore/5.4.0/QtCore -I../../include/QtCore -I.moc -o .obj/qabstractsocketengine.o socket/qabstractsocketengine.cpp image/qimage_conversions.cpp:2257:9: error: expected '}' before numeric constant 0, 0, 0, 0 ^ image/qimage_conversions.cpp:2257:9: error: expected '}' before numeric constant image/qimage_conversions.cpp:2257:9: error: expected ',' or ';' before numeric constant image/qimage_conversions.cpp:2258:5: error: expected declaration before '}' token }, // Format_RGBA ^ More information about Qt testing at https://wiki.ubuntu.com/Touch/QtTesting ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: qt5.4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1400244 Title: Qtbase 5.4.0 fails to build on powerpc Status in qtbase-opensource-src package in Ubuntu: New Bug description: Build log at https://launchpadlibrarian.net/192081247/buildlog_ubuntu- vivid-powerpc.qtbase-opensource-src_5.4.0~rc- 0ubuntu1~vivid1~test3_FAILEDTOBUILD.txt.gz g++ -c -include .pch/Qt5Network -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -O2 -fvisibility=hidden -fvisibility-inlines-hidden -std=c++0x -fno-exceptions -Wall -W -D_REENTRANT -fPIC -DQT_NO_USING_NAMESPACE -DQT_BUILD_NETWORK_LIB -DQT_BUILDING_QT -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_BEFORE=0x05 -DQT_NO_EXCEPTIONS -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_CORE_LIB -I../../mkspecs/linux-g++ -I. -I../../include -I../../include/QtNetwork -I../../include/QtNetwork/5.4.0 -I../../include/QtNetwork/5.4.0/QtNetwork -Ikernel -I../../include/QtCore/5.4.0 -I../../include/QtCore/5.4.0/QtCore -I../../include/QtCore -I.moc -o .obj/qabstractsocketengine.o socket/qabstractsocketengine.cpp image/qimage_conversions.cpp:2257:9: error: expected '}' before numeric constant 0, 0, 0, 0 ^ image/qimage_conversions.cpp:2257:9: error: expected '}' before numeric constant image/qimage_conversions.cpp:2257:9: error: expected ',' or ';' before numeric constant image/qimage_conversions.cpp:2258:5: error: expected declaration before '}' token }, // Format_RGBA ^ More information about Qt testing at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1400244/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400235] Re: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep
Marius B. Kotsbak, please do not apport-collect further unless specifically requested to do so. ** Tags removed: apport-collected reproducible ** Description changed: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 - --- - .tmp.unity.support.test.1: - - ApportVersion: 2.14.7-0ubuntu10 - Architecture: amd64 - CasperVersion: 1.346 - CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' - CompositorRunning: compiz - CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' - CompositorUnredirectFSW: true - CurrentDesktop: Unity - DistUpgraded: Fresh install - DistroCodename: vivid - DistroRelease: Ubuntu 15.04 - DistroVariant: ubuntu - DkmsStatus: - bbswitch, 0.7, 3.16.0-25-generic, x86_64: installed - nvidia-331, 331.89, 3.16.0-25-generic, x86_64: installed - nvidia-331-uvm, 331.89, 3.16.0-25-generic, x86_64: installed - ExtraDebuggingInterest: Yes, including running git bisection searches - GraphicsCard: - NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Dell Device [1028:05cc] - LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) - MachineType: Dell Inc. Precision M4800 - Package: xorg 1:7.7+7ubuntu2 - PackageArchitecture: amd64 - ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=en_US.UTF-8 - SHELL=/bin/bash - ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- - ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 - Renderer: Software - Tags: vivid ubuntu reproducible compiz-0.9 - Uname: Linux 3.16.0-25-generic x86_64 - UpgradeStatus: No upgrade log present (probably fresh install) - UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo - _MarkForUpload: True - dmi.bios.date: 06/26/2014 -
[Touch-packages] [Bug 1394645] Re: OSK doesn't appear after OA login
** Also affects: qtmir (Ubuntu RTM) Importance: Undecided Status: New ** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1394645 Title: OSK doesn't appear after OA login Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu Keyboard: Invalid Status in The Webapps-core project: Confirmed Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Status in qtmir package in Ubuntu RTM: New Status in unity8 package in Ubuntu RTM: New Bug description: Test case. - Remove Twitter account in System Settings. - Open Twitter app and login. - Tap to create new tweet/message. Expected result. - OSK must appear. Actual result. - OSK doesn't show up. Also happens with GMail. current build number: 116 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09.es-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1394645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1357321] Re: QNetworkAccessManager doesn't support roaming on Ubuntu
Start InternetCheckercmd with wifi enabled, with the known wifi router unpowered or out of range, while connected to mobile data. (will not work like this when manually enabling/disabling wifi) It will return something like this: phablet@ubuntu-phablet:~$ InternetCheckercmd/InternetCheckercmd (Checker::Checker:14) - configuration ccmni0 QFlags(0x2|0x4|0x8) (Checker::createGetRequest:30) - Initiate HTTP GET Request (Checker::finishedSlot:35) - configuration ccmni0 QFlags(0x2|0x4|0x8) (Checker::finishedSlot:39) - HTTP GET Reply Code: 0 and Name: Unknown error (reply code 0 means success) With the InternetCheckercmd still running, either walk into range of a known/configured wifi, or power on the wifi router that is known and configured, so the phone will auto connect to it. Wait for the wifi indicator to show there is a wifi connection. Notice that the get request is still going through the mobile data connection, instead of the wifi connection. This means anything keeping a QNAM instance and using it to do random get requests will be using expensive mobile data instead of cheaper wifi, even though wifi is connected. Try this again with the patched QNAM and QtBearer plugin, and it will change the configuration which it uses for the get request. ** Attachment added: QNAM Internet checker https://bugs.launchpad.net/savilerow/+bug/1357321/+attachment/4276051/+files/InternetCheckercmd.tgz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1357321 Title: QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: Invalid Status in The Savilerow project: New Status in network-manager package in Ubuntu: Invalid Status in ofono package in Ubuntu: Invalid Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu RTM: In Progress Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399597] Re: The last oxide upload breaks autopkgtests with a package installation failure
This bug was fixed in the package oxide-qt - 1.3.5-0ubuntu6 --- oxide-qt (1.3.5-0ubuntu6) vivid; urgency=medium * Use the new conflict arrangement still, but change the dependency order of Oxide's own codecs packages to prefer the -extras. This should hopefully solve the problem when setting up the autopkgtest environment with packages that have a hard depedency on the -extras package. (LP: #1399597) -- Timo Jyrinki timo-jyri...@ubuntu.com Fri, 05 Dec 2014 13:39:34 + ** Changed in: oxide-qt (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1399597 Title: The last oxide upload breaks autopkgtests with a package installation failure Status in apt package in Ubuntu: New Status in oxide-qt package in Ubuntu: Fix Released Bug description: The last packaging change upload (https://code.launchpad.net/~bzoltan/oxide/packaging.vivid-improved- conflicts/+merge/243515) broke autopkgtests of many packages that try to install Oxide during preparation of the environment. See for example https://jenkins.qa.ubuntu.com/job/vivid-adt-qtcreator- plugin-ubuntu/lastBuild/ARCH=amd64,label=adt/console This prevents migration of several packages. --- Unpacking oxideqt-codecs:amd64 (1.3.5-0ubuntu4) ... dpkg: considering removing oxideqt-codecs:amd64 in favour of oxideqt-codecs-extra:amd64 ... dpkg: oxideqt-codecs:amd64 is not properly installed; ignoring any dependencies on it dpkg: yes, will remove oxideqt-codecs:amd64 in favour of oxideqt-codecs-extra:amd64 --- Setting up oxideqt-codecs-extra:amd64 (1.3.5-0ubuntu4) ... dpkg: error processing package oxideqt-codecs (--configure): no package named `oxideqt-codecs' is installed, cannot configure --- Errors were encountered while processing: oxideqt-codecs E: Sub-process /usr/bin/dpkg returned an error code (1) Because of this it'll be reverted until a better solution is offered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1399597/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399597] Re: The last oxide upload breaks autopkgtests with a package installation failure
This needs reverting. It will result in -extras being pulled in to the desktop seed, which is not acceptable -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1399597 Title: The last oxide upload breaks autopkgtests with a package installation failure Status in apt package in Ubuntu: New Status in oxide-qt package in Ubuntu: Fix Released Bug description: The last packaging change upload (https://code.launchpad.net/~bzoltan/oxide/packaging.vivid-improved- conflicts/+merge/243515) broke autopkgtests of many packages that try to install Oxide during preparation of the environment. See for example https://jenkins.qa.ubuntu.com/job/vivid-adt-qtcreator- plugin-ubuntu/lastBuild/ARCH=amd64,label=adt/console This prevents migration of several packages. --- Unpacking oxideqt-codecs:amd64 (1.3.5-0ubuntu4) ... dpkg: considering removing oxideqt-codecs:amd64 in favour of oxideqt-codecs-extra:amd64 ... dpkg: oxideqt-codecs:amd64 is not properly installed; ignoring any dependencies on it dpkg: yes, will remove oxideqt-codecs:amd64 in favour of oxideqt-codecs-extra:amd64 --- Setting up oxideqt-codecs-extra:amd64 (1.3.5-0ubuntu4) ... dpkg: error processing package oxideqt-codecs (--configure): no package named `oxideqt-codecs' is installed, cannot configure --- Errors were encountered while processing: oxideqt-codecs E: Sub-process /usr/bin/dpkg returned an error code (1) Because of this it'll be reverted until a better solution is offered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1399597/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399401] Re: SmartScopesProxy should allow send the User Agent also when doing the remote-scopes request
*** This bug is a duplicate of bug 1389273 *** https://bugs.launchpad.net/bugs/1389273 ** This bug has been marked a duplicate of bug 1389273 Track app sales per partner -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1399401 Title: SmartScopesProxy should allow send the User Agent also when doing the remote-scopes request Status in unity-scopes-api package in Ubuntu: Confirmed Bug description: In the following call: SmartScopesClient.get_remote_scopes(): GET https://dash.ubuntu.com/smartscopes/v2/remote-scopes?locale=en ...the SmartScopesProxy is not sending the normal User Agent (with partner, etc). The server receives 'Mozilla/5.0', which is not very useful. The SmartScopesProxy should send the User Agent like when doing the search and preview requests, specially because in the remote-scopes request is needed to decide which scopes to enable for different partners. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1399401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399597] Re: The last oxide upload breaks autopkgtests with a package installation failure
:( The ubuntu6 was approved by a core-dev on IRC. I originally asked people to get this sorted out during US timezone Friday, but it didn't get forward and more landings were stuck in -proposed. I filed bug #1400275 as the continuation bug. Please add in there why desktop shouldn't depend on the oxideqt-codecs-extra package, since I see they are both in main. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1399597 Title: The last oxide upload breaks autopkgtests with a package installation failure Status in apt package in Ubuntu: New Status in oxide-qt package in Ubuntu: Fix Released Bug description: The last packaging change upload (https://code.launchpad.net/~bzoltan/oxide/packaging.vivid-improved- conflicts/+merge/243515) broke autopkgtests of many packages that try to install Oxide during preparation of the environment. See for example https://jenkins.qa.ubuntu.com/job/vivid-adt-qtcreator- plugin-ubuntu/lastBuild/ARCH=amd64,label=adt/console This prevents migration of several packages. --- Unpacking oxideqt-codecs:amd64 (1.3.5-0ubuntu4) ... dpkg: considering removing oxideqt-codecs:amd64 in favour of oxideqt-codecs-extra:amd64 ... dpkg: oxideqt-codecs:amd64 is not properly installed; ignoring any dependencies on it dpkg: yes, will remove oxideqt-codecs:amd64 in favour of oxideqt-codecs-extra:amd64 --- Setting up oxideqt-codecs-extra:amd64 (1.3.5-0ubuntu4) ... dpkg: error processing package oxideqt-codecs (--configure): no package named `oxideqt-codecs' is installed, cannot configure --- Errors were encountered while processing: oxideqt-codecs E: Sub-process /usr/bin/dpkg returned an error code (1) Because of this it'll be reverted until a better solution is offered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1399597/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373039] Re: Crash in QML compiler if terminated whilst compiling asynchronous components
This bug was fixed in the package qtdeclarative-opensource-src - 5.3.2-3ubuntu2 --- qtdeclarative-opensource-src (5.3.2-3ubuntu2) vivid; urgency=medium * debian/patches/Avoid-race-condition-in-QQmlEngine-on-shutdown.patch - Cherry-pick an app shutdown crash fix (LP: #1373039) * debian/patches/Fix-crashes-when-calling-Array.sort-with-imperfect-s.patch - Cherry-pick a fix for a crasher in Array.sort (LP: #1295119) -- Timo Jyrinki timo-jyri...@ubuntu.com Wed, 03 Dec 2014 08:32:46 + ** Changed in: qtdeclarative-opensource-src (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1373039 Title: Crash in QML compiler if terminated whilst compiling asynchronous components Status in camera-app package in Ubuntu: Fix Released Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Bug description: Reproducible on mako and krillin using devel-proposed r248 or rtm r50 This is easiest to reproduce with the camera-app, as this has a number of large components that get loaded asynchronously on start-up, however I believe it should be possible to trigger in any app that contains asynchronous Loaders. Steps to reproduce 1. Start camera-app 2. Whilst loading, swipe to the app switcher. 3. Close camera-app. Expected result App closes cleanly Actual result Sometimes the app segfaults whilst closing It may take multiple attempts to cause a crash, as the SIGTERM signal has to be received at a certain point during the compilation process for the crash to occur. Back trace of an example crash: There are still 1 items in the process of being created at engine destruction. [Thread 0xac267450 (LWP 5576) exited] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb1a3e450 (LWP 5561)] 0xb6618dd6 in createNode (left=false, parent=0x0, v=@0x31: error reading variable, k=@0x2d: error reading variable, this=0xae598538) at /usr/include/arm-linux-gnueabihf/qt5/QtCore/qmap.h:216 216 new (n-key) Key(k); (gdb) bt #0 0xb6618dd6 in createNode (left=false, parent=0x0, v=@0x31: error reading variable, k=@0x2d: error reading variable, this=0xae598538) at /usr/include/arm-linux-gnueabihf/qt5/QtCore/qmap.h:216 #1 QMapNodeunsigned int, QV4::ExecutableAllocator::ChunkOfPages*::copy (this=0x21, d=d@entry=0xae598538) at /usr/include/arm-linux-gnueabihf/qt5/QtCore/qmap.h:246 #2 0xb6618e02 in QMapNodeunsigned int, QV4::ExecutableAllocator::ChunkOfPages*::copy (this=0xb11a5c28, d=d@entry=0xae598538) at /usr/include/arm-linux-gnueabihf/qt5/QtCore/qmap.h:249 #3 0xb6618e02 in QMapNodeunsigned int, QV4::ExecutableAllocator::ChunkOfPages*::copy (this=0xae54a2f8, d=d@entry=0xae598538) at /usr/include/arm-linux-gnueabihf/qt5/QtCore/qmap.h:249 #4 0xb6618e4e in QMapunsigned int, QV4::ExecutableAllocator::ChunkOfPages*::detach_helper (this=0x6ae34) at /usr/include/arm-linux-gnueabihf/qt5/QtCore/qmap.h:969 #5 0xb6618950 in detach (this=0x6ae34) at /usr/include/arm-linux-gnueabihf/qt5/QtCore/qmap.h:378 #6 insert (avalue=synthetic pointer, akey=optimized out, this=0x6ae34) at /usr/include/arm-linux-gnueabihf/qt5/QtCore/qmap.h:676 #7 QV4::ExecutableAllocator::allocate (this=0x6ae30, size=592, size@entry=578) at jsruntime/qv4executableallocator.cpp:179 #8 0xb65bc900 in ExecutableMemoryHandle (size=578, allocator=optimized out, this=0xae5af100) at ../3rdparty/masm/stubs/ExecutableAllocator.h:66 #9 allocate (size=578, this=0xb1a3cfbc) at ../3rdparty/masm/stubs/ExecutableAllocator.h:97 #10 JSC::LinkBuffer::linkCode (this=this@entry=0xb1a3d068, ownerUID=ownerUID@entry=0x0, effort=effort@entry=JSC::JITCompilationMustSucceed) at ../3rdparty/masm/assembler/LinkBuffer.cpp:79 #11 0xb65b18de in LinkBuffer (effort=JSC::JITCompilationMustSucceed, ownerUID=0x0, masm=0xae5a9aa0, globalData=..., this=0xb1a3d068) at ../3rdparty/masm/assembler/LinkBuffer.h:92 #12 QV4::JIT::Assembler::link (this=0xae5a9aa0, codeSize=codeSize@entry=0xb1a3d0e8) at jit/qv4isel_masm.cpp:141 #13 0xb65b2918 in QV4::JIT::InstructionSelection::run (this=optimized out, functionIndex=optimized out) at jit/qv4isel_masm.cpp:360 #14 0xb65658f0 in QV4::EvalInstructionSelection::compile (this=this@entry=0xae564070, generateUnitData=generateUnitData@entry=false) at compiler/qv4isel_p.cpp:85 #15 0xb6617608 in QV4::Script::precompile (module=module@entry=0xb1a3d460, unitGenerator=unitGenerator@entry=0xb1a3d49c, engine=engine@entry=0x6b290, url=..., source=..., reportedErrors=reportedErrors@entry=0xb1a3d414) at jsruntime/qv4script.cpp:397 #16 0xb666b5ac in QQmlScriptBlob::dataReceived (this=0xae5a8a18, data=...) at qml/qqmltypeloader.cpp:2698 #17 0xb66650ac in
[Touch-packages] [Bug 1394893] Re: package ureadahead 0.100.0-16 failed to install/upgrade: triggers looping, abandoned
** Changed in: ureadahead (Ubuntu Trusty) Assignee: Canonical Desktop Team (canonical-desktop-team) = Iain Lane (laney) ** Changed in: ureadahead (Ubuntu Utopic) Assignee: Canonical Desktop Team (canonical-desktop-team) = Iain Lane (laney) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1394893 Title: package ureadahead 0.100.0-16 failed to install/upgrade: triggers looping, abandoned Status in ureadahead package in Ubuntu: Fix Released Status in ureadahead source package in Trusty: New Status in ureadahead source package in Utopic: New Bug description: Happend on today's sudo apt-get dist-upgrade ProblemType: Package DistroRelease: Ubuntu 15.04 Package: ureadahead 0.100.0-16 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 Date: Fri Nov 21 09:17:23 2014 DuplicateSignature: package:ureadahead:0.100.0-16:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2014-11-03 (17 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141103) SourcePackage: ureadahead Title: package ureadahead 0.100.0-16 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1394893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400235] Re: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep
** Changed in: xorg (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: New Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1400235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386698] Re: Canned queries to favorited scopes don't preserve search query string
This bug was fixed in the package unity8 - 8.01+15.04.20141205-0ubuntu1 --- unity8 (8.01+15.04.20141205-0ubuntu1) vivid; urgency=low [ CI Train Bot ] * Resync trunk [ Albert Astals ] * Replace Scopes Overview by the new Manage Dash (LP: #1386698, #1368670) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 05 Dec 2014 10:55:50 + ** Changed in: unity8 (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1386698 Title: Canned queries to favorited scopes don't preserve search query string Status in unity-scopes-shell package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: New Bug description: I do a search in the scopes scope, and got some results with recommendations... example of the request and two results from there: https://pastebin.canonical.com/119509/ If I tap into the recommendation for a simple scope, it gets opened and with the query searched automatically, all good! But if I tap into the recommendation for an aggregator scope, it gets opened, but the query is NOT searched automatically. It should. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1386698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347652] Re: [design] Sort Items in Launcher By Frequency Used
** Changed in: unity8 (Ubuntu) Status: Incomplete = Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1347652 Title: [design] Sort Items in Launcher By Frequency Used Status in Ubuntu UX bugs: Won't Fix Status in unity8 package in Ubuntu: Won't Fix Bug description: This is something that you will hopefully think is a good idea , or at least spurn a discussion for further improvements. When you have limited screen real estate eg: most budget laptops are 1366 x 768 and have quite a few items on the launcher bar , it can be a bit unweildy to find the app you are looking for. My Idea is thus :- Add a feature to the Unity bar whereby apps are ordered by frequency used - most frequently used apps appear at the top of the list and least used towards the bottom. the Ubuntu button should always remain at the top , independant of the sort. If this were to be implemented then the user should be able to enable / disable it from the control panel if they wise to have the current operation. I think this would be a great useability improvement. Thanks Nick To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1347652/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368670] Re: [Dash] Simplify 'Manage Dash' area
This bug was fixed in the package unity8 - 8.01+15.04.20141205-0ubuntu1 --- unity8 (8.01+15.04.20141205-0ubuntu1) vivid; urgency=low [ CI Train Bot ] * Resync trunk [ Albert Astals ] * Replace Scopes Overview by the new Manage Dash (LP: #1386698, #1368670) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 05 Dec 2014 10:55:50 + ** Changed in: unity8 (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1368670 Title: [Dash] Simplify 'Manage Dash' area Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in unity-scope-mediascanner package in Ubuntu: Fix Released Status in unity-scopes-shell package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in unity-scope-mediascanner source package in Utopic: Confirmed Status in unity-scopes-shell source package in Utopic: Confirmed Status in unity8 source package in Utopic: Confirmed Status in unity-scopes-shell package in Ubuntu RTM: In Progress Status in unity8 package in Ubuntu RTM: Triaged Bug description: UX Testing Report: Replace the current bottom edge screens with the simpler Complete list of Scopes design. New Manage Dash design can be found here: https://sites.google.com/a/canonical.com/unity-8-dash-rtm-1/scope-structure-navigation/my-feeds-structure Additional UX Testing Report findings addressed by the redesign: Poor discoverability and comprehension of scopes - The use of labelings that do not include the word 'scope'/'scopes' Lack of visual distinctions between apps and scopes in the 'manage dash' screen Undefined relationship between apps and scopes Search function does not help the discovery of scopes No dedicated place for adding scopes on the dash Poor memorability in locating the' manage dash' screen again The impact of making a scope favourite is unclear Lack of indication of the nature of the scopes under 'all' tab on 'manage dash' Navigation between manage dash and apps scope was difficult Expect to see categorises instead of content --- [EDIT] Please refer to the Dash Feeds RTM usability fix for this bug: https://docs.google.com/a/canonical.com/document/d/1LsjdqKDVcFN8Zxb_Oe-Zk1X_DiqviXr8D7-ELt2LEFI/edit?usp=sharing To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1368670/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1395073] Re: package ureadahead 0.100.0-16 failed to install/upgrade: udløsere er cyklisk afhængige, afbrudt
*** This bug is a duplicate of bug 1394893 *** https://bugs.launchpad.net/bugs/1394893 ** This bug has been marked a duplicate of bug 1394893 package ureadahead 0.100.0-16 failed to install/upgrade: triggers looping, abandoned -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1395073 Title: package ureadahead 0.100.0-16 failed to install/upgrade: udløsere er cyklisk afhængige, afbrudt Status in ureadahead package in Ubuntu: New Bug description: Error turned up during apt-get dist-upgrade ProblemType: Package DistroRelease: Ubuntu 15.04 Package: ureadahead 0.100.0-16 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 Date: Fri Nov 21 17:46:46 2014 DuplicateSignature: package:ureadahead:0.100.0-16:udløsere er cyklisk afhængige, afbrudt ErrorMessage: udløsere er cyklisk afhængige, afbrudt InstallationDate: Installed on 2014-10-25 (27 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 (20140822) SourcePackage: ureadahead Title: package ureadahead 0.100.0-16 failed to install/upgrade: udløsere er cyklisk afhængige, afbrudt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1395073/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394893] Re: package ureadahead 0.100.0-16 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dpkg (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1394893 Title: package ureadahead 0.100.0-16 failed to install/upgrade: triggers looping, abandoned Status in dpkg package in Ubuntu: Confirmed Status in ureadahead package in Ubuntu: Fix Released Status in dpkg source package in Trusty: Invalid Status in ureadahead source package in Trusty: Invalid Status in dpkg source package in Utopic: Invalid Status in ureadahead source package in Utopic: Invalid Bug description: Happend on today's sudo apt-get dist-upgrade ProblemType: Package DistroRelease: Ubuntu 15.04 Package: ureadahead 0.100.0-16 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 Date: Fri Nov 21 09:17:23 2014 DuplicateSignature: package:ureadahead:0.100.0-16:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2014-11-03 (17 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141103) SourcePackage: ureadahead Title: package ureadahead 0.100.0-16 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1394893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394893] Re: package ureadahead 0.100.0-16 failed to install/upgrade: triggers looping, abandoned
Looks like it's probably better to add a Breaks from dpkg, like in 1.7.22 in Debian: * Add Breaks on old man-db, fontconfig and readahead-fedora packages using awaiting triggers, as they produce trigger cycles. Closes: #768599 instead of SRUing. ** Changed in: ureadahead (Ubuntu Trusty) Status: New = Invalid ** Changed in: ureadahead (Ubuntu Utopic) Status: New = Invalid ** Also affects: dpkg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1394893 Title: package ureadahead 0.100.0-16 failed to install/upgrade: triggers looping, abandoned Status in dpkg package in Ubuntu: Confirmed Status in ureadahead package in Ubuntu: Fix Released Status in dpkg source package in Trusty: Invalid Status in ureadahead source package in Trusty: Invalid Status in dpkg source package in Utopic: Invalid Status in ureadahead source package in Utopic: Invalid Bug description: Happend on today's sudo apt-get dist-upgrade ProblemType: Package DistroRelease: Ubuntu 15.04 Package: ureadahead 0.100.0-16 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 Date: Fri Nov 21 09:17:23 2014 DuplicateSignature: package:ureadahead:0.100.0-16:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2014-11-03 (17 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141103) SourcePackage: ureadahead Title: package ureadahead 0.100.0-16 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1394893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394893] Re: package ureadahead 0.100.0-16 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dpkg (Ubuntu Utopic) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1394893 Title: package ureadahead 0.100.0-16 failed to install/upgrade: triggers looping, abandoned Status in dpkg package in Ubuntu: Confirmed Status in ureadahead package in Ubuntu: Fix Released Status in dpkg source package in Trusty: Invalid Status in ureadahead source package in Trusty: Invalid Status in dpkg source package in Utopic: Invalid Status in ureadahead source package in Utopic: Invalid Bug description: Happend on today's sudo apt-get dist-upgrade ProblemType: Package DistroRelease: Ubuntu 15.04 Package: ureadahead 0.100.0-16 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 Date: Fri Nov 21 09:17:23 2014 DuplicateSignature: package:ureadahead:0.100.0-16:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2014-11-03 (17 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141103) SourcePackage: ureadahead Title: package ureadahead 0.100.0-16 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1394893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393800] Re: Ubuntu 14.10 shut down slow after sleep
I have the shutdown time improved by editing both /etc/init/modemmanager.conf and /etc/init/network-manager.conf via adding a line to them: kill timeout 1 The original post on that idea is from: http://www.hecticgeek.com/2012/10/speed-up-ubuntu-shutdown-process/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1393800 Title: Ubuntu 14.10 shut down slow after sleep Status in modemmanager package in Ubuntu: Confirmed Bug description: I upgraded from 14.04 to 14.10 recently. My laptop does not shut down properly anymore. It used to take only 5 sec to shutdown in 14.04. But now it needs ca. 5 min to shut down after sleep. If it never slept, then shut down process is normal. The message on the shut down screen has something to do with ModemManager: ModemManager: ModemManager is shut down ModemManager: Could not acquire the 'org.freedesktop.ModemManager1' service name it stays like that for ca. 5 min before it suddenly shuts down. I added stop on runlevel [06] to the network-manager.conf file. It did not help. I used shutdown -h now. It did not help. modemmanager: Installed: 1.2.0-1 Candidate: 1.2.0-1 Version table: *** 1.2.0-1 0 500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: modemmanager 1.2.0-1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Tue Nov 18 15:10:26 2014 InstallationDate: Installed on 2012-03-22 (970 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: modemmanager UpgradeStatus: Upgraded to utopic on 2014-10-24 (25 days ago) mtime.conffile..etc.init.modemmanager.conf: 2014-11-18T10:37:43.218538 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1393800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394893] Re: package ureadahead 0.100.0-16 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dpkg (Ubuntu Trusty) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1394893 Title: package ureadahead 0.100.0-16 failed to install/upgrade: triggers looping, abandoned Status in dpkg package in Ubuntu: Confirmed Status in ureadahead package in Ubuntu: Fix Released Status in dpkg source package in Trusty: Invalid Status in ureadahead source package in Trusty: Invalid Status in dpkg source package in Utopic: Invalid Status in ureadahead source package in Utopic: Invalid Bug description: Happend on today's sudo apt-get dist-upgrade ProblemType: Package DistroRelease: Ubuntu 15.04 Package: ureadahead 0.100.0-16 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 Date: Fri Nov 21 09:17:23 2014 DuplicateSignature: package:ureadahead:0.100.0-16:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2014-11-03 (17 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141103) SourcePackage: ureadahead Title: package ureadahead 0.100.0-16 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1394893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1234940] Re: [SF-only] frequent unity crash on Mako
** Changed in: unity8 (Ubuntu) Status: Incomplete = Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1234940 Title: [SF-only] frequent unity crash on Mako Status in QT Ubuntu: Expired Status in unity8 package in Ubuntu: Won't Fix Bug description: I experience a unity crash probably 4 or more times per day. Can't really pin down what triggers it. I finally today got what I am pretty sure is a clean crash file for it, so attaching To manage notifications about this bug go to: https://bugs.launchpad.net/qtubuntu/+bug/1234940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394893] Re: package ureadahead 0.100.0-16 failed to install/upgrade: triggers looping, abandoned
** Changed in: dpkg (Ubuntu Trusty) Status: Confirmed = Invalid ** Changed in: dpkg (Ubuntu Utopic) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1394893 Title: package ureadahead 0.100.0-16 failed to install/upgrade: triggers looping, abandoned Status in dpkg package in Ubuntu: Confirmed Status in ureadahead package in Ubuntu: Fix Released Status in dpkg source package in Trusty: Invalid Status in ureadahead source package in Trusty: Invalid Status in dpkg source package in Utopic: Invalid Status in ureadahead source package in Utopic: Invalid Bug description: Happend on today's sudo apt-get dist-upgrade ProblemType: Package DistroRelease: Ubuntu 15.04 Package: ureadahead 0.100.0-16 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 Date: Fri Nov 21 09:17:23 2014 DuplicateSignature: package:ureadahead:0.100.0-16:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2014-11-03 (17 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141103) SourcePackage: ureadahead Title: package ureadahead 0.100.0-16 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1394893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1024204] Re: package python3 3.2.3-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4
I have the same problem with upgrading ubuntu server from 14.04 to 14.10. Unpacking ubuntu-minimal (1.327) ... Setting up python3 (3.4.2-1) ... running python rtupdate hooks for python3.4... dpkg-query: package 'rhythmbox-plugin-magnatune' is not installed Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. Traceback (most recent call last): File /usr/bin/py3clean, line 200, in module main() File /usr/bin/py3clean, line 186, in main pfiles = set(dpf.from_package(options.package)) File /usr/share/python3/debpython/files.py, line 53, in from_package raise Exception(cannot get content of %s % package_name) Exception: cannot get content of rhythmbox-plugin-magnatune error running python rtupdate hook rhythmbox-plugin-magnatune dpkg-query: package 'rhythmbox-plugin-zeitgeist' is not installed Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. Traceback (most recent call last): File /usr/bin/py3clean, line 200, in module main() File /usr/bin/py3clean, line 186, in main pfiles = set(dpf.from_package(options.package)) File /usr/share/python3/debpython/files.py, line 53, in from_package raise Exception(cannot get content of %s % package_name) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1024204 Title: package python3 3.2.3-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4 Status in python3-defaults package in Ubuntu: Fix Released Bug description: Setting up python3 (3.2.3-3) ... running python rtupdate hooks for python3.2... Traceback (most recent call last): File /usr/bin/py3clean, line 182, in module main() File /usr/bin/py3clean, line 174, in main files = files pfiles TypeError: unsupported operand type(s) for : 'generator' and 'generator' error running python rtupdate hook screen-resolution-extra Traceback (most recent call last): File /usr/bin/py3clean, line 182, in module main() File /usr/bin/py3clean, line 174, in main files = files pfiles TypeError: unsupported operand type(s) for : 'generator' and 'generator' error running python rtupdate hook ubuntu-drivers-common dpkg: error processing python3 (--configure): subprocess installed post-installation script returned error exit status 4 ProblemType: Package DistroRelease: Ubuntu 12.10 Package: python3 3.2.3-3 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.3-0ubuntu4 Architecture: amd64 Date: Fri Jul 13 01:02:18 2012 ErrorMessage: subprocess installed post-installation script returned error exit status 4 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20101202) PackageArchitecture: all SourcePackage: python3-defaults Title: package python3 3.2.3-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1024204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1337221] Re: qmlscene crashed with SIGSEGV in QmlIR::QmlUnitGenerator::generate()
Instead of expiring, this would be a useful bug to keep around since it has a test case. We'd just need a simpler test case to show to the upstream. Confirmed happening with qtdeclarative-opensource-src 5.3.2-3ubuntu2 in vivid. ** Changed in: qtdeclarative-opensource-src (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1337221 Title: qmlscene crashed with SIGSEGV in QmlIR::QmlUnitGenerator::generate() Status in qtdeclarative-opensource-src package in Ubuntu: Confirmed Bug description: Running a project I hadn't touched in a while [1] caused the crash. However a basic hello world QML file [2] is fine. [1] - https://github.com/jamesodhunt/qml-noughts-and-crosses [2] - http://qt-project.org/doc/qt-5/qmlfirststeps.html ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: qmlscene 5.3.0-3ubuntu6 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Thu Jul 3 09:30:26 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlscene InstallationDate: Installed on 2014-04-11 (82 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409) ProcCmdline: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlscene -I /home/username/src/qml/qml-noughts-and-crosses -I /usr/bin -I /usr/lib/i386-linux-gnu/qt5/qml /home/username/src/qml/qml-noughts-and-crosses/noughts-and-crosses.qml SegvAnalysis: Segfault happened at: 0x7ff039273c89 _ZN5QmlIR16QmlUnitGenerator8generateERNS_8DocumentE+41: mov (%rax),%rax PC (0x7ff039273c89) ok source (%rax) (0x) not located in a known VMA region (needed readable region)! destination %rax ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: qtdeclarative-opensource-src StacktraceTop: QmlIR::QmlUnitGenerator::generate(QmlIR::Document) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 Title: qmlscene crashed with SIGSEGV in QmlIR::QmlUnitGenerator::generate() UpgradeStatus: Upgraded to utopic on 2014-05-08 (55 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1337221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399223] Re: python-testtools should be upgraded to version 1.5.0
It also looks like we need unittest2=0.8.0? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-testtools in Ubuntu. https://bugs.launchpad.net/bugs/1399223 Title: python-testtools should be upgraded to version 1.5.0 Status in python-testtools package in Ubuntu: Incomplete Bug description: We are using an old version of testtools on ubuntu which prevents us from running all dashboard tests and keeping the dashboard from being green. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/1399223/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1358340] Re: [Indicators] Complete greeter profiles
** Changed in: unity8 (Ubuntu) Importance: Undecided = High ** Changed in: unity8 (Ubuntu) Status: Triaged = In Progress ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) = Michael Terry (mterry) ** Changed in: unity8 (Ubuntu RTM) Status: Triaged = New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1358340 Title: [Indicators] Complete greeter profiles Status in The Date and Time Indicator: Invalid Status in The Messaging Menu: Fix Released Status in Transfer Indicator: Fix Released Status in Ubuntu UX bugs: Fix Released Status in The Unity 8 shell: Fix Released Status in gsettings-ubuntu-touch-schemas package in Ubuntu: Fix Released Status in indicator-datetime package in Ubuntu: Invalid Status in indicator-messages package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu: Fix Released Status in indicator-transfer package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: In Progress Status in unity8 package in Ubuntu RTM: New Bug description: A recent change in the interest of security removed access to the indicators when the phone is locked and the greeter is showing. This was an accentual change based on a misunderstanding There had been a plan to support media playback control via the sound indicator. Without this the user must unlock the phone in order to simply pause the music or change songs, etc. Desired resolution: - Revert the change that caused this issue - Add a switch to System Settings to enable security conscious user to switch off Launcher and Greeter access while the phone is locked. This setting should *always* be off by default. https://wiki.ubuntu.com/SecurityAndPrivacySettings#Locking To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1358340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399223] Re: python-testtools should be upgraded to version 1.5.0
Hum... could you provide a source package for this? Or what particularly is required in terms of packaging changes? ** Changed in: python-testtools (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-testtools in Ubuntu. https://bugs.launchpad.net/bugs/1399223 Title: python-testtools should be upgraded to version 1.5.0 Status in python-testtools package in Ubuntu: Incomplete Bug description: We are using an old version of testtools on ubuntu which prevents us from running all dashboard tests and keeping the dashboard from being green. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/1399223/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400181] Re: Merge nss 2:3.17.2-1 (main) from Debian unstable (main)
This bug was fixed in the package nss - 2:3.17.2-1ubuntu1 --- nss (2:3.17.2-1ubuntu1) vivid; urgency=low * Merge from Debian unstable. (LP: #1400181) Remaining changes: - debian/rules: + Add x32 support. + Also ship blapi.h and alghmac.h in libnss3-dev. - debian/control, debian/libnss3-nssdb.*, debian/libnss3.symbols, debian/pkcs11.txt, debian/rules: + Add back support for shared cert and key databases. nss (2:3.17.2-1) unstable; urgency=medium * New upstream release. nss (2:3.17.1-1) unstable; urgency=high * New upstream release. - Fixes CVE-2014-1568. - Add support for ppc64el, with a non-broken patch. Closes: #745757. * debian/libnss3.symbols: Add NSSUTIL_3.17.1 symbol versions. -- Artur Rona ari-tc...@ubuntu.com Mon, 08 Dec 2014 00:26:25 +0100 ** Changed in: nss (Ubuntu) Status: Confirmed = Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-1568 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1400181 Title: Merge nss 2:3.17.2-1 (main) from Debian unstable (main) Status in nss package in Ubuntu: Fix Released Bug description: nss (2:3.17.2-1) unstable; urgency=medium * New upstream release. -- Mike Hommey gland...@debian.org Sat, 18 Oct 2014 13:22:04 +0900 nss (2:3.17.1-1) unstable; urgency=high * New upstream release. - Fixes CVE-2014-1568. - Add support for ppc64el, with a non-broken patch. Closes: #745757. * debian/libnss3.symbols: Add NSSUTIL_3.17.1 symbol versions. -- Mike Hommey gland...@debian.org Wed, 24 Sep 2014 22:16:32 +0900 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1400181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400290] [NEW] apt-get install ubuntu-minimal missing dependencies
Public bug reported: I have error during upgrading ubuntu server 14.04 to 14.10 $ sudo apt-get install ubuntu-minimal Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: dh-python lsb-release python3 Suggested packages: lsb python3-doc python3-tk python3-venv The following NEW packages will be installed: dh-python lsb-release python3 ubuntu-minimal 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/75.4 kB of archives. After this operation, 604 kB of additional disk space will be used. Do you want to continue? [Y/n] Selecting previously unselected package python3. (Reading database ... 40984 files and directories currently installed.) Preparing to unpack .../python3_3.4.2-1_amd64.deb ... Unpacking python3 (3.4.2-1) ... Selecting previously unselected package dh-python. Preparing to unpack .../dh-python_1.20140511-1_all.deb ... Unpacking dh-python (1.20140511-1) ... Selecting previously unselected package lsb-release. Preparing to unpack .../lsb-release_4.1+Debian11ubuntu8_all.deb ... Unpacking lsb-release (4.1+Debian11ubuntu8) ... Selecting previously unselected package ubuntu-minimal. Preparing to unpack .../ubuntu-minimal_1.327_amd64.deb ... Unpacking ubuntu-minimal (1.327) ... Processing triggers for man-db (2.7.0.2-2) ... Setting up python3 (3.4.2-1) ... running python rtupdate hooks for python3.4... dpkg-query: package 'ubiquity-frontend-gtk' is not installed Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. Traceback (most recent call last): File /usr/bin/py3clean, line 200, in module main() File /usr/bin/py3clean, line 186, in main pfiles = set(dpf.from_package(options.package)) File /usr/share/python3/debpython/files.py, line 53, in from_package raise Exception(cannot get content of %s % package_name) Exception: cannot get content of ubiquity-frontend-gtk error running python rtupdate hook ubiquity-frontend-gtk dpkg-query: package 'ubiquity' is not installed Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. Traceback (most recent call last): File /usr/bin/py3clean, line 200, in module main() File /usr/bin/py3clean, line 186, in main pfiles = set(dpf.from_package(options.package)) File /usr/share/python3/debpython/files.py, line 53, in from_package raise Exception(cannot get content of %s % package_name) Exception: cannot get content of ubiquity error running python rtupdate hook ubiquity dpkg-query: package 'ubuntu-drivers-common' is not installed Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. Traceback (most recent call last): File /usr/bin/py3clean, line 200, in module main() File /usr/bin/py3clean, line 186, in main pfiles = set(dpf.from_package(options.package)) File /usr/share/python3/debpython/files.py, line 53, in from_package raise Exception(cannot get content of %s % package_name) Exception: cannot get content of ubuntu-drivers-common error running python rtupdate hook ubuntu-drivers-common dpkg: error processing package python3 (--configure): subprocess installed post-installation script returned error exit status 4 dpkg: dependency problems prevent configuration of dh-python: dh-python depends on python3:any (= 3.3.2-2~); however: Package python3 is not configured yet. dpkg: error processing package dh-python (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of lsb-release: lsb-release depends on python3; however: Package python3 is not configured yet. lsb-release depends on python3:any (= 3.3.2-2~); however: Package python3 is not configured yet. dpkg: error processing package lsb-release (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of ubuntu-minimal: ubuntu-minimal depends on lsb-release; however: Package lsb-release is not configured yet. ubuntu-minimal depends on python3; however: Package python3 is not configured yet. dpkg: error processing package ubuntu-minimal (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: python3 dh-python lsb-release ubuntu-minimal E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1400290 Title: apt-get install ubuntu-minimal missing dependencies Status in ubuntu-meta package in Ubuntu: New Bug description: I have error during upgrading ubuntu server 14.04 to 14.10 $ sudo
[Touch-packages] [Bug 1388876] Re: Pinch to zoom not supported when taking video
** Also affects: camera-app Importance: Undecided Status: New ** Changed in: camera-app Status: New = Confirmed ** Changed in: camera-app Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1388876 Title: Pinch to zoom not supported when taking video Status in Camera App: Confirmed Status in camera-app package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open the camera application 2. Press the Video button to switch to video mode 3. Place two fingers on the screen and move them apart to attempt to zoom Expected result: The picture zooms in and a slider appears indicating the zoom level Actual result: The slider appears but the picture does not zoom in and there is no marker on the slider to indicate the zoom level To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1388876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389597] Re: Delete button should be listed first in the confirmation dialog
** Changed in: camera-app Status: In Progress = Fix Committed ** Changed in: camera-app (Ubuntu) Status: New = Fix Released ** Changed in: camera-app (Ubuntu RTM) Status: New = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1389597 Title: Delete button should be listed first in the confirmation dialog Status in Camera App: Fix Committed Status in camera-app package in Ubuntu: Fix Released Status in camera-app package in Ubuntu RTM: Fix Committed Bug description: Using rtm 142 - start the camera application - swipe to left to go to the photo roll - click on a photo - select delete - the dialog displayed has delete at the bottom, that's inconsistent with dialogs in gallery and other applications where the action is listed at the top of the dialog To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1389597/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368140] Re: add guide lines overlay option
** Changed in: camera-app Assignee: (unassigned) = Florian Boucault (fboucault) ** Changed in: camera-app (Ubuntu) Assignee: (unassigned) = Florian Boucault (fboucault) ** Changed in: camera-app Status: Confirmed = In Progress ** Changed in: camera-app (Ubuntu) Status: Confirmed = In Progress ** Tags added: ww51 ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Status: New = In Progress ** Changed in: canonical-devices-system-image Assignee: (unassigned) = Florian Boucault (fboucault) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1368140 Title: add guide lines overlay option Status in Camera App: In Progress Status in the base for Ubuntu mobile products: In Progress Status in camera-app package in Ubuntu: In Progress Bug description: Both iOS and Android cameras have an option to overlay 2 evenly-spaced vertical and 2 evenly-spaced horizonal white guide lines. These are a very useful alignment aid when composing a shot. For details: http://en.wikipedia.org/wiki/Rule_of_thirds Bonus points if we could have a Fibonacci spiral option too :-) : http://en.wikipedia.org/wiki/Golden_spiral To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1368140/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376495] Re: autopilot3 run camera_app.tests.test_zoom.TestCameraZoom.test_slider_zoom_out crashes camera-app
** Changed in: camera-app Status: In Progress = Fix Released ** Changed in: camera-app (Ubuntu RTM) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1376495 Title: autopilot3 run camera_app.tests.test_zoom.TestCameraZoom.test_slider_zoom_out crashes camera-app Status in Camera App: Fix Released Status in camera-app package in Ubuntu: Fix Released Status in camera-app package in Ubuntu RTM: In Progress Bug description: Summary: autopilot3 run camera_app.tests.test_zoom.TestCameraZoom.test_slider_zoom_out crashes camera-app steps: 1. phablet-click-test-setup -s $ANDROID_SERIAL 2. phablet-config -s $ANDROID_SERIAL autopilot --dbus-probe enable 3. adb -s $ANDROID_SERIAL shell 4. cd autopilot 5. autopilot3 run camera_app.tests.test_zoom.TestCameraZoom.test_slider_zoom_out - 6. ls /var/crash expected results: test passes without crashing camera app actual results: test crashes camera app base: system-image.ubuntu.com http_port: 80 https_port: 443 channel: ubuntu-touch/devel-proposed device: mako build_number: 263 channel_target: ubuntu-touch/utopic-proposed version_detail: ubuntu=20140930,device=20140929.1,custom=mako-0.6,version=263 com.ubuntu.camera 3.0.0.387 To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1376495/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371245] Re: trust-store dialog (location) not asked on the first boot after a clean flash
** Tags removed: rtm14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1371245 Title: trust-store dialog (location) not asked on the first boot after a clean flash Status in Camera App: Incomplete Status in camera-app package in Ubuntu: Incomplete Bug description: current build number: 48 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-09-18 18:32:37 version version: 48 version ubuntu: 20140918.1 version device: 20140917-19d7408 version custom: 1410739265 Flashed with: ubuntu-device-flash --channel=ubuntu-touch/ubuntu- rtm/14.09-proposed --bootstrap --developer-mode --password=1234 After first boot (wizard and etc), try opening the camera-app and you'll see that the trust-store dialog will not show up to the screen and the user is able to use the app. Dialog shows up after rebooting it though, so it seems to be a first- boot specific issue. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1371245/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394645] Re: OSK doesn't appear after OA login
*** This bug is a duplicate of bug 1381292 *** https://bugs.launchpad.net/bugs/1381292 This was fixed in trunk with this commit: https://code.launchpad.net/~josharenson/unity8/fix_trust_store_focus/+merge/239567 Commit needs backporting to RTM -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1394645 Title: OSK doesn't appear after OA login Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu Keyboard: Invalid Status in The Webapps-core project: Confirmed Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: Triaged Bug description: Test case. - Remove Twitter account in System Settings. - Open Twitter app and login. - Tap to create new tweet/message. Expected result. - OSK must appear. Actual result. - OSK doesn't show up. Also happens with GMail. current build number: 116 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09.es-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1394645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389611] Re: swipe to the photo roll hint should wrap rather than elide
** Changed in: camera-app Status: In Progress = Fix Committed ** Changed in: camera-app (Ubuntu RTM) Status: New = In Progress ** Changed in: canonical-devices-system-image Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1389611 Title: swipe to the photo roll hint should wrap rather than elide Status in Camera App: Fix Committed Status in the base for Ubuntu mobile products: In Progress Status in camera-app package in Ubuntu: Fix Released Status in camera-app package in Ubuntu RTM: In Progress Bug description: Using rtm 142 (with updated translations done manually from launchpad), the new swipe to the photo roll hint is eliding, but it leads to the text difficult to understand in some locales... Screenshot from a french example attached to show the issue To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1389611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381292] Re: Clicking permissions dialog in camera app causes app to lose focus
Bug #1394645 is a duplicate, please transfer image task status from there. ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Milestone: None = 14.09-ota-1 ** Changed in: unity8 (Ubuntu RTM) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1381292 Title: Clicking permissions dialog in camera app causes app to lose focus Status in the base for Ubuntu mobile products: New Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: Triaged Bug description: Steps to reproduce: 1. Start with a fresh flash of the device (or clear all permissions data from the camera app, wasn't sure how to do this) 2. Start the camera app 3. When the dialog comes up asking if the camera can use your current location, click deny Results: Dialog closes, camera stays black as it likely doesn't have active focus Expected results: Dialog closes and camera resumes To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1381292/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394645] Re: OSK doesn't appear after OA login
*** This bug is a duplicate of bug 1381292 *** https://bugs.launchpad.net/bugs/1381292 Please transfer image task status to the original bug #1381292. ** Changed in: unity8 (Ubuntu) Status: New = Fix Released ** Changed in: unity8 (Ubuntu RTM) Milestone: None = 14.09-ota-1 ** Changed in: unity8 (Ubuntu RTM) Status: New = Triaged ** No longer affects: qtmir (Ubuntu) ** No longer affects: qtmir (Ubuntu RTM) ** This bug has been marked a duplicate of bug 1381292 Clicking permissions dialog in camera app causes app to lose focus -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1394645 Title: OSK doesn't appear after OA login Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu Keyboard: Invalid Status in The Webapps-core project: Confirmed Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: Triaged Bug description: Test case. - Remove Twitter account in System Settings. - Open Twitter app and login. - Tap to create new tweet/message. Expected result. - OSK must appear. Actual result. - OSK doesn't show up. Also happens with GMail. current build number: 116 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09.es-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1394645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400296] Re: No scopes are visible in the all page of the manage scopes page
** Changed in: unity8 (Ubuntu) Status: New = In Progress ** Branch linked: lp:~saviq/unity8/bump-manage-dash ** Changed in: unity8 (Ubuntu) Status: In Progress = Fix Released ** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Also affects: unity-scope-click (Ubuntu) Importance: Undecided Status: New ** No longer affects: unity8 (Ubuntu RTM) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1400296 Title: No scopes are visible in the all page of the manage scopes page Status in unity-scope-click package in Ubuntu: New Status in unity8 package in Ubuntu: Fix Released Bug description: STEPS: 1. Swipe in the launcher and press the Ubuntu button *Moves to the home scope 2. Swipe up from the bottom of the screen *Manage scopes is revealed on the Favourited page 3. Check there are scopes visible here *The favourite scopes are all visible 4. Tap on all *Moves to the all page 5. Swipe up and ensure there are scopes available *Multiple scopes are visible as you scroll EXPECTED: I expect to see scopes on the all page ACTUAL: Favourite Scopes show as expected but on the all tab there are no scopes shown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1400296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400297] [NEW] PageHeadState doens't correctly update head.contents
Public bug reported: See this small example code: http://paste.ubuntu.com/9426167/ As you can see, I set both PageHeadState to change their 'contents' property when changing state. The expected behavior would be to have in the page head a Label when state is default and a TextEntry when in search state. However after some interactions (switching state 2 times) both the Label and the Entry are shown. As this doesn't happen with other properties, this should not happen with contents. I can set a 'visible' property to each component as workaround though. Thanks, Giulio ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Attachment added: testqml.qml https://bugs.launchpad.net/bugs/1400297/+attachment/4276096/+files/testqml.qml -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1400297 Title: PageHeadState doens't correctly update head.contents Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: See this small example code: http://paste.ubuntu.com/9426167/ As you can see, I set both PageHeadState to change their 'contents' property when changing state. The expected behavior would be to have in the page head a Label when state is default and a TextEntry when in search state. However after some interactions (switching state 2 times) both the Label and the Entry are shown. As this doesn't happen with other properties, this should not happen with contents. I can set a 'visible' property to each component as workaround though. Thanks, Giulio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1400297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400235] Re: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep
I am not sure if I am able to get the change to Nvidia driver working running the live CD image. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400235 Title: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep Status in xorg package in Ubuntu: Incomplete Bug description: When the laptop is either set to sleep by entering Fn-F1 or by timeout, the screen is black after waking it up again (using the power button, it does not wake by mousepad movement or key presses). In earlier Ubuntu versions (14.04), a workaround was to enter a terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does not seem to work anymore. The problem is is present in todays (2014-12-8) Vivid daily image (booted with nomodeset, but not done any configuration of the screen). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CasperVersion: 1.346 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 8 08:28:24 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141207) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset -- Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 08:27:01 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.1.901-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1400235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400296] Re: No scopes are visible in the all page of the manage scopes page
** Branch linked: lp:~stolowski/unity-scopes-shell/add-breaks-unity8 ** Changed in: unity-scope-click (Ubuntu) Status: New = Invalid ** Also affects: unity-scopes-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-scopes-shell (Ubuntu) Assignee: (unassigned) = Pawel Stolowski (stolowski) ** Changed in: unity-scopes-shell (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1400296 Title: No scopes are visible in the all page of the manage scopes page Status in unity-scope-click package in Ubuntu: Invalid Status in unity-scopes-shell package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: STEPS: 1. Swipe in the launcher and press the Ubuntu button *Moves to the home scope 2. Swipe up from the bottom of the screen *Manage scopes is revealed on the Favourited page 3. Check there are scopes visible here *The favourite scopes are all visible 4. Tap on all *Moves to the all page 5. Swipe up and ensure there are scopes available *Multiple scopes are visible as you scroll EXPECTED: I expect to see scopes on the all page ACTUAL: Favourite Scopes show as expected but on the all tab there are no scopes shown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1400296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367325] Re: [phone-app] empty state missing in recent view and empty address book
** Branch linked: lp:~boiko/dialer-app/rtm-empty_state -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1367325 Title: [phone-app] empty state missing in recent view and empty address book Status in Address Book App: Fix Released Status in the base for Ubuntu mobile products: Confirmed Status in Dialer app for Ubuntu Touch: In Progress Status in Ubuntu UX bugs: Fix Committed Status in address-book-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu RTM: In Progress Bug description: 1. Open Phone app, make sure you didn't receive or made any calls 2. Carry out a bottom edge swipe 3. The list is blank Same applies for the Address book app --- Desired solution: Please implement the empty state screen as per design. It is confusing for the user not seeing anything in this view. Please implement a screen saying No recent calls and have a look on the empty screen in the messaging app as a reference. To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1367325/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367325] Re: [phone-app] empty state missing in recent view and empty address book
** Changed in: dialer-app (Ubuntu RTM) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1367325 Title: [phone-app] empty state missing in recent view and empty address book Status in Address Book App: Fix Released Status in the base for Ubuntu mobile products: Confirmed Status in Dialer app for Ubuntu Touch: In Progress Status in Ubuntu UX bugs: Fix Committed Status in address-book-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu RTM: In Progress Bug description: 1. Open Phone app, make sure you didn't receive or made any calls 2. Carry out a bottom edge swipe 3. The list is blank Same applies for the Address book app --- Desired solution: Please implement the empty state screen as per design. It is confusing for the user not seeing anything in this view. Please implement a screen saying No recent calls and have a look on the empty screen in the messaging app as a reference. To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1367325/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400296] Re: No scopes are visible in the all page of the manage scopes page
** Changed in: unity8 (Ubuntu) Status: Fix Released = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1400296 Title: No scopes are visible in the all page of the manage scopes page Status in unity-scope-click package in Ubuntu: Invalid Status in unity-scopes-shell package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: STEPS: 1. Swipe in the launcher and press the Ubuntu button *Moves to the home scope 2. Swipe up from the bottom of the screen *Manage scopes is revealed on the Favourited page 3. Check there are scopes visible here *The favourite scopes are all visible 4. Tap on all *Moves to the all page 5. Swipe up and ensure there are scopes available *Multiple scopes are visible as you scroll EXPECTED: I expect to see scopes on the all page ACTUAL: Favourite Scopes show as expected but on the all tab there are no scopes shown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1400296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1284308] Re: Bogus another operation in progress error. Can't copy files from a bluetooth device
Confirmed on Ubuntu Gnome 14.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1284308 Title: Bogus another operation in progress error. Can't copy files from a bluetooth device Status in bluez package in Ubuntu: Confirmed Status in gnome-vfs-obexftp package in Ubuntu: Confirmed Status in gvfs package in Ubuntu: Confirmed Status in obex-data-server package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files from the phone to the computer (which already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose bluetooth settings 3 - select the phone among the listed devices 4 - click on Browse files 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer = I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is another operation in progress. Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then ejected the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error This location could not be displayed. Another operation in progress, so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when ejecting the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:44318 acl:198 sco:0 events:355 errors:0 TX bytes:6132 acl:178 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400297] Re: PageHeadState doens't correctly update head.contents
This seems similar to bug 1341814 where the head contents are not correctly handled when switching page head state. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1400297 Title: PageHeadState doens't correctly update head.contents Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: See this small example code: http://paste.ubuntu.com/9426167/ As you can see, I set both PageHeadState to change their 'contents' property when changing state. The expected behavior would be to have in the page head a Label when state is default and a TextEntry when in search state. However after some interactions (switching state 2 times) both the Label and the Entry are shown. As this doesn't happen with other properties, this should not happen with contents. I can set a 'visible' property to each component as workaround though. Thanks, Giulio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1400297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1280325] Re: package glib-networking-common 2.38.1-0ubuntu1 failed to install/upgrade: package glib-networking-common is already installed and configured
apport information ** Tags added: apport-collected utopic ** Description changed: Impossible to download/install a progra through Lubuntu Software Center 00:00.0 Host bridge: Intel Corporation 82915G/P/GV/GL/PL/910GL Memory Controller Hub (rev 04) Subsystem: FIRST INTERNATIONAL Computer Inc Device 925d Flags: bus master, fast devsel, latency 0 Capabilities: access denied 00:01.0 PCI bridge: Intel Corporation 82915G/P/GV/GL/PL/910GL PCI Express Root Port (rev 04) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: c000-cfff Memory behind bridge: d800-d80f Prefetchable memory behind bridge: d000-d7ff Capabilities: access denied Kernel driver in use: pcieport 00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 03) Subsystem: FIRST INTERNATIONAL Computer Inc Device 925d Flags: bus master, fast devsel, latency 0, IRQ 42 Memory at d820 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied Kernel driver in use: snd_hda_intel 00:1d.0 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03) (prog-if 00 [UHCI]) Subsystem: FIRST INTERNATIONAL Computer Inc Device 925d Flags: bus master, medium devsel, latency 0, IRQ 23 I/O ports at e300 [size=32] Kernel driver in use: uhci_hcd 00:1d.1 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03) (prog-if 00 [UHCI]) Subsystem: FIRST INTERNATIONAL Computer Inc Device 925d Flags: bus master, medium devsel, latency 0, IRQ 19 I/O ports at e000 [size=32] Kernel driver in use: uhci_hcd 00:1d.2 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03) (prog-if 00 [UHCI]) Subsystem: FIRST INTERNATIONAL Computer Inc Device 925d Flags: bus master, medium devsel, latency 0, IRQ 18 I/O ports at e100 [size=32] Kernel driver in use: uhci_hcd 00:1d.3 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03) (prog-if 00 [UHCI]) Subsystem: FIRST INTERNATIONAL Computer Inc Device 925d Flags: bus master, medium devsel, latency 0, IRQ 16 I/O ports at e200 [size=32] Kernel driver in use: uhci_hcd 00:1d.7 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03) (prog-if 20 [EHCI]) Subsystem: FIRST INTERNATIONAL Computer Inc Device 925d Flags: bus master, medium devsel, latency 0, IRQ 23 Memory at d8204000 (32-bit, non-prefetchable) [size=1K] Capabilities: access denied Kernel driver in use: ehci-pci 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d3) (prog-if 01 [Subtractive decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=32 I/O behind bridge: d000-dfff Memory behind bridge: d810-d81f Prefetchable memory behind bridge: 4000-400f Capabilities: access denied 00:1f.0 ISA bridge: Intel Corporation 82801FB/FR (ICH6/ICH6R) LPC Interface Bridge (rev 03) Subsystem: Intel Corporation 82801FB/FR (ICH6/ICH6R) LPC Interface Bridge Flags: bus master, medium devsel, latency 0 Kernel driver in use: lpc_ich 00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 03) (prog-if 8a [Master SecP PriP]) Subsystem: FIRST INTERNATIONAL Computer Inc Device 2651 Flags: bus master, medium devsel, latency 0, IRQ 18 I/O ports at 01f0 [size=8] I/O ports at 03f4 [size=1] I/O ports at 0170 [size=8] I/O ports at 0374 [size=1] I/O ports at f000 [size=16] Kernel driver in use: ata_piix 00:1f.2 IDE interface: Intel Corporation 82801FB/FW (ICH6/ICH6W) SATA Controller (rev 03) (prog-if 8f [Master SecP SecO PriP PriO]) Subsystem: FIRST INTERNATIONAL Computer Inc Device 2651 Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 19 I/O ports at e400 [size=8] I/O ports at e500 [size=4] I/O ports at e600 [size=8] I/O ports at e700 [size=4] I/O ports at e800 [size=16] Capabilities: access denied Kernel driver in use: ata_piix 00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03) Subsystem: FIRST INTERNATIONAL Computer Inc Device 2651 Flags: medium devsel, IRQ 11 I/O ports at 0500 [size=32] 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV370
[Touch-packages] [Bug 1399861] Re: top errors out when a cpu is taken offline
I can confirm this behaviour for procps-3.2.8. Additional information: procps is not used in newer releases any longer. At least as of 14.04 it is replaced by procps-ng, the top implementation of which handles this scenario correctly. ** Changed in: procps (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1399861 Title: top errors out when a cpu is taken offline Status in procps package in Ubuntu: Confirmed Bug description: 1. start top in a session 2. press '1' to show the CPUs individually 3. in a separate (root) session, shut down a cpu like this: # echo 0 /sys/devices/system/cpu/cpu2/online 4. top will exit with a message like this: top: failed /proc/stat read Related: when reactivating a cpu, top will only continue to show the first N-1 cpus in its display. The workaround for people who want to keep an active system monitor up, can do: $ while true; do top; done cpus_refresh() assumes that Cpu_tot never changes; it reads that many cpu* entries from /proc/stat, incorrectly interpreting the 'intr' line as a failed cpu line read. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1399861/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400312] [NEW] On desktop, windowed mode should be the default
Public bug reported: Right now desktops start up in Side Stage mode but it should be windowed mode. Currently it is required to set com.canonical.unity8.usage-mode to Windowed in order to enable windowed mode. ** Affects: qtdeclarative-opensource-src (Ubuntu) Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Affects: unity8-desktop-session (Ubuntu) Importance: Undecided Status: New ** Summary changed: - On desktop, windowed mode should be by default + On desktop, windowed mode should be the default -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1400312 Title: On desktop, windowed mode should be the default Status in qtdeclarative-opensource-src package in Ubuntu: New Status in unity8 package in Ubuntu: New Status in unity8-desktop-session package in Ubuntu: New Bug description: Right now desktops start up in Side Stage mode but it should be windowed mode. Currently it is required to set com.canonical.unity8.usage-mode to Windowed in order to enable windowed mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1400312/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400312] Re: On desktop, windowed mode should be the default
An .override file shipped by the desktop session could be a first step. Ultimately we want info about the system peripherals to base our decision upon. ** Also affects: unity8-desktop-session (Ubuntu) Importance: Undecided Status: New ** Also affects: qtdeclarative-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1400312 Title: On desktop, windowed mode should be the default Status in qtdeclarative-opensource-src package in Ubuntu: New Status in unity8 package in Ubuntu: New Status in unity8-desktop-session package in Ubuntu: New Bug description: Right now desktops start up in Side Stage mode but it should be windowed mode. Currently it is required to set com.canonical.unity8.usage-mode to Windowed in order to enable windowed mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1400312/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
Because we don't show a text entry if PAM (the authentication module) does not respond correctly. We wait for PAM to ask the passoword not the opposite, and if PAM fails there is nothing we can do about. Briefly PAM works like that: we ask to authenticate the current user, pam responds asking us to show a text entry with some text (like Password:, etc...), we send the password to pam, etc. If for some reasons pam cannot authenticate the current user, it answers with an error. Gnome Screensaver was working out of the box? 2014-12-08 9:41 GMT+01:00 Philipp Wendler 1311...@bugs.launchpad.net: I cannot imagine how a missing password input field in the lock screen could be related to an LDAP configuration issue on our side. If the authentication would fail after entering the password, then yes, of course this could be such a problem. But a password field should always be shown by the unlock screen, regardless of the authentication backend. Also our LDAP configuration is working for several years now without problems. Only since the upgrade to Ubuntu 14.04 this problem with the lock screen has started appearing. All other applications, including the login screen (lightdm) are working fine. By the way, we have a dual monitor setup, too. Our home file systems are on an NFS fileserver, mounted using automount and with root_squash enabled (this means that root does not have full access to my home directory, but only the same rights as all other accounts). If there is a root process trying to access files in my home this would fail. -- You received this bug notification because you are a bug assignee. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Andrea Azzarone http://launchpad.net/~andyrock http://wiki.ubuntu.com/AndreaAzzarone -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400297] Re: PageHeadState doens't correctly update head.contents
Yes they are definitely similar. Feel free to mark this bug as duplicate if you want. Thanks nik :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1400297 Title: PageHeadState doens't correctly update head.contents Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: See this small example code: http://paste.ubuntu.com/9426167/ As you can see, I set both PageHeadState to change their 'contents' property when changing state. The expected behavior would be to have in the page head a Label when state is default and a TextEntry when in search state. However after some interactions (switching state 2 times) both the Label and the Entry are shown. As this doesn't happen with other properties, this should not happen with contents. I can set a 'visible' property to each component as workaround though. Thanks, Giulio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1400297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400312] Re: On desktop, windowed mode should be the default
The override can be shipped in ubuntu-settings, that package is installed on desktop installations only. Once we get per sessions default (needs glib work which is ongoing) we can do better -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1400312 Title: On desktop, windowed mode should be the default Status in qtdeclarative-opensource-src package in Ubuntu: New Status in unity8 package in Ubuntu: New Status in unity8-desktop-session package in Ubuntu: New Bug description: Right now desktops start up in Side Stage mode but it should be windowed mode. Currently it is required to set com.canonical.unity8.usage-mode to Windowed in order to enable windowed mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1400312/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398998] Re: Cannot provide multi-arch click packages for scopes
** Branch linked: lp:~unity-api-team/unity-scopes-api/multi-arch-click ** Changed in: unity-scopes-api (Ubuntu) Assignee: (unassigned) = Pete Woods (pete-woods) ** Changed in: click (Ubuntu) Status: New = Invalid ** Changed in: unity-scopes-api (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1398998 Title: Cannot provide multi-arch click packages for scopes Status in click package in Ubuntu: Invalid Status in unity-scopes-api package in Ubuntu: In Progress Bug description: Currently, click packages with scopes cannot provide the same scope for multiple architectures, as the hook takes the directory name that the scope is in, but does not support the .so for the scope being in a sub-directory based on the arch triplet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1398998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
I must have missed something. Permissions on what path? And what should the permissions be? Michael Peek On 12/06/2014 09:03 AM, Andrea Azzarone wrote: We released a fix but it does not work. The one we released was about text entry not showing randomly on multimonitor and seems to be fixed. Probably what you can reproduce now is a problem with permissions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400133] Re: Wireless USB mouse not recognised by ubuntu 14.04 64 bit
Capone Cash, thank you for reporting this and helping make Ubuntu better. Could you please run the following command in a Terminal as it will automatically gather and attach updated debug information to this report: apport-collect -p xorg 1400133 Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1400133 Title: Wireless USB mouse not recognised by ubuntu 14.04 64 bit Status in xorg package in Ubuntu: Incomplete Bug description: Ensure you report the bug via ubuntu-bug xorg as outlined above. What is the full manufacturer and model of your mouse. How is your mouse connected to your PC: serial, PS/2, USB, USB wireless, etc. What mechanism does your mouse use: roller ball, optical, trackball, etc. How many physical buttons and scrollwheels does you mouse have? MAnufacturer and model: Akai, Model: wlm-5330 Connected via USB port, wireless Optical mouse, 2,4ghz 3 phyisical buttons + scroll To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1400133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
But a password field should always be shown by the unlock screen, regardless of the authentication backend. No. For example, if smart card authentication is in use, the PIN entry field should not be shown until and unless the smart card is inserted in the reader. If challenge-response authentication is in use, it would incorrect to display the response field until the user ID has been entered and a challenge presented. There are a number of scenarios in which it is just wrong to present a password field. It is correct for the Unity lock screen to not always displaying a password entry field when it has not been instructed to do so by the underlying auth mech. Any authentication dialog that does so, and actually authenticates the user as a result, possibly has a critical security vulnerability. It would be a good idea to audit your local authentication setup if you are seeing this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377220] Re: Google Chrome crash with mesa 10.3 on Intel GPU
Issue might be actually the X driver and mesa disagreeing how to handle the memory buffers. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757435 ** Bug watch added: Debian Bug tracker #757435 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757435 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1377220 Title: Google Chrome crash with mesa 10.3 on Intel GPU Status in Chromium Browser: Unknown Status in mesa package in Ubuntu: Confirmed Bug description: When I start google-chrome on my Ubuntu 14.10 system the process it uses to test for a working GPU crashes and then Chrome falls back to software rendering. In chrome://gpu/ I get: Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Flash: Software only, hardware acceleration unavailable Flash Stage3D: Software only, hardware acceleration unavailable Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable Compositing: Software only, hardware acceleration unavailable Multiple Raster Threads: Unavailable Rasterization: Software only, hardware acceleration unavailable Threaded Rasterization: Unavailable Video Decode: Software only, hardware acceleration unavailable Video Encode: Software only, hardware acceleration unavailable WebGL: Unavailable Driver Bug Workarounds clear_uniforms_before_first_program_use count_all_in_varyings_packing disable_ext_occlusion_query disable_post_sub_buffers_for_onscreen_surfaces scalarize_vec_and_mat_constructor_args Problems Detected GPU process was unable to boot: GPU access is disabled in chrome://settings. Disabled Features: all [...] In Ubuntu 14.04 (and also previous versions), on the same laptop, the exact same Google Chrome used to work perfectly with GPU acceleration. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libgl1-mesa-dri 10.3.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 BootLog: Scanning for Btrfs filesystems * Setting sensors limits [240G [234G[ OK ] * Setting up X socket directories... [240G [234G[ OK ] CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: kwin CurrentDesktop: KDE Date: Fri Oct 3 17:48:09 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: kubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0494] MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-20-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Oct 2 13:54:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8685 vendor AUO xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1377220/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1203565] Re: 045e:009c [H87-PRO] Microsoft Keyboard Elite for Bluetooth dead keys problem
** Tags added: vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1203565 Title: 045e:009c [H87-PRO] Microsoft Keyboard Elite for Bluetooth dead keys problem Status in bluez package in Ubuntu: Incomplete Bug description: In Precise with 4.60 version of bluez I can pair my keyboard and mouse perfectly. === The problem is that dead keys of my keyboard (I mean -L or R- CTRL, ALT, SUPER, -L or R- SHIFT, ALT-GR) doesn't work with my current motherboard (whether application I opened, console included). It does work correctly with other motherboards. The new motherboard is an 1150 Haswell one from Asus. What I can say is : 1/ When booting, my BIOS recognize perfectly the dead keys of my keyboard, meaning that the bluetooth dongle or the motherboard is not directly concerned. 2/ When doing a second installation of Ubuntu, same problem. 3/ When trying the option 'keyboard layout' (whatever layout I choose), I don't see those dead keys flashing, meaning the system doesn't react at all when pressing them. 4/ By chance, I found another keyboard (same model, same brand), same problem, meaning the keyboard is not concerned (it works on the older motherboard, then it was poor chance that the keyboard broked just before reinstalling). 5/ Tried the setxkbmap command (with sudo or without), nothing's better 6/ Tried the xmodmap command, I see the 0x codes for Left SHIFT, all dead keys are there (see attachment) 7/ Normal keyboard (no wireless) works perfectly 8/ Put the dongle on an other usb slot doesn't change anything 9/ Command xev doesn't makes changes when pressing dead keys. For me it's clearly a Ubuntu's system bug, with my motherboard (Asus H87-PRO socket 1150). --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: syl4375 F...m rhythmbox CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'PAD'/'RME Digi96/8 PAD at 0xf400, irq 19' Mixer name : '' Components : '' Controls : 10 Simple ctrls : 6 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf308 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 24 Simple ctrls : 4 Card2.Amixer.info: Card hw:2 'NVidia_1'/'HDA NVidia at 0xe308 irq 16' Mixer name : 'Nvidia GPU 0a HDMI/DP' Components : 'HDA:10de000a,10de0101,00100100' Controls : 24 Simple ctrls : 4 DistroRelease: Ubuntu 12.04 MachineType: ASUS All Series MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-36-generic root=UUID=d2f8f163-a1ee-4332-a910-d593309cd2a6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.5.0-36.57~precise1-generic 3.5.7.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.5.0-36-generic N/A linux-backports-modules-3.5.0-36-generic N/A linux-firmware1.79.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: precise running-unity Uname: Linux 3.5.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio bluetooth boinc cdrom dip lp lpadmin netdev plugdev sambashare scanner sudo video dmi.bios.date: 04/08/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd04/08/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87-PRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1203565/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372548] Re: Phone field doesn't accept symbols #*()
** Branch linked: lp:~renatofilho/telephony-service/fix-1372548 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1372548 Title: Phone field doesn't accept symbols #*() Status in Address Book App: Confirmed Status in address-book-app package in Ubuntu: New Status in address-book-app package in Ubuntu RTM: New Bug description: The phone field in address book doesn't accept symbols available in the keyboard for phone numbers: #* Test case: - Open Contacts app. - Add a new contact. - Go to Phone number field. - Press + key for 5 seconds and select these symbols: *#() Expected result: - Field accepts symbols as part of a telephone number. Actual result: - Only + symbol is accepted. To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1372548/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399011] Re: [Call]Cannot enter '#' and '*' in dialing interface after entered numbers
** Branch linked: lp:~renatofilho/telephony-service/fix-1372548 ** Changed in: dialer-app Assignee: Gustavo Pichorim Boiko (boiko) = Renato Araujo Oliveira Filho (renatofilho) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1399011 Title: [Call]Cannot enter '#' and '*' in dialing interface after entered numbers Status in Dialer app for Ubuntu Touch: Confirmed Status in dialer-app package in Ubuntu: New Status in dialer-app package in Ubuntu RTM: New Bug description: From barajas bug: https://bugs.launchpad.net/barajas/+bug/1395633 [Software Release/Version Build Date] M34 [Preconditions] 1.None [Procedures] 1.Go to Dialing interface,enter some numbers 2.Try to enter # or *, check it. [Expect results] can enter # and * after entered numbers. [Actual results] Cannot enter # and *, but there is keypad tone. [Reproduce] Always To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1399011/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration
http://askubuntu.com/questions/557149/14-10-dual-monitors-are-displayed- as-distorted-single-screen-mode -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1382462 Title: Desktop/windows painted incorrectly in dual monitor configuration Status in xorg package in Ubuntu: Confirmed Bug description: My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached to DisplayPort. I was using Nvidia 331.38 prioprietary driver for quite a long time with Ubuntu 14.04 LTS and everything worked perfectly. Today I upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed the following problem: 1. When I boot up the computer with the monitor connected, the login screen looks fine. Both displays get detected properly and resolutions are ok (1920x1080 on the builtin laptop display and 2560x1600 on U3011) and screen contents scaled properly. 2. Then I log into my account, for 3 seconds U3011 displays some rubbish (but it was always like that) and when it finally logs in, it displays everything stretched horizontally through both my screens. It looks as if it tried to paint the contents of a single display on two of them, by stretching the content horizontally, so everything (icons, windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar seem to render correctly and the resolution/size of the top menu is correct. Physical resolution of both screens is ok. I'll attach a photo, because it is hard to describe how it looks. 3. I cannot use system in this state - mouse click position seems to not be synchronized with what's on the display - e.g. I can start applications, but then they don't react to mouseclicks. However: booting up without the second display connected, logging in and *then* connecting the second display works fine. If I boot up with connected monitor and log in (desktop distorted), disconnecting and connecting monitor does *not* help. After disconnecting the U3011, the builtin display is painted ok, but after connecting, it returns back to the incorrect state and both are rendered incorrectly. The only thing that helps recovering from this state seems to be disconnecting the second monitor, reboot, logging in and then connecting. Suspending to memory and waking up does not change the layout of the screen (neither fixes the broken one nor destroys the good one). Using a Guest session instead of my account does not fix my problem (I was hoping this was something screwed up in my .config). Switching to a Guest user account while I'm using both monitors in the good layout creates a session with a broken layout. Then logging out from Guest and switching back to my original session restores the good layout. The good layout seems to not be forgotten until I finish the session and logout. The bad layout is created whenever I start a new session with both monitors plugged in. BTW: I'm using a docking station - not sure if it is related - if you think it might be, I can try with connecting the monitor directly. I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem remains. I also tried to go into the Displays configuration when everything is ok, apply the settings there (without any changes) in hope it will persist them somehow, but after restart it is broken again. I also tried reinstalling nvidia 331.89 drivers, because it complained about not being able to install nvidia-uvm during the upgrade process (reported separately), and now all nvidia packages installed cleanly. Before that I also got rid of all the ppa mainline kernels I had, just in case they mess something up. I remember the same problem happened on Ubuntu 14.04 when I tried to upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy workaround was to downgrade back to official 331.38. Now I have no choice :( Some other observations that may or may not be related to the problem, but I disclose them anyway, maybe they are helpful: * Notifications (e.g. network connection) displayed on the login screen in dual screen mode seem to be misplaced and instead of being painted in the upper right corner of one of the displays they get painted in some hard to logically explain position - neither at the center, nor in any corner. * The splash screen of IntelliJ IDEA (this is using Java / AWT probably) is also rendered in a strange position - below the center of the laptop screen, moved to the right (but not touching the edge), instead of exact center as it should be. * GMail notification just displayed at the moment when I'm writing it exactly at the left-lower corner of the bigger screen (U3011). * Nvidia settings lists only U3011 in the list of the devices (attached screenshot). * Ubuntu Display configuration dialog detects
