[Bug 1914858] Re: autoamtically suspend right after login - when booted with Thinkpad lid closed
** Description changed: - Reproduce: - 0. Make sure the laptop is being charged by external power. + 0. Make sure the laptop is being charged by an external power. + 1. Boot with the lid closed (e.g. by starting reboot and close the lid). + 2. When login screen presents, then login with password - 3. Ubuntu 20.10 goes to sleep. Hit a key to wake it. dmesg attached at the end. - 3 used to be reliably reproducible but now is sometimes reproducible. - the dmesg was collected when this bug happened. + 3a. Ubuntu 20.10 goes to sleep. Hit a key to wake it. dmesg attached at + the end. + + 3b. Ubuntu 20.04 sometimes go to sleep (10%). + + The following dmesg is collected from Ubuntu 20.10 where this can be reliably reproduced. However since I can't solve this I had to + downgrade to Ubuntu 20.04 where the attached debug info (produced + by `ubuntu-bug linux`) is collected. Notes: - - The laptop ThinkPad-X1-Carbon-6th is upgraded from 20.04. - - The "Energy" setting in gnome-control-center is set to suspend only in battery mode. + - The "Energy" setting in gnome-control-center is set to suspend only in + battery mode, but the bug is reproduced with external power. -- [ 76.499494] PM: suspend entry (s2idle) [ 76.536273] Filesystems sync: 0.036 seconds [ 76.544283] Freezing user space processes ... (elapsed 0.004 seconds) done. [ 76.548306] OOM killer disabled. [ 76.548307] Freezing remaining freezable tasks ... (elapsed 0.048 seconds) done. [ 76.597228] printk: Suspending console(s) (use no_console_suspend to debug) [ 76.717831] e1000e: EEE TX LPI TIMER: 0011 [ 79.349561] usb usb3: root hub lost power or was reset [ 79.349565] usb usb4: root hub lost power or was reset [ 79.480262] ACPI: EC: interrupt blocked [ 81.656861] ACPI: EC: interrupt unblocked [ 84.645047] usb usb3: root hub lost power or was reset [ 84.645052] usb usb4: root hub lost power or was reset [ 87.491291] e1000e :00:1f.6 enp0s31f6: Failed to disable ULP [ 87.603196] OOM killer enabled. [ 87.603198] Restarting tasks ... [ 87.603397] pci_bus :07: Allocating resources [ 87.603425] pci_bus :3b: Allocating resources [ 87.616426] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) [ 87.620031] done. [ 87.631119] thermal thermal_zone5: failed to read out thermal zone (-61) [ 87.775462] PM: suspend exit [ 87.906564] e1000e :00:1f.6 enp0s31f6: NIC Link is Down [ 88.108092] iwlwifi :02:00.0: Applying debug destination EXTERNAL_DRAM [ 88.241926] iwlwifi :02:00.0: Applying debug destination EXTERNAL_DRAM [ 88.309721] iwlwifi :02:00.0: FW already configured (0) - re-configuring [ 90.965280] e1000e :00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 90.965334] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s31f6: link becomes ready. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: a 2194 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: a 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 6 21:48:20 2021 MachineType: LENOVO 20KHS1BP00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=a77757cf-4a1b-4a8b-964a-bea19ccac95a ro nouveau.modeset=0 RelatedPackageVersions: - linux-restricted-modules-5.4.0-42-generic N/A - linux-backports-modules-5.4.0-42-generic N/A - linux-firmware1.187.9 + linux-restricted-modules-5.4.0-42-generic N/A + linux-backports-modules-5.4.0-42-generic N/A + linux-firmware1.187.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET71W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1BP00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KHS1BP00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1BP00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1BP00 dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO -- You received this bug notification
[Bug 1905127] Re: autoamtically suspend right after login - when booted with Thinkpad lid closed
*** This bug is a duplicate of bug 1914858 *** https://bugs.launchpad.net/bugs/1914858 ** This bug has been marked a duplicate of bug 1914858 autoamtically suspend right after login - when booted with Thinkpad lid closed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905127 Title: autoamtically suspend right after login - when booted with Thinkpad lid closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1905127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914858] [NEW] autoamtically suspend right after login - when booted with Thinkpad lid closed
Public bug reported: Reproduce: 0. Make sure the laptop is being charged by external power. 1. Boot with the lid closed (e.g. by starting reboot and close the lid). 2. When login screen presents, then login with password 3. Ubuntu 20.10 goes to sleep. Hit a key to wake it. dmesg attached at the end. 3 used to be reliably reproducible but now is sometimes reproducible. the dmesg was collected when this bug happened. Notes: - The laptop ThinkPad-X1-Carbon-6th is upgraded from 20.04. - The "Energy" setting in gnome-control-center is set to suspend only in battery mode. -- [ 76.499494] PM: suspend entry (s2idle) [ 76.536273] Filesystems sync: 0.036 seconds [ 76.544283] Freezing user space processes ... (elapsed 0.004 seconds) done. [ 76.548306] OOM killer disabled. [ 76.548307] Freezing remaining freezable tasks ... (elapsed 0.048 seconds) done. [ 76.597228] printk: Suspending console(s) (use no_console_suspend to debug) [ 76.717831] e1000e: EEE TX LPI TIMER: 0011 [ 79.349561] usb usb3: root hub lost power or was reset [ 79.349565] usb usb4: root hub lost power or was reset [ 79.480262] ACPI: EC: interrupt blocked [ 81.656861] ACPI: EC: interrupt unblocked [ 84.645047] usb usb3: root hub lost power or was reset [ 84.645052] usb usb4: root hub lost power or was reset [ 87.491291] e1000e :00:1f.6 enp0s31f6: Failed to disable ULP [ 87.603196] OOM killer enabled. [ 87.603198] Restarting tasks ... [ 87.603397] pci_bus :07: Allocating resources [ 87.603425] pci_bus :3b: Allocating resources [ 87.616426] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) [ 87.620031] done. [ 87.631119] thermal thermal_zone5: failed to read out thermal zone (-61) [ 87.775462] PM: suspend exit [ 87.906564] e1000e :00:1f.6 enp0s31f6: NIC Link is Down [ 88.108092] iwlwifi :02:00.0: Applying debug destination EXTERNAL_DRAM [ 88.241926] iwlwifi :02:00.0: Applying debug destination EXTERNAL_DRAM [ 88.309721] iwlwifi :02:00.0: FW already configured (0) - re-configuring [ 90.965280] e1000e :00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 90.965334] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s31f6: link becomes ready. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 6 21:48:20 2021 MachineType: LENOVO 20KHS1BP00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=a77757cf-4a1b-4a8b-964a-bea19ccac95a ro nouveau.modeset=0 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET71W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1BP00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KHS1BP00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1BP00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1BP00 dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914858 Title: autoamtically suspend right after login - when booted with Thinkpad lid closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905127] Re: autoamtically suspend right after login - when booted with Thinkpad lid closed
ran the given command, authorised in the browser, got a popup message: "No additional information collected" have a look at the issue itself, there is a good chance the engineer can see this problem without much additional information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905127 Title: autoamtically suspend right after login - when booted with Thinkpad lid closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1905127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905127] Re: autoamtically suspend right after login - when booted with Thinkpad lid closed
Kernel: $ uname -a Linux thinkpad 5.8.0-29-generic #31-Ubuntu SMP Fri Nov 6 12:37:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux adding HandleLidSwitch=ignore to /etc/systemd/logind.conf makes this problem disappear, however, it is not desirable that the laptop ignore lid closing. It simply should not trigger lid closing if it was closed before Ubuntu starts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905127 Title: autoamtically suspend right after login - when booted with Thinkpad lid closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1905127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905127] [NEW] autoamtically suspend right after login - when booted with Thinkpad lid closed
Public bug reported: Reproduce: 0. Make sure the laptop is being charged by external power. 1. Boot with lid closed (e.g. by starting reboot and close the lid). 2. When login screen presents, login with password 3. Ubuntu 20.10 goes to sleep. Hit a key to wake it. dmesg attached at the end. Notes: - The laptop ThinkPad-X1-Carbon-6th is upgraded from 20.04. - The "Energe" setting in gnome-control-center is set to suspend only in battery mode. -- [ 76.499494] PM: suspend entry (s2idle) [ 76.536273] Filesystems sync: 0.036 seconds [ 76.544283] Freezing user space processes ... (elapsed 0.004 seconds) done. [ 76.548306] OOM killer disabled. [ 76.548307] Freezing remaining freezable tasks ... (elapsed 0.048 seconds) done. [ 76.597228] printk: Suspending console(s) (use no_console_suspend to debug) [ 76.717831] e1000e: EEE TX LPI TIMER: 0011 [ 79.349561] usb usb3: root hub lost power or was reset [ 79.349565] usb usb4: root hub lost power or was reset [ 79.480262] ACPI: EC: interrupt blocked [ 81.656861] ACPI: EC: interrupt unblocked [ 84.645047] usb usb3: root hub lost power or was reset [ 84.645052] usb usb4: root hub lost power or was reset [ 87.491291] e1000e :00:1f.6 enp0s31f6: Failed to disable ULP [ 87.603196] OOM killer enabled. [ 87.603198] Restarting tasks ... [ 87.603397] pci_bus :07: Allocating resources [ 87.603425] pci_bus :3b: Allocating resources [ 87.616426] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) [ 87.620031] done. [ 87.631119] thermal thermal_zone5: failed to read out thermal zone (-61) [ 87.775462] PM: suspend exit [ 87.906564] e1000e :00:1f.6 enp0s31f6: NIC Link is Down [ 88.108092] iwlwifi :02:00.0: Applying debug destination EXTERNAL_DRAM [ 88.241926] iwlwifi :02:00.0: Applying debug destination EXTERNAL_DRAM [ 88.309721] iwlwifi :02:00.0: FW already configured (0) - re-configuring [ 90.965280] e1000e :00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 90.965334] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s31f6: link becomes ready. ** Affects: 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/1905127 Title: autoamtically suspend right after login - when booted with Thinkpad lid closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1905127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904975] [NEW] project URL in package description wrong
Public bug reported: Currently: $ apt-cache show ayatana-indicator-datetime | grep github Homepage: https://github.com/ArcticaProject/ayatana-indicator-datetime Should be: https://github.com/AyatanaIndicators/ayatana-indicator-datetime ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ayatana-indicator-datetime (not installed) ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 20 16:51:30 2020 SourcePackage: ayatana-indicator-datetime UpgradeStatus: Upgraded to groovy on 2020-11-16 (4 days ago) ** Affects: ayatana-indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904975 Title: project URL in package description wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-datetime/+bug/1904975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904553] [NEW] cash thanks to dependency missing
Public bug reported: The error can be solved by installing the following packages: $ sudo apt-get install ruby-addressable ruby-diva ruby-memoist ruby- delayer ruby-delayer-deferred ruby-pluggaloid Steps to reproduce the bug: $ apt-get install mikutter $ mikutter Traceback (most recent call last): 26: from /usr/share/mikutter/mikutter.rb:56:in `' 25: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in `require' 24: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in `require' 23: from /usr/share/mikutter/core/boot/load_plugin.rb:10:in `' 22: from /usr/share/mikutter/core/miquire_plugin.rb:98:in `load_all' 21: from /usr/share/mikutter/core/miquire_plugin.rb:38:in `each_spec' 20: from /usr/share/mikutter/core/miquire_plugin.rb:35:in `each' 19: from /usr/share/mikutter/core/miquire_plugin.rb:35:in `each' 18: from /usr/share/mikutter/core/miquire_plugin.rb:40:in `block in each_spec' 17: from /usr/share/mikutter/core/miquire_plugin.rb:99:in `block in load_all' 16: from /usr/share/mikutter/core/miquire_plugin.rb:149:in `load' 15: from /usr/share/mikutter/core/utils.rb:288:in `atomic' 14: from /usr/share/mikutter/core/utils.rb:288:in `synchronize' 13: from /usr/share/mikutter/core/utils.rb:288:in `block in atomic' 12: from /usr/share/mikutter/core/miquire_plugin.rb:150:in `block in load' 11: from /usr/share/mikutter/core/miquire_plugin.rb:150:in `each' 10: from /usr/share/mikutter/core/miquire_plugin.rb:151:in `block (2 levels) in load' 9: from /usr/share/mikutter/core/miquire_plugin.rb:149:in `load' 8: from /usr/share/mikutter/core/utils.rb:288:in `atomic' 7: from /usr/share/mikutter/core/utils.rb:288:in `synchronize' 6: from /usr/share/mikutter/core/utils.rb:288:in `block in atomic' 5: from /usr/share/mikutter/core/miquire_plugin.rb:159:in `block in load' 4: from /usr/share/mikutter/core/miquire_plugin.rb:159:in `load' 3: from /usr/share/mikutter/plugin/gui/gui.rb:16:in `' 2: from /usr/lib/ruby/vendor_ruby/pluggaloid/plugin.rb:36:in `create' 1: from /usr/lib/ruby/vendor_ruby/pluggaloid/plugin.rb:36:in `instance_eval' /usr/share/mikutter/plugin/gui/gui.rb:18:in `block in ': uninitialized constant Pluggaloid::STREAM (NameError) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: mikutter 4.0.6+dfsg1-1 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 17 22:14:16 2020 PackageArchitecture: all SourcePackage: mikutter UpgradeStatus: Upgraded to groovy on 2020-11-16 (1 days ago) ** Affects: mikutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904553 Title: cash thanks to dependency missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mikutter/+bug/1904553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861289] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323836/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861289] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323841/+files/WifiSyslog.txt ** 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/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861289] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323837/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861289] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323835/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861289] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323839/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861289] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323834/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861289] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323833/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861289] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323832/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861289] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323838/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861289] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323840/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861289] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323831/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861289] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323829/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861289] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323828/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861289] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323830/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861289] Re: No virtual terminals and NAutoVTs=6 setting ineffective
apport information ** Tags added: apport-collected eoan ** Description changed: This is not the same bug as #1758512 - that bug is about an unresponsive key combination, this bug is reproducible without pressing any key- combination. Reproduce: Using Ubuntu 19.10. Manually modified /etc/systemd/logind.conf by uncommenting this: [Login] NAutoVTs=6 ReserveVT=6 According to man logind.conf this would result 6 virtual terminals spawned. Bug behaviour: Reboot and run $ sudo fgconsole --next-available 3 Expected: Given I've configured 6 auto virtual terminals this number should be higher than 6. Bug behaviour Reboot and run: $ sudo chvt 3 Got a screen with a black background and a single blinking cursor at upper left corner Expected: Seeing a login prompt + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: weiwu 1703 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2019-06-11 (232 days ago) + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + MachineType: LENOVO 20KHS1BP00 + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b9df6bda-4eaa-4420-9573-12ab02da707d ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-26-generic N/A + linux-backports-modules-5.3.0-26-generic N/A + linux-firmware1.183.3 + Tags: eoan + Uname: Linux 5.3.0-26-generic x86_64 + UpgradeStatus: Upgraded to eoan on 2019-11-15 (75 days ago) + UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare staff sudo + _MarkForUpload: True + dmi.bios.date: 06/25/2018 + dmi.bios.vendor: LENOVO + dmi.bios.version: N23ET50W (1.25 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20KHS1BP00 + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40697 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrN23ET50W(1.25):bd06/25/2018:svnLENOVO:pn20KHS1BP00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1BP00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad X1 Carbon 6th + dmi.product.name: 20KHS1BP00 + dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th + dmi.product.version: ThinkPad X1 Carbon 6th + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323827/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861289] [NEW] No virtual terminals and NAutoVTs=6 setting ineffective
Public bug reported: This is not the same bug as #1758512 - that bug is about an unresponsive key combination, this bug is reproducible without pressing any key- combination. Reproduce: Using Ubuntu 19.10. Manually modified /etc/systemd/logind.conf by uncommenting this: [Login] NAutoVTs=6 ReserveVT=6 According to man logind.conf this would result 6 virtual terminals spawned. Bug behaviour: Reboot and run $ sudo fgconsole --next-available 3 Expected: Given I've configured 6 auto virtual terminals this number should be higher than 6. Bug behaviour Reboot and run: $ sudo chvt 3 Got a screen with a black background and a single blinking cursor at upper left corner Expected: Seeing a login prompt ** Affects: linux (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/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797747] [NEW] none of the fonts in xfonts-100dpi-transcoded is available to fc
Public bug reported: Reproduce. 1. Make sure bitmap fonts are allowed e.g. by deleting /etc/fonts/conf.d/70-no-bitmaps.conf 2. Install xfonts-100dpi-transcoded 3. Search for Lucida font - there is none: $ fc-list | grep Lucida --- Solution: install xfonts-100dpi instead of xfonts-100dpi-transcoded. -- Suggested action: If xfonts-100dpi-transcoded has no effect by itself, shouldn't it be marked as depending on xfonts-100dpi? ** Affects: xfonts-100dpi (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/1797747 Title: none of the fonts in xfonts-100dpi-transcoded is available to fc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfonts-100dpi/+bug/1797747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790034] [NEW] el-get installed but doesn't provide el-get-install emacs command
Public bug reported: 1. $ sudo apt-get install el-get 2. $ emacs 3. Use meta-x then type el-get. get "No Match". This is tested on Ubuntu 16.04 LTS and 18.04 LTS, while in 16.04 TLS the command to call emacs is 'emacs24' and 18.04 is 'emacs25' Also, `meta-x el-get-install` is tried with the same error. P.S. It's possible that this because the user needs to do some configuration not mentioned in the package-description in order to use el-get after installing. If it is the case, this issue was created on the ground that such configurations are unexpected and breaks the ubuntu install-and-use paradigm. ** Affects: el-get (Ubuntu) Importance: Undecided Status: New ** Description changed: 1. $ sudo apt-get install el-get 2. $ emacs 3. Use meta-x then type el-get. get "No Match". This is tested on Ubuntu 16.04 LTS and 18.04 LTS, while in 16.04 TLS the command to call emacs is 'emacs24' and 18.04 is 'emacs25' Also, `meta-x el-get-install` is tried with the same error. + + P.S. I anticipated that this is because the user needs to do some + configuration in order to use el-get. The bug was issued on the ground + that such configurations are unexpected and breaks the ubuntu install- + and-use paradigm. ** Description changed: 1. $ sudo apt-get install el-get 2. $ emacs 3. Use meta-x then type el-get. get "No Match". This is tested on Ubuntu 16.04 LTS and 18.04 LTS, while in 16.04 TLS the command to call emacs is 'emacs24' and 18.04 is 'emacs25' Also, `meta-x el-get-install` is tried with the same error. - P.S. I anticipated that this is because the user needs to do some - configuration in order to use el-get. The bug was issued on the ground - that such configurations are unexpected and breaks the ubuntu install- - and-use paradigm. + P.S. It's possible that this because the user needs to do some + configuration not mentioned in the package-description in order to use + el-get after installing. The bug was issued on the ground that such + configurations are unexpected and breaks the ubuntu install-and-use + paradigm. ** Description changed: 1. $ sudo apt-get install el-get 2. $ emacs 3. Use meta-x then type el-get. get "No Match". This is tested on Ubuntu 16.04 LTS and 18.04 LTS, while in 16.04 TLS the command to call emacs is 'emacs24' and 18.04 is 'emacs25' Also, `meta-x el-get-install` is tried with the same error. P.S. It's possible that this because the user needs to do some configuration not mentioned in the package-description in order to use - el-get after installing. The bug was issued on the ground that such - configurations are unexpected and breaks the ubuntu install-and-use - paradigm. + el-get after installing. If it is the case, this issue was created on + the ground that such configurations are unexpected and breaks the ubuntu + install-and-use paradigm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790034 Title: el-get installed but doesn't provide el-get-install emacs command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/el-get/+bug/1790034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747324] [NEW] default url-viewer not suitable for Linux
Public bug reported: Default url-viewer value is 'open _URL_' In Linux, open(1) is the command for "start a program on a new virtual terminal", not for opening a web browser. The reason that this configuration still worked, is because it didn't at all. url-viewer requires the full path, therefore, 'open _URL_', missing the leading '/bin/', triggers an internal exception which makes alpine fall back to the default browser - probably /usr/bin/x-www-browser. I suggest to change default url-viewer value to '/usr/bin/xdg-open _URL_' for the Ubuntu package thanks to Ubuntu shipping xdg-utils. ** Affects: alpine (Ubuntu) Importance: Undecided Status: New ** Description changed: Default url-viewer value is 'open _URL_' In Linux, open(1) is the command for "start a program on a new virtual terminal", not for opening a web browser. The reason that this configuration still worked, is because it didn't at - all. url-viewer requires the full path, therefore, 'open _URL_', instead - of '/bin/open _URL_' triggers an internal exception and makes alpine - fall back to the default browser (probably /usr/bin/x-www-browser) + all. url-viewer requires the full path, therefore, 'open _URL_', missing + the leading '/bin/', triggers an internal exception which makes alpine + fall back to the default browser - probably /usr/bin/x-www-browser. The sensible action to do here is to use '/usr/bin/xdg-open' which is shipped in Ubuntu to open the default browser configured in unity- control-center. - - I suggest to change default url-viewer value to '/usr/bin/xdg-open _URL_' for the Ubuntu package. + I suggest to change default url-viewer value to '/usr/bin/xdg-open + _URL_' for the Ubuntu package. ** Description changed: Default url-viewer value is 'open _URL_' In Linux, open(1) is the command for "start a program on a new virtual terminal", not for opening a web browser. The reason that this configuration still worked, is because it didn't at all. url-viewer requires the full path, therefore, 'open _URL_', missing the leading '/bin/', triggers an internal exception which makes alpine fall back to the default browser - probably /usr/bin/x-www-browser. - The sensible action to do here is to use '/usr/bin/xdg-open' which is - shipped in Ubuntu to open the default browser configured in unity- - control-center. - I suggest to change default url-viewer value to '/usr/bin/xdg-open _URL_' for the Ubuntu package. ** Description changed: Default url-viewer value is 'open _URL_' In Linux, open(1) is the command for "start a program on a new virtual terminal", not for opening a web browser. The reason that this configuration still worked, is because it didn't at all. url-viewer requires the full path, therefore, 'open _URL_', missing the leading '/bin/', triggers an internal exception which makes alpine fall back to the default browser - probably /usr/bin/x-www-browser. I suggest to change default url-viewer value to '/usr/bin/xdg-open - _URL_' for the Ubuntu package. + _URL_' for the Ubuntu package thanks to Ubuntu shipping xdg-utils. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747324 Title: default url-viewer not suitable for Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alpine/+bug/1747324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453538] Re: Invisible mouse pointer
Interesting, qkiz. This is what I experimented 1. Edit /etc/default/grub Change the line – GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash” to GRUB_CMDLINE_LINUX_DEFAULT="" 2. update grub sudo update-grub2 3. reboot. What I got: 1) plymouth seems to be disabled, there is no purple splash. In fact, the screen never go purple, it: 2) screen display black when lightdm started, black, with only a white movable mouse pointer. 3) Here I can type my password blindly, then the normal desktop shows up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453538 Title: Invisible mouse pointer To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1453538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453538] Re: Invisible mouse pointer
Pavlo Shchelokovskyy (pshchelo) wrote on 2015-08-12: > FWIW solution proposed here worked for me > gsettings set org.gnome.settings-daemon.plugins.cursor active false If it works for you, you probably had a different bug. This bug's effect start since the login screen, and as far as I know gsettings only affects the current login user. In order to be sure, I configured my lightdm to auto-login. I intend to check if gsettings can make the pointer show up, now that culprit (login screen) is skipped. It resulted something very weird. - Cursor would show up on the left side if I move it to the rightmost position. If I move leftward a bit, it would slip off from left edge of the screen. I could not click one of the unity tool bar icons because the cursor can go to at most left edge only, and not a little more right. - Desktop wallpaper is not showing up. Desktop is black and blank (blank means no icons) - Shortcut keys has no response. Super key doesn't call up HUD, and Ctrl+Shift+T doesn't call up terminal. Effectively in this limbo status the user has nothing to do but to restart computer again. I had to manually edit /etc/lightdm.conf to prevent auto-login again. Without autlogin, my host behaves exactly as previously described - "no pointer but click works, restart lightdm helps". By the way the desktop wall paper, HUD and desktop icons are all back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453538 Title: Invisible mouse pointer To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1453538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1326885] Re: desktop start rotated
I won't report again with latest kernel because (from my experience) I do not expect it to be solved (or that it solved because of people reporting bugs), but I still provide the following information to save the time for those who wish to find a workaround - I do not know a workaround, but I know the following would not work: The following methods would not prevent the desktop to rotate automatically after login: - delete /lib/udev/accelerometer - comment out the only line in /lib/udev/rules.d/61-accelerometer.rules Since the rotate-after-login does not alter input matrix, which is still horizental, touch-screen will be useless right after login, until you rotate the screen back (with xrandr -o randr). If, instead of preventing auto-rotate-after-login, you wish to rotate input matrix as well to make the machine at least usable, the following command would not work: $ xinput set-prop 9 --type=float Coordinate Transformation Matrix 0 -1 1 1 0 0 0 0 1 The effect of that command is zero: input matrix remain the same (horizental) while the screen is auto-rotated to vertical. If you wish to study the issue, a starting point is the accelerometer device, which can be found in /proc/bus/input/devices Find out the event device (in my case event4) then you can find out which driver drives it by: $ cat /sys/devices/platform/asus_laptop/input/input4/device/driver -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1326885 Title: desktop start rotated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1326885] Re: desktop start rotated
I noticed this bug is marked as kernel-bug-exists-upstream -- I do not think this is a kernel bug, because everything was fine before login, a kernel bug should exhabit before login. Also that it only affects after- login, not affecting screen rotation during the session. But I am no expert to remove that tag with confidence. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1326885 Title: desktop start rotated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1326885] [NEW] desktop start rotated
Public bug reported: Running Ubuntu 14.04 on bModo12 (same hardware as WeTab). Right after login the screen rotates to rightwards (no matter what direction the screen is actually at). I had to run this everytime: $ xrandr -o normal Note this is not gravity sensor at work. If gravity sensor is at work, and turned screen leftwards or rightwards, 'xrandr -o normal' will not have any effect. Expected behaviour: the desktop rotation is decided by gravity sensor, or, without its input, defaults to normal. ** Affects: linux (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/1326885 Title: desktop start rotated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322396] Re: light sensor misjudge ambience light
Can anyone provide a workaround first? For example how to prevent light sensor from working at all, disable the module or kernel feature that uses it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322396 Title: light sensor misjudge ambience light To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1326885] Re: desktop start rotated
apport information ** Tags added: apport-collected trusty ** Description changed: Running Ubuntu 14.04 on bModo12 (same hardware as WeTab). Right after login the screen rotates to rightwards (no matter what direction the screen is actually at). I had to run this everytime: $ xrandr -o normal Note this is not gravity sensor at work. If gravity sensor is at work, and turned screen leftwards or rightwards, 'xrandr -o normal' will not have any effect. - Expected behaviour: the desktop rotation is decided by gravity sensor, - or, without its input, defaults to normal. + Expected behaviour: the desktop rotation is decided by gravity sensor, or, without its input, defaults to normal. + --- + ApportVersion: 2.14.1-0ubuntu3.2 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.04 + InstallationDate: Installed on 2014-04-28 (38 days ago) + InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) + Package: linux (not installed) + Tags: trusty + Uname: Linux 3.15.0-031500rc5-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1326885/+attachment/4125982/+files/ProcEnviron.txt ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Description changed: Running Ubuntu 14.04 on bModo12 (same hardware as WeTab). Right after login the screen rotates to rightwards (no matter what direction the screen is actually at). I had to run this everytime: $ xrandr -o normal Note this is not gravity sensor at work. If gravity sensor is at work, and turned screen leftwards or rightwards, 'xrandr -o normal' will not have any effect. - Expected behaviour: the desktop rotation is decided by gravity sensor, or, without its input, defaults to normal. - --- + Expected behaviour: the desktop rotation should be decided by gravity sensor, or, without its input, defaults to normal. If it is intended that even without gravity sensor input the desktop should rotate anyway, then it should do so since login screen, not to change orientation right after login. + --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-04-28 (38 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Package: linux (not installed) Tags: trusty Uname: Linux 3.15.0-031500rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True ** Description changed: Running Ubuntu 14.04 on bModo12 (same hardware as WeTab). Right after login the screen rotates to rightwards (no matter what direction the screen is actually at). I had to run this everytime: $ xrandr -o normal Note this is not gravity sensor at work. If gravity sensor is at work, and turned screen leftwards or rightwards, 'xrandr -o normal' will not have any effect. - Expected behaviour: the desktop rotation should be decided by gravity sensor, or, without its input, defaults to normal. If it is intended that even without gravity sensor input the desktop should rotate anyway, then it should do so since login screen, not to change orientation right after login. + Expected behaviour: the desktop rotation should be decided by gravity sensor, or, without its input, defaults to normal. If it is intended that even without gravity sensor input the desktop should rotate anyway (because it consider itself running on a tablet) then it should do so since login screen, not to change orientation right after login. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-04-28 (38 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Package: linux (not installed) Tags: trusty Uname: Linux 3.15.0-031500rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1326885 Title: desktop start rotated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1326885] Re: desktop start rotated kernel-bug-exists-upstream
I was expecting you to ask me to try development kernel - I am a sysop and I do not think this is a kernel issue, more like you automatically require trying development kernel - so, in fact when I collect data I was already using development kernel. And yes for sure I experience this problem using Ubuntu's release kernel as well. Can you add to the workflow to check whether or not the bug report already uses latest kernel, before asking for testing on latest kernel? ** Tags added: kernel-bug-exists-upstream ** 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/1326885 Title: desktop start rotated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322396] Re: light sensor misjudge ambience light
tested on 3.15.0-031500rc5-generic. The censor still misjudge ambience light, and flickers the screen when there are no noticable light change. ** Tags added: kernel-bug-exists-upstream ** 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/1322396 Title: light sensor misjudge ambience light To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322396] [NEW] light sensor misjudge ambience light
Public bug reported: Running Ubuntu 14.04 on bModo12 (same hardware as WeTab). When running on battery, the screen changes brightness frequently, by itself, while there are little change in ambience light. In fact, if I just place it stablly on the table and observe from distance, it turns bright and dark all by itself happyly, once a few seconds. It is unbearable to use. I installed brightness control applet indicator-brightness, and hoped manual control overwrites automatic ambience light sensor. But no, automatic sensor overwrites manual setting. If I set brightness to 10, for example, it is bright for one second, and back to darkness. I urgenly need a workaround - a method to turn off light sensor and force always brightest light output. Kindly offer a workaround before solving this bug. Thanks! My hardware and system is the same when I reported bug 1318639 - and the bug always exists since I installed the OS in day 1. Inform me if you insist on a new machine-generated PC/OS information set. ** Affects: linux (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/1322396 Title: light sensor misjudge ambience light To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1123943] Re: Chrontel CH7036 chip not supported
@carli I guess it is easier and more useful to push for a change from Debian side, since multiple desk distros depend on Debian. Maybe close this one and re-file it in Debian? I don't know packaging to try it myself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1123943 Title: Chrontel CH7036 chip not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1123943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1123943] Re: Chrontel CH7036 chip not supported
The procedure on http://lackofalucidmind-en.blogspot.de/2014/01/hdmi- output.html if followed strictly except git-checking out latest code, not the specified revision, works on Ubuntu 14.04 64-bit too. Verified. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1123943 Title: Chrontel CH7036 chip not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1123943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318639] [NEW] Bluetooth mouse connects but does not move pointer
Public bug reported: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackballid=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] ↳ USB 2.0 Cameraid=14 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: 1. computer boots without mouse3 device (mouse not 'oiled' by Windows) 2. user click bluetooth mouse and mouse3 device come to exist, that means mouse3 is the USB mouse 3. but it doesn't generate any data when moving, compare to a real mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1 event0 event11 event2 event5 event8 micemouse2 $ sudo -i # od /dev/input/mouse3 ^C # od /dev/input/mouse2 000 177430 034000 17 174070 034377 177364 171070 034375 020 177766 171070 034375 176765 173070 034373 176367 174470 040 034374 175367 175070 034373 175775 176470 034375 177375 060 177470 034377 17 177470 014377 000377 176470 014377 100 000771 172430 014001 000764 172030 014002 000766 173030 120 014001 001371 175030 014001 000775 177030 014001 000377 ^C The most singular thing that happened is: in one occassion, I boot into Windows 8 and use the mouse, when I reboot back, the cursor go on moving for a few minutes and mute. It seems, using it in Windows 'oils' the mouse. But I couldn't repeatly reproduce this. I am very certain about this. The cursor doesn't move even right after the first time add-new- bluetooth device wizard quit successfully, the single one time it worked, is after Windows 8 oiled it. My devices are: $ lspci 00:00.0 Host bridge: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx DMI Bridge 00:02.0 VGA compatible controller: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller 00:02.1 Display controller: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller 00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 04) 00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5
[Bug 1318639] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1318639/+attachment/4110601/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318639] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1318639/+attachment/4110607/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318639] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1318639/+attachment/4110604/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318639] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1318639/+attachment/4110600/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318639] Re: Bluetooth mouse connects but does not move pointer
apport information ** Tags added: apport-collected trusty ** Description changed: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] ↳ USB 2.0 Camera id=14 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: 1. computer boots without mouse3 device (mouse not 'oiled' by Windows) 2. user click bluetooth mouse and mouse3 device come to exist, that means mouse3 is the USB mouse 3. but it doesn't generate any data when moving, compare to a real mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1 event0 event11 event2 event5 event8 micemouse2 $ sudo -i # od /dev/input/mouse3 ^C # od /dev/input/mouse2 000 177430 034000 17 174070 034377 177364 171070 034375 020 177766 171070 034375 176765 173070 034373 176367 174470 040 034374 175367 175070 034373 175775 176470 034375 177375 060 177470 034377 17 177470 014377 000377 176470 014377 100 000771 172430 014001 000764 172030 014002 000766 173030 120 014001 001371 175030 014001 000775 177030 014001 000377 ^C The most singular thing that happened is: in one occassion, I boot into Windows 8 and use the mouse, when I reboot back, the cursor go on moving for a few minutes and mute. It seems, using it in Windows 'oils' the mouse. But I couldn't repeatly reproduce this. I am very certain about this. The cursor doesn't move even right after the first time add-new- bluetooth device wizard quit successfully, the single one time it worked, is after Windows 8 oiled it. My devices are: $ lspci 00:00.0 Host bridge: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx DMI Bridge 00:02.0 VGA compatible controller: Intel Corporation Atom Processor
[Bug 1318639] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1318639/+attachment/4110605/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318639] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1318639/+attachment/4110609/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318639] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1318639/+attachment/4110602/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318639] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1318639/+attachment/4110613/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318639] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1318639/+attachment/4110603/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318639] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1318639/+attachment/4110612/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318639] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.launchpad.net/bugs/1318639/+attachment/4110611/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318639] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1318639/+attachment/4110608/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318639] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1318639/+attachment/4110606/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318639] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1318639/+attachment/4110614/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Description changed: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] - ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] - ↳ Power Buttonid=6[slave keyboard (3)] - ↳ Video Bus id=7[slave keyboard (3)] - ↳ Power Buttonid=8[slave keyboard (3)] - ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] - ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] - ↳ USB 2.0 Camera id=14 [slave keyboard (3)] - ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] - ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] + ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] + ↳ Power Buttonid=6[slave keyboard (3)] + ↳ Video Bus id=7[slave keyboard (3)] + ↳ Power Buttonid=8[slave keyboard (3)] + ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] + ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] + ↳ USB 2.0 Camera id=14 [slave keyboard (3)] + ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] + ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: - 1. computer boots without mouse3 device (mouse not 'oiled' by Windows) - 2. user click bluetooth mouse and mouse3 device come to exist, that means mouse3 is the USB mouse - 3. but it doesn't generate any data when moving, compare to a real mouse mouse2 + 1. computer boots, /dev/inputs/mouse3 device does not exist + 2. user click bluetooth mouse and /dev/inputs/mouse3 device come to exist, that means mouse3 is the bluetooth + 3. but it doesn't generate any data when moving, compare to a real USB mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 - $ ls + $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1
[Bug 1318639] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1318639/+attachment/4110610/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318639] Re: Bluetooth mouse connects but does not move pointer
** Description changed: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] ↳ USB 2.0 Camera id=14 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: 1. computer boots, /dev/inputs/mouse3 device does not exist 2. user click bluetooth mouse and /dev/inputs/mouse3 device come to exist, that means mouse3 is the bluetooth 3. but it doesn't generate any data when moving, compare to a real USB mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1 event0 event11 event2 event5 event8 micemouse2 $ sudo -i # od /dev/input/mouse3 ^C # od /dev/input/mouse2 000 177430 034000 17 174070 034377 177364 171070 034375 020 177766 171070 034375 176765 173070 034373 176367 174470 040 034374 175367 175070 034373 175775 176470 034375 177375 060 177470 034377 17 177470 014377 000377 176470 014377 100 000771 172430 014001 000764 172030 014002 000766 173030 120 014001 001371 175030 014001 000775 177030 014001 000377 ^C The most singular thing that happened is: in one occassion, I boot into Windows 8 and use the mouse, when I reboot back, the cursor go on moving for a few minutes and mute. It seems, using it in Windows 'oils' the mouse. But I couldn't repeatly reproduce this. I am very certain about this. The cursor doesn't move even right after the first time add-new- bluetooth device wizard quit successfully, the single one time it worked, is after Windows 8 oiled it. - My devices are: - - $ lspci - 00:00.0 Host bridge: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx DMI Bridge - 00:02.0 VGA compatible controller: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller - 00:02.1
[Bug 1318639] Re: Bluetooth mouse connects but does not move pointer
** Description changed: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] ↳ USB 2.0 Camera id=14 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: 1. computer boots, /dev/inputs/mouse3 device does not exist 2. user click bluetooth mouse and /dev/inputs/mouse3 device come to exist, that means mouse3 is the bluetooth 3. but it doesn't generate any data when moving, compare to a real USB mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1 event0 event11 event2 event5 event8 micemouse2 $ sudo -i # od /dev/input/mouse3 ^C # od /dev/input/mouse2 000 177430 034000 17 174070 034377 177364 171070 034375 020 177766 171070 034375 176765 173070 034373 176367 174470 040 034374 175367 175070 034373 175775 176470 034375 177375 060 177470 034377 17 177470 014377 000377 176470 014377 100 000771 172430 014001 000764 172030 014002 000766 173030 120 014001 001371 175030 014001 000775 177030 014001 000377 ^C The most singular thing that happened is: in one occassion, I boot into Windows 8 and use the mouse, when I reboot back, the cursor go on moving for a few minutes and mute. It seems, using it in Windows 'oils' the mouse. But I couldn't repeatly reproduce this. I am very certain about this. The cursor doesn't move even right after the first time add-new- bluetooth device wizard quit successfully, the single one time it worked, is after Windows 8 oiled it. + On another behavior: power applet seems to prevent the mouse going + sleep, which it does by itself in a few minutes in Windows - until all + power drains out from the mouse, but it is a trivial problem that I can + afford not to solve. + ---
[Bug 1318639] Re: Bluetooth mouse connects but does not move pointer
With the kernel you suggested, 3.15.0-031500rc5-generic, the bluetooth applet does not show up. If I manually enable bluetooth (it started inactive) in control panel, the user interface says bluetooth inactive even though the knob is turned on - hints activation failed. The controls for adding new bluetooth devices are gray. There is of course no mouse-battery power indicator. ** Tags added: kernel-unable-to-test-upstream ** 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/1318639 Title: Bluetooth mouse connects but does not move pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1123943] Re: Chrontel CH7036 chip not supported
Did any one try to make this work on Ubuntu 14.04? On a different issue, does anyone know of a driver for Broadcom Crystal HD 1080p? VD920H it is, lspci lists: 02:00.0 Multimedia controller: Broadcom Corporation BCM70015 Video Decoder [Crystal HD] How can I take advantage of that with VLC or mplayer? I know it is off- topic, but googling 10 minutes there is no right place to discuss this issue. Maybe you can throw me a link and I´ll discuss it elsewhere. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1123943 Title: Chrontel CH7036 chip not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1123943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1235991] Re: Can't “use system keyboard layout” in Saucy
I switched from IBUS to FCITX for this reason and a few others. ibus development is slowing down significantly when FCITX is pacing up - development activity usually predicts future bug number and fix-speed. It seems we are back to the old days of 200x when each region (China, Taiwan, Japan etc) prompts their own input platform intead of their own input methods, and that the hope of a high quality input platform for all input methods is fading away. FCITX was notorious for its strong personality of insisting on using Simplified Chinese and China Mainland government's encoding instead of UTF-8 for configuration files, repelling non-Chinese users. They changed to English configuration files now, but I don't think they became international and design for other language users - the user interface has toleratable English. Normally I prefer International project over local (culture-speaking) software but in this case fcitx development is much more active. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1235991 Title: Can't “use system keyboard layout” in Saucy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1235991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1123943] Re: Chrontel CH7036 chip not supported
If I had HDMI turned off to start with, your method would not turn it on. There was no error message in the complete process following your instruction, but HDMI display shows 'no signal'. $ sudo /usr/sbin/ch7036_start /usr/sbin/ch7036_monitor: starts Found device ID 0x56 Found revision ID 0x81 Mode 1024x768 (95) 1024x768, dot clock 6500 -Hsync -Vsync H: start 1048, end 1184, skew 0, total 1344 V: start 771, end 777, total 806 Firmware size = 3295 bytes. As said, the device works on Windows 7. I down-tuned the resolution, because even on Windows 7, the max resolution offered for HDMI is 1280x720, smaller than LVDS's native resolution and CH7036's advertised max resolution (both are 1366x768). As you can see the resolution is 1024x768, that means in Linux I down- tuned it even lower than Windows 7, because in xrandr, the next resolution below 1366x768 is 1024x768. I was rather surprised when I look up the specs of WeTab and found that bModo has exactly the same configuration, including CPU type, memory, hard disk space and resolution. It really look like bModo 12 is just another casing of WeTab. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1123943 Title: Chrontel CH7036 chip not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1123943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1123943] Re: Chrontel CH7036 chip not supported
A few days ago there was a post of a different workaround: Installing the Chrontel Ch7036/HDMI - Output on Ubuntu http://lackofalucidmind-en.blogspot.de/2014/01/hdmi-output.html I tried following the instruction myself and to my surprise once the executable is launched (/usr/sbin/ch7036_start) it turns off my HDMI which was originally on (I had rebooted to Windows and had turned it on, and rebooted to Linux while it is still on). Perhaps that's because I am not using a chrome book. I used an x86-64 tablet, bModo 12, designed for Windows 7. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1123943 Title: Chrontel CH7036 chip not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1123943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261371] [NEW] ZaphodHeads configuration read but ignored
Public bug reported: Reproduce: 1. Configured ZaphodHeads to use only one output. Start X. 2. in Xorg.log it is correctly read, nevertheless it grab all outputs and display mirrored content on all of them. Expected: 1. X only uses the specified output. The other output have no graphical content. Provided the xorg.conf file to reproduce the problem and the Xorg log. Doubchecked the output name in ZaphodHeads configuration is correct. P.S. The xorg.conf also specified only one monitor being used (with Option Monitor-LVDS Monitor0 and that only one Screen is defined to use it), X nevertheless used both screens - perhaps because RandR is kept on, but ZaphodHeads should have higher priority over RandR, right? Full xorg.conf corrsponding to the attached Xorg.0.log: Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files ModulePath /usr/lib/xorg/modules FontPath /usr/share/fonts/X11/misc FontPath /usr/share/fonts/X11/cyrillic FontPath /usr/share/fonts/X11/100dpi/:unscaled FontPath /usr/share/fonts/X11/75dpi/:unscaled FontPath /usr/share/fonts/X11/Type1 FontPath /usr/share/fonts/X11/100dpi FontPath /usr/share/fonts/X11/75dpi FontPath built-ins EndSection Section Module Load glx EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/input/mice Option ZAxisMapping 4 5 6 7 EndSection Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameMonitor Model EndSection Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz, ### percent: f% ### [arg]: arg optional #Option NoAccel # [bool] #Option SWcursor # [bool] #Option EnablePageFlip# [bool] #Option ColorTiling # [bool] #Option ColorTiling2D # [bool] #Option RenderAccel # [bool] #Option SubPixelOrder # [str] #Option AccelMethod # str #Option EXAVSync # [bool] #Option EXAPixmaps# [bool] #Option ZaphodHeads # str #Option EnablePageFlip# [bool] #Option SwapbuffersWait # [bool] Identifier Card0 Driver radeon Option ZaphodHeads LVDS Option Monitor-LVDS Monitor0 BusID PCI:0:1:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 SubSection Display Viewport 0 0 Depth 1 EndSubSection SubSection Display Viewport 0 0 Depth 4 EndSubSection SubSection Display Viewport 0 0 Depth 8 EndSubSection SubSection Display Viewport 0 0 Depth 15 EndSubSection SubSection Display Viewport 0 0 Depth 16 EndSubSection SubSection Display Viewport 0 0 Depth 24 EndSubSection EndSection ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Attachment added: X.org.0.log https://bugs.launchpad.net/bugs/1261371/+attachment/3930301/+files/Xorg.0.log.old -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261371 Title: ZaphodHeads configuration read but ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1261371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1235991] Re: Can't “use system keyboard layout” in Saucy
Not only dvorak, which can mark down the priority of this bug thanks to its techy user-base: This bug also affect any European-keyboard layout users who learned to type Chinese / Japanese. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1235991 Title: Can't “use system keyboard layout” in Saucy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1235991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1243091] [NEW] system keyboad layout setting has no effect
Public bug reported: Reproduce: 1. The Ubuntu system default keyboad layout configure to Generic 105-key (Intl) PC this can be done with $ sudo dpkg-reconfigure keyboard-configuration You can verify if the setting is in effect by typing AltGr + e and you should key in 'é'. You should be able to get this behaviour even in the console (Ctrl+Alt+F1). (The Alt key right to the space bar, even if it is just labeled Alt, it is AltGr in effect) 2. run ibus-setup and check the checkbox Use System Keyboard, it is on the last tab. 3. reboot and login, and type AltGr + e, you just get plain e, not 'é' and you don't get 'é' even if you have switched away from input method (typically by tapping left shift key a single time.) Expected: 3. once the setting is in effect, AltGr + e should produce 'é' when i-bus is active. Workaround: Not any workaround found. I tried to load a Generic 105-key (Intl) PC layout with /usr/bin/xmodmap, and this method works when I am not in Gnome (in fluxbox) and ibus is not activated, but it has no effect when ibus is activate. Why this issue is important: For example, a German who can do Chinese would naturally wish to use his familiar German keyboard layout without havin to switch off ibus-table. So does every user of non-English keyboard layout. ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Description changed: Reproduce: 1. The Ubuntu system default keyboad layout configure to Generic 105-key (Intl) PC this can be done with $ sudo dpkg-reconfigure keyboard-configuration You can verify if the setting is in effect by typing AltGr + e and you - should key in 'é'. + should key in 'é'. You should be able to get this behaviour even in the + console (Ctrl+Alt+F1). (The Alt key right to the space bar, even if it is just labeled Alt, it is AltGr in effect) 2. run ibus-setup and check the checkbox Use System Keyboard, it is on the last tab. 3. reboot and login, and type AltGr + e, you just get plain e, not 'é' and you don't get 'é' even if you have switched away from input method (typically by tapping left shift key) Expected: 3. once the setting is in effect, AltGr + e should produce 'é' when i-bus is active. Workaround: Not any workaround found. I tried to load a Generic 105-key (Intl) PC layout with /usr/bin/xmodmap, and this method works when I am not in Gnome (in fluxbox) and ibus is not activated, but it has no effect when ibus is activate. Why this issue is important: For example, a German who can do Chinese would naturally wish to use his familiar German keyboard layout without havin to switch off ibus-table. So does every user of non-English keyboard layout. ** Description changed: Reproduce: 1. The Ubuntu system default keyboad layout configure to Generic 105-key (Intl) PC this can be done with $ sudo dpkg-reconfigure keyboard-configuration You can verify if the setting is in effect by typing AltGr + e and you should key in 'é'. You should be able to get this behaviour even in the console (Ctrl+Alt+F1). (The Alt key right to the space bar, even if it is just labeled Alt, it is AltGr in effect) 2. run ibus-setup and check the checkbox Use System Keyboard, it is on the last tab. 3. reboot and login, and type AltGr + e, you just get plain e, not 'é' and you don't get 'é' even if you have switched away from input method - (typically by tapping left shift key) + (typically by tapping left shift key a single time.) Expected: 3. once the setting is in effect, AltGr + e should produce 'é' when i-bus is active. Workaround: Not any workaround found. I tried to load a Generic 105-key (Intl) PC layout with /usr/bin/xmodmap, and this method works when I am not in Gnome (in fluxbox) and ibus is not activated, but it has no effect when ibus is activate. Why this issue is important: For example, a German who can do Chinese would naturally wish to use his familiar German keyboard layout without havin to switch off ibus-table. So does every user of non-English keyboard layout. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1243091 Title: system keyboad layout setting has no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1243091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099289] Re: Touch screen stops respoding to clicking after running for a while
Previously I said, that when the computer no longer respond to touchpad clicks, it also stops to respond to physical mouse clicks. This I managed to reproduce again, thus I can confirm this behaviour. And I confirm this happens not only to firefox but also to amule, which uses wxwidget. i guess this misbehavior applies to anything that is not gtk (e.g. tcl/tk). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099289 Title: Touch screen stops respoding to clicking after running for a while To manage notifications about this bug go to: https://bugs.launchpad.net/evdev/+bug/1099289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099289] Re: Touch screen stops respoding to clicking after running for a while
** Summary changed: - Touch screen stops clicking... + Touch screen stops respoding to clicking after running for a while -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099289 Title: Touch screen stops respoding to clicking after running for a while To manage notifications about this bug go to: https://bugs.launchpad.net/evdev/+bug/1099289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099289] Re: Touch screen stops respoding to clicking after running for a while
I found that when this happens, Firefox also stops to respond to clicks - real mouse click, not only touch-pad clicks. And that this doesn't happen to other software like Nautilous, and that this happens only in firefox, not on its titlebar (which traditionally is part of a window- manager - things changed so much nowadays I don't even knnow how to address it now). I am guessing this behaviour ascribes to this bug -- it happened twice on my tablet, and if it keep happening I would be able to say for sure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099289 Title: Touch screen stops respoding to clicking after running for a while To manage notifications about this bug go to: https://bugs.launchpad.net/evdev/+bug/1099289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1071341] Re: bluetooth usb 0489:e048 Foxconn / Hon Hai fail to scan
** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1071341 Title: bluetooth usb 0489:e048 Foxconn / Hon Hai fail to scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1071341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1071341] Re: bluetooth usb 0489:e048 Foxconn / Hon Hai fail to scan
Tried exactly the version requested (v3.7-rc2-raring). It resulted unity failing to load properly (expected, because i was using fglrx driver which perhpas compile against my previous kernel). Nevertheless, new kernel doesn't work. Without unity, I can still do 'hcitool scan' as root. No device is found by it. In order to try if 'hcitool scan' in general work with the new kernel, I put on a secondary external USB bluetooth adaptor, indending to try scan again with that adaptor. But it resulted bluetoothd segment fault right after USB device plugged in. I rebooted to the old kernel and did 'hcitool -i hci1 scan', whcih uses the external bluetooth adaptor, and I do find device, meaning the device in test is not to be suspected. Would you be so kind to provide a workaround? I mentioned in previous post a commandline workaround which force use of external USB adaptor, but in reality it works very unstable. I guess a stable workaround would require preventing the kernel discovering the first internal bluetooth adaptor. P. S. If you have kernel source, have you poke in to see if the DEVICE id in question was referred to there? ** Tags removed: needs-upstream-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1071341 Title: bluetooth usb 0489:e048 Foxconn / Hon Hai fail to scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1071341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1071341] [NEW] bluetooth usb 0489:e048 Foxconn / Hon Hai fail to scan
Public bug reported: Device work properly in Windows 7. tristan@lyonesse:~$ sudo hcitool dev Devices: hci064:27:37:49:65:D2 tristan@lyonesse:~$ sudo hcitool scan Scanning ... tristan@lyonesse:~$ (no output) scan also fail with bluetooth-applet. force connection results timeout: tristan@lyonesse:~$ sudo bluez-simple-agent hci0 64:27:37:49:65:D2Creating device failed: org.bluez.Error.ConnectionAttemptFailed: Page Timeout This buggy behaviour looks the same as http://askubuntu.com/questions/125506/bluetooth-atheros-ar5bbu22-not-working However that is a question of a same-named device of different ID (0489:e03c), and the patch supplied by answer to that question was already integraded to the verson of kernal I have. tristan@lyonesse:~$ uname -a Linux lyonesse 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux # usb-devices T: Bus=05 Lev=01 Prnt=01 Port=04 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0489 ProdID=e048 Rev=00.01 S: Manufacturer=Atheros Communications S: Product=Bluetooth USB Host Controller S: SerialNumber=Alaska Day 2006 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb # lsusb Bus 005 Device 003: ID 0489:e048 Foxconn / Hon Hai Hardware: Iconia W500. This computer has Atheros WIFI adapter -- some google search seems to sugest this information revelent. tristan@lyonesse:~$ lspci | tail -n1 01:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01) This issue look similar to #1030233, but the workaround offered in #1030233, the one that appends /sys/bus/usb/drivers/btusb/new_id, doesn't solve this problem. P.S. As a user I'd very appreciate workarounds before using released fix. Or, at least please comment a method to hide this device from its drivers, because the very existance of this device makes 2nd external USB bluetooth useless - worse than not having the device at all. Seems bluetooth-applet only utilize the first bluetooth adapter it found. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tristan1881 F pulseaudio /dev/snd/controlC0: tristan1881 F pulseaudio Date: Thu Oct 25 22:50:03 2012 MachineType: acer ICONIA Tab W500 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=/dev/sda1 ro RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2011 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: WT1 dmi.board.vendor: acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.14:bd08/12/2011:svnacer:pnICONIATabW500:pvrV1.14:rvnacer:rnWT1:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: ICONIA Tab W500 dmi.product.version: V1.14 dmi.sys.vendor: acer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug quantal running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1071341 Title: bluetooth usb 0489:e048 Foxconn / Hon Hai fail to scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1071341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1071341] Re: bluetooth usb 0489:e048 Foxconn / Hon Hai fail to scan
This is to document a failed attempt to make use of 2nd external USB bluetooth adapter, intending to workaround this bug. 1. bluetooth-applet: there is no way to configuure which adapter to use. Deadend. 2. blueman: two adapters are displayed, but user only given the choice which adapter visible, not which adapter to use to pare and connect new devices. 3. bluez-simple-agent In general from google search it seems the method to connect using command line changes once half a year, rendering most search results useless, only to waste time. The latest method I can find fail to connect the device: pairing is successful, but not connecting: # bluez-simple-agent hci1 00:60:D1:00:4B:78 RequestPinCode (/org/bluez/664/hci1/dev_00_60_D1_00_4B_78) Enter PIN Code: Release New device (/org/bluez/664/hci1/dev_00_60_D1_00_4B_78) root@lyonesse:~# dbus-send --print-reply --system --dest=org.bluez /org/bluez/n/hci1/dev_00_60_D1_00_4B_78 org.bluez.Input.Connect Error org.freedesktop.DBus.Error.UnknownObject: Method Connect with signature on interface org.bluez.Input doesn't exist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1071341 Title: bluetooth usb 0489:e048 Foxconn / Hon Hai fail to scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1071341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1071341] Re: bluetooth usb 0489:e048 Foxconn / Hon Hai fail to scan
Sorry -- commandline method works, only after I submitted the form. Besides, I copied the wrong line from experimental output of # dbus- send. Should be this: root@lyonesse:~# dbus-send --print-reply --system --dest=org.bluez /org/bluez/664/hci1/dev_00_60_D1_00_4B_78 org.bluez.Input.Connect Error org.bluez.Error.Failed: Host is down (112) [to try again] root@lyonesse:~# dbus-send --print-reply --system --dest=org.bluez /org/bluez/664/hci1/dev_00_60_D1_00_4B_78 org.bluez.Input.Connect Error org.bluez.Error.AlreadyConnected: Already Connected [wait 5 minutes, the mouse start moving] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1071341 Title: bluetooth usb 0489:e048 Foxconn / Hon Hai fail to scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1071341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 802545] Re: Bluetooth not working on Acer W500 tablet
I can confirm it still doesn't work for me on 12.10 (64-bit). The behavior: bluetooth icon is shown, with a right-click menu option to turn it off, which should mean it is on. To add a bluetooth device, clicking Bluetooth setting on the notification icon right-click menu results nothing - no new window. Go to gnome control panel and access bluetooth setting from there. The window shows bluetooth is on. Click + to add a new device, it scans for half an hour not being able to find any device (another computer next to it can find 3+ devices). If turn local computer visible, other computers cannot see it. restarting bluetooth service does not help (no change in behaviour). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/802545 Title: Bluetooth not working on Acer W500 tablet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/802545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 568855] Re: song ti and other bitmap fonts are not available even if using yes-bitmaps rule
New discovery: If I load the font with fontforge, save it using UTF intead of the original GB encoding, then I got new files that can be listed in fc-list. So I guess fontconfig ignores fonts encoded in GB encoding. The easiest fix is to ask X.org to deliver these 2 fonts in UTF instead. Which would be a different bug on a different tracker (X.org instead of launchpad), right? ** Attachment added: The new font file for SongTi saved from fontforge in UTF. https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/568855/+attachment/3203185/+files/SongtiMedium-16.pcf.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/568855 Title: song ti and other bitmap fonts are not available even if using yes- bitmaps rule To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/568855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 311297] Re: growisofs unable to burn dual layer DVD-R
Dear Gray Did you post the following message to the bug tracker and sent me a copy, or did you only post to me? I ask this because there are little I can help on technical issues, you will have more luck on forums or bug trackers. I am always confused about burning stuff and my only way to help the community is to complain to them:) please do try to post this message on debian cdwriter mailing list. http://lists.debian.org/cdwrite/ As that is the single most helpful mailing list on DVD/CD burning issue there. Someone there answers question in surprising accuracy, once you do you know what I mean:) Best. Zhang Weiwu On 01/12/2011 05:33 PM, gray wrote: Hi I am running Debian Squeeze i386, fully updated as of 11 am this morning. In the last few days there has ben a k3b update, since which I have not been able to burn data dvds correctly - I have tried various suggestions located on the net, mostly involving checking permissions, adding myself to the burning group, cdrom group etc, none of which have been of any use. ISO dvds seem to work here and there, but all data dvds (using verbatim dvd-r dvds) fail with the Unable to fixate the disk - The disk might still be readable error. I have done 7 dvds in a row, all with the same result. Debian Squeeze is installed on a latop and the dvd-burner is an internal. The system was bought around 18 months ago with Ubuntu 8.04 installed from a South African company called Sahara. lspci: 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.3 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03) 00:1f.6 Signal processing controller: Intel Corporation 82801I (ICH9 Family) Thermal Subsystem (rev 03) 01:00.0 Network controller: Intel Corporation WiFi Link 5100 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) Please see below for debug info from k3b: Devices --- Optiarc DVD RW AD-7580S FA01 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump] [%7] K3b::IsoImager --- mkisofs print size result: 25335 (51886080 bytes) System --- K3b Version: 2.0.1 KDE Version: 4.4.5 (KDE 4.4.5) QT Version: 4.6.3 Kernel: 2.6.32-5-686 Used versions --- mkisofs: 1.1.11 cdrecord: 1.1.11 cdrecord --- scsidev: '/dev/sr0' devname: '/dev/sr0' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Wodim version: 1.1.11 SCSI buffer size: 64512 Beginning DMA speed test. Set CDR_NODMATEST environment variable if device communication breaks or freezes immediately after that. TOC Type: 1 = CD-ROM Driveropts: 'burnfree' Device type: Removable CD-ROM Version: 5 Response Format: 2 Capabilities : Vendor_info: 'Optiarc ' Identification : 'DVD RW AD-7580S ' Revision : 'FA01' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: 0x0011
[Bug 470683] Re: ATAPI DMA disabled for reliablity issues (Karmic)
Fabio wrote: Is this problem present with the latest updated Karmic's or lucid's packages? This issue is tested to be existing on Ubuntu 10.10 (I am using an 64-bit Desktop version). Although I am not sure if it should be reported here: more like a kernel issue to me. -- ATAPI DMA disabled for reliablity issues (Karmic) https://bugs.launchpad.net/bugs/470683 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 159518] Re: no display in google analytics
I guess this bug is the same as upstream: http://savannah.gnu.org/bugs/?30100 ** Bug watch added: GNU Savannah Bug Tracker #30100 http://savannah.gnu.org/bugs/?30100 -- no display in google analytics https://bugs.launchpad.net/bugs/159518 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 637671] Re: ibus python 100 % cpu for ever
@Karl Lattimer on #32: you suggested me to check #625793, which I think is not affecting me, because that bug have gnome-setting-daemon taking 100% CPU while I had python taking all CPU resource. -- ibus python 100 % cpu for ever https://bugs.launchpad.net/bugs/637671 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 663628] Re: always check disk for error upon starting
*** This bug is a duplicate of bug 616287 *** https://bugs.launchpad.net/bugs/616287 Reading the description of #616287 I am pretty sure now that this bug I report is a duplicate of #616287 thus I marked this bug invalid. ** Changed in: mountall (Ubuntu) Status: Incomplete = Invalid ** This bug has been marked a duplicate of bug 616287 umountfs doesn't cleanly unmount / on reboot * You can subscribe to bug 616287 by following this link: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/616287/+subscribe -- always check disk for error upon starting https://bugs.launchpad.net/bugs/663628 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 616287] Re: umountfs doesn't cleanly unmount / on reboot
I can confirm it happens to me with my favorite xdm/fluxbox combination that I use since early this century. In most cases I could not cleanly shut down, seeing the message file system busy for / before power goes off on my laptop. Using 10.10 64-bit. -- umountfs doesn't cleanly unmount / on reboot https://bugs.launchpad.net/bugs/616287 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 311297] Re: growisofs unable to burn dual layer DVD-R
A bit of information to save your time googling, but check timestampe of this comment to decide if you should google again. a. this problem seems to be the same as #439281. Please QA people take a look and close one of them in case of dups. b. this post Layer break for DVD+R DL with growisofs / dvd+rw-tools seems to suggest to me that the problem is related to incorrect layer- break position, but the article did not offer ways to find out what is the right value for layer-break point. http://stephane.emisfr.info/en/2009/09/11/layer-break-for-dvdr-dl-with- growisofs-dvdrw-tools/ c. the incompatibility between growisofs and DVD-R DL is reported in multiple bug trackers, but strangely, not in Debian bug tracker, it is strange, because, growisofs is now (IMHO) a debian project. Interestingly the problem seems to be reported in 2007 to Debian cdwrite mailing list: http://lists.debian.org/cdwrite/2007/03/msg00022.html without getting any attention. d. K3B bug report about this issue mentioned this problem might will be gone when K3B switch to cdrecord. It is not clear to me if K3B is to swicth from growisofs to cdrecord or from the GPL wodim to non-GPL cdrecord. e. the explicite mention of 'growisofs compatibility with DVD-R DL' seems to hint this issue doesn't exist with wodim/cdrecord. In my test case, the DVD-R DL which could not start burning due to the very problem of this issue, can be burnt, but with fixate error, with wodim. The following snip of wodim output showed the error message. However, the disco burnt with this very error message can be read successfully. Track 01: Total bytes read/written: 7991693312/7991693312 (3902194 sectors). Writing time: 2896.302s Average write speed 2.0x. Min drive buffer fill was 91% Fixating... Errno: 5 (Input/output error), flush cache scsi sendcmd: no error CDB: 35 00 00 00 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 72 0B 00 00 00 00 00 0E 09 0C 00 00 00 00 00 00 Sense Key: 0x0 No Additional Sense, Segment 11 Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 131.203s timeout 120s Trouble flushing the cache wodim: Cannot fixate disk. Fixating time: 131.209s wodim: fifo had 125878 puts and 125878 gets. wodim: fifo was 0 times empty and 87500 times full, min fill was 90%. -- growisofs unable to burn dual layer DVD-R https://bugs.launchpad.net/bugs/311297 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 663628] Re: always check disk for error upon starting
Thanks. I followed advice of another Ubuntu user to remove the 'splash quiet' tag from grub.cfg to have the following discovery: - every time boots it says file system was not cleanly shut down that a check is forced. - every time when I shut down the PC (strangely now I can shut down the PC) the last message on the screen is: - umount / : file system busy Both messages are according to my memory, thus not exact, but the time is too short to write down the messages. So the case look obvious to me now, that for some reason the root file system could not be successfully umounted when shut down. I don't have /forcefsck file. -- always check disk for error upon starting https://bugs.launchpad.net/bugs/663628 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 629919] Re: Ubuntu 10.10 can not be closed, start the shutdown process but remains in the splash screen
Ah, you fixed it with fglrx drvier but I experience the same behavior (as described in this bug's title) with nvidia card, although I am not sure if the underlying cause is the same. -- Ubuntu 10.10 can not be closed, start the shutdown process but remains in the splash screen https://bugs.launchpad.net/bugs/629919 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 663628] [NEW] always check disk for error upon starting
Public bug reported: Binary package hint: upstart Samsung X10 with Ubuntu 10.10, a new installation. Ubuntu booting always check disk for error. While it always happen to me, I am not sure if this would happen with a clean shutdown, as I never managed to. I suffer from the phenomenon of not possible to clean shutdown, as described in #629919. Although I can successfully reboot (also a phenomenon of #629919) but successful reboot results a disk check anyway. That's all information I can provide. The splash screen concealed other information that might be useful, like which partition is being checked (can it be the dual-boot windows partition?) and what reason it is checked (not clean shut down? something wrong with the clock that make upstart think check haven't been done in a decade or so?). I'll provide other info on requests. ** Affects: upstart (Ubuntu) Importance: Undecided Status: New -- always check disk for error upon starting https://bugs.launchpad.net/bugs/663628 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 637671] Re: ibus python 100 % cpu for ever
Offer some information for those who don't use an DE: I am a bit surprised that I hit this problem too as I thought non-DE users are immune to such problems as they can decide if turn on the input method or not by .xsession. Fact is .xsession no longer have control over what input method to run or in which mode (IM_MODULE/XIM). I don't use gnome at all on my Ubuntu Maverick 32-bit and what I use for XIM is decided in .xsession (which launches fluxbox), now having this 100% cpu problem, I commented out everything related to xim daemon: #export GTK_IM_MODULE=ibus #export XMODIFIERS=@im=ibus #/usr/bin/ibus-daemon --xim and that doesn't help. With all these commented out, ibus run as usual, means I will not have control over xim daemon like I used to. My preference of using xim (instead of *K_IM_MODULE) is so that I still have control over it in .xsession. It seems things changed now. -- ibus python 100 % cpu for ever https://bugs.launchpad.net/bugs/637671 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 568855] Re: song ti and other bitmap fonts are not available even if using yes-bitmaps rule
Hi. A complete solution for this problem is published here: http://www.zhangweiwu.name/100921.html Quote: Unfortunately font-config can make use of fewer encodings than X11 can do, thus not all bitmap fonts available to X11 will present in fc-list. After a few experiments it seems to me that only X11 fonts whos name string contain 'iso' can be recognized by font-config. To make use of such fonts you need to convert its encoding. To make it short, it seems this problem can be solved by shipping referred fonts re-encoded in unicode. referred fonts are Songti, Fang Songti. There perhaps are other fonts that should be re-encoded too. -- song ti and other bitmap fonts are not available even if using yes-bitmaps rule https://bugs.launchpad.net/bugs/568855 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 419182] Re: KVM and audio driver in Windows 7
As I do have a physical ES1370 sound card I want to share my experience. 1. I installed Windows 7 64-bit Advanced Home Edition, Windows notified it tried but cannot find a driver for it. 2. I tried to go to Device Manager and ask for a driver update, selected to let windows choose the right driver on internet. It prompts fail to find any driver. 3. Google on the Internet finds multiple website offering download of a driver whose file name is creative_es1370_60_win7.rar and titled ES1370/ES1371/ES1373 driver for Windows 7 version 6.00, which doesn't work for me. Examples: http://download.pchome.net/driver/hardware/sound/download-100249.html http://driver.cnd8.com/qudong/13203.htm ( both site checks HTTP head referral thus I cannot give direct download link. But on the later site, the download link is easy to find without reading Chinese, look at lower left column of the page where there is a column of 3 anmiated download icon, any one of these icon should work.) It confuses me that the driver is not offered on English websites but I only found them on Chinese sites. Download the driver, unpackage it to a folder, in Device Manager I update driver and specified location of the driver, Windows 7 prompts me no driver was found in that place. Open the .inf file in the drvier package it is obvious this is a generic driver for almost a hundred different models of sound cards. Conclusion: still no clue of a working driver of ES1370 The wiki page on http://www.linux-kvm.org/page/Sound suggested Windows 7 should find the driver by itself from the Internet, but the driver constantly crash. It is not true in my case. My Win7 cannot find the driver by itself, although, there is a chance it work without crash thanks to the physical device in presence. -- KVM and audio driver in Windows 7 https://bugs.launchpad.net/bugs/419182 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 419182] Re: KVM and audio driver in Windows 7
As I do have a physical ES1370 sound card I want to share my experience. 1. I installed Windows 7 64-bit Advanced Home Edition, Windows notified it tried but cannot find a driver for it. 2. I tried to go to Device Manager and ask for a driver update, selected to let windows choose the right driver on internet. It prompts fail to find any driver. 3. Google on the Internet finds multiple website offering download of a driver whose file name is creative_es1370_60_win7.rar and titled ES1370/ES1371/ES1373 driver for Windows 7 version 6.00, which doesn't work for me. Examples: http://download.pchome.net/driver/hardware/sound/download-100249.html http://driver.cnd8.com/qudong/13203.htm ( both site checks HTTP head referral thus I cannot give direct download link. But on the later site, the download link is easy to find without reading Chinese, look at lower left column of the page where there is a column of 3 anmiated download icon, any one of these icon should work.) It confuses me that the driver is not offered on English websites but I only found them on Chinese sites. Download the driver, unpackage it to a folder, in Device Manager I update driver and specified location of the driver, Windows 7 prompts me no driver was found in that place. Open the .inf file in the drvier package it is obvious this is a generic driver for almost a hundred different models of sound cards. Conclusion: still no clue of a working driver of ES1370 The wiki page on http://www.linux-kvm.org/page/Sound suggested Windows 7 should find the driver by itself from the Internet, but the driver constantly crash. It is not true in my case. My Win7 cannot find the driver by itself, although, there is a chance it work without crash thanks to the physical device in presence. -- KVM and audio driver in Windows 7 https://bugs.launchpad.net/bugs/419182 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 568855] Re: song ti and other bitmap fonts are not available even if using yes-bitmaps rule
Hi Arne nice to see you again and see you work on this issue! I just wish to mention that on 10.04 this issue seems still exist, can there be an instruction how to make Chinese bitmap fonts, e.g. -isas-fangsong ti-medium-r-normal--16-160-72-72-c-160-gb2312.1980-0 usable in most software, e.g. gimp? I also tried the instruction from http://www.alanbriolat.co.uk/2009/04/enable-bitmap-fonts-on-ubuntu-jaunty/ -- song ti and other bitmap fonts are not available even if using yes-bitmaps rule https://bugs.launchpad.net/bugs/568855 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 568855] [NEW] song ti and other bitmap fonts are not available even if using yes-bitmaps rule
Public bug reported: Binary package hint: fontconfig Having 70-yes-bitmaps.conf replacing 70-no-bitmaps.conf in /etc/fonts/conf.d/ does not make available all bitmap fonts. Reproduce: 1) have 70-yes-bitmaps.conf set; 2) some bitmap fonts in /usr/share/fonts/X11/misc are then available in fc-list. Some others are not. Example of those are available on both xlsfont and fc-list: /usr/share/fonts/X11/misc/unifont.pcf.gz in xfonts-unifont package xlsfont says -gnu-unifont-medium-r-normal--0-0-75-75-c-0-iso10646-1 -gnu-unifont-medium-r-normal--16-160-75-75-c-80-iso10646-1 -unifoundry.com-gnu unifont-medium-r-normal--0-0-0-0-p-0-iso10646-1 fc-list says: unifont.pcf:style=Regular unifont:style=Medium Example of those are available on xlsfont but not on fc-list: /usr/share/fonts/X11/misc/gb16st.pcf.gz in xfonts-base package. xlsfont says: -isas-song ti-medium-r-normal--0-0-72-72-c-0-gb2312.1980-0 -isas-song ti-medium-r-normal--16-160-72-72-c-160-gb2312.1980-0 -isas-song ti-medium-r-normal--24-240-72-72-c-240-gb2312.1980-0 the font is not in fc-list. Rationate why we need to make bitmap font available: +-- | It should not happen that the system asks users to use scalable font instead of bitmap font | when there is no scalable font replacement available. +-- In the west there are san-serif, serif as main typefaces, each have an italic typefaces. These can be said of basic typefaces. The four basic typefaces in Chinese typography are: - Song ti: two varients: low contrast book varient: scalable offered by ttf-arphic-uming package. heavy contrast title / strong varient: NO SCALABLE available, xfonts-base offer a bitmap one: Song Ti - Kaiti. scalable offered by ttf-arphic-ukai package. - Fangsong ti. NO SCALABLE available, xfonts-base offer a bitmap one. - HeiTi. scalable offered by ttf-droid package. The four-basics all have scalable versions in MS Windows since 95'. As you can see some basic things only have bitmap version so far, in Ubuntu packages. It should not be too difficult to make them work. ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: fontconfig Having 70-yes-bitmaps.conf replacing 70-no-bitmaps.conf in /etc/fonts/conf.d/ does not make available all bitmap fonts. Reproduce: 1) have 70-yes-bitmaps.conf set; - 2) some bitmap fonts in /usr/share/fonts/X11/misc are then available, varify by fc-list. Some others are not. + 2) some bitmap fonts in /usr/share/fonts/X11/misc are then available in fc-list. Some others are not. Example of those are available on both xlsfont and fc-list: /usr/share/fonts/X11/misc/unifont.pcf.gz in xfonts-unifont package - xlsfont says + xlsfont says - -gnu-unifont-medium-r-normal--0-0-75-75-c-0-iso10646-1 - -gnu-unifont-medium-r-normal--16-160-75-75-c-80-iso10646-1 - -unifoundry.com-gnu unifont-medium-r-normal--0-0-0-0-p-0-iso10646-1 - - fc-list says: - - unifont.pcf:style=Regular - unifont:style=Medium + -gnu-unifont-medium-r-normal--0-0-75-75-c-0-iso10646-1 + -gnu-unifont-medium-r-normal--16-160-75-75-c-80-iso10646-1 + -unifoundry.com-gnu unifont-medium-r-normal--0-0-0-0-p-0-iso10646-1 + fc-list says: + + unifont.pcf:style=Regular + unifont:style=Medium Example of those are available on xlsfont but not on fc-list: /usr/share/fonts/X11/misc/gb16st.pcf.gz in xfonts-base package. - xlsfont says: + xlsfont says: - -isas-song ti-medium-r-normal--0-0-72-72-c-0-gb2312.1980-0 - -isas-song ti-medium-r-normal--16-160-72-72-c-160-gb2312.1980-0 - -isas-song ti-medium-r-normal--24-240-72-72-c-240-gb2312.1980-0 + -isas-song ti-medium-r-normal--0-0-72-72-c-0-gb2312.1980-0 + -isas-song ti-medium-r-normal--16-160-72-72-c-160-gb2312.1980-0 + -isas-song ti-medium-r-normal--24-240-72-72-c-240-gb2312.1980-0 - the font is not in fc-list. + the font is not in fc-list. Rationate why we need to make bitmap font available: Despite the general trend of using anti-alias fonts there are still many very good reasons to use bitmap fonts for Asian text. Correct me if I am wrong, but there is not another Fangsong Ti in Ubuntu package than -isas-fangsong ti-medium-r-normal--16-160-72-72-c-160-gb2312.1980-0 in xfonts-base. Faongsong Ti is one of the 4 basic fonts of Chinese, to Chinese users, as basic as Italic to westerners. It should not happen that the system asks users to use scalable font instead of bitmap font when there is no scalable font with similiar look. ** Description changed: Binary package hint: fontconfig Having 70-yes-bitmaps.conf replacing 70-no-bitmaps.conf in /etc/fonts/conf.d/ does not make available all bitmap fonts. Reproduce: 1) have 70-yes-bitmaps.conf set; 2) some bitmap fonts in /usr/share/fonts/X11/misc are then available in fc-list. Some
[Bug 499662] [NEW] unify text files to UTF-8
Public bug reported: Binary package hint: fortune-zh 1. /usr/share/doc/fortune-zh/README.Debian is encoded GB2312 while majority of other text on Ubuntu are UTF-8, including the fortune files in this fortune package. I think it should be unified to UTF-8 ** Affects: fortune-zh (Ubuntu) Importance: Undecided Status: New -- unify text files to UTF-8 https://bugs.launchpad.net/bugs/499662 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 499664] [NEW] some ideographs broken
Public bug reported: Binary package hint: fortune-zh I am not sure if people really reads these poems in the package, because there are error once a few poems and not seems attracting attention for correction. e.g. check the following output, every line contain wrong ideographs. $ grep ꆼ /usr/share/games/fortunes/*00 /usr/share/games/fortunes/tang300:《宣州谢ꆼ楼饯别校书叔云》 /usr/share/games/fortunes/tang300:昔日太宗拳毛ꆼ，近时郭家狮子花。 /usr/share/games/fortunes/tang300:忆昨路绕锦亭东，先主武侯同ꆼ宫。 /usr/share/games/fortunes/tang300:舞剑器，壮其蔚ꆼ，问其所师，曰：“余公孙大娘弟子也。” /usr/share/games/fortunes/tang300:玳ꆼ急管曲复终，乐极哀来月东出。 /usr/share/games/fortunes/tang300:人生如此自可乐，岂必局束为人ꆼ。 /usr/share/games/fortunes/tang300:夜投佛寺上高阁，星月掩映云ꆼꆼ。 /usr/share/games/fortunes/tang300:中朝大官老于事，讵肯感激徒ꆼ婀。 /usr/share/games/fortunes/tang300:烟销日出不见人，ꆼ乃一声山水绿。 /usr/share/games/fortunes/tang300:ꆼ武古通作牙爪，仪曹外郎载笔随。 /usr/share/games/fortunes/tang300:呜呼圣王及圣相，相与ꆼ赫流淳熙。 /usr/share/games/fortunes/tang300:南山截竹为ꆼ篥，此乐本自龟兹出。 /usr/share/games/fortunes/tang300:熊咆龙吟殷岩泉，ꆼ深林兮惊层巅。 /usr/share/games/fortunes/tang300:黄门飞ꆼ不动尘，御厨络绎送八珍。 /usr/share/games/fortunes/tang300:腰下宝ꆼ青珊瑚，可怜王孙泣路隅。 /usr/share/games/fortunes/tang300:花门ꆼ面请雪耻，慎勿出口他人狙。 /usr/share/games/fortunes/tang300:春窗曙灭九微火，九微片片飞花ꆼ。 /usr/share/games/fortunes/tang300:山口潜行始隈ꆼ，山开旷望旋平陆。 /usr/share/games/fortunes/tang300:噫吁ꆼ，危呼高哉！ /usr/share/games/fortunes/tang300:问君西游何时还，畏途ꆼ岩不可攀。 /usr/share/games/fortunes/tang300:飞湍瀑流争喧ꆼ，石冰崖转石万壑雷。 /usr/share/games/fortunes/tang300:今夜ꆼ州月，闺中只独看。 /usr/share/games/fortunes/tang300:寒山转苍翠，秋水日潺ꆼ。 /usr/share/games/fortunes/tang300:汉女输ꆼ布，巴人讼芋田。 /usr/share/games/fortunes/tang300:仆失路艰虞，遭时徽ꆼ。 /usr/share/games/fortunes/tang300:作者：韩ꆼ /usr/share/games/fortunes/tang300:作者：沈ꆼ期 /usr/share/games/fortunes/tang300:未必逢ꆼ缴，孤飞自可疑。 /usr/share/games/fortunes/tang300:积雨空林烟火迟，蒸藜炊黍饷东ꆼ。 /usr/share/games/fortunes/tang300:迢ꆼ太华俯咸京，天外三峰削不成。 /usr/share/games/fortunes/tang300:河山北枕秦关险，驿路西连汉ꆼ平。 /usr/share/games/fortunes/tang300:作者：韩ꆼ /usr/share/games/fortunes/tang300:惊风乱ꆼ芙蓉水。密雨斜侵薜荔墙。 /usr/share/games/fortunes/tang300:同穴ꆼ冥何所望，他生缘会更难期。 /usr/share/games/fortunes/tang300:《自河南经乱,关内阻饥,兄弟离散,各在一处.因望月有感,聊书所怀,寄上浮梁大兄,于潜七兄,乌江十五兄,兼示符离及下ꆼ弟妹》 /usr/share/games/fortunes/tang300:远路应悲春ꆼ晚，残宵犹得梦依稀。 /usr/share/games/fortunes/tang300:玉ꆼ缄札何由达，万里云罗一雁飞。 /usr/share/games/fortunes/tang300:遥窥正殿帘开处，袍ꆼ宫人扫御床。 /usr/share/games/fortunes/tang300:昨夜裙带解，今朝ꆼ子飞。 /usr/share/games/fortunes/tang300:昨夜上皇新授ꆼ，太真含笑入帘来。 /usr/share/games/fortunes/tang300:渭城朝雨ꆼ轻尘，客舍青青柳色新。 ** Affects: fortune-zh (Ubuntu) Importance: Undecided Status: New -- some ideographs broken https://bugs.launchpad.net/bugs/499664 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 499663] [NEW] recommend text in zh-hant
Public bug reported: Binary package hint: fortune-zh The package is fortune-zh, not fortune-zh-hans, however the text are in zh-hans. People might as well expect it to be zh-hant. It might make more sense to change it to original zh-hant since all text in this fortune package dates back more than 500 years ago and thus all first published in zh-hant. zh-hans is the translated version, and translation can only introduce errors instead of reducing errors. ** Affects: fortune-zh (Ubuntu) Importance: Undecided Status: New -- recommend text in zh-hant https://bugs.launchpad.net/bugs/499663 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 308303] Re: Rosegarden should depend on timidity
I recently learned fluidsync can also be used as software synthesizer except it doesn't come with any sound font, unlike timidity that can play music on its own (because of the package it depends). In short there is more than one way to do software synthesize. -- Rosegarden should depend on timidity https://bugs.launchpad.net/bugs/308303 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 231798] Re: thunderbird ldap active directory
Hi. Both are reasonable behavior if you could not bind to the LDAP server, which might happen if you have wrong Bind DN / password. In order to proove the bind dn and password is working, in case ldap server is openldap, you need to enable certain error log (e.g. at debug level 256) and attach the error log here. This may need help from ldap server administrator. -- thunderbird ldap active directory https://bugs.launchpad.net/bugs/231798 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 365440] Re: Chinese Characters Missing When Printing
This bug is especially easy to reproduce when you try to open a document authored on Microsoft Windows Simplified Chinese edition. Since one reason is the lack of Windows fonts on Linux, here is a screenshot of how I correct this problem by configuring a font mapping table in OpenOffice's options. See the screenshot. I install this font-mapping for all customers at the moment as a workaround. This lack of proper font mapping issue isn't new, it has been at least 5 years old. ** Attachment added: Screenshot of openoffice option the font mapping table http://launchpadlibrarian.net/28537806/snapshot.png -- Chinese Characters Missing When Printing https://bugs.launchpad.net/bugs/365440 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 308303] Re: Rosegarden should depend on timidity
I just started trying these and getting rosegarden working is surprisingly difficult in my case. I'd even compare the difficulty to Apache configuration with ssl + authenticate against openldap database for a newbie who just managed to understand configure vsftpd. There are a lot of cases that this works, that doesn't etc and strange behavior. As of dependency, reading documents (especially this one: http://wiki.debian.org/DebianEdu/Documentation/Manuals/Rosegarden/Setup) you can see rosegarden expects professional users, and assume you have hardware midi device. This is IMHO basically a wrong approch because new user has to manage to get it work before deciding going professional and buy hardware devices, whlie there is no second Linux free software with similiar function but orient beginner so they had to begin with professional software. But, if you make rosegarden depends on timidity it might make professional users who hate to have timidity running pissed off. Personally I don't mind piss off some professional users and sometimes I would love to do so when they cannot think user-oriented. I'd vote a yes on this but still want to share above information with you. -- Rosegarden should depend on timidity https://bugs.launchpad.net/bugs/308303 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 307160] Re: Please, update freemind to version 0.8.1
Just for the information of someone who come here by google and feel as confused as I am: 1) Debian's bug is here: tp://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485629 2) 0.8 depends on a library which is not acceptable to Debian; 0.9 doesn't. -- Please, update freemind to version 0.8.1 https://bugs.launchpad.net/bugs/307160 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
