[Bug 1351305] Re: [Toshiba Portege Z35-AST3N01] Touchpad / Trackpoint recognised as generic mouse
Summary: This is fixed in kernel 3.17-rc1. Detail: Researching this for my daughter (Ruth Marsden) I've found this issue has been known on the kernel mailing lists for sometime. See http://www.spinics.net/lists/linux-input/msg29123.html. The issue relates to touchpad devices using the ALPS v7 protocol. These devices are reported in this post to have device info as follows: Device ID = 0x73, 0x03, 0x0a Firmware ID = 0x88, 0xb*, 0x** Which includes my daughter's Toshiba Z35 which has this Device ID and Firmware ID = 0x88, 0xb3, 0x22 A kernel patch has been in production over the last few weeks. See http://www.spinics.net/lists/linux-input/msg32703.html and related posts. This patch was added on 9th August and can be found in the Ubuntu kernel daily builds from then and the weekly build at http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc1-utopic/ . To install this see the Installing upstream kernels section of https://wiki.ubuntu.com/Kernel/MainlineBuilds . We've tested the 3.17-rc1 kernel on my daughter's Toshiba Z35 laptop and can confirm that both touchpad and trackpoint devices work. They are recognised as an AlpsPS/2 ALPS DualPoint TouchPad and the touchpad section now appears in System Settings Mouse Touchpad. In particular disabling while typing is available and works. Presumably a kernel with this patch will be released in Ubuntu in due course. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1351305 Title: [Toshiba Portege Z35-AST3N01] Touchpad / Trackpoint recognised as generic mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1351305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1338063] Re: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed
Workround provided from upstream dialogue - Thank you Aaron. See http://marc.info/?l=linux-acpim=140686098023199w=2 In summary: Switching to use the intel-backlight interface rather than the acpi_video0 interface makes the controls for brightness work after suspend. This can be done by creating, or adding to, the file /etc/X11/xorg.conf with the section below: Section Device Identifier Intel Graphics Driver intel Option AccelMethod sna Option Backlight intel_backlight Driver intel BusID PCI:0:2:0 EndSection -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338063 Title: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1338063] Re: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed
Reported upstream. See http://marc.info/?l=linux- acpim=140658075422146w=2. As requested from upstream am attaching output from acpidump as acpidump.txt ** Attachment added: acpidump.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+attachment/4165307/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338063 Title: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1338063] Re: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed
Christopher, Thank you for your guidance on this issue. I want to make sure I report this upstream in the correct way and am unsure of which upstream list I should be using. https://wiki.ubuntu.com/DebuggingKernelSuspend mentions says Suspend and Resume use facilities within your BIOS called ACPI. Should I therefore report to the linux-a...@vger.kernel.org list? Or should I use the linux...@vger.kernel.org list which is mentioned in the SUSPEND TO RAM section of http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS ? Or, since the bug refers to a Toshiba laptop should I use the platform-driver-...@vger.kernel.org list which is mentioned in the TOSHIBA ACPI EXTRAS DRIVER section? Or something else? I appreciate your help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338063 Title: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1338063] Re: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed
I have tested against the kernel at http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.16-rc5-utopic/ and can confirm that the bug as reported still persists. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Tags removed: kernel-bug-exists-upstream-3.16-rc4 ** Tags added: kernel-bug-exists-upstream-3.16-rc5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338063 Title: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1338063] Re: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed
In answer to: if you remove the kernel parameter elevator=noop does this change anything? No it does not change anything. I tried with this kernel parameter removed on the latest mainline upstream kernel 3.16-rc4. As requested, tested on Precise 12.04.0 and 12.04.3 both obtained from http://old-releases.ubuntu.com/releases/12.04.0/. Used Live CD method. In both cases the bug as originally reported occurred. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338063 Title: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1338063] Re: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed
In answer to did this problem not occur in a release prior to Trusty?: I'm sorry, I don't know for sure. I only noticed the problem the day I first reported it, however my behaviour regarding shutdowns rather than suspends has recently changed so that may well be why I noticed it. My wife hadn't noticed it on her computer (see mention in comment #6) until I specifically tested for it. However in comment #9 above I report testing and getting the same result with kernel version 3.8.0-31 which must date from when I had Raring running on my computer. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338063 Title: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1338063] Re: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed
As requested I followed the steps in https://wiki.ubuntu.com/DebuggingKernelSuspend. Results are: 1. Information from sticker on computer: Manufacurer: Toshiba Model: Protege Z835-ST6N03 Part No: PT224U-01W00C 2. Bios is already upgraded to latest version 1.80. 3. Booted in mianline upstream kernel 3.16-rc4. Suspended with pm-trace and awakened successfully. cat /proc/acpi/wakeup wakeup result is attached. 4. Resume trace result: a) Resume succeeded, though LCD brightness controls fail as originally reported. b) Result of: dmesg mesg.txt will be attached. c) Searched dmesg.txt for Magic number and got: . [0.864274] Magic number: 6:405:689 [0.864395] rtc_cmos 00:05: setting system clock to 2014-07-09 15:41:36 UTC (1404920496) . d) Searched dmesg.txt for hash match and got no lines matching search. e) Not sure whether brightness controls failing counts as graphics related issue. So will attach Xorg.0.log and Xorg.0.log.old just in case. ** Attachment added: wakeup https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+attachment/4148944/+files/wakeup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338063 Title: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1338063] Re: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed
** Attachment added: Xorg.0.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+attachment/4148946/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338063 Title: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1338063] Re: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed
** Attachment added: dmesg.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+attachment/4148945/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338063 Title: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1338063] Re: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed
** Attachment added: Xorg.0.log.old https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+attachment/4148947/+files/Xorg.0.log.old ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338063 Title: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1338063] Re: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed
Installed latest upstream mainline kernel: 3.16.0-031600rc4-generic Unfortunately this failed to solve the problem. Brightness control on systems settings and via function keys works on initial boot but ceases to work after a suspend, as before. Thank you for your help. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-3.16.0-031600rc4-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338063 Title: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1338063] Re: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed
Clarification: I have gone back to older kernels on my machine to confirm my feeling that this only started happening recently. The oldest kernel on my machine is 3.8.0-31-generic. The problem also occurs with when booted with this kernel so my feeling that this was recent is wrong. I have edited the original bug report to remove my assertion that it had seemed to have only started recently. ** Description changed: Using Ubuntu 14.04. Recently updated to kernel version Ubuntu 3.13.0-30.54-generic 3.13.11.2 I expect brightness of my LCD screen to remain the same and be controllable after waking from suspend. It doesn't and isn't. - - This seems to have only started recently - presumably after a recent - update. What happens: Brightness controls fully working after initial boot, both through function keys and system settings. After putting computer into suspend and then re-awakening the LCD screen comes up with lowest brightness in actual appearance but settings still show the brightness as set at suspend time. Controls for brightness have become ineffective - they slide the brightness bar along but make no difference to the actual brightness of the screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.54 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: john 2060 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: john 2060 F pulseaudio CurrentDesktop: Unity Date: Sat Jul 5 18:55:05 2014 InstallationDate: Installed on 2012-06-04 (760 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: TOSHIBA PORTEGE Z835 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=865f4d37-5ceb-4e4a-b59b-032fa8a2c80b ro quiet splash elevator=noop vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.13.0-30-generic N/A - linux-backports-modules-3.13.0-30-generic N/A - linux-firmware 1.127.4 + linux-restricted-modules-3.13.0-30-generic N/A + linux-backports-modules-3.13.0-30-generic N/A + linux-firmware 1.127.4 RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (68 days ago) dmi.bios.date: 02/08/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.60 dmi.board.asset.tag: 00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.60:bd02/08/2012:svnTOSHIBA:pnPORTEGEZ835:pvrPT224U-01W00C:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z835 dmi.product.version: PT224U-01W00C dmi.sys.vendor: TOSHIBA -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338063 Title: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1338063] Re: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed
Christopher, thank you for your advice and my apologies for not following the protocol of first checking for BIOS updates. I have now updated the BIOS. Results of sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date are: Version 1.80 04/18/2013 so the update has worked. Unfortunately the problem still persists as previously described. Please note the problem also manifests on my wife's Toshiba Protege Z835-ST8305 which I have also updated to the latest BIOS. Her computer is also running Ubuntu 14.04 with kernel version Ubuntu 3.13.0-30.55-generic 3.13.11.2 Thank you for your help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338063 Title: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1338063] Re: Brightness control lost after suspend screen dimmed
Upgrade to Ubuntu 3.13.0-30.55-generic 3.13.11.2 does not solve the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338063 Title: Brightness control lost after suspend screen dimmed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1338063] [NEW] Brightness control lost after suspend screen dimmed
Public bug reported: Using Ubuntu 14.04. Recently updated to kernel version Ubuntu 3.13.0-30.54-generic 3.13.11.2 I expect brightness of my LCD screen to remain the same and be controllable after waking from suspend. It doesn't and isn't. This seems to have only started recently - presumably after a recent update. What happens: Brightness controls fully working after initial boot, both through function keys and system settings. After putting computer into suspend and then re-awakening the LCD screen comes up with lowest brightness in actual appearance but settings still show the brightness as set at suspend time. Controls for brightness have become ineffective - they slide the brightness bar along but make no difference to the actual brightness of the screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.54 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 2060 F pulseaudio CurrentDesktop: Unity Date: Sat Jul 5 18:55:05 2014 InstallationDate: Installed on 2012-06-04 (760 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: TOSHIBA PORTEGE Z835 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=865f4d37-5ceb-4e4a-b59b-032fa8a2c80b ro quiet splash elevator=noop vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (68 days ago) dmi.bios.date: 02/08/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.60 dmi.board.asset.tag: 00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.60:bd02/08/2012:svnTOSHIBA:pnPORTEGEZ835:pvrPT224U-01W00C:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z835 dmi.product.version: PT224U-01W00C dmi.sys.vendor: TOSHIBA ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: lspci-vnvn.log https://bugs.launchpad.net/bugs/1338063/+attachment/4146124/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338063 Title: Brightness control lost after suspend screen dimmed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1338063] Re: Brightness control lost after suspend screen dimmed
Clarification: Screen does not always come up dimmed after suspend. Screen comes up with setting prior to suspend. If the computer has gone into suspend itself after being unused for a certain amount of time it comes up dimmed, even if not deliberately set to this by the user. In these circumstances the computer has dimmed the screen some time prior to going into suspend. In all cases controls no longer function after suspend as reported in initial post. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338063 Title: Brightness control lost after suspend screen dimmed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1085169] Re: LibreOffice Menus Stop Working even with libreoffice=1:3.6.2~rc2-0ubuntu4 and indicator-appmenu=12.10.3-0ubuntu2.1
** Changed in: libreoffice (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085169 Title: LibreOffice Menus Stop Working even with libreoffice=1:3.6.2~rc2-0ubuntu4 and indicator- appmenu=12.10.3-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1085169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1085169] Re: LibreOffice Menus Stop Working even with libreoffice=1:3.6.2~rc2-0ubuntu4 and indicator-appmenu=12.10.3-0ubuntu2.1
This bug is also affecting me and my wife. Running on amd64 laptop with no special video drivers. Confirm I am have amd64 versions of libreoffice-core 1:3.6.2~rc2-0ubuntu4 and indicator-appmenu 12.10.3-0ubuntu2.1 installed. It happens on both my and my wife's computers (same amd64 software configuration but I have full Libreoffice metapackage while she has just standard install from quantal upgrade). How to reproduce the bug: Use Libre Office Writer for some variable time ranging from a very few minutes upwards. Work using mouse to select a menu item from the menu bar (on the top line in the indicator menu area). Suddenly, for no apparent reason, the menu items stop functioning. Libreoffice can still be controlled using the icons but actions for which no item exists cannot be performed. The HUD display, despite showing a picture of Libreoffice writer to the left, also stops working. It does not give any Libreoffice actions in response to typing. It offers only items from the indicator panel, e.g. Skype, Dropbox Network. If a second Libreoffice document is opened it does not display the bug. Work-round: Close and re-open the file. Today my wife worked for about five hours on LibreOffice writer and had the problem five times. I worked a similar period of time and today didn't have it at all, though did yesterday. If there is any tracking software we could run to help track down what is triggering this please let us know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085169 Title: LibreOffice Menus Stop Working even with libreoffice=1:3.6.2~rc2-0ubuntu4 and indicator- appmenu=12.10.3-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1085169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1085169] Re: LibreOffice Menus Stop Working even with libreoffice=1:3.6.2~rc2-0ubuntu4 and indicator-appmenu=12.10.3-0ubuntu2.1
I spoke to soon. Got back in this evening and did another half-hour's work tonight and it happened twice on my computer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085169 Title: LibreOffice Menus Stop Working even with libreoffice=1:3.6.2~rc2-0ubuntu4 and indicator- appmenu=12.10.3-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1085169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 739184] Re: [Libreoffice] Mnemonics do not work in Unity
Still happening for me after the upgrade released to fix bug #1064962 https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1064962. Using a 64-bit system upgraded from Precise to Quantal with all latest updates installed. Please release a fix soon as without it all the fancy work to make a HUD is fruitless for the type of work where being able to stick with the keyboard is most useful - i.e. office applications. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/739184 Title: [Libreoffice] Mnemonics do not work in Unity To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/739184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064962] Re: [SRU] Global menubar items do not work when opening a document directly from nautilus with no LibreOffice instance running
Any plans to fix the failed amd-64 build in ppa:bjoern-michaelsen /libreoffice-quantaltest-2012060 so we can help to test it in a 64-bit environment? Or does the Fix Commited and references to SRU mean that we are going to see it in the quantal-updates any day now for 64-bit as well as 32-bit? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064962 Title: [SRU] Global menubar items do not work when opening a document directly from nautilus with no LibreOffice instance running To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1064962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 796245] [NEW] Weather Data for Dhaka, Bangladesh not updating regularly
Public bug reported: The METAR weather feed for Dhaka has been VGZR. However this feed has not been reliably transmitting data recently. (see http://weather.gladstonefamily.net/site/VGZR). Therefore up to date weather data has not been showing in the desktop panel applet. There is a more recent weather feed at VGHS which is at Dhaka Airport (see http://weather.gladstonefamily.net/site/VGHS) and uses the new name for the airport (i.e. Hazrat Shajahal Intl Airport not Zia Intl Airport). As a work-around I have updated the code used by the applet using gconf, but this update will be lost whenever the information is refreshed from /usr/share/libgweather/Locations.xml. I believe you should add an entry for VGHS in the Locations.xml file and make this the default for Dhaka. I am still using Ubuntu 10.04.2 LTS with libgweather 2.30.0-0ubuntu1 but I have inspected the Locations file in revision 47 in the Oneiric branch and it also only has VGZR, not VGHS for Dhaka. I am also emailing the maintainer of the weather stations list at http://www.rap.ucar.edu/weather/surface/stations.txt to make the same point as this is impact many sites delivering weather information from METAR data. ** Affects: libgweather (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/796245 Title: Weather Data for Dhaka, Bangladesh not updating regularly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/796245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 296863] Re: If too many timezone are configured, lower ones are cut off the screen with no way to see them
This bug is particularly annoying for users of netbooks and the Ubuntu Netbook Edition. My 600 pixel deep screen cuts off the fourth location listed which is very irritating as I work with people in many countries round the world and often travel across timezones. Although I am a newbie, if i knew how, I'd put my hand to fixing it myself as this seems to have been stuck in the wishlist for more than two years over in gnome-bugs. Ubuntu Desktop Experience team - can you push this along please? Ubuntu 10.4 Clock 2.30.2 -- If too many timezone are configured, lower ones are cut off the screen with no way to see them https://bugs.launchpad.net/bugs/296863 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 296863] Re: If too many timezone are configured, lower ones are cut off the screen with no way to see them
oops, I meant to ask the Canonical Desktop Experience Team if they could push this along. -- If too many timezone are configured, lower ones are cut off the screen with no way to see them https://bugs.launchpad.net/bugs/296863 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 496616] Re: Mediaplayer crashed with pa_stream_writable_size() failed: Connection terminated
Removing gstream0.10-pulseaudio resolves the problem for me on a Toshiba NB200 with: j...@jdm-nb:~$ uname -a Linux JDM-NB 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:27:30 UTC 2010 i686 GNU/Linux Totem Movie Player 2.30.2 using GStreamer 0.10.28 and (after removal of gstream0.10-pulseaudio): j...@jdm-nb:~$ dpkg -l | egrep -e 'alsa|pulse' ii alsa-base 1.0.22.1+dfsg-0ubuntu3 ALSA driver configuration files ii alsa-utils 1.0.22-0ubuntu5 ALSA utilities ii bluez-alsa 4.60-0ubuntu8 Bluetooth audio support ii gstreamer0.10-alsa 0.10.28-1 GStreamer plugin for ALSA ii libcanberra-pulse 0.22-1ubuntu2 PulseAudio backend for libcanberra ii libesd-alsa0 0.2.41-6ubuntu1 Enlightened Sound Daemon (ALSA) - transition ii libpulse-browse0 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14 PulseAudio client libraries (zeroconf suppor ii libpulse-mainloop-glib0 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14 PulseAudio client libraries (glib support) ii libpulse0 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14 PulseAudio client libraries rc libsdl1.2debian-alsa 1.2.13-4ubuntu4 Simple DirectMedia Layer (with X11 and ALSA ii libsdl1.2debian-pulseaudio 1.2.14-4ubuntu1 Simple DirectMedia Layer (with X11 and Pulse ii pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14 PulseAudio sound server ii pulseaudio-esound-compat 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14 PulseAudio ESD compatibility layer ii pulseaudio-module-bluetooth 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14 Bluetooth module for PulseAudio sound server ii pulseaudio-module-gconf 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14 GConf module for PulseAudio sound server ii pulseaudio-module-x11 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14 X11 module for PulseAudio sound server ii pulseaudio-utils 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14 Command line tools for the PulseAudio sound -- Mediaplayer crashed with pa_stream_writable_size() failed: Connection terminated https://bugs.launchpad.net/bugs/496616 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577353] Re: System can not find root device with kernel 2.6.32-22
** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- System can not find root device with kernel 2.6.32-22 https://bugs.launchpad.net/bugs/577353 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577353] Re: System can not find root device with kernel 2.6.32-22
I am experiencing this bug on my wife's Toshiba NB200 netbook, but it is not occuring on my identical hardware. Software environments on the two machines are also almost identical: - Both started with Karmic UNR as dual boot retaining, but hardly ever using, the supplied Windows7 starter edition. - Both machines were regularly updated automatically through Update Manager, usually within twelve hours of each other. - Both upgraded to Lucid by normal upgrade procedure driven by Update Manager over a slow internet connection. - Both updated from kernel 2.6.32.21 to 2.6.32.22 Main differences are that my machine has more software packages added, and my wife has a greater propensity to solve user problems by switching off the power and re-booting! See original report in comment #28 in bug #360378. Note that simply choosing to load 2.6.32.21 from Grub was not enough to solve the problem. I had to manually copy in an alternative initrd.img file as explained in comment #28 in bug #360378. I'm still a newbie in Ubuntu so if you would like logs and configuration files posted, or upstream packages tested, please give me step by step advice or point me to an appropriate how to page. -- System can not find root device with kernel 2.6.32-22 https://bugs.launchpad.net/bugs/577353 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577353] Re: System can not find root device with kernel 2.6.32-22
Correction to comment #3 above. The cross reference to bug #360378 should be to comment #27. -- System can not find root device with kernel 2.6.32-22 https://bugs.launchpad.net/bugs/577353 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 360378] Re: Gave up waiting for root device after upgrade then busybox console
I had the same problem on my wife's Netbook (Toshiba NB200) after upgrading from Ubuntu Netbook Remix 9.10 to Lucid using the standard upgrade procedure. I tried the extending the rootdelay altering the Grub instructions to look for /dev/sdax instead of the UUID but neither worked. However after downloading a Lucid Ubuntu Netbook Edition .iso image and booting from a USB drive Rick Silva's suggestion at comment #26 above worked. I copied initrd.img-2.6.32-21-generic from the RAM disk once I'd booted off the USB drive. I can now boot from 2.6.32.21 on my hard drive. HOWEVER I cannot boot from 2.6.32.22-generic which was installed a few days ago by the Update Manager. Using synaptic to remove 2.6.32.22-generic and re-install it does not solve the problem. The initrd.img I copied from the USB boot is about 12.9 Mb but the initrd.img files on my hard disk are about 7.6 Mb. What is the underlying problem here? Is there something else about my upgrade to Lucid which is resulting in initrd.img files being damaged, or incorrectly constructed? How might I diagnose what is going on? I'm not expert in Linux boot time processes, but I'm happy to do my bit to diagnose the underlying issue. I'd like to see this fixed properly so Ubuntu genuinely can be used by ordinary humans, like my wife, not just people who roam technical websites. -- Gave up waiting for root device after upgrade then busybox console https://bugs.launchpad.net/bugs/360378 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
