[Touch-packages] [Bug 1425484] Re: wizard aborts and goes directly to the dash
** Changed in: unity8 (Ubuntu) Importance: Undecided = High ** Changed in: unity8 (Ubuntu) Importance: High = Critical -- 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/1425484 Title: wizard aborts and goes directly to the dash Status in unity8 package in Ubuntu: Confirmed Bug description: TEST CASE: 1. Go to system-settings and do a factory reset 2. After reboot in the wizard, dismiss the first SIM PIN dialog 3. Select 'French' in the list of languages 4. Tap on 'Continue' EXPECT RESULT The step 'device security' is displayed ACTUAL RESULT A blank screen is displayed (empty page with the default background) and after a few seconds the wizard stops and the dash loads. The edge intro is skipped. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity8 8.02+15.04.20150224-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Wed Feb 25 11:41:16 2015 InstallationDate: Installed on 2015-02-25 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1425484/+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 1353988] Re: Taglib causes crash
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: taglib (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to taglib in Ubuntu. https://bugs.launchpad.net/bugs/1353988 Title: Taglib causes crash Status in taglib package in Ubuntu: Confirmed Bug description: TagLib 1.9.1 has known bug: https://github.com/taglib/taglib/issues/308 Sometime it causes programs(clementine, amarok, qmmp and other with taglib usage) crash while reading tags. Please, apply attached patch, or update taglib from git. Unfortunately, upstream is not released yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/taglib/+bug/1353988/+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 1353988] Re: Taglib causes crash
Any workarounds? Fixed taglib deb package or something? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to taglib in Ubuntu. https://bugs.launchpad.net/bugs/1353988 Title: Taglib causes crash Status in taglib package in Ubuntu: Confirmed Bug description: TagLib 1.9.1 has known bug: https://github.com/taglib/taglib/issues/308 Sometime it causes programs(clementine, amarok, qmmp and other with taglib usage) crash while reading tags. Please, apply attached patch, or update taglib from git. Unfortunately, upstream is not released yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/taglib/+bug/1353988/+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 1389215] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327204/+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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
** Attachment added: debdiff for Trusty https://bugs.launchpad.net/ubuntu-mate/+bug/1351890/+attachment/4327234/+files/gtk2-trusty-debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+ GUI Toolkit: Fix Released Status in Ubuntu MATE: Triaged Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Confirmed Status in gtk+2.0 package in Debian: Confirmed Bug description: Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+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 1351890] Re: Changing external screen resolution with dual monitors
** Attachment added: debdiff for Precise https://bugs.launchpad.net/ubuntu-mate/+bug/1351890/+attachment/4327223/+files/gtk2-precise-debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+ GUI Toolkit: Fix Released Status in Ubuntu MATE: Triaged Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Confirmed Status in gtk+2.0 package in Debian: Confirmed Bug description: Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+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 1425523] [NEW] Cannot connect to device with MTP
Public bug reported: From an Ubuntu Vivid host, the device is not visible over MTP. Disconnecting/reconnecting the cable doesn't change anything. I can connect to the device over adb. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: mtp-server 0.0.4+15.04.20150219-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Wed Feb 25 14:16:52 2015 InstallationDate: Installed on 2015-02-25 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: mtp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mtp (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug armhf vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1425523 Title: Cannot connect to device with MTP Status in mtp package in Ubuntu: Confirmed Bug description: From an Ubuntu Vivid host, the device is not visible over MTP. Disconnecting/reconnecting the cable doesn't change anything. I can connect to the device over adb. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: mtp-server 0.0.4+15.04.20150219-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Wed Feb 25 14:16:52 2015 InstallationDate: Installed on 2015-02-25 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: mtp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1425523/+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 1425523] Re: Cannot connect to device with MTP
** Changed in: mtp (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1425523 Title: Cannot connect to device with MTP Status in mtp package in Ubuntu: Confirmed Bug description: From an Ubuntu Vivid host, the device is not visible over MTP. Disconnecting/reconnecting the cable doesn't change anything. I can connect to the device over adb. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: mtp-server 0.0.4+15.04.20150219-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Wed Feb 25 14:16:52 2015 InstallationDate: Installed on 2015-02-25 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: mtp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1425523/+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 1389215] XorgLog.txt
apport information ** Attachment added: XorgLog.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327214/+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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1389215] xdpyinfo.txt
apport information ** Attachment added: xdpyinfo.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327219/+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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1195353] Re: SDK should provide support to rearrange items in a ListView
** Branch unlinked: lp:~zsombi/ubuntu-ui-toolkit/83-dragging -- 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/1195353 Title: SDK should provide support to rearrange items in a ListView Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: For the clock core app, as per design, it is required to implement ListView where the user can drag and drop to rearrange the items in the ListView. You can see the official wireframe designs at http://design.canonical.com/wp-content/uploads/clock_add_city- 1024x8901.png to see what I meant. It would be best if the SDK can provide support to implement this since it may also be useful to other apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1195353/+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 1340206] Re: [Network Menu] Enabling flight mode still shows the wifi icon
This is still happening current build number: 122 device name: krillin channel: ubuntu-touch/devel-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1340206 Title: [Network Menu] Enabling flight mode still shows the wifi icon Status in Network Menu: Triaged Status in Ubuntu UX bugs: Triaged Status in indicator-network package in Ubuntu: Confirmed Status in indicator-network source package in Utopic: Confirmed Status in indicator-network source package in Vivid: Confirmed Status in Ubuntu RTM: New Bug description: When we enable flight mode the wifi icon is still shown. https://wiki.ubuntu.com/Networking#Title: On the phone ... the title ... should consist of: Flight Mode indication: ✈ the Flight Mode icon, if Flight Mode is on, otherwise nothing at all. ... Finally, Wi- Fi status indication: ... nothing at all To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1340206/+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 708493] Re: Can't login anymore: Read from socket failed: Connection reset by peer
** Tags added: oneiric precise -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/708493 Title: Can't login anymore: Read from socket failed: Connection reset by peer Status in openssh package in Ubuntu: Confirmed Status in openssh package in Debian: New Bug description: After todays update to 1:5.7p1-1ubuntu1 I cannot login to SOME (!) of my servers. Example of a server failing: ~$ ssh -v root@mail OpenSSH_5.7p1 Debian-1ubuntu1, OpenSSL 0.9.8o 01 Jun 2010 debug1: Reading configuration data /home/hildeb/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to mail [141.42.202.200] port 22. debug1: Connection established. debug1: identity file /home/hildeb/.ssh/id_rsa type -1 debug1: identity file /home/hildeb/.ssh/id_rsa-cert type -1 debug1: identity file /home/hildeb/.ssh/id_dsa type 2 debug1: Checking blacklist file /usr/share/ssh/blacklist.DSA-1024 debug1: Checking blacklist file /etc/ssh/blacklist.DSA-1024 debug1: identity file /home/hildeb/.ssh/id_dsa-cert type -1 debug1: identity file /home/hildeb/.ssh/id_ecdsa type -1 debug1: identity file /home/hildeb/.ssh/id_ecdsa-cert type -1 debug1: Remote protocol version 1.99, remote software version OpenSSH_5.5p1 Debian-6 debug1: match: OpenSSH_5.5p1 Debian-6 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.7p1 Debian-1ubuntu1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-ctr hmac-md5 none debug1: kex: client-server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP Read from socket failed: Connection reset by peer There is NOTHING in daemon.log, auth.log or syslog on the server I'm trying to connect to. Example of a server NOT failing: $ ssh -v root@netsight OpenSSH_5.7p1 Debian-1ubuntu1, OpenSSL 0.9.8o 01 Jun 2010 debug1: Reading configuration data /home/hildeb/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to netsight [10.47.2.222] port 22. debug1: Connection established. debug1: identity file /home/hildeb/.ssh/id_rsa type -1 debug1: identity file /home/hildeb/.ssh/id_rsa-cert type -1 debug1: identity file /home/hildeb/.ssh/id_dsa type 2 debug1: Checking blacklist file /usr/share/ssh/blacklist.DSA-1024 debug1: Checking blacklist file /etc/ssh/blacklist.DSA-1024 debug1: identity file /home/hildeb/.ssh/id_dsa-cert type -1 debug1: identity file /home/hildeb/.ssh/id_ecdsa type -1 debug1: identity file /home/hildeb/.ssh/id_ecdsa-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.5p1 Debian-6 debug1: match: OpenSSH_5.5p1 Debian-6 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.7p1 Debian-1ubuntu1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-ctr hmac-md5 none debug1: kex: client-server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Server host key: RSA 18:ce:76:c7:7c:f4:98:94:28:8f:62:4a:31:e8:5b:c9 debug1: Host 'netsight' is known and matches the RSA host key. debug1: Found key in /home/hildeb/.ssh/known_hosts:56 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: publickey debug1: Offering DSA public key: /home/hildeb/.ssh/id_dsa debug1: Server accepts key: pkalg ssh-dss blen 433 debug1: Authentication succeeded (publickey). Authenticated to netsight ([10.47.2.222]:22). debug1: channel 0: new [client-session] debug1: Requesting no-more-sessi...@openssh.com debug1: Entering interactive session. debug1: Sending environment. debug1: Sending env LC_MESSAGES = en_US.utf8 debug1: Sending env LANG = de_DE.UTF-8 ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: openssh-client 1:5.7p1-1ubuntu1 ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37 Uname: Linux 2.6.37-12-generic x86_64 Architecture: amd64 Date: Thu Jan 27 09:13:15 2011 ProcEnviron: LANGUAGE=en_US:en LANG=de_DE.UTF-8 LC_MESSAGES=en_US.utf8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-ssh N/A keychain N/A
[Touch-packages] [Bug 1423855] Re: Unity can't show the global menu item for some gnome apps
** Also affects: indicator-appmenu (Ubuntu) Importance: Undecided Status: New -- 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/1423855 Title: Unity can't show the global menu item for some gnome apps Status in Unity: Triaged Status in indicator-appmenu package in Ubuntu: New Status in unity package in Ubuntu: Triaged Bug description: Unity can't show the global menu item for some gnome apps. For example, the 'terminal' menu for gnome-terminal, or the 'calculator' menu for gnome-calculator cannot be opened. Other menus can be displayed (file, edit,...) This is a recent regression I think. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150219.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Feb 20 21:14:01 2015 InstallationDate: Installed on 2015-01-31 (20 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1423855/+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 1389215] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327207/+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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1389215] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327209/+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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1389215] NvidiaBugReportLog.txt
apport information ** Attachment added: NvidiaBugReportLog.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327206/+files/NvidiaBugReportLog.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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1389215] LightdmLog.txt
apport information ** Attachment added: LightdmLog.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327203/+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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
** Attachment added: debdiff for Utopic https://bugs.launchpad.net/ubuntu-mate/+bug/1351890/+attachment/4327235/+files/gtk2-utopic-debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+ GUI Toolkit: Fix Released Status in Ubuntu MATE: Triaged Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Confirmed Status in gtk+2.0 package in Debian: Confirmed Bug description: Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+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 1263228] Re: icons in indicators are small (difficult to view on FullHD display and smaller than was on 12.04)
Moving this over to an ido bug. The individual widgets live there, so that's where it'll need to be fixed/tracked. ** No longer affects: indicator-application ** No longer affects: indicator-datetime ** No longer affects: indicator-keyboard ** No longer affects: indicator-messages ** No longer affects: indicator-session ** No longer affects: indicator-sound ** No longer affects: indicator-power ** No longer affects: libindicator ** No longer affects: gnome-panel (Ubuntu) ** Package changed: indicator-application (Ubuntu) = ido (Ubuntu) ** No longer affects: indicator-datetime (Ubuntu) ** No longer affects: indicator-keyboard (Ubuntu) ** No longer affects: indicator-messages (Ubuntu) ** No longer affects: indicator-session (Ubuntu) ** No longer affects: indicator-sound (Ubuntu) ** No longer affects: libindicator (Ubuntu) -- 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/1263228 Title: icons in indicators are small (difficult to view on FullHD display and smaller than was on 12.04) Status in ido package in Ubuntu: Triaged Status in indicator-power package in Ubuntu: Fix Released Bug description: I have Ubuntu 14.04 with all updates installed. My screen resolution is 1920x1080 (FullHD) at 16.4 inches. Icons from the menu of newest indicator-keyboard and other gnome-panel icons are very small (difficult to read). Please adapt icon sizes to large screen resolutions. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-keyboard 0.0.0+14.04.20131125-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.7-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Sat Dec 21 00:41:25 2013 InstallationDate: Installed on 2013-10-20 (61 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to trusty on 2013-11-19 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1263228/+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 1425544] [NEW] Aggregator scopes must not forward location setting to scopes
Public bug reported: If a user explicitly denies location to a specific scope, then the scope should never ever receive location data even though a possible aggregator scope got location data granted. ** Affects: unity-scopes-shell (Ubuntu) Importance: High Assignee: Michi Henning (michihenning) Status: New ** Changed in: unity-scopes-shell (Ubuntu) Importance: Undecided = High ** Changed in: unity-scopes-shell (Ubuntu) Assignee: (unassigned) = Michi Henning (michihenning) -- 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/1425544 Title: Aggregator scopes must not forward location setting to scopes Status in unity-scopes-shell package in Ubuntu: New Bug description: If a user explicitly denies location to a specific scope, then the scope should never ever receive location data even though a possible aggregator scope got location data granted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1425544/+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 1373598] Re: apt-get update fails, hash sum mismatches (trusty)
For the german users: Could you please run ping -c 2 de.archive.ubuntu.com right after you have observed the hash sum mismatch error on updating your package list from the german sources. A colleage of mine and I have tetermined a poisening mirror in germany at the TU-Dresden and whant some confirmations that it is really and only this mirror. The maintainer of the mirror could not observe the error on his testcomputer. This is why we whant also to have the information in which part of gemany (Bundesland) you obverse the error. Maybe it is something between the mirror and us(where ever we are). Please paste the output of the ping above and the location(Bundesland) where you are. -- 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/1373598 Title: apt-get update fails, hash sum mismatches (trusty) Status in apt package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: 1. Release: Description: Ubuntu 14.04.1 LTS Release: 14.04 2. not a package. The whole distro is broken. 3. I always expect apt-get update to work, at least with Ubuntu's own repositories. 4. apt-get update failed, and later apt-get dist upgrade It started with this when doing a normal apt-get update W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/main/source/Sources Hash Sum mismatch W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/main/binary-amd64/Packages Hash Sum mismatch W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/universe/binary-i386/Packages Hash Sum mismatch E: Some index files failed to download. They have been ignored, or old ones used instead. When doing a dist-upgrade, I then got this: E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-3.13.0-36-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-extra-3.13.0-36-generic.postinst line 1025. No apport report written because the error message indicates its a followup error from a previous failure. dpkg: error processing package linux-image-extra-3.13.0-36-generic (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-image-extra-3.13.0-36-generic; however: Package linux-image-extra-3.13.0-36-generic is not configured yet. dpkg: error processing package linux-image-generic (--configure): dependency problems - leaving unconfigured Setting up linux-headers-3.13.0-36 (3.13.0-36.63) ... Setting up linux-headers-3.13.0-36-generic (3.13.0-36.63) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.13.0-36-generic /boot/vmlinuz-3.13.0-36-generic Setting up linux-headers-generic (3.13.0.36.43) ... No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-image-generic (= 3.13.0.36.43); however: Package linux-image-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured And later this at the end: Processing triggers for libc-bin (2.19-0ubuntu6.3) ... E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.5 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Wed Sep 24 21:57:55 2014 InstallationDate: Installed on 2013-05-09 (503 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to trusty on 2014-05-04 (142 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1373598/+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 1425199] Re: when trying to launch unity8-in-lxc sesssion, indicator-sound-service crashed with signal 5 in main()
*** This bug is a duplicate of bug 1425024 *** https://bugs.launchpad.net/bugs/1425024 OK - I filed bug 1425494 with the log files attached. Am 24.02.2015 um 20:33 schrieb Christopher Townsend: Hi Daniel, I would be surprised that indicator-sound crashing is the cause of you not being able to log in. The crash seems to be due to indicator-sound not getting the session DBus which is an issue in and of itself, so we'll leave this bug as is. Could you please do the following (I apologize for extra work, but it will help me)? - Open a new bug report against unity8-lxc. - Attach the following logs to the bug report (if they exist): - /var/log/lightdm/unity-system-compositor.log - /var/log/lightdm/lightdm.log - ~/.cache/upstart/unity8.log Thanks! ** Information type changed from Private to Public ** Changed in: unity8-lxc (Ubuntu) Status: New = Triaged ** Changed in: unity8-lxc (Ubuntu) Importance: Undecided = Medium ** Changed in: unity8-lxc (Ubuntu) Assignee: (unassigned) = Christopher Townsend (townsend) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1425199 Title: when trying to launch unity8-in-lxc sesssion, indicator-sound-service crashed with signal 5 in main() Status in indicator-sound package in Ubuntu: New Status in unity8-lxc package in Ubuntu: Triaged Bug description: When trying to launch the Unity 8 in LXC session from the official packages, lightdm freezes after logging in with the user's data. After launching into the regular (Xubuntu, in this case) session, a crash of indicator-sound is reported. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150219.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4 Uname: Linux 3.18.0-12-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 Date: Tue Feb 24 18:21:32 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service InstallationDate: Installed on 2015-02-05 (18 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150205) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: indicator-sound StacktraceTop: main () Title: indicator-sound-service crashed with signal 5 in main() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1425199/+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 1389215] DkmsStatus.txt
apport information ** Attachment added: DkmsStatus.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327197/+files/DkmsStatus.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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1425539] Re: apport-gtk crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1416773 *** https://bugs.launchpad.net/bugs/1416773 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1416773, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1425539/+attachment/4327225/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1425539/+attachment/4327227/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1425539/+attachment/4327229/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1425539/+attachment/4327230/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1425539/+attachment/4327231/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1425539/+attachment/4327232/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1425539/+attachment/4327233/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1416773 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1425539 Title: apport-gtk crashed with SIGABRT in g_assertion_message() Status in apport package in Ubuntu: New Bug description: happened updating to vv ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: apport-gtk 2.16.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CrashReports: 644:0:118:0:2015-02-25 23:15:49.365123074 +0900:2015-02-25 23:15:49.365123074 +0900:/var/crash/_usr_bin_do-release-upgrade.0.upload 640:1000:118:1091118:2015-02-25 23:15:03.935653448 +0900:2015-02-25 23:15:04.935653448 +0900:/var/crash/_usr_bin_gnome-shell.1000.crash 640:1000:118:4931791:2015-02-25 23:15:11.540857553 +0900:2015-02-25 23:15:12.540857553 +0900:/var/crash/_usr_share_apport_apport-gtk.1000.crash 640:0:118:2814757:2015-02-25 23:15:45.329101085 +0900:2015-02-25 23:15:46.329101085 +0900:/var/crash/_usr_bin_do-release-upgrade.0.crash CurrentDesktop: GNOME Date: Wed Feb 25 23:15:05 2015 ExecutablePath: /usr/share/apport/apport-gtk ExecutableTimestamp: 1423569428 InstallationDate: Installed on 2015-01-18 (38 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 (20141022.1) InterpreterPath: /usr/bin/python3.4 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcCwd: /home/dougie Signal: 6 SourcePackage: apport StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_window_set_titlebar () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to vivid on 2015-02-25 (0 days ago) UserGroups: adm bluetooth cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1425539/+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 1205032] Re: Indicator-sound's menu looks different on Cairo-Dock applet
** Package changed: indicator-sound (Ubuntu) = ido (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ido in Ubuntu. https://bugs.launchpad.net/bugs/1205032 Title: Indicator-sound's menu looks different on Cairo-Dock applet Status in ido package in Ubuntu: Triaged Bug description: Hello, This bug is maybe not due to Indicator-Sound but since this indicator has been ported to a service (since we have to load /usr/share/unity/indicators/com.canonical.indicator.sound), its menu looks different when using it with Cairo-Dock or with indicator-loader. As you can see on the screenshot (indicator-sound_loader-vs-cairo-dock.png), players menu entries reserve more spaces with Cairo-Dock. Note: ido_init() has been called once and these new indicators are loaded with desktop profile. More info: https://bazaar.launchpad.net/~cairo-dock-team/cairo-dock-plug-ins/plug-ins/view/head:/Indicator-applet3/indicator-applet3.c#L29 The code is not so big and not so different than indicator-loader: https://bazaar.launchpad.net/~indicator-applet-developers/libindicator/trunk.13.10/view/head:/tools/indicator-loader.c The dock just loads the applet and popup the menu (IndicatorObjectEntry-menu) Any idea of what is wrong? :) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-sound 12.10.2+13.10.20130725-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2 Uname: Linux 3.10.0-5-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 Date: Thu Jul 25 19:43:46 2013 InstallationDate: Installed on 2011-08-10 (715 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110803.1) MarkForUpload: True SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1205032/+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 1389215] UnitySupportTest.txt
apport information ** Attachment added: UnitySupportTest.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327213/+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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1389215] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327211/+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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1389215] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327210/+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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1389215] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327212/+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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1425529] Re: /var/log owned by wrong group (android_input)
** Summary changed: - /var/log owned by wrong group after a factory reset + /var/log owned by wrong group (android_input) ** Description changed: - After a factory reset the directory /var/log is owned by android_input - instead of syslog. + After flashing a krillin with: + ubuntu-device-flash touch --bootstrap --channel devel-proposed --recovery-image recovery.img + + /var/log is owned by the wrong group. $ ls -ld /var/log /userdata/system-data/var/log drwxrwxr-x 11 root android_input 4096 févr. 25 14:15 /userdata/system-data/var/log drwxrwxr-x 11 root android_input 4096 févr. 25 14:15 /var/log ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: rsyslog 7.4.4-1ubuntu14 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Wed Feb 25 14:37:15 2015 InstallationDate: Installed on 2015-02-25 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.rsyslog: [deleted] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1425529 Title: /var/log owned by wrong group (android_input) Status in rsyslog package in Ubuntu: New Bug description: After flashing a krillin with: ubuntu-device-flash touch --bootstrap --channel devel-proposed --recovery-image recovery.img /var/log is owned by the wrong group. $ ls -ld /var/log /userdata/system-data/var/log drwxrwxr-x 11 root android_input 4096 févr. 25 14:15 /userdata/system-data/var/log drwxrwxr-x 11 root android_input 4096 févr. 25 14:15 /var/log ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: rsyslog 7.4.4-1ubuntu14 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Wed Feb 25 14:37:15 2015 InstallationDate: Installed on 2015-02-25 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.rsyslog: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1425529/+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 819296] Re: unity-panel-service crashed with SIGABRT in raise()
Official support for Ubuntu 11.10 Oneiric Ocelot has ended. If this error is still occurring on Ubuntu 14.10 Utopic Unicorn please run ubuntu-bug to file a new bug report so that we can get a fresh set of log files and system information. ** Changed in: libdbusmenu (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdbusmenu in Ubuntu. https://bugs.launchpad.net/bugs/819296 Title: unity-panel-service crashed with SIGABRT in raise() Status in DBus Menu: Confirmed Status in libdbusmenu package in Ubuntu: Invalid Bug description: Was clicking around in the indicators at the time. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: unity-services 4.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-7.8-generic 3.0.0 Uname: Linux 3.0.0-7-generic i686 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unitydialog,unityshell] CrashCounter: 1 Date: Mon Aug 1 08:30:39 2011 EcryptfsInUse: Yes ExecutablePath: /usr/lib/unity/unity-panel-service InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110422) ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: unity StacktraceTop: ?? () from /lib/ld-linux.so.2 raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 g_assertion_message (domain=0x9b6f86 GLib, file=0xa056e8 /build/buildd/glib2.0-2.29.14/./glib/gvarianttypeinfo.c, line=165, func=0xa05930 g_variant_type_info_check, message=value optimized out) at /build/buildd/glib2.0-2.29.14/./glib/gtestutils.c:1425 g_assertion_message_expr (domain=0x9b6f86 GLib, file=0xa056e8 /build/buildd/glib2.0-2.29.14/./glib/gvarianttypeinfo.c, line=165, func=0xa05930 g_variant_type_info_check, expr=0xa05760 info-alignment == 0 || info-alignment == 1 || info-alignment == 3 || info-alignment == 7) at /build/buildd/glib2.0-2.29.14/./glib/gtestutils.c:1436 Title: unity-panel-service crashed with SIGABRT in raise() UpgradeStatus: Upgraded to oneiric on 2011-07-27 (5 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/819296/+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 1389215] Re: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver.
The problem still persist on my laptop running Ubuntu 14.04 LTS Trusty Thar, all packages updated up to 2015-02-25. -- 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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: Incomplete Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati:
[Touch-packages] [Bug 1389215] Re: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver.
apport information ** Tags added: apport-collected possible-manual-nvidia-install ** Description changed: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Nov 4 01:40:35 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such
[Touch-packages] [Bug 1389215] nvidia-installer.log.txt
apport information ** Attachment added: nvidia-installer.log.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327217/+files/nvidia-installer.log.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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
[Touch-packages] [Bug 1389215] Xrandr.txt
apport information ** Attachment added: Xrandr.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327216/+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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1389215] Re: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver.
** 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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
[Touch-packages] [Bug 1389215] nvidia-settings.txt
apport information ** Attachment added: nvidia-settings.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327218/+files/nvidia-settings.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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1389215] LightdmGreeterLogOld.txt
apport information ** Attachment added: LightdmGreeterLogOld.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327202/+files/LightdmGreeterLogOld.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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
[Touch-packages] [Bug 1415029] Re: Not yet available but configured providers should be added as soon as they become available
Version: ubuntu-touch/stable/bq-aquaris.en r18 krillin Just tried to switch to HERE supported location after having initially been set to GPS only. A reboot was required before the HERE app was able to find my location. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1415029 Title: Not yet available but configured providers should be added as soon as they become available Status in the base for Ubuntu mobile products: Fix Released Status in location-service package in Ubuntu: In Progress Status in ubuntu-location-provider-here package in Ubuntu: In Progress Status in ubuntu-location-provider-here package in Ubuntu RTM: Fix Released Bug description: Right now, the location service tries to instantiate configured providers at startup. In specific corner cases, some of the configured sensors might not be available and the service should be able to be notified when those providers become available. In particular, this affects the wizard running on first boot, and subsequent login to the user session. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1415029/+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 1423394] Re: Unity Desktop Crashes when using Google Chrome Browser
Have you tried to disable hardware acceleration in Chrome (advanced settings)? -- 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/1423394 Title: Unity Desktop Crashes when using Google Chrome Browser Status in unity package in Ubuntu: Incomplete Bug description: 1.) Description: Ubuntu 14.04.1 LTS Release: 14.04 2.) google-chrome-stable: Installed: 40.0.2214.111-1 Candidate: 40.0.2214.111-1 Version table: *** 40.0.2214.111-1 0 500 http://dl.google.com/linux/chrome/deb/ stable/main amd64 Packages 100 /var/lib/dpkg/status 3.) Expect to see video play and no crashing. 4.) When using Google Chrome (current version 40.0.2214.111 (64-bit)) and attempting to watch any Youtube video, the Unity Desktop experiences a crash and the Unity Desktop (unity start/search and task bar) disappear. I am unable to launch a terminal window. All Window menus disappear (i.e. Minimize, Maximize, Close) including those that are related to the top right shutdown/restart/logoff menu. Desktop background remains viewable and Desktop icons are also viewable. Keyboard input starts to malfunction in window sections. --- ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,snap,resize,move,imgpng,grid,regex,mousepoll,place,vpswitch,compiztoolbox,gnomecompat,animation,session,wall,fade,unitymtgrabhandles,expo,scale,workarounds,ezoom,unityshell] CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-08-24 (544 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) Package: unity 7.2.3+14.04.20140826-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Tags: trusty third-party-packages Uname: Linux 3.13.0-45-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-18 (276 days ago) UserGroups: adm lp lpadmin sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1423394/+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 1353988] Re: Taglib causes crash
You can use package from here: https://launchpad.net/~forkotov02/+archive/ubuntu/ppa -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to taglib in Ubuntu. https://bugs.launchpad.net/bugs/1353988 Title: Taglib causes crash Status in taglib package in Ubuntu: Confirmed Bug description: TagLib 1.9.1 has known bug: https://github.com/taglib/taglib/issues/308 Sometime it causes programs(clementine, amarok, qmmp and other with taglib usage) crash while reading tags. Please, apply attached patch, or update taglib from git. Unfortunately, upstream is not released yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/taglib/+bug/1353988/+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 1389215] BootLog.txt
apport information ** Attachment added: BootLog.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327194/+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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1389215] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327196/+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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1389215] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327195/+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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1389215] DpkgLog.txt
apport information ** Attachment added: DpkgLog.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327198/+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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1389215] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327205/+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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1389215] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327208/+files/ProcEnviron.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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1424653] Re: Cannot unlock lock screen when using user without password
** Also affects: unity Importance: Undecided Status: New -- 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/1424653 Title: Cannot unlock lock screen when using user without password Status in Unity: New Status in unity package in Ubuntu: New Bug description: Creating a new user without login password makes the lock screen (Ctrl+Alt+L) unlockable because it asks for a password and none works (even blank). Ubuntu 14.04 and Ubuntu 14.10 clean installs and fully updated. In Ubuntu 14.10: Unity 7.3.1+14.10.20141016-0ubuntu1 Expected: No password to unlock and unlock the screen. What happens: The lock screens request a password to the user without it and doesn't unlock the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1424653/+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 1373598] Re: apt-get update fails, hash sum mismatches (trusty)
The TU-Dresden mirror info page could be found here: https://launchpad.net/ubuntu/+mirror/ubuntu.mirror.tudos.de-archive -- 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/1373598 Title: apt-get update fails, hash sum mismatches (trusty) Status in apt package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: 1. Release: Description: Ubuntu 14.04.1 LTS Release: 14.04 2. not a package. The whole distro is broken. 3. I always expect apt-get update to work, at least with Ubuntu's own repositories. 4. apt-get update failed, and later apt-get dist upgrade It started with this when doing a normal apt-get update W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/main/source/Sources Hash Sum mismatch W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/main/binary-amd64/Packages Hash Sum mismatch W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/universe/binary-i386/Packages Hash Sum mismatch E: Some index files failed to download. They have been ignored, or old ones used instead. When doing a dist-upgrade, I then got this: E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-3.13.0-36-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-extra-3.13.0-36-generic.postinst line 1025. No apport report written because the error message indicates its a followup error from a previous failure. dpkg: error processing package linux-image-extra-3.13.0-36-generic (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-image-extra-3.13.0-36-generic; however: Package linux-image-extra-3.13.0-36-generic is not configured yet. dpkg: error processing package linux-image-generic (--configure): dependency problems - leaving unconfigured Setting up linux-headers-3.13.0-36 (3.13.0-36.63) ... Setting up linux-headers-3.13.0-36-generic (3.13.0-36.63) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.13.0-36-generic /boot/vmlinuz-3.13.0-36-generic Setting up linux-headers-generic (3.13.0.36.43) ... No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-image-generic (= 3.13.0.36.43); however: Package linux-image-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured And later this at the end: Processing triggers for libc-bin (2.19-0ubuntu6.3) ... E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.5 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Wed Sep 24 21:57:55 2014 InstallationDate: Installed on 2013-05-09 (503 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to trusty on 2014-05-04 (142 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1373598/+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 1389512] Re: Xorg freeze
kurt stoller, thank you for reporting this and helping make Ubuntu better. As per http://www.msi.com/support/mb/K9N2GMFD.html#down-bios an update to your computer's buggy and outdated BIOS is available (1.8). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, and the information above is provided, then please mark this report Status New. Thank you for your understanding. ** 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/1389512 Title: Xorg freeze Status in xorg package in Ubuntu: Incomplete Bug description: the screen consistantly locks up when I am using applications in such as Firefox. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 304.123 Wed Jul 2 11:08:21 PDT 2014 GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 21:35:37 2014 DistUpgraded: 2014-10-28 00:39:50,317 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.123, 3.13.0-37-generic, i686: installed ExtraDebuggingInterest: No GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation C77 [GeForce 8200] [10de:0849] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] K9N2GM-FIH [1462:7508] InstallationDate: Installed on 2014-08-03 (93 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) MachineType: MICRO-STAR INTERANTONAL CO.,LTD MS-7508 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=499d044d-0967-4db2-8de7-a74ddf50359a ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to utopic on 2014-10-28 (7 days ago) dmi.bios.date: 05/12/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.0 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7508 dmi.board.vendor: MICRO-STAR INTERANTONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERANTONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.0:bd05/12/2008:svnMICRO-STARINTERANTONALCO.,LTD:pnMS-7508:pvr1.0:rvnMICRO-STARINTERANTONALCO.,LTD:rnMS-7508:rvr1.0:cvnMICRO-STARINTERANTONALCO.,LTD:ct3:cvr1.0: dmi.product.name: MS-7508 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERANTONAL CO.,LTD version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A 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~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Nov 4 21:09:54 2014 xserver.configfile: default xserver.devices: inputPower Button
[Touch-packages] [Bug 1425484] Re: wizard aborts and goes directly to the dash
** Changed in: unity8 (Ubuntu) Status: New = Confirmed -- 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/1425484 Title: wizard aborts and goes directly to the dash Status in unity8 package in Ubuntu: Confirmed Bug description: TEST CASE: 1. Go to system-settings and do a factory reset 2. After reboot in the wizard, dismiss the first SIM PIN dialog 3. Select 'French' in the list of languages 4. Tap on 'Continue' EXPECT RESULT The step 'device security' is displayed ACTUAL RESULT A blank screen is displayed (empty page with the default background) and after a few seconds the wizard stops and the dash loads. The edge intro is skipped. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity8 8.02+15.04.20150224-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Wed Feb 25 11:41:16 2015 InstallationDate: Installed on 2015-02-25 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1425484/+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 1425484] [NEW] wizard aborts and goes directly to the dash
Public bug reported: TEST CASE: 1. Go to system-settings and do a factory reset 2. After reboot in the wizard, dismiss the first SIM PIN dialog 3. Select 'French' in the list of languages 4. Tap on 'Continue' EXPECT RESULT The step 'device security' is displayed ACTUAL RESULT A blank screen is displayed (empty page with the default background) and after a few seconds the wizard stops and the dash loads. The edge intro is skipped. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity8 8.02+15.04.20150224-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Wed Feb 25 11:41:16 2015 InstallationDate: Installed on 2015-02-25 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity8 (Ubuntu) Importance: Critical Status: Confirmed ** Tags: apport-bug armhf qa-promotion vivid -- 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/1425484 Title: wizard aborts and goes directly to the dash Status in unity8 package in Ubuntu: Confirmed Bug description: TEST CASE: 1. Go to system-settings and do a factory reset 2. After reboot in the wizard, dismiss the first SIM PIN dialog 3. Select 'French' in the list of languages 4. Tap on 'Continue' EXPECT RESULT The step 'device security' is displayed ACTUAL RESULT A blank screen is displayed (empty page with the default background) and after a few seconds the wizard stops and the dash loads. The edge intro is skipped. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity8 8.02+15.04.20150224-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Wed Feb 25 11:41:16 2015 InstallationDate: Installed on 2015-02-25 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1425484/+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 1424015] Re: App names cannot be translated
See also Bug #1383841 -- 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/1424015 Title: App names cannot be translated Status in unity-scope-click package in Ubuntu: Invalid Bug description: Currently apps inside the store have not their name translated in different languages. If someone submits a Google Docs app, it will be its name, while it could be translated (in Italian Google Documenti for example) and be easier to identify for non-English people. As far as I know, the desktop file can have translated entries, so the app will have its name translated once installed. For this reason I think that probably the easiest way (to not duplicate efforts to the developer) would be to use these entries to show the app name translated in the different languages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1424015/+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 1418060] Re: [FFe] QML compilation cache patch needs adaptation for Qt 5.4
Patch headers added. Upstream discussion is currently being planned, there should be enough time to discuss and get it to Qt 5.6 which will have feature freeze somewhere around July. -- 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/1418060 Title: [FFe] QML compilation cache patch needs adaptation for Qt 5.4 Status in qtdeclarative-opensource-src package in Ubuntu: In Progress Bug description: -- FFe -- Since we're past the feature freeze, bringing this patch back needs an exception, even though it's a regression fix at the same time. Summary: - The patch allows opt-in, environment variable controlled use of storing some cache data when loading QML files. Without the environment variable there are no changes. - Not having the patch is a performance regression on application startup time on the phones from Qt 5.3.2. - The patch already shipped in Qt 5.3.2, but needed adjustments for 5.4 that were not done on time when Qt 5.4 was otherwise ready to land before feature freeze, so the patch was commented out. - The patch is also shipping on the sold Bq phones. - The proposed changes are in the MP below, that is uncommenting the patch in debian/patches/series and the rebasing (the full patch is 25 files changed, 703 insertions(+), 14 deletions(-)). As usual, we have a wide testing being done also on this rebased-to- Qt-5.4.0 patch. Upstreaming is being considered now that the patch seems to work for our purposes. It might need more than code discussions since upstream developer is also selling a proprietary product that offers somewhat similar benefits. -- Original bug report -- The environment variable controlled new functionality provided by QML compilation cache patch (landed for Qt 5.3.2) needs adaptation for Qt 5.4, as it does not currently apply. Attachment shows a summary of the patch applying problems. More information about Qt 5.4 at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1418060/+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 1306857] Re: apport authentication windows isn't localized
This bug is fixed with Ubuntu kylin 15.04 x64 daily build 20150224 ** Changed in: ubuntukylin Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1306857 Title: apport authentication windows isn't localized Status in Apport crash detection/reporting: Fix Released Status in Ubuntu Kylin: Fix Released Status in apport package in Ubuntu: Fix Released Bug description: apport authentication windows isn't localized, see auth.png To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1306857/+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 1423855] Re: Unity can't show the global menu item for some gnome apps
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-appmenu (Ubuntu) Status: New = Confirmed -- 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/1423855 Title: Unity can't show the global menu item for some gnome apps Status in Unity: Triaged Status in indicator-appmenu package in Ubuntu: Confirmed Status in unity package in Ubuntu: Triaged Bug description: Unity can't show the global menu item for some gnome apps. For example, the 'terminal' menu for gnome-terminal, or the 'calculator' menu for gnome-calculator cannot be opened. Other menus can be displayed (file, edit,...) This is a recent regression I think. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150219.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Feb 20 21:14:01 2015 InstallationDate: Installed on 2015-01-31 (20 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1423855/+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 1425529] [NEW] /var/log owned by wrong group after a factory reset
Public bug reported: After a factory reset the directory /var/log is owned by android_input instead of syslog. $ ls -ld /var/log /userdata/system-data/var/log drwxrwxr-x 11 root android_input 4096 févr. 25 14:15 /userdata/system-data/var/log drwxrwxr-x 11 root android_input 4096 févr. 25 14:15 /var/log ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: rsyslog 7.4.4-1ubuntu14 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Wed Feb 25 14:37:15 2015 InstallationDate: Installed on 2015-02-25 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.rsyslog: [deleted] ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1425529 Title: /var/log owned by wrong group after a factory reset Status in rsyslog package in Ubuntu: New Bug description: After a factory reset the directory /var/log is owned by android_input instead of syslog. $ ls -ld /var/log /userdata/system-data/var/log drwxrwxr-x 11 root android_input 4096 févr. 25 14:15 /userdata/system-data/var/log drwxrwxr-x 11 root android_input 4096 févr. 25 14:15 /var/log ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: rsyslog 7.4.4-1ubuntu14 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Wed Feb 25 14:37:15 2015 InstallationDate: Installed on 2015-02-25 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.rsyslog: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1425529/+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 1389215] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327193/+files/BootDmesg.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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1389215] LightdmDisplayLog.txt
apport information ** Attachment added: LightdmDisplayLog.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327200/+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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1389215] GconfCompiz.txt
apport information ** Attachment added: GconfCompiz.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327199/+files/GconfCompiz.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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1389215] LightdmGreeterLog.txt
apport information ** Attachment added: LightdmGreeterLog.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327201/+files/LightdmGreeterLog.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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1389215] XorgLogOld.txt
apport information ** Attachment added: XorgLogOld.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327215/+files/XorgLogOld.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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1389215] xserver.devices.txt
apport information ** Attachment added: xserver.devices.txt https://bugs.launchpad.net/bugs/1389215/+attachment/4327220/+files/xserver.devices.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/1389215 Title: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver. Status in xorg package in Ubuntu: New Bug description: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
[Touch-packages] [Bug 1425484] Re: wizard aborts and goes directly to the dash
It also happens after a fresh flash with bootstrap. -- 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/1425484 Title: wizard aborts and goes directly to the dash Status in unity8 package in Ubuntu: Confirmed Bug description: TEST CASE: 1. Go to system-settings and do a factory reset 2. After reboot in the wizard, dismiss the first SIM PIN dialog 3. Select 'French' in the list of languages 4. Tap on 'Continue' EXPECT RESULT The step 'device security' is displayed ACTUAL RESULT A blank screen is displayed (empty page with the default background) and after a few seconds the wizard stops and the dash loads. The edge intro is skipped. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity8 8.02+15.04.20150224-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Wed Feb 25 11:41:16 2015 InstallationDate: Installed on 2015-02-25 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1425484/+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 1363400] Re: [wizard] allows to Continue without connecting to network
** Changed in: ubuntu-ux Status: Fix Committed = Fix Released -- 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/1363400 Title: [wizard] allows to Continue without connecting to network Status in the base for Ubuntu mobile products: Fix Released Status in Ubuntu UX bugs: Fix Released Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu RTM: Fix Released Bug description: The wifi page of the wizard lets you select the network, but doesn't wait for a connection to enable the Continue button. Until connected, the button should probably say Skip, and if there's a connection in progress, that should be cancelled. Or we need a modal dialog introduced (like the one we have for notifications in the shell) in the wizard as well, so that you need to cancel the password entry before being able to skip. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: ubuntu-system-settings-wizard 0.3+14.10.20140828.2~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.6-0ubuntu2 Architecture: armhf Date: Sat Aug 30 11:17:34 2014 InstallationDate: Installed on 2014-08-30 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140830-030204) SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) upstart.ubuntu-system-settings-wizard-cleanup.log: Ending wizard Resetting MIR_SOCKET to /run/mir_socket () ubuntu-system-settings-wizard stop/waiting To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1363400/+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 1423855] Re: Unity can't show the global menu item for some gnome apps
** Changed in: indicator-appmenu (Ubuntu) Status: Confirmed = Triaged ** Changed in: indicator-appmenu (Ubuntu) Importance: Undecided = High -- 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/1423855 Title: Unity can't show the global menu item for some gnome apps Status in Unity: Triaged Status in indicator-appmenu package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Bug description: Unity can't show the global menu item for some gnome apps. For example, the 'terminal' menu for gnome-terminal, or the 'calculator' menu for gnome-calculator cannot be opened. Other menus can be displayed (file, edit,...) This is a recent regression I think. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150219.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Feb 20 21:14:01 2015 InstallationDate: Installed on 2015-01-31 (20 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1423855/+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 1424233] Re: RFE lxc: lxc should do a better jon of housekeeping containers
All the LXC commands default to tracking a single lxcpath which is /var/lib/lxc or whatever you set as lxc.lxcpath in /etc/lxc/lxc.conf It is actually a feature that LXC will not attempt to keep track of containers outside that path because that's what we expect other container managers (like LXD) to do. There have been talks to support a list of lxc paths separated by a colon in lxc.lxcpath and as an argument of -P which will allow LXC to keep track of containers in multiple paths but that's still being discussed and there are problems with that which still need to be thought through. Anyway, all that to say, LXC upstream has absolutely no interest in keeping track of all containers on the system, if the user manually created containers outside of the lxcpath which LXC tracks, we assume they've done so on purpose and so will not interfere. ** Changed in: lxc (Ubuntu) Status: New = Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1424233 Title: RFE lxc: lxc should do a better jon of housekeeping containers Status in lxc package in Ubuntu: Won't Fix Bug description: Right now lxc does a pretty poor job wrt. managing containers, i.e. one needs to know, where containers have been installed to be able to access/use/manage them (option -P dir) unless they've been installed in the default location. Even if one knows the install path, it is still a pain to work with corresponding lxc commands, because one always needs to specify -P ... This really sucks (especially if one needs to service foreign machines). So the proposal is, that if a zone gets created, lxc puts a symlink to the related config under /etc/lxc/cfg/ or something like that and all lxc tools like lxc-ls first check this directory, and if the link destination exists, it has all information it needs to know., i.e. all -P idontknow madness is not required anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1424233/+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 1390120] Re: Manually set time and date reverts to Automatically on restart (Ubuntu Phone)
Unsure what's going on there, but on my rtm bq device automatic doesn't reverts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1390120 Title: Manually set time and date reverts to Automatically on restart (Ubuntu Phone) Status in systemd package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: 1a - On OS build #6 (Channel: ubuntu-touch/ubuntu-rtm/14.09), I open Time Date settings and select Manually under Set the time and date: 2a - I set the time manually from Old_Time to New_Time and wait for New_Time to display in the Date Time Indicator at top-right 3a - Then restart Ubuntu Phone and Date Time Indicator shows New_Time for 10 seconds and then reverts to Old_Time 4a - Time Date settings agree with Old_Time and Automatically has been selected under Set the time and date: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1390120/+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 1425477] [NEW] After some time of LXC usage SSH fails with `openpty: Permission denied`
Please show us the exact commands you used to create and run the containers. Please show us the userids you are running them as, and contents of /etc/subuid. Please show /proc/slef/mountinfo both from the host and a container. status: incomplete ** Changed in: lxc (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1425477 Title: After some time of LXC usage SSH fails with `openpty: Permission denied` Status in lxc package in Ubuntu: Incomplete Bug description: I'm running Ubuntu 14.04.2 LTS on GNU/Linux 3.13.0-45-generic x86_64 as a host machine for tests run on LXC guests. After a few test runs on LXC machines, startup of next LXC machine hangs indefinitely. At the same time SSH connections to the host machine display PTY allocation request failed on channel 0 and SSH logs in auth.log Feb 25 05:19:28 remotedev sshd[18578]: error: openpty: Permission denied Feb 25 05:19:28 remotedev sshd[18628]: error: session_pty_req: session 0 alloc failed Only reboot brings the machine back to usable state. I've tried destroying the non-starting LXC guest, stopping removing all guests, purging lxc and lxc-templates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1425477/+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 1360316] Re: Logging out the desktop session just goes back to the Unity 8 Session Greeter
Marking the unity8-desktop-session task Invalid as this fix is in unity8 itself. ** Changed in: unity8-desktop-session (Ubuntu) Status: Confirmed = Invalid -- 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/1360316 Title: Logging out the desktop session just goes back to the Unity 8 Session Greeter Status in unity8 package in Ubuntu: In Progress Status in unity8-desktop-session package in Ubuntu: Invalid Bug description: When trying to log out of the desktop session, you are taken back to the Unity 8 Session Greeter. The desired behavior should be to go back to the LightDM greeter when logging out. This is with version 8.00+14.10.20140822-0ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1360316/+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 1336731] Re: [dash] Sticky headings when scrolling the dash should have some visible separation from the icons that slide under them.
** Changed in: ubuntu-ux Assignee: Estibaliz Landa Torres (estilanda) = (unassigned) ** Changed in: ubuntu-ux Assignee: (unassigned) = James Mulholland (jamesjosephmulholland) -- 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/1336731 Title: [dash] Sticky headings when scrolling the dash should have some visible separation from the icons that slide under them. Status in Ubuntu UI Toolkit: Invalid Status in Ubuntu UX bugs: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Fix Released Bug description: Sticky headings when scrolling the dash should have some visible separation from the icons that slide under them. When scrolling the dash you see sticky headings like Recent and My apps. This is great but there's no visible delineation between the heading background that icons are sliding under and the icons themselves. They just appear and disappear. I think we need a better visual cue for what's happening. Like making the heading transparent so you can see the icons slide under. Or perhaps a simple drop shadow across the edge the icons go under. # system-image-cli -i current build number: 106 device name: mako channel: devel alias: ubuntu-touch/utopic last update: 2014-07-02 10:17:01 version version: 106 version ubuntu: 20140701 version device: 20140625 # dpkg -l | grep unity8 ii unity8 7.89+14.10.20140627-0ubuntu1 armhf Unity 8 shell ii unity8-common 7.89+14.10.20140627-0ubuntu1 all Unity 8 shell (common files) ii unity8-private:armhf 7.89+14.10.20140627-0ubuntu1 armhf Unity 8 private libs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1336731/+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 1392187] Re: the Log out and Shut down menu show the same Log-Out dialog
Marking the unity8-desktop-session task as Invalid since the fix is in unity8 itself. ** Changed in: unity8-desktop-session (Ubuntu) Status: Triaged = Invalid -- 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/1392187 Title: the Log out and Shut down menu show the same Log-Out dialog Status in unity8 package in Ubuntu: In Progress Status in unity8-desktop-session package in Ubuntu: Invalid Bug description: the Log out and Shut down menu show the same Log-Out dialog, and when confirmed to log out or shut down, they all just go back to greeter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1392187/+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 1417714] Re: package apport 2.14.7-0ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: apport (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1417714 Title: package apport 2.14.7-0ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in apport package in Ubuntu: Confirmed Bug description: This is related to bug 1385817 ProblemType: Package DistroRelease: Ubuntu 14.10 Package: apport 2.14.7-0ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 Date: Tue Feb 3 13:21:29 2015 DuplicateSignature: package:apport:2.14.7-0ubuntu8.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-12-30 (400 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20131219) PackageArchitecture: all SourcePackage: apport Title: package apport 2.14.7-0ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1417714/+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 1365020] Re: option subject-match not working
tried again with network-manager 0.9.8.8-0ubuntu28 problem still exists. the subject-match line is read by network-manager but has no effect at all. If i created a wpa_suplicant configuration instead the string is verified and the connection will not be established with the wrong string.So i can confirm wpa_supplicant working properly but network-manager is still broken somehow. -- 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/1365020 Title: option subject-match not working Status in network-manager package in Ubuntu: Incomplete Bug description: NetworkManager supports checking the radius certificates used within 802.1X Infrastructures. These Options are subject-match and phase2-subject-match. However is these options are set the are read by networkmanager at connection activation, but is silently ignored. Even if the String supplied by this option is known wrong the connection can be established. This is a bis isues within wide spread WPA2-Infrastructures like eduroam where SSID on the network is well known. This issue exist in pakage Network-manager 0.9.8.8-0ubuntu7 (amd64) In other distributions like Debian 7.6 (network-mamanger 0.9.4.0-10) the option is working well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1365020/+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 1425484] Re: wizard aborts and goes directly to the dash
** Changed in: unity8 (Ubuntu) Assignee: (unassigned) = Michael Terry (mterry) ** Changed in: unity8 (Ubuntu) Status: Confirmed = 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/1425484 Title: wizard aborts and goes directly to the dash Status in unity8 package in Ubuntu: Triaged Bug description: TEST CASE: 1. Go to system-settings and do a factory reset 2. After reboot in the wizard, dismiss the first SIM PIN dialog 3. Select 'French' in the list of languages 4. Tap on 'Continue' EXPECT RESULT The step 'device security' is displayed ACTUAL RESULT A blank screen is displayed (empty page with the default background) and after a few seconds the wizard stops and the dash loads. The edge intro is skipped. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity8 8.02+15.04.20150224-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Wed Feb 25 11:41:16 2015 InstallationDate: Installed on 2015-02-25 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1425484/+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 1422879] Re: GPS stays active after location data is used by a scope (even after not not using the scopes anymore)
Testing the build from silo 3 confirms that the GPS active / inactive signal is being sent to the location service 5 seconds after the screen turns off. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1422879 Title: GPS stays active after location data is used by a scope (even after not not using the scopes anymore) Status in the base for Ubuntu mobile products: In Progress Status in location-service package in Ubuntu: New Status in unity8 package in Ubuntu: New Status in unity-scopes-api package in Ubuntu RTM: In Progress Status in unity8 package in Ubuntu RTM: New Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 237 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-02-17 17:04:34 version version: 237 version ubuntu: 20150217 version device: 20150216-fe747ac version custom: 20150207-538-29-183 You can easily see if the GPS is active or not by checking the logcat output (running as root). In this case the hardware remains on (consumed by the location-service) after opening a scope such as the weather channel one, and retrieving location. To reproduce: 1 - Reboot the phone; 2 - Open logcat as root: sudo /system/bin/logcat 3 - From today's scope, click on the weather icon (opening the weather channel scopes) 4 - See that the GPS is active and location works as expected 5 - Move away from that scope, and check logcat's output (it will stay active, meaning that the location-service is still active). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1422879/+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 1153671] Re: Port to python3-launchpadlib
Another blocker: bug 1425575 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1153671 Title: Port to python3-launchpadlib Status in apport package in Ubuntu: In Progress Status in python-launchpadlib package in Ubuntu: Fix Released Bug description: Apport-cli depends on python3-launchpadlib for some actions, but it is not installable (currently). For example, apport-cli -u 542452 ERROR: The launchpadlib Python module is not installed. This functionality is not available. The current candidates for installation on raring only include python- launchpadlib (which is python2 based). I believe this bug is relevant: https://bugs.launchpad.net/launchpadlib/+bug/1060734 I'm filing this against apport in the event raring is shipped without a python3-launchpadlib package. I would recommend updating the error to make what is needing to be installed more clear. IE, ERROR: The launchpadlib Python3 module is not installed (python3-launchpadlib). This functionality is not available. Also consider adding the library as a suggested dependency. In addition, should the package not land, further steps may be required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1153671/+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 1425578] [NEW] Window title sometimes gets rendered underneath controls
Public bug reported: If it's relevant I have all LIM settings at default (enabled, show on mouse over). When changing workspaces, the controls of a maximised unfocused window sometimes get rendered behind the controls of that window. 1. Maximise a window (I use firefox) 2. Focus another window on the same workspace. 3. Switch workspaces, wait for the title to change, switch back. 4. The window title is behind the controls See attached screenshot ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150219.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Feb 25 16:20:55 2015 InstallationDate: Installed on 2012-10-07 (870 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2013-05-07 (659 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages vivid -- 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/1425578 Title: Window title sometimes gets rendered underneath controls Status in unity package in Ubuntu: New Bug description: If it's relevant I have all LIM settings at default (enabled, show on mouse over). When changing workspaces, the controls of a maximised unfocused window sometimes get rendered behind the controls of that window. 1. Maximise a window (I use firefox) 2. Focus another window on the same workspace. 3. Switch workspaces, wait for the title to change, switch back. 4. The window title is behind the controls See attached screenshot ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150219.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Feb 25 16:20:55 2015 InstallationDate: Installed on 2012-10-07 (870 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2013-05-07 (659 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1425578/+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 1425580] Re: Smaller toogle switch in Vivid makes it difficult to control
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Confirmed -- 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/1425580 Title: Smaller toogle switch in Vivid makes it difficult to control Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Vivid comes with a smaller toogle switch, that make it more difficult to control, at least with my fingers. current build number: 122 device name: krillin channel: ubuntu-touch/devel-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1425580/+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 1425580] [NEW] Smaller toogle switch in Vivid makes it difficult to control
Public bug reported: Vivid comes with a smaller toogle switch, that make it more difficult to control, at least with my fingers. current build number: 122 device name: krillin channel: ubuntu-touch/devel-proposed ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: qa-promotion -- 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/1425580 Title: Smaller toogle switch in Vivid makes it difficult to control Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Vivid comes with a smaller toogle switch, that make it more difficult to control, at least with my fingers. current build number: 122 device name: krillin channel: ubuntu-touch/devel-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1425580/+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 1421060] Re: Boost log uses all inodes if file system is full
good to know, can track it here for vivid as well ** Changed in: canonical-devices-system-image Milestone: None = ww11-2015 ** Changed in: canonical-devices-system-image Status: New = In Progress -- 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/1421060 Title: Boost log uses all inodes if file system is full Status in the base for Ubuntu mobile products: In Progress Status in unity-scopes-api package in Ubuntu: In Progress Bug description: boost::log, if file rotation happens while the file system is full, creates hundreds of empty log files per log directory, eventually consuming all available inodes. But reported here: https://svn.boost.org/trac/boost/ticket/11016 We need to track this. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421060/+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 1419829] Re: [Scope] location settings are enabled by default
** Summary changed: - Scope location settings are enabled by default + [Scope] location settings are enabled by default ** Tags added: usability -- 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/1419829 Title: [Scope] location settings are enabled by default Status in the base for Ubuntu mobile products: New Status in Ubuntu UX bugs: New Status in unity-scopes-shell package in Ubuntu: New Bug description: This is in contrast to the rest of the system where user have to explicitly grant access right upfront. Possible solution would be to add a new page in phone setup wizard asking for whether scopes are allowed to use location or not and then applying this to individual scope location settings. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419829/+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 1421718] Re: Ubuntu Phone Store: No message when no applications found
** Tags added: usability ** Summary changed: - Ubuntu Phone Store: No message when no applications found + [Ubuntu Phone Store] No message when no applications found -- 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/1421718 Title: [Ubuntu Phone Store] No message when no applications found Status in the base for Ubuntu mobile products: New Status in Ubuntu UX bugs: New Status in unity-scope-click package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Hi! Steps: 1. Open Store. 2. Search RRS (Not RSS). 3. Bug: Nothing found, but you can't see a message for this. 4. Search RSS. 5. OK: You see 5 applications found message. Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421718/+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 1413290] Re: Handling large numbers of favourited scopes
** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags added: usability ** Summary changed: - Handling large numbers of favourited scopes + [scopes] Handling large numbers of favourited scopes -- 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/1413290 Title: [scopes] Handling large numbers of favourited scopes Status in Ubuntu UX bugs: New Status in unity8 package in Ubuntu: New Bug description: Version: ubuntu-touch/ubuntu-rtm/14.09-proposed r202 krillin Currently there does not appear to be a limit to the number of scopes that can be favourited. Apart from consuming phone resources, this causes the pagination dots at the top to exceed the width of one scope page (see attachments). Should we limit the number of favourited scopes? Display the pagination dots differently? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1413290/+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 991997] Re: Wrong comment in /etc/default/halt: Default behavior of halt changed to halt only instead of powering off
I think the current behavior is correctly, but the comment in /etc/default/halt sould be updated. Currently, this file is only used by /sbin/shutdown (or by the /etc/init.d/halt, that can be called by the /sbin/shutdown depending of the situation). Updating the comment may avoid user misunderstands. In Trusty, this file is packaged in the initscripts package: http://packages.ubuntu.com/trusty/amd64/initscripts/filelist The default file should be: # Default behaviour of shutdown -h. Set to halt or poweroff. HALT=poweroff I'm attaching a patch to the current initscripts package. ** Patch added: bug_halt_outdated_docs.patch https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/991997/+attachment/4327304/+files/bug_halt_outdated_docs.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/991997 Title: Wrong comment in /etc/default/halt: Default behavior of halt changed to halt only instead of powering off Status in sysvinit package in Ubuntu: Confirmed Status in upstart package in Ubuntu: Invalid Bug description: Hi, I just installed 12.04 and running sudo halt only halts the system instead of powering it off. This worked fine on 10.04 - running halt by itself powered off the machine and it looks like it is still configured to poweroff the box in /etc/default/halt in Precise but that doesn't happen. Is this the intended behavior? If so, is it documented somewhere? I saw a comment here: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/880240/comments/4 That said that halt no longer powers off the system, but I have been unable to find any documention explaining the change. Thanks, Charles ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: upstart 1.5-0ubuntu5 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: rr26xx ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Mon Apr 30 07:48:35 2012 InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Release amd64 (20120424.1) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/991997/+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 987027] Re: command halt does not turn off computer
*** This bug is a duplicate of bug 991997 *** https://bugs.launchpad.net/bugs/991997 ** This bug is no longer a duplicate of bug 880240 system doesn't turn off if sudo halt is given ** This bug has been marked a duplicate of bug 991997 Wrong comment in /etc/default/halt: Default behavior of halt changed to halt only instead of powering off -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/987027 Title: command halt does not turn off computer Status in upstart package in Ubuntu: Confirmed Bug description: command halt does not turn off computer. This command correctly close all linux comand, sessions etc...but does not turn off computer. Thanks for your help. LGDN ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: upstart 1.5-0ubuntu5 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic i686 ApportVersion: 2.0.1-0ubuntu5 Architecture: i386 Date: Sun Apr 22 23:58:37 2012 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110302) SourcePackage: upstart UpgradeStatus: Upgraded to precise on 2012-02-02 (79 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/987027/+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 1416048] Re: Expected to be able to pause a video by tapping on anywhere of the video
** Changed in: ubuntu-ux Status: New = Triaged ** Changed in: ubuntu-ux Importance: Undecided = Medium ** Summary changed: - Expected to be able to pause a video by tapping on anywhere of the video + [media player] Expected to be able to pause a video by tapping on anywhere of the video -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediaplayer-app in Ubuntu. https://bugs.launchpad.net/bugs/1416048 Title: [media player] Expected to be able to pause a video by tapping on anywhere of the video Status in Media Player App: Confirmed Status in Ubuntu UX bugs: Triaged Status in mediaplayer-app package in Ubuntu: New Bug description: Tapping anywhere on the video that is playing should pause it and vice versa. To manage notifications about this bug go to: https://bugs.launchpad.net/mediaplayer-app/+bug/1416048/+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 1425618] [NEW] Window larger than screen
Public bug reported: Sorry if my english isn't understood (I'm from Uruguay). On some computers, if I maximize a window, its size is larger than screen (video: https://www.youtube.com/watch?v=NX10vYe-J_U). A workaround is to change the monitor resolution/frequency after system starts, but if lightdm is restarted it returns. The problem appears after update lightdm (1.2.3-0ubuntu2.5). With previous version (1.2.1-0ubuntu1) error doesn't happen. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.3-0ubuntu2.5 ProcVersionSignature: Ubuntu 3.2.0-77.112-generic 3.2.66 Uname: Linux 3.2.0-77-generic i686 ApportVersion: 2.0.1-0ubuntu17.8 Architecture: i386 Date: Wed Feb 25 15:26:53 2015 InstallationMedia: Lubuntu 12.04 Precise Pangolin - Release i386 (20120423) MarkForUpload: True ProcEnviron: LANGUAGE=es_UY:es TERM=xterm PATH=(custom, no user) LANG=es_UY.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: i386 larger lightdm precise screen size window -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1425618 Title: Window larger than screen Status in lightdm package in Ubuntu: New Bug description: Sorry if my english isn't understood (I'm from Uruguay). On some computers, if I maximize a window, its size is larger than screen (video: https://www.youtube.com/watch?v=NX10vYe-J_U). A workaround is to change the monitor resolution/frequency after system starts, but if lightdm is restarted it returns. The problem appears after update lightdm (1.2.3-0ubuntu2.5). With previous version (1.2.1-0ubuntu1) error doesn't happen. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.3-0ubuntu2.5 ProcVersionSignature: Ubuntu 3.2.0-77.112-generic 3.2.66 Uname: Linux 3.2.0-77-generic i686 ApportVersion: 2.0.1-0ubuntu17.8 Architecture: i386 Date: Wed Feb 25 15:26:53 2015 InstallationMedia: Lubuntu 12.04 Precise Pangolin - Release i386 (20120423) MarkForUpload: True ProcEnviron: LANGUAGE=es_UY:es TERM=xterm PATH=(custom, no user) LANG=es_UY.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1425618/+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 1425578] Re: Window title sometimes gets rendered underneath controls
** Attachment added: controls.png https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1425578/+attachment/4327267/+files/controls.png -- 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/1425578 Title: Window title sometimes gets rendered underneath controls Status in unity package in Ubuntu: New Bug description: If it's relevant I have all LIM settings at default (enabled, show on mouse over). When changing workspaces, the controls of a maximised unfocused window sometimes get rendered behind the controls of that window. 1. Maximise a window (I use firefox) 2. Focus another window on the same workspace. 3. Switch workspaces, wait for the title to change, switch back. 4. The window title is behind the controls See attached screenshot ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150219.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Feb 25 16:20:55 2015 InstallationDate: Installed on 2012-10-07 (870 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2013-05-07 (659 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1425578/+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 1425523] Re: Cannot connect to device with MTP
** Changed in: mtp (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1425523 Title: Cannot connect to device with MTP Status in mtp package in Ubuntu: Confirmed Bug description: From an Ubuntu Vivid host, the device is not visible over MTP. Disconnecting/reconnecting the cable doesn't change anything. I can connect to the device over adb. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: mtp-server 0.0.4+15.04.20150219-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Wed Feb 25 14:16:52 2015 InstallationDate: Installed on 2015-02-25 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: mtp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1425523/+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 1228567] Re: at-spi2 daemon error messages in .xsession-errors
Present in 14.04LTS. Not solveable by chown user:user .Xauthority to active user, as some googling suggests. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1228567 Title: at-spi2 daemon error messages in .xsession-errors Status in at-spi2-core package in Ubuntu: Confirmed Bug description: Sometimes I get the following messages in .xsession-errors init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd respawning too fast, stopped I use a Lenovo Thinkpad Twist convertible with touch screen, using Onboard in tablet mode. Can perhaps have a relation with bug 1227173. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1228567/+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 1356950] Re: [messaging-app] missing visual hints when switching SIMs in thread
** Changed in: ubuntu-ux Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1356950 Title: [messaging-app] missing visual hints when switching SIMs in thread Status in Messaging App: Fix Released Status in Ubuntu UX bugs: Fix Released Status in messaging-app package in Ubuntu: Fix Released Status in history-service package in Ubuntu RTM: Fix Released Status in messaging-app package in Ubuntu RTM: Fix Released Bug description: If using a dual SIM device, it is possible to switch between the two SIMs in one thread. If user selects an other SIM from the header sub-section, a visual hint/indication should be visible in the actual messaging thread. Please refer to the attached image. To manage notifications about this bug go to: https://bugs.launchpad.net/messaging-app/+bug/1356950/+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 1424966] Re: /usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service:5:reset_timer:unity::indicator::datetime::LiveClock::Impl::on_timerfd_cond:g_main_dispatch
consider for ota crash fix ** Changed in: canonical-devices-system-image Milestone: None = ww13-ota -- 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/1424966 Title: /usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime- service:5:reset_timer:unity::indicator::datetime::LiveClock::Impl::on_timerfd_cond:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate Status in the base for Ubuntu mobile products: New Status in indicator-datetime package in Ubuntu: In Progress Bug description: It happened randomly but several time on RTM/krillin. According to errors.u.c it started with 13.10.0+15.04.20150213.1-0ubuntu1 on vivid and 13.10.0+15.04.20150213~rtm-0ubuntu1 on RTM. [ Charles Kerr ] * change the WallClock to detect time changes from TFD_TIMER_CANCEL_ON_SET, e.g. when ntp--manual is toggled The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-datetime. This problem was most recently seen with version 13.10.0+15.04.20150213.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/3b8aefe51ab8eae0b64a89605ae01d5433da3000 contains more details. current build number: 242 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-02-23 08:07:23 version version: 242 version ubuntu: 20150223 version device: 20150216-fe747ac version custom: 20150216-561-29-186 Trace: https://errors.ubuntu.com/bucket/?id=/usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service%3A5%3Areset_timer%3Aunity%3A%3Aindicator%3A%3Adatetime%3A%3ALiveClock%3A%3AImpl%3A%3Aon_timerfd_cond%3Ag_main_dispatch%3Ag_main_context_dispatch%3Ag_main_context_iterate To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1424966/+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 1339778] Re: Plugging in Logitech H340 USB headset breaks mouse click behaviour
Sorry, I am not going to take a few hours out of my workday to test this issue, especially when coupled with the chance of bricking my machine with a live dev-release of the OS. However, on a brighter note, the issue seems resolved for me with Ubuntu 14.04.2 using the 3.13.0-45-generic kernel. I discovered that the headset worked normally sometime this month. I am unsure when. -- 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/1339778 Title: Plugging in Logitech H340 USB headset breaks mouse click behaviour Status in xorg package in Ubuntu: Incomplete Bug description: Ubuntu: 14.04 LTS xorg: 1:7.7+1ubuntu8 Expected: Mouse behaviour should be unaffected when a USB headset is plugged in. What happened instead: When a Logitech H340 USB headset is plugged in the mouse stops behaving correctly. The primary button appears to be down all the time. Programs fail to respond to clicks from the mouse (so the window-focus cannot be changed). The tracking of X-Y coordinates seems to be fine. (The information reported by ubuntu-bug xorg was collected with the headset plugged in.) I tested this behaviour with Firefox, GNOME Terminal, and Nautilus as the primary window. In the case of Nautilus the icon under the mouse cursor is selected, and moves with the mouse cursor. In the case of the other two programs text is selected when the mouse moves. I see the same behaviour when the mouse (a Logitec also) is unplugged and the inbuilt trackpad is used to move the mouse cursor. For completeness I unplugged the mouse and keyboard, so the headset was the only device connected to the external USB ports and I saw the same behaviour, with the primary button appearing to be down. This problem appears to be similar to the issue reported with the Logitech G930 headset. However, the H340 is a comparatively simple headset as it is wired and lacks any volume buttons, nor does it have a mute. https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1155819 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom] CompositorRunning: None CurrentDesktop: GNOME Date: Wed Jul 9 08:41:54 2014 DistUpgraded: 2014-07-06 17:47:29,838 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.11.0-24-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1657] Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6730M/6770M/7690M XT] [1002:6740] (rev ff) (prog-if ff) InstallationDate: Installed on 2011-08-15 (1059 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=1a802fd8-d29f-436f-9a48-75d174a47c13 ro acpi_osi=Linux quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-07-07 (2 days ago) dmi.bios.date: 10/05/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1B dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1657 dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.31 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1B:bd10/05/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr05951024471020100:rvnHewlett-Packard:rn1657:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 05951024471020100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati:
[Touch-packages] [Bug 1188569] Re: Some keyboard shortcuts randomly stop working
A workaround is to either open a terminal or Alt+F2 and issue the command 'unity' . This fixes the shortcuts by restarting unity, but all applications keep running, wihout login/out. You may want to try to run this command on resume|thaw in /usr/lib/pm- utils, since the keyboards (for me) seem to get lost on docking/undocking and related resumes; but I'm still testing, so i don't now if this is a robust (automatic) workaround. -- 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/1188569 Title: Some keyboard shortcuts randomly stop working Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Hi, Certain shortcuts randomly stops working in my computer. They are Super+s (workspace switcher), Super+Up (switch to workspace above) and Super+Down (switch to workspace below). Other shortcuts work fine. A few notes that might help: 1- Reassigning shortcuts make them work again except for Super+s. 2- Rebooting make shortcuts work. 3- I have been using these shortcuts with many previous ubuntu versions and my preferences are old. 4- I am not sure of certain steps that produces the problem. The shortcuts sometimes stop working but once they stop, they do not work unless I reassign them or reboot. I am using Ubuntu 13.04. Thank you ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,regex,grid,mousepoll,place,wall,snap,resize,vpswitch,session,animation,gnomecompat,imgpng,commands,move,workarounds,fade,unitymtgrabhandles,expo,scale,ezoom,unityshell] Date: Fri Jun 7 13:40:06 2013 InstallationDate: Installed on 2013-05-27 (11 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1188569/+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 1425598] Re: No expired certificate dialog
Not seeing that. I’m getting the expired certificate warning as expected. Do note that if you previously discarded the warning for the given domain, your choice will be remembered for the duration of the session, so you won’t see the warning again. But if you close the browser and open it again, you will see the warning page again. ** Changed in: webbrowser-app (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1425598 Title: No expired certificate dialog Status in webbrowser-app package in Ubuntu: Incomplete Bug description: image 122 vivid-proposed Navigate to a site with expired certificates like: https://testssl- expire.disig.sk/ You should see a an error that certificates are expired or something. It rather opens the site without any warning. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: webbrowser-app 0.23+15.04.20150217.1-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Wed Feb 25 16:54:04 2015 InstallationDate: Installed on 2015-02-25 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1425598/+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 1416157] Re: [osk] emoji menu should toggle in both directions
** Summary changed: - emoji menu should toggle in both directions + [osk] emoji menu should toggle in both directions ** Changed in: ubuntu-ux Assignee: (unassigned) = Jouni Helminen (jounihelminen) ** Changed in: ubuntu-ux Status: New = Fix Released ** Changed in: ubuntu-ux Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1416157 Title: [osk] emoji menu should toggle in both directions Status in the base for Ubuntu mobile products: Fix Released Status in Ubuntu Keyboard: Fix Released Status in Ubuntu UX bugs: Fix Released Status in ubuntu-keyboard package in Ubuntu: Fix Released Status in ubuntu-keyboard package in Ubuntu RTM: Fix Released Bug description: If the emoji keyboard is installed (we are adding it as a default), we should automatically toggle between the emoji layout and the previous layout when tapping on the globe menu. Currently we only toggle out of the emoji layout back to the default layout when pressing the globe but don't toggle back to the emoji layout when clicking from the default layout. This makes it very tedious if you are typing a message and switching between layouts as you always have to press the globe, and then press Emoji from the menu. Currently single tap displays the menu with the settings, etc, but I think it would be better to only do this on a long press. It is how iOS works Steps to reproduce: - enable emoji keyboard if not on (in system settings) - launch messaging app - start typing a message - click the globe Expected results: - switch to emoji layout immediately Actual results: - menu displayed, have to pick Emoji layout - start typing emojis - click the globe again - we are correctly switched back to the previous layout - type some more - now click the globe again for more emojis menu displayed, have to pick Emoji layout from there. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1416157/+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 1425625] Re: Vivid image 121: Gps tag is permanently turn off on krillin when the custom tarball is installed
not sure how this will function for real as we don't currently have a way to test on a full image. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1425625 Title: Vivid image 121: Gps tag is permanently turn off on krillin when the custom tarball is installed Status in indicator-location package in Ubuntu: New Bug description: STEPS: 1. Install image 121 and install the krillin custom tarball 2. Boot the device and use the recommend here location check box in the location page 3. Drag down the location indicator 4. Enable gps 5. drag down the indicator 6. enable gps a second time 7. reboot the device once gps stays on 8. check the locations indicator again EXPECTED: I expect to see happen what happens on rtm ACTUAL: Gps is turned off on reboot, and doesn't function when enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1425625/+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 1153671] Re: Port to python3-launchpadlib
Next blocker: bug 1425627 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1153671 Title: Port to python3-launchpadlib Status in apport package in Ubuntu: In Progress Status in python-launchpadlib package in Ubuntu: Fix Released Bug description: Apport-cli depends on python3-launchpadlib for some actions, but it is not installable (currently). For example, apport-cli -u 542452 ERROR: The launchpadlib Python module is not installed. This functionality is not available. The current candidates for installation on raring only include python- launchpadlib (which is python2 based). I believe this bug is relevant: https://bugs.launchpad.net/launchpadlib/+bug/1060734 I'm filing this against apport in the event raring is shipped without a python3-launchpadlib package. I would recommend updating the error to make what is needing to be installed more clear. IE, ERROR: The launchpadlib Python3 module is not installed (python3-launchpadlib). This functionality is not available. Also consider adding the library as a suggested dependency. In addition, should the package not land, further steps may be required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1153671/+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
