[Bug 2065430] Re: Screen doesn't wake from keyboard action when keyboard is connected to monitor USB hub.
After interacting with the issue further, it seems that the display 'wake-up' is delayed to ~10 seconds after a key is pressed (keyboard or mouse) as opposed to within a few seconds of that key press. The bug description and name should probably be updated to reflect this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065430 Title: Screen doesn't wake from keyboard action when keyboard is connected to monitor USB hub. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-550/+bug/2065430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065430] Re: Screen doesn't wake from keyboard action when keyboard is connected to monitor USB hub.
I was unable to test another graphics card in the pcie slot, but the intel graphics from the cpu do not reproduce this issue. I've also tested with another monitor with similar specs and the issue doesn't occur on that one, so I think it's isolated to only one monitor I have (the affected monitor is the NEC one in MonitorsUser.xml.txt). I do think that the PCI bus errors are probably related to the motherboard. Freezing and lockups are common with the SKU (XPS-8940 w/ discrete gpu). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065430 Title: Screen doesn't wake from keyboard action when keyboard is connected to monitor USB hub. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-550/+bug/2065430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065430] [NEW] Screen doesn't wake from keyboard action when keyboard is connected to monitor USB hub.
Public bug reported: After locking screen, the keyboard is not able to "wake up" the display even after entering password and logging in (Able to log in successfully, but display is still in standby mode). A mouse click has to be performed to get the display to turn on. Both keyboard and mouse are connected to the built-in USB hub on the display. When keyboard is connected directly to tower, this issue also occurs. Using Ubuntu 24.04 LTS with Nvidia graphics (nvidia-driver-550) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.fabric-imex-mgmt: DeviceFileMinor: 4323 DeviceFileMode: 256 DeviceFileModify: 1 .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 550.67 Tue Mar 12 23:54:15 UTC 2024 GCC version: gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu4) ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 10 13:16:53 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu DkmsStatus: nvidia/550.67, 6.8.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation RocketLake-S GT1 [UHD Graphics 750] [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell RocketLake-S GT1 [UHD Graphics 750] [1028:09c5] NVIDIA Corporation GA104 [GeForce RTX 3060 Ti Lite Hash Rate] [10de:2489] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GA104 [GeForce RTX 3060 Ti Lite Hash Rate] [1028:c976] InstallationDate: Installed on 2024-05-08 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Dell Inc. XPS 8940 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=371a1462-1a28-4016-a538-438b39d00567 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2022 dmi.bios.release: 2.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.0 dmi.board.name: 0K3CM7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.0:bd09/14/2022:br2.10:svnDellInc.:pnXPS8940:pvr:rvnDellInc.:rn0K3CM7:rvrA00:cvnDellInc.:ct3:cvr:sku09C5: dmi.product.family: XPS dmi.product.name: XPS 8940 dmi.product.sku: 09C5 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065430 Title: Screen doesn't wake from keyboard action when keyboard is connected to monitor USB hub. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2065430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667750]
Looks like this is more of a firmware issue with these docks and/or a driver issue with the 8152, so I'm throwing this back onto the queue where it was. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667750 Title: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1667750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862302] [NEW] zfs 0.8.1 requires new userland tools for Ubunt 18.04
Public bug reported: I am running Ubuntu 18.04: lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 Ever since HWE Kernel 5.3 images were introduced, ZFS module is shipped in version 0.8.1 . modinfo /lib/modules/5.3.0-28-generic/kernel/zfs/zfs.ko |head filename: /lib/modules/5.3.0-28-generic/kernel/zfs/zfs.ko version:0.8.1-1ubuntu14.3 license:CDDL author: OpenZFS on Linux description:ZFS alias: devname:zfs alias: char-major-10-249 srcversion: F3C94D5226BB5E654A00EF1 depends:zlua,spl,znvpair,zcommon,icp,zunicode,zavl retpoline: Y Unfortuanetly all userland tools for zfs are still for ZFS 0.7.5. apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.7.5-1ubuntu16.7 Candidate: 0.7.5-1ubuntu16.7 Could you please provide 0.8.1 userland tools for 18.04 HWE kernels? ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Description changed: I am running Ubuntu 18.04: lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 - Ever since HWE Kernel 5.3 images were introduced ZFS module in version - 0.8.1 shipped. + Ever since HWE Kernel 5.3 images were introduced, the ZFS module is + shipped in version 0.8.1. modinfo /lib/modules/5.3.0-28-generic/kernel/zfs/zfs.ko |head filename: /lib/modules/5.3.0-28-generic/kernel/zfs/zfs.ko version:0.8.1-1ubuntu14.3 license:CDDL author: OpenZFS on Linux description:ZFS alias: devname:zfs alias: char-major-10-249 srcversion: F3C94D5226BB5E654A00EF1 depends:zlua,spl,znvpair,zcommon,icp,zunicode,zavl retpoline: Y Unfortuanetly all userland tool for zfs are still for ZFS 0.7.5. apt-cache policy zfsutils-linux zfsutils-linux: - Installed: 0.7.5-1ubuntu16.7 - Candidate: 0.7.5-1ubuntu16.7 - + Installed: 0.7.5-1ubuntu16.7 + Candidate: 0.7.5-1ubuntu16.7 Can you please provide 0.8.1 userland tools for 18.04 HWE kernels? ** Description changed: I am running Ubuntu 18.04: lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 - Ever since HWE Kernel 5.3 images were introduced, the ZFS module is - shipped in version 0.8.1. + Ever since HWE Kernel 5.3 images were introduced ZFS module in version + 0.8.1 shipped. modinfo /lib/modules/5.3.0-28-generic/kernel/zfs/zfs.ko |head filename: /lib/modules/5.3.0-28-generic/kernel/zfs/zfs.ko version:0.8.1-1ubuntu14.3 license:CDDL author: OpenZFS on Linux description:ZFS alias: devname:zfs alias: char-major-10-249 srcversion: F3C94D5226BB5E654A00EF1 depends:zlua,spl,znvpair,zcommon,icp,zunicode,zavl retpoline: Y - Unfortuanetly all userland tool for zfs are still for ZFS 0.7.5. + Unfortuanetly all userland tools for zfs are still for ZFS 0.7.5. apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.7.5-1ubuntu16.7 Candidate: 0.7.5-1ubuntu16.7 - Can you please provide 0.8.1 userland tools for 18.04 HWE kernels? + Could you please provide 0.8.1 userland tools for 18.04 HWE kernels? ** Description changed: I am running Ubuntu 18.04: lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 - Ever since HWE Kernel 5.3 images were introduced ZFS module in version - 0.8.1 shipped. + Ever since HWE Kernel 5.3 images were introduced, ZFS module is shipped + in version 0.8.1 . modinfo /lib/modules/5.3.0-28-generic/kernel/zfs/zfs.ko |head filename: /lib/modules/5.3.0-28-generic/kernel/zfs/zfs.ko version:0.8.1-1ubuntu14.3 license:CDDL author: OpenZFS on Linux description:ZFS alias: devname:zfs alias: char-major-10-249 srcversion: F3C94D5226BB5E654A00EF1 depends:zlua,spl,znvpair,zcommon,icp,zunicode,zavl retpoline: Y Unfortuanetly all userland tools for zfs are still for ZFS 0.7.5. apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.7.5-1ubuntu16.7 Candidate: 0.7.5-1ubuntu16.7 Could you please provide 0.8.1 userland tools for 18.04 HWE kernels? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862302 Title: zfs 0.8.1 requires new userland tools for Ubunt 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1862302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729674]
Looks like this is more of a firmware issue with these docks and/or a driver issue with the 8152, so I'm throwing this back onto the queue where it was. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750165] Re: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang (Intel I219-LM )
** Package changed: ubuntu => linux-lts-xenial (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750165 Title: e1000e :00:1f.6 eno1: Detected Hardware Unit Hang (Intel I219-LM ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1750165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750165] [NEW] e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang (Intel I219-LM )
Public bug reported: I am running Ubuntu 16.04 on a Supermicro X11SAE mainboard. The machines was put into service several months ago. Ever since that time, the NIC eno1 is causing problems from time to time. When the machine boots up everything seems to be fine for a while. For no particular reason (from what I could see so far) the device seems to hang and is thus causing performance drop downs and lots of log messages. This is the setup: root@server2:~# lsb_release -rd Description:Ubuntu 16.04.3 LTS Release:16.04 root@server2:~# uname -a Linux server2 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux There are two onboard NICs put together in a bond0 plus a third gateway NIC: This is my /etc/network/interfaces file: auto lo iface lo inet loopback auto enp7s0 iface enp7s0 inet static address 192.168.178.254 netmask 255.255.255.0 network 192.168.178.0 broadcast 192.168.178.255 gateway 192.168.178.1 auto eno1 iface eno1 inet manual bond-master bond0 auto eno2 iface eno2 inet manual bond-master bond0 auto bond0 iface bond0 inet manual bond-mode 802.3ad bond-miimon 100 bond-lacp-rate 1 slaves eno1 eno2 post-up ifup br0 iface br0 inet static address 192.168.3.254 netmask 255.255.255.0 network 192.168.3.0 dns-nameserver 192.168.3.254 dns-search localdomain broadcast 192.168.3.255 bridge_ports bond0 bridge_stp off bridge_fd 0 bridge_maxwait 0 The onboard NIC eno1 and enp7s0 are served by the e1000e driver. The eno0 uses the igb driver. (see below) root@server2:~# lspci |grep Ether 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-LM (rev 31) 06:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) 07:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection root@server2:~# ethtool -i eno1 driver: e1000e version: 3.2.6-k firmware-version: 0.8-4 expansion-rom-version: bus-info: :00:1f.6 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no root@server2:~# ethtool -i eno2 driver: igb version: 5.3.0-k firmware-version: 3.25, 0x85cc expansion-rom-version: bus-info: :06:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no root@server2:~# ethtool -i enp7s0 driver: e1000e version: 3.2.6-k firmware-version: 1.8-0 expansion-rom-version: bus-info: :07:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no After every reboot it takes a while for the eno1 to start hanging (between hours and days). dmesg then shows messages like this every few seconds: [1874222.304742] e1000e :00:1f.6 eno1: Detected Hardware Unit Hang: TDH <0> TDT <2> next_to_use <2> next_to_clean<0> buffer_info[next_to_clean]: time_stamp <11bece461> next_to_watch<0> jiffies <11becebd3> next_to_watch.status <0> MAC Status <80083> PHY Status <796d> PHY 1000BASE-T Status <3800> PHY Extended Status<3000> PCI Status <10> [1874224.304604] e1000e :00:1f.6 eno1: Detected Hardware Unit Hang: TDH <0> TDT <2> next_to_use <2> next_to_clean<0> buffer_info[next_to_clean]: time_stamp <11bece461> next_to_watch<0> jiffies <11becedc7> next_to_watch.status <0> MAC Status <80083> PHY Status <796d> PHY 1000BASE-T Status <3800> PHY Extended Status<3000> PCI Status <10> [1874224.308396] e1000e :00:1f.6 eno1: Reset adapter unexpectedly [1874224.308447] e1000e :00:1f.6 eno1: speed changed to 0 for port eno1 [1874224.396431] bond0: link status definitely down for interface eno1, disabling it [1874228.310205] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [1874228.312176] bond0: link status definitely up for interface eno1, 1000 Mbps full duplex Those are the standard settings for the affected NIC: root@server2:~# ethtool -k eno1 Features for eno1: rx-checksumming: on tx-checksumming: on tx-checksum-ipv4: off [fixed] tx-checksum-ip-generic: on tx-checksum-ipv6: off [fixed] tx-checksum-fcoe-cr
[Bug 1720219] Re: Repeated keys stop after a few characters (^@ character spam every second)
I confirm that Workaround proposed by eros2 worked on my laptop Lenovo Flex 14 with Xubuntu 17.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720219 Title: Repeated keys stop after a few characters (^@ character spam every second) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722979] Re: QWidget: Must construct a QApplication before a QWidget
this only happen when one installed wireshark(and wireshark-qt) without installing wireshark-gtk, but wireshark-gtk is an optional dependency -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722979 Title: QWidget: Must construct a QApplication before a QWidget To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireshark/+bug/1722979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722979] [NEW] QWidget: Must construct a QApplication before a QWidget
Public bug reported: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Artful Aardvark (development branch) Release:17.10 Codename: artful $ apt show wireshark Package: wireshark Version: 2.4.0-1 Priority: optional Section: universe/net Origin: Ubuntu Maintainer: Balint Reczey Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 54.3 kB Depends: wireshark-qt | wireshark-gtk Conflicts: ethereal (<< 1.0.0-3) Replaces: ethereal (<< 1.0.0-3) Homepage: http://www.wireshark.org/ Download-Size: 4,390 B APT-Manual-Installed: no APT-Sources: http://mirrors.aliyun.com/ubuntu artful/universe amd64 Packages Description: network traffic analyzer - meta-package Wireshark is a network "sniffer" - a tool that captures and analyzes packets off the wire. Wireshark can decode too many protocols to list here. . This is a meta-package for Wireshark. $ wireshark QWidget: Must construct a QApplication before a QWidget Aborted ** Affects: wireshark (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/1722979 Title: QWidget: Must construct a QApplication before a QWidget To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireshark/+bug/1722979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713391] Re: glib-compile-schemas invalid free in per session override
It was only showing this core dump when installing package with apt before. but after upgrade to latest packages today (apt update && apt full-upgrade), I can't login to GDM (black screen). The workaround is remove the package sogoupinyin, which provide this file /usr/share/glib-2.0/schemas/50_sogoupinyin.gschema.override but now I can't use the best Chinese pinyin IME on linux... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713391 Title: glib-compile-schemas invalid free in per session override To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1713391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712283] Re: Cannot resolve DNS in artful daily
jarod@ubuntu-pc:~$ ll /etc/resolv.conf -rw-r--r-- 1 root root 78 Aug 28 09:38 /etc/resolv.conf jarod@ubuntu-pc:~$ cat /etc/resolv.conf # Generated by NetworkManager nameserver 114.114.114.114 # this entry is manually add by me nameserver 127.0.1.1 jarod@ubuntu-pc:~$ systemctl status systemd-resolved ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2017-08-28 09:44:24 CST; 1 day 3h ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Main PID: 3137 (systemd-resolve) Status: "Processing requests..." Tasks: 1 (limit: 4915) CGroup: /system.slice/systemd-resolved.service └─3137 /lib/systemd/systemd-resolved Aug 28 09:44:24 ubuntu-pc systemd[1]: Starting Network Name Resolution... Aug 28 09:44:24 ubuntu-pc systemd-resolved[3137]: Positive Trust Anchors: Aug 28 09:44:24 ubuntu-pc systemd-resolved[3137]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 Aug 28 09:44:24 ubuntu-pc systemd-resolved[3137]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Aug 28 09:44:24 ubuntu-pc systemd-resolved[3137]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.i Aug 28 09:44:24 ubuntu-pc systemd-resolved[3137]: Using system hostname 'ubuntu-pc'. Aug 28 09:44:24 ubuntu-pc systemd[1]: Started Network Name Resolution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712283 Title: Cannot resolve DNS in artful daily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712283] Re: Cannot resolve DNS in artful daily
update to systemd (234-2ubuntu9) doesn't help, after reboot I still need manually add nameserver to /etc/resolve.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712283 Title: Cannot resolve DNS in artful daily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674568] Re: depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic: No such file or directory
same error. $ ls /boot/ abi-4.10.0-22-generic initrd.img-4.10.0-22-generic initrd.img-4.4.0-14-generic initrd.img-4.4.0-8-generic memtest86+_multiboot.bin config-4.10.0-22-generic initrd.img-4.4.0-10-generic initrd.img-4.4.0-15-generic initrd.img-4.4.0-9-generic System.map-4.10.0-22-generic efi initrd.img-4.4.0-12-generic initrd.img-4.4.0-2-generic memtest86+.bin vmlinuz-4.10.0-22-generic grub initrd.img-4.4.0-13-generic initrd.img-4.4.0-7-generic memtest86+.elf $ ls /var/lib/initramfs-tools/ 4.10.0-22-generic 4.4.0-12-generic 4.4.0-14-generic 4.4.0-2-generic 4.4.0-7-generic 4.4.0-9-generic 4.4.0-10-generic 4.4.0-13-generic 4.4.0-15-generic 4.4.0-4-generic 4.4.0-8-generic all kernel version except 4.10.0-22-generic already deleted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674568 Title: depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1674568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610765] Re: Apparmor refuses mysqld open on /etc/mysql/my.cnf.migrated causing it to fail to start
MySQL started to throw apparmor errors after enabling slow-query-logs. I haven't used this log option for quite some time. So it probably sat for a few years (and several migrations) uncommented in my my.cnf. It turned out that the variable name had changes. The entry used to be "log_slow_queries = /var/..." now it needs to be "slow-query-log-file = /var/..." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610765 Title: Apparmor refuses mysqld open on /etc/mysql/my.cnf.migrated causing it to fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1610765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573982] Re: LVM boot problem - volumes not activated after upgrade to Xenial
Last night I ran into the same problem. I upgraded from 12.04 LTS to 16.04.1 LTS Server and got stuck at boot. The last message complained about a UUID not being present. It turned out it was the /usr FS. Doing an "lvm lvscan" from the initrd prompt showed all but one LVs inactive. The only one active was bootvg/root. I then booted via rescue system and added "lvm vgchange -ay" in /usr/share/initramfs-tools/scripts/local-top/lvm2 right before "exit 0". After running "update-initramfs -k all -c" and rebooting the server got up again. The bootvg is on a RAID1 disk controlled via mdadm. mdadm --detail /dev/md1 /dev/md1: Version : 1.2 Creation Time : Sat Dec 20 16:49:58 2014 Raid Level : raid1 Array Size : 971924032 (926.90 GiB 995.25 GB) Used Dev Size : 971924032 (926.90 GiB 995.25 GB) Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Update Time : Mon Jan 23 09:50:47 2017 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Name : XXX:1 UUID : :::814e Events : 21001 Number Major Minor RaidDevice State 0 8 190 active sync /dev/sdb3 2 831 active sync /dev/sda3 pvs PV VG Fmt Attr PSize PFree /dev/md1 bootvg lvm2 a-- 926.90g 148.90g The /boot FS is on sda1/sdb1 also via RAID1 sda2 and sda2 are swap fdisk -l /dev/sda Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x Device Boot StartEndSectors Size Id Type /dev/sda1 204810260471024000 500M fd Linux raid autodetect /dev/sda2 1026048941465583886084G 82 Linux swap / Solaris /dev/sda3 9414656 1953525167 1944110512 927G fd Linux raid autodetect lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 dpkg -l lvm2 ii lvm2 2.02.133-1ubuntu amd64Linux Logical Volume Manager -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573982 Title: LVM boot problem - volumes not activated after upgrade to Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1573982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157171] Re: NFS mounts in /etc/fstab fail
I dug a little deeper and found that only 2 of my 4 NFS Shares were mentioned in the mountall.log. The /var/log/upstart/statd-mounting*.log for the 2 other filesystems also contained "Terminated" as their only line. The machine booted 4 times today with no error in the logs so far. So the error is not reproduce-able... The following might not be directly related to this issue, but some logs under /var/log/upstart show errors multiple times about missing files.: upstart-socket-bridge.log: upstart-socket-bridge: Unable to write pid file: No such file or directory upstart-udev-bridge.log: upstart-udev-bridge: Unable to write pid file: No such file or directory ureadahead-other.log: ureadahead:/var/lib/ureadahead/var.pack: No such file or directory I think that all of those errors are a result of /var not being mounted when the process is started. /var resides on a separate LV as do /boot, /home, /usr, /var and /tmp. This is my /etc/fstab: /dev/mapper/vdrstorage-root / xfs defaults0 1 UUID=e5f29573-ce86-4f23-9b5f-68f6b1961943 /boot ext4defaults 0 2 /dev/mapper/vdrstorage-home /home xfs defaults0 2 /dev/mapper/vdrstorage-tmp /tmpxfs defaults0 2 /dev/mapper/vdrstorage-usr /usrxfs defaults0 2 /dev/mapper/vdrstorage-var /varxfs defaults0 2 /dev/mapper/vdrstorage-swap noneswapsw 0 0 192.168.3.42:/mnt/grave/video0 /video0 nfs rsize=32768,wsize=32768,rw,hard,intr,tcp,nfsvers=3,addr=192.168.3.42 0 0 192.168.3.42:/mnt/dvdisos /mnt/dvdisos nfs rsize=32768,wsize=32768,rw,hard,intr,tcp,nfsvers=3,addr=192.168.3.42 0 0 192.168.3.42:/mp3 /mp3 nfs nfsvers=3,rsize=2048,wsize=2048,tcp 0 0 192.168.3.42:/mnt/mplayer /mplayer nfs nfsvers=3,rsize=2048,wsize=2048,tcp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157171 Title: NFS mounts in /etc/fstab fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1157171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157171] Re: NFS mounts in /etc/fstab fail
Both files show exactly one entry: cat /var/log/upstart/statd-mounting-_video0.log /var/log/upstart/statd-mounting-_mp3.log Terminated Terminated -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157171 Title: NFS mounts in /etc/fstab fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1157171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157171] Re: NFS mounts in /etc/fstab fail
I forgot... Ubuntu 13.10 64bit server is running on my machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157171 Title: NFS mounts in /etc/fstab fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1157171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157171] Re: NFS mounts in /etc/fstab fail
The problem of NFS shares not being mounted does still exist. /var/log/upstart/mountall.log showed the following today: mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: an incorrect mount option was specified mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: an incorrect mount option was specified mountall: mount /video0 [940] terminated with status 32 mountall: mount /mp3 [949] terminated with status 32 mountall: Disconnected from Plymouth My /etc/fstab looks like this for the two mounts: 192.168.3.42:/mnt/grave/video0 /video0 nfs rsize=32768,wsize=32768,rw,hard,intr,tcp,nfsvers=3,addr=192.168.3.42 0 192.168.3.42:/mp3 /mp3 nfs nfsvers=3,rsize=2048,wsize=2048,tcp I would also guess, that there is some kind of race condition where nfs filesystems are supposed to mounted before statd and/or network is running. As long as eth0 got its IP via DHCP there were also lines like this in the log: mount.nfs: Network is unreachable mount.nfs: Network is unreachable mountall: mount /video0 [812] terminated with status 32 mountall: mount /mp3 [815] terminated with status 32 BTW: My machine boots from a 250GB SSD. When the mounting of the above filesystems fail, it does not start a self added service which should start on the following conditions: start on (started dbus and started udev and started irserver and mounted MOUNTPOINT=/video0) ** Changed in: nfs-utils (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157171 Title: NFS mounts in /etc/fstab fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1157171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000129] [NEW] fcitx crash when active the IM
Public bug reported: [INFO] /build/buildd/fcitx-4.2.0/src/core/errorhandler.c:58-FCITX -- Get Signal No.: 28 Obtained 6 stack frames. fcitx() [0x4010aa] /lib/x86_64-linux-gnu/libc.so.6(+0x364c0) [0x7fc03691d4c0] /lib/x86_64-linux-gnu/libpthread.so.0(sem_wait+0x2e) [0x7fc036cb1fce] fcitx() [0x400f46] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7fc03690876d] fcitx() [0x400f8d] [INFO] /build/buildd/fcitx-4.2.0/src/core/errorhandler.c:58-FCITX -- Get Signal No.: 11 Obtained 10 stack frames. fcitx() [0x4010aa] /lib/x86_64-linux-gnu/libc.so.6(+0x364c0) [0x7fc03691d4c0] /usr/lib/x86_64-linux-gnu/libgooglepinyin.so.0(_ZN10ime_pinyin8UserDict23locate_first_in_offsetsEPKNS0_18UserDictSearchableE+0x62) [0x7fc030862dd2] /usr/lib/x86_64-linux-gnu/libgooglepinyin.so.0(_ZN10ime_pinyin8UserDict9_get_lpisEPKttPNS_10LmaPsbItemEmPb+0x17d) [0x7fc030864ebd] /usr/lib/x86_64-linux-gnu/libgooglepinyin.so.0(_ZN10ime_pinyin8UserDict11extend_dictEtPKNS_11DictExtParaEPNS_10LmaPsbItemEmPm+0x32) [0x7fc030865142] /usr/lib/x86_64-linux-gnu/libgooglepinyin.so.0(_ZN10ime_pinyin12MatrixSearch10extend_dmiEPNS_11DictExtParaEPNS_13DictMatchInfoE+0x30a) [0x7fc03085b73a] /usr/lib/x86_64-linux-gnu/libgooglepinyin.so.0(_ZN10ime_pinyin12MatrixSearch15add_char_qwertyEv+0x3c2) [0x7fc03085be32] /usr/lib/x86_64-linux-gnu/libgooglepinyin.so.0(_ZN10ime_pinyin12MatrixSearch6searchEPKcm+0xca) [0x7fc03085d1fa] /usr/lib/x86_64-linux-gnu/libgooglepinyin.so.0(im_search+0x1e) [0x7fc03085f54e] /usr/lib/x86_64-linux-gnu/fcitx/fcitx-googlepinyin.so(+0x2698) [0x7fc030a73698] ** Affects: fcitx (Ubuntu) Importance: Undecided Status: New ** Tags: precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000129 Title: fcitx crash when active the IM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fcitx/+bug/1000129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 925524] Re: 10.04 11.04 11.10 imon lirc not responding on boot work after suspend resume
I'm about 99% certain this will be fixed by this patch: http://patchwork.linuxtv.org/patch/9685/ The suspend/resume cycles resubmit the missing rx_urb right now, which un-wedges the driver. This patch will be in 3.3 sooner or later, and was cc'd to stable, so it should also wind up in 3.2.x eventually. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925524 Title: 10.04 11.04 11.10 imon lirc not responding on boot work after suspend resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/925524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778296] Re: lirc not working correctly on 2.6.38 kernel
No clue. I don't use *buntu at all, let alone follow its development releases. The bug I had in mind was fixed in kernel 3.0 though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/778296 Title: lirc not working correctly on 2.6.38 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/778296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 655512] Re: /dev/lirc0 disappeared after upgrade from 2.6.35-20 to -22
If I'm thinking clearly, the 0.8.7-0ubuntu4.1 package has the requisite ioctl patches to work just fine with the in-kernel lirc drivers. And lirc_i2c is dead, its functionality is entirely replaced by the in- kernel ir-kbd-i2c driver. And lirc-modules-source should not be used. Ever. Its been removed from this distro. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/655512 Title: /dev/lirc0 disappeared after upgrade from 2.6.35-20 to -22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/655512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 819832] Re: IR device misconfigured or not configured at all in Ubuntu 11.04
That hardware is fully supported by the upstream (as of 2.6.39) ite-cir driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/819832 Title: IR device misconfigured or not configured at all in Ubuntu 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/819832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778296] Re: lirc not working correctly on 2.6.38 kernel
wrt comment #13, there's a bug in the mceusb driver that affects some IR signals, which was fixed in kernel 3.0 with the stable tree cc'd. I believe it should end up in 2.6.39 stable, dunno if 2.6.38 stable is actually being maintained anymore, so no clue if ubuntu will ever get the fix before its next release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/778296 Title: lirc not working correctly on 2.6.38 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/778296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778296] Re: lirc not working correctly on 2.6.38 kernel
In reply to comment #6, you're doing it wrong. On multiple levels. You are trying to use devinput, but the mceusb driver hasn't been configured to use the hauppauge rc5 keymap. Then you're trying to use a raw IR config with that. Won't work. You need to use /dev/lirc0 for a raw IR config. For devinput, lircd.conf.devinput, and the kernel driver's keymap for the remote you're using needs to be loaded so that something is actually mapping the raw IR signals to linux input layer keycodes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/778296 Title: lirc not working correctly on 2.6.38 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/778296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 810459] Re: package lirc-modules-source 0.8.7-0ubuntu4.1 failed to install/upgrade: lirc kernel module failed to build
The lirc drivers are provided by the kernel now, lirc-modules-source should be thrown off a cliff. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/810459 Title: package lirc-modules-source 0.8.7-0ubuntu4.1 failed to install/upgrade: lirc kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/810459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 807291] Re: Mouse and keyboard unresponsive until re-plugged in
I encounter the same issue after upgrade from 11.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/807291 Title: Mouse and keyboard unresponsive until re-plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/807291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787742] Re: lirc_atiusb non functional with snapstream firefly
Something is wonky in Ubuntu. lircd tries to get exclusive access to the input device, which prevents any of its events from being delivered to X. It works perfectly fine in other distros -- I have an ATI RemoteWonder II myself, works perfectly fine in Fedora. Not sure what's going on. One guess would be that maybe Ubuntu has lircd feeding keys back into the input layer via uinput. If you do a ps ax |grep lirc, can you see the full lircd command line? If there's a -u or --uinput in there, that's probably the cause. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787742 Title: lirc_atiusb non functional with snapstream firefly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/787742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 603468] Re: Lirc too verbose when crashing
The spew is from the imon kernel driver, and can probably be rate- limited. I'll add an entry to my TODO list. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/603468 Title: Lirc too verbose when crashing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/603468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
Okay, if its multiple machines, I put the blame squarely on the ftdi_sio and dib0700 drivers for apparently not implementing any suspend/resume support. I've actually dug out my usb-uirt hardware, which has some usb- serial ftdi driver as well, iirc., and will see if I can reproduce the issue and try to better understand it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/359356 Title: USB device attached to different ttyUSB after resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/359356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
Choice excerpts from dmesg: [0.00] Atom PSE erratum detected, BIOS microcode update recommended [0.00] ACPI: BIOS bug: multiple APIC/MADT found, using 0 [0.00] ACPI: If "acpi_apic_instance=2" works better, notify linux-a...@vger.kernel.org [0.180781] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored I'd suggest seeing if there's a BIOS update available for your system, which may or may not improve suspend/resume functionality a bit. Especially if its taking more than a minute to resume. However, that aside, looking at both the dib0700 driver and the ftdi_sio driver, I noticed they lack suspend or resume functions entirely. The ftdi_sio driver may have the default usb-serial suspend routine wired up to it somehow though. But anyway, I'm not sure if the usb core is possibly behaving as expected, disconnecting the devices, rather than suspending them, or if its the usb chipset not suspending properly. The incremented ttyUSBx device makes some degree of sense though. If lircd has an active client (such as irxevent) at suspend time, then the IR device (/dev/ttyUSB0) will be open, in which case, it can't be fully removed. Thus, when the device is reconnected, it gets ttyUSB1, as there's still a lingering reference to ttyUSB0. No clients, 0 gets fully freed up, and can be allocated again. I'll have to see about getting some ftdi usb IR hardware one of these days to get a better understanding of what's going on. I do stand by the assertion that lirc isn't actually doing anything wrong here though. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/359356 Title: USB device attached to different ttyUSB after resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/359356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
Still sounds like a kernel-level issue underneath. Can you provide dmesg output from after a fresh boot, suspend and resume? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/359356 Title: USB device attached to different ttyUSB after resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/359356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
99% certain this is not an lirc bug, it is a kernel bug. Devices disconnecting and reconnecting on suspend/resume is indicative of buggy support for the usb chipset on the system(s) in question. The isn't anything in lirc that assigns ttyUSB devices, that is purely the kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/359356 Title: USB device attached to different ttyUSB after resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/359356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387443] Re: LIRC killed or sees new usbdevice after suspend
For the record, suspend and resume with both the mceusb and streamzap drivers in 2.6.38 and up works just fine her, without stopping/starting lircd. Pretty sure cases where they aren't working are either old kernels and/or IR device drivers, or buggy usb chipset support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/387443 Title: LIRC killed or sees new usbdevice after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/387443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387443] Re: LIRC killed or sees new usbdevice after suspend
For the love of all that is good, do NOT use that atrocious xbmc wiki script, that's Doing It Wrong on multiple levels, particularly for the very latest lirc bits. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/387443 Title: LIRC killed or sees new usbdevice after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/387443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 789819] Re: Lirc mceusb resume problem
Already posted a link to the patch in comment #9. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/789819 Title: Lirc mceusb resume problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/789819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 789819] Re: Lirc mceusb resume problem
The added udev rules look fine, they should be harmless and unrelated here. The pm-suspend log looks fine too. The problem is that your usb controller appears to be forcing a full disconnect and reconnect of all usb devices. That equates to a new mceusb device being plugged in, and some udev and/or upstart rule running that restarts lirc. Take a look at the lirc initscript and whatever else is installed as part of the ubuntu lirc package. For #3, you're more than welcome to pull a copy of the patch and build a kernel locally to test. Having a non-functional irw post-resume is expected in this case. The mceusb device got disconnected, then the kernel oopsed on reconnect. The rc-core subsystem and mceusb driver are both in suspect states, and memory corruption has occurred. All bets are off at that point, until you reboot. The nyxboard is mostly uninteresting, its simply an HID device. The fact there's RF involved is entirely opaque to the kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/789819 Title: Lirc mceusb resume problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/789819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 789819] Re: Lirc mceusb resume problem
So three problems here: 1) During resume, we see this: kernel: [ 29.950131] usb 4-3: USB disconnect, address 2 This is your mceusb device. For some reason, your USB chipset isn't being suspended correctly, and its causing a full disconnect and reconnect of at least mceusb device. That's bad (and not mceusb's fault). 2) lirc is being restarted, rather than simply left running. The lirc daemon should be able to handle a lirc device coming and going from underneath it without requiring a restart like this, best as I can recall. But I think its some Ubuntu "feature-add" udev rule that restarts lircd when a new device is connected -- see item #1, the reconnect looks like a new device being connected. 3) When lirc is being restarted, its calling show_protocols before everything is actually wired up, which is indeed the bug I referenced earlier that a fix for has already been sent upstream. kernel: [ 30.053825] Pid: 1693, comm: cat Tainted: PW 2.6.38-10-generic #44-Ubuntu System manufacturer System Product Name/E35M1-I DELUXE kernel: [ 30.053832] RIP: 0010:[] [] show_protocols+0xf7/0x130 [rc_core] At this point, nothing more that I can do. The fix for #3 was sent upstream and the stable team cc'd, so in theory, that patch will eventually make it into a stable series kernel and then into an Ubuntu kernel. Item #2 requires someone in Ubuntu-land who knows better what's going on to evaluate, and #1, not sure, probably requires someone in usb-land upstream to fix suspend and resume with your particular usb chipset. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/789819 Title: Lirc mceusb resume problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/789819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 789819] Re: Lirc mceusb resume problem
Is the Ubuntu lirc initscript restarting lircd on resume? Or is this a udev rule running? Gotta be one of those two, since otherwise, I don't know what would be triggering the call to show_protocols. You included the trace for your wireless doing something bad, but omitted the bulk of the trace for the actual oops. Can I get the full oops trace please? Basically, I think this is a manifestation of something I've already submitted a fix for upstream, but its a slightly unexpected one. http://git.kernel.org/?p=linux/kernel/git/jarod/linux-2.6-ir.git;a=commitdiff;h=43a931f8c6f291a7d0c055bc282bdc1847b299e7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/789819 Title: Lirc mceusb resume problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/789819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 789819] Re: Lirc mceusb resume problem
What is this business about: 8< Jun 16 19:28:46 htpc kernel: [ 186.431342] lirc_dev: module unloaded Jun 16 19:28:46 htpc kernel: [ 186.441789] lirc_dev: IR Remote Control driver registered, major 250 Jun 16 19:28:46 htpc kernel: [ 186.444385] ir_lirc_codec: Unknown parameter `lirc_dev' 8< You appear to have something still running (like that horrific xbmc script) that is doing BAD THINGS. I just tried to reproduce the problem here with a sane install, and the mceusb driver suspends and resumes just fine when you don't do crazy crap like trying to force-remove modules. Left an active session running, spitting out key data received by the mceusb hardware, and it picks up and keeps on working after a full suspend and resume cycle. As far as I'm concerned, there's no mceusb driver bug here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/789819 Title: Lirc mceusb resume problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/789819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 789819] Re: Lirc mceusb resume problem
Okay, so it looks like there may well be some work that needs to be done on the resume function of the mceusb driver. Getting that squared away is the real answer to this problem, not some highly questionable script. I have the topseed 1784:0008 device myself, should be able to reproduce (and fix) the problem in relatively short order. Sidebar: this bug really should have been reported at bugzilla.kernel.org and/or brought to the attention of the lirc or linux-media mailing lists, but then again, that why I (as a non-Ubuntu user) went ahead and subscribed myself to launchpad lirc bugs... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/789819 Title: Lirc mceusb resume problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/789819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 657954] Re: No default remote configuration was included for Hauppauge Nova-T 500; You will need to include your own custom configuration for this remote
Pretty sure that 2.6.32-era driver code for the Nova-T 500 doesn't support anything but a Hauppauge RC5 remote, without significant hacking. You may have better luck with a 2.6.38 kernel, or at least, a media_build replacement of all your v4l/dvb/rc code. http://www.linuxtv.org/wiki/index.php/How_to_Obtain ,_Build_and_Install_V4L-DVB_Device_Drivers Even then, you'll probably have some manual work to do to create key mappings for that remote. No clue what signals it actually sends. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/657954 Title: No default remote configuration was included for Hauppauge Nova-T 500; You will need to include your own custom configuration for this remote -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 794234] Re: imon and/or rc_imon_pad cause kernel oops
Which of the traces in the arch ticket are you seeing? The one Benjamin Hodgetts was seeing is definitely fixed in the upstream kernel, including the 2.6.38.y stable tree. The other one from nicoalas is news to me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/794234 Title: imon and/or rc_imon_pad cause kernel oops -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787735] Re: Snapstream Firefly non-functional
On Jun 7, 2011, at 12:31 AM, Dan Christian wrote: > Ya, but that's not something an ordinary user knows how to figure out. > I couldn't find any docs on how to setup devinput, what it is, or > when to use it. http://lirc.org/html/devinput.html > It's not at all clear from the documentation how to find and debug > each of these steps: > Which driver (the docs say the atilibusb driver is right, not > ati_remote; What docs are you referring to here? > but everything has changed in recent kernels). > What device (I didn't know which directory to look in the device tree, > which device file to pick, or why). See prior link. > What configuration lircd needs for that (hardware.conf setup isn't > actually documented). hardware.conf is a Debian creation that Ubuntu inherited from there. Upstream lirc has nothing to do with it, so I can't help there. > What lircd.conf is needed for the above steps (and why). The question of which lircd.conf is covered at that link. The why is because all devinput devices have keys mapped to the standard linux input layer key namespace, as defined in include/linux/input.h, so its impossible for a key to have any other value than the ones that are defined in that config. > What .lirc/mythtv file (actually, once irw works, this step isn't so hard). > > To make it even worse, what are the ir_* drivers that seems to get > loaded automatically? I couldn't find any info on them. 'modinfo ' is usually a start. You could also ask about them on the lirc or linux-media mailing lists. They're in-kernel decoders for raw IR hardware, used to map raw IR scancodes to linux input layer key namespace. > Are they stepping on the user's configuration? In this case, no, not at all. The firefly is RF. The IR decoders only have something to do if your receiver passes along raw IR samples. > The mythbuntu control panel is supposed to make this easy, but it was > crashing on me, and it's configuration was broken in 10.10 and 11.04. Well, the mythbuntu control panel is another piece of software that is completely and totally out of upstream lirc's control. I've never even seen it, let alone tried to use it. If its broken, well, that's on the people who maintain it. A fair amount has changed in the IR world lately, and its all been discussed 100% in the open on the lirc and linux-media mailing lists. (Nb: if it wasn't already understood, I don't actually use Ubuntu myself). > The software stack may work, but user's can't figure it out. I don't > want to belittle much hard work, but things don't look good from a > user perspective. Honestly, I have to blame hardware.conf's auto-population thing that the lirc deb runs and/or the mythbuntu control center for most of this. Its actually *very* simple to set these things up by hand. It seems like the tooling is just out of date with reality. > Thanks you for all your effort. I hope this view from a user's > perspective is constructive (but it feels like I'm whining about > something I got for free :-). Yes and no. I do know that a central documentation repository kept up to date with the latest and greatest information for how to configure every remote under the sun would be helpful. I just don't have the time to create such a thing. I do answer quite a bit of email on the aforementioned mailing lists though. The mythbuntu control center and hardware.conf issues are well out of my control though. -- Jarod Wilson ja...@wilsonet.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787735 Title: Snapstream Firefly non-functional -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 763412] Re: mceusb devices stopped working in natty
Its not "some conflict". The kernel has IR drivers in it now, with protocol decoders, so you get native linux input layer events from most stock remotes, no lirc required whatsoever. There's also an lirc bridge driver in the kernel for "legacy" mode, but the need to disable the in- kernel decoders when using it has been covered umpteen times on multiple mailing lists and forums, and *should* be handled automatically with the latest lirc initscript in ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/763412 Title: mceusb devices stopped working in natty -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787735] Re: Snapstream Firefly non-functional
I'm still quite sure ati_remote + lircd's devinput driver works just fine for the firefly hardware when you're talking to the right event device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787735 Title: Snapstream Firefly non-functional -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 789819] Re: Lirc mceusb resume problem
That "automatic lirc resume script" is full of fail. Wtf is it trying to rmmod/modprobing the driver for? Who comes up with this sort of dreadful crap? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/789819 Title: Lirc mceusb resume problem -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787735] Re: Snapstream Firefly non-functional
ati_remote apparently doesn't have everything in the driver properly wired up for udev to create the persistent symlink in by-id/, so you'll have to use some other means of discovery. You can point straight to a /dev/input/eventX device, or by name or phys, per http://lirc.org/html/devinput.html. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787735 Title: Snapstream Firefly non-functional -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787735] Re: Snapstream Firefly non-functional
You need to fill in REMOTE_DEVICE, per my prior comment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787735 Title: Snapstream Firefly non-functional -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787735] Re: Snapstream Firefly non-functional
Okay, dmesg looks much better. I'm assuming some "helpful" Ubuntu lirc package bit is adding that blacklist file. Remove it. Let ati_remote load. Instruct lircd to use the 'devinput' driver, with device '/dev/input/by-id/', and the lircd.conf.devinput config provided by lirc. Dunno how or if that's doable with the mythbuntu control center stuff, but its certainly doable by simply editing /etc/lirc/hardware.conf and lircd.conf by hand. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787735 Title: Snapstream Firefly non-functional -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787735] Re: Snapstream Firefly non-functional
Also, from dmesg: [ 31.654252] lirc_dev: IR Remote Control driver registered, major 61 [ 31.654621] ir_lirc_codec: Unknown symbol lirc_dev_fop_poll (err 0) [ 31.655146] ir_lirc_codec: Unknown symbol lirc_dev_fop_open (err 0) [ 31.655242] ir_lirc_codec: disagrees about version of symbol lirc_get_pdata [ 31.655245] ir_lirc_codec: Unknown symbol lirc_get_pdata (err -22) [ 31.655361] ir_lirc_codec: Unknown symbol lirc_dev_fop_close (err 0) [ 31.655453] ir_lirc_codec: Unknown symbol lirc_dev_fop_read (err 0) [ 31.655536] ir_lirc_codec: disagrees about version of symbol lirc_register_driver [ 31.655538] ir_lirc_codec: Unknown symbol lirc_register_driver (err -22) [ 31.655731] ir_lirc_codec: Unknown symbol lirc_dev_fop_ioctl (err 0) Please, please, please, remove the travesty that is lirc-modules-source and all its remnants. Its never going to work on 2.6.38. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787735 Title: Snapstream Firefly non-functional -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787735] Re: Snapstream Firefly non-functional
Ah, so you've blacklisted ati_remote, ok, that makes more sense then. But why do that? Let ati_remote load, and then use lircd's devinput mode. (Not that atilibusb shouldn't work too). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787735 Title: Snapstream Firefly non-functional -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787742] Re: lirc_atiusb non functional with snapstream firefly
"Editing atilibusb out of /etc/modprobe.d/lirc-blacklist allows the module to be loaded" is, um, well, nonsensical. Config files in /etc/modprobe.d/ are for configuring kernel module loading params. atilibusb isn't a kernel module. Its a userspace lircd driver plugin. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787742 Title: lirc_atiusb non functional with snapstream firefly -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787735] Re: Snapstream Firefly non-functional
lsusb and dmesg output after a clean boot please. My suspicion: the in- kernel ati_remote driver is already bound to it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787735 Title: Snapstream Firefly non-functional -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 626030] Re: lirc does not have support for ITE8708 receiver
This is now supported by the ite-cir driver that was merged in 2.6.39. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/626030 Title: lirc does not have support for ITE8708 receiver -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778296] Re: lirc not working correctly on 2.6.38 kernel
OP: Note also though: devinput mode with the windows media center rc-6 keymap loaded isn't going to work at all with a TiVo remote. You need to either load a tivo keymap (which I don't think exists until kernel 2.6.39 or .40), or just use the /dev/lirc0 method with the TiVo lircd.conf you were previously using. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/778296 Title: lirc not working correctly on 2.6.38 kernel -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778296] Re: lirc not working correctly on 2.6.38 kernel
There are two perfectly valid ways to use the mceusb driver, one is via the "default" lirc driver and /dev/lirc0, the other is using devinput and the mceusb device's input layer event device (or better, its symlink in /dev/input/by-id/). The current problem with trying to use devinput mode is that the lirc initscript is disabling all the in-kernel decoders, upon which devinput mode relies to get raw IR scancodes translated into Linux input layer event keycodes. The simple fix for this sort of thing I threw into the Fedora lirc initscripts was to NOT twiddle /sys/class/rc/rc*/protocols when the lirc driver mode is set to devinput. I'd suggest doing the same here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/778296 Title: lirc not working correctly on 2.6.38 kernel -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778026] [NEW] lirc-modules-source breaks in-kernel lirc support
Public bug reported: Binary package hint: lirc-modules-source Ubuntu 11.04 is shipping with a 2.6.38 kernel, which has numerous lirc device drivers from the staging tree enabled, as well as rc-core infrastructure and several new rc-core device drivers. The rc-core drivers and the in-kernel lirc device drivers rely on the lirc device interface driver (lirc_dev.ko) provided by the kernel to provide the lirc character device interface needed by lircd. Also shipping is an lirc-modules-source package, based on lirc 0.8.7-era out-of-tree lirc device driver code. When this package is installed and dkms builds modules, they override the in-kernel ones, most troubling being lirc_dev.ko: # find /lib/modules/$(uname -r)/ -name lirc_dev.ko /lib/modules/2.6.38-8-generic/kernel/drivers/media/rc/lirc_dev.ko /lib/modules/2.6.38-8-generic/updates/dkms/lirc_dev.ko Now when any of the in-kernel lirc drivers or an rc-core driver with support for the ir-lirc-codec bridge driver tries to load, you get something like the following: # modprobe ir-lirc-codec FATAL: Error inserting ir_lirc_codec (/lib/modules/2.6.38-8-generic/kernel/drivers/media/rc/ir-lirc-codec.ko): Unknown symbol in module, or unknown parameter (see dmesg) # dmesg | grep ir_lirc_codec [ 13.439407] ir_lirc_codec: Unknown symbol lirc_dev_fop_poll (err 0) [ 13.439557] ir_lirc_codec: Unknown symbol lirc_dev_fop_open (err 0) [ 13.439622] ir_lirc_codec: disagrees about version of symbol lirc_get_pdata [ 13.439623] ir_lirc_codec: Unknown symbol lirc_get_pdata (err -22) [ 13.439706] ir_lirc_codec: Unknown symbol lirc_dev_fop_close (err 0) [ 13.439770] ir_lirc_codec: Unknown symbol lirc_dev_fop_read (err 0) [ 13.439824] ir_lirc_codec: disagrees about version of symbol lirc_register_driver [ 13.439826] ir_lirc_codec: Unknown symbol lirc_register_driver (err -22) [ 13.439960] ir_lirc_codec: Unknown symbol lirc_dev_fop_ioctl (err 0) This completely breaks in-kernel drivers' lirc support. Please either stop shipping lirc-modules-source, or properly update it to build against the in-kernel lirc bits (and preferably, strip out the entirely redundant drivers). ** Affects: lirc (Ubuntu) Importance: Critical Status: Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/778026 Title: lirc-modules-source breaks in-kernel lirc support -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 663497] Re: Transmitter (irsend) broken in 10.10
http://lirc.git.sourceforge.net/git/gitweb.cgi?p=lirc/lirc;a=commitdiff;h=77c9429dde46f108ab4ba47791977abae3a6af3c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/663497 Title: Transmitter (irsend) broken in 10.10 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666493] Re: Maverick's imon kernel module does not support protocol switching (regression)
I've had at least one report that the 2.6.36 imon module behaves as expected for another imon/mce user -- but it does still require v4l- utils ir-keytable. However, I don't think the problem here is actually in the imon code itself, but rather in the ir layer, so simply pulling in imon.c from 2.6.36 into 2.6.35.x isn't likely to be sufficient to fix the problem. I do have an updated ir layer backported for 2.6.35 that I've patched into the Fedora kernels, which does work as well, but I've already been told its too invasive a patchset for an Ubuntu SRU kernel. However, another possible alternative... I *think* a ~10-line patch that adds back a modparam for choosing which ir protocol to use at module load time would work too. I actually put such a thing together for upstream, but in talking with others there, we decided against pushing it, as its expected that by the end of 2.6.37 development, we'll be uploading *all* keytables from userspace using udev anyway, so adding a modparam upstream would be irrelevant and/or redundant. -- Maverick's imon kernel module does not support protocol switching (regression) https://bugs.launchpad.net/bugs/666493 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 517956] Re: Timing problem (garbage characters) in lirc-driver for iMon PAD VFD 15c2:0036
I've patched a 5ms exit delay into the send_packet() function in lirc_imon in current lirc cvs (and in the merged-upstream-in-2.6.35 imon driver). The microsecond delays were a bit on the low side. This 5ms delay doesn't show any functional regressions on any of the three imon devices I've got, and does indeed fix garbage displaying on my own 0x0044 (Antec Veris Elite) VFD -- a problem that only cropped up with the latest motherboard in this system, its been just fine w/all other motherboards (*only* the motherboard was changed in this system, all other components are identical to a prior setup where the VFD behaved just fine). lirc 0.8.7 should be released within a week or three, and will carry this fix (as does the imon driver in 2.6.35+). -- Timing problem (garbage characters) in lirc-driver for iMon PAD VFD 15c2:0036 https://bugs.launchpad.net/bugs/517956 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 422035] Re: Syslog fills up with generic-usb "control queue full"
There's a patch for this in the 2.6.32.y stable tree: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.32.y.git;a=commitdiff;h=7e1228c91635433ff63583dbdc6f1a1249dd5116 -- Syslog fills up with generic-usb "control queue full" https://bugs.launchpad.net/bugs/422035 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 521878] Re: console keymap settings lost after reboot
** Description changed: Binary package hint: console-data I am running Lucid-amd64 on my machine. lsb_release -rd Description:Ubuntu lucid (development branch) Release:10.04 I installed it via: debootstrap --arch amd64 lucid /tftpboot/ubuntu-10.4 http://de.archive.ubuntu.com/ubuntu/ chroot /tftpboot/ubuntu-10.4 apt-get install language-pack-en apt-get install nfs-common linux-image-2.6.32-13-generic console-data ### I set the keymap to qwertz -> Germany -> latin1 - no dead keys. ### groupadd ... useradd ... passwd ... vigr ... After editing /etc/initramfs-tools/initramfs.conf for boot via NFS and updating the initrd, I bootet the machine via PXE and had an english keymap after first login. I then did "dpkg-reconfigure console-data". The following dialog showed the settings I did during install. After dpkg-reconfigure was done, I had the correct console keyboard layout again. But after a reboot, I was back to the English layout. Even with a working German layout I cannot type any Umlauts (äöü) or ß. dpkg -l|egrep "kbd|console-data|language-pack" shows the following: ii console-data 2:1.10-1 keymaps, fonts, charset maps, fallback table ii kbd 1.15-1ubuntu1 Linux console font and keytable utilities ii language-pack-en 1:10.04+20100206.1 translation updates for language English ii language-pack-en-base1:10.04+20100206.1 translations for language English - Thanks for your help. + + After some digging in /etc/init.d/ I found keyboard-setup and keymap.sh. + dpkg showed the files were contained in the following packets: + + dpkg -S /etc/init.d/keyboard-setup + console-setup: /etc/init.d/keyboard-setup + dpkg -S /etc/init.d/keymap.sh + console-common: /etc/init.d/keymap.sh + + After a look into /etc/init.d/keymap.sh I found the following lines: + + # If setupcon is present, then we've been superseded by console-setup. + if type setupcon >/dev/null 2>&1; then + exit 0 + fi + + After that I took a look into /etc/init.d/keyboard-setup. + + The last 4 lines in /etc/default/console-setup looked like this: + + XKBMODEL="pc105" + XKBLAYOUT="us" + XKBVARIANT="" + XKBOPTIONS="" + + That explains, why the machine always comes up with an English layout. + This also means I have to do "dpkg-reconfigure console-setup" to change the layout. + + So after installing console-data I would have expected at least a + warning , telling me that what ever I set up under this dialogue will + have no affect when console-setup is installed. + + Thank you. -- console keymap settings lost after reboot https://bugs.launchpad.net/bugs/521878 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 521878] Re: console keymap settings lost after reboot
** Description changed: Binary package hint: console-data I am running Lucid-amd64 on my machine. lsb_release -rd Description:Ubuntu lucid (development branch) Release:10.04 I installed it via: debootstrap --arch amd64 lucid /tftpboot/ubuntu-10.4 http://de.archive.ubuntu.com/ubuntu/ chroot /tftpboot/ubuntu-10.4 apt-get install language-pack-en apt-get install nfs-common linux-image-2.6.32-13-generic console-data ### I set the keymap to qwertz -> Germany -> latin1 - no dead keys. ### groupadd ... useradd ... passwd ... vigr ... - After editing /etc/initramfs-tools/initramfs.conf for boot via NFS and updating the initrd, I bootet the machine via PXE and had an english keymap after fist login. + After editing /etc/initramfs-tools/initramfs.conf for boot via NFS and updating the initrd, I bootet the machine via PXE and had an english keymap after first login. I then did "dpkg-reconfigure console-data". The following dialog showed the settings I did during install. After dpkg-reconfigure was done, I had the correct console keyboard layout again. But after a reboot, I was back to the English layout. Even with a working German layout I cannot type any Umlauts (äöü) or ß. dpkg -l|egrep "kbd|console-data|language-pack" shows the following: ii console-data 2:1.10-1 keymaps, fonts, charset maps, fallback table ii kbd 1.15-1ubuntu1 Linux console font and keytable utilities ii language-pack-en 1:10.04+20100206.1 translation updates for language English ii language-pack-en-base1:10.04+20100206.1 translations for language English Thanks for your help. -- console keymap settings lost after reboot https://bugs.launchpad.net/bugs/521878 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 521878] [NEW] console keymap settings lost after reboot
Public bug reported: Binary package hint: console-data I am running Lucid-amd64 on my machine. lsb_release -rd Description:Ubuntu lucid (development branch) Release:10.04 I installed it via: debootstrap --arch amd64 lucid /tftpboot/ubuntu-10.4 http://de.archive.ubuntu.com/ubuntu/ chroot /tftpboot/ubuntu-10.4 apt-get install language-pack-en apt-get install nfs-common linux-image-2.6.32-13-generic console-data ### I set the keymap to qwertz -> Germany -> latin1 - no dead keys. ### groupadd ... useradd ... passwd ... vigr ... After editing /etc/initramfs-tools/initramfs.conf for boot via NFS and updating the initrd, I bootet the machine via PXE and had an english keymap after fist login. I then did "dpkg-reconfigure console-data". The following dialog showed the settings I did during install. After dpkg-reconfigure was done, I had the correct console keyboard layout again. But after a reboot, I was back to the English layout. Even with a working German layout I cannot type any Umlauts (äöü) or ß. dpkg -l|egrep "kbd|console-data|language-pack" shows the following: ii console-data 2:1.10-1 keymaps, fonts, charset maps, fallback table ii kbd 1.15-1ubuntu1 Linux console font and keytable utilities ii language-pack-en 1:10.04+20100206.1 translation updates for language English ii language-pack-en-base1:10.04+20100206.1 translations for language English Thanks for your help. ** Affects: console-data (Ubuntu) Importance: Undecided Status: New -- console keymap settings lost after reboot https://bugs.launchpad.net/bugs/521878 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 477270] Re: XDMCP cannot be enabled via custom.conf
I forgot to provide the link to the docu page. Here it is: http://library.gnome.org/admin/gdm/stable/configuration.html.en -- XDMCP cannot be enabled via custom.conf https://bugs.launchpad.net/bugs/477270 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 477270] [NEW] XDMCP cannot be enabled via custom.conf
Public bug reported: Binary package hint: gdm I am running Ubuntu 9.10 x86_64 with gdm 2.28.1-0ubuntu1. According to point 5.4.4 on the Gnome gdm docu page an "Enable=true" under [xdmcp] in /etc/gdm/custom.conf should be sufficient to enable XDMCP from gdm. Unfortunately it isn't. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- XDMCP cannot be enabled via custom.conf https://bugs.launchpad.net/bugs/477270 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 468928] Re: no prompt to enter the admin passwort upon package installation
*** This bug is a duplicate of bug 442498 *** https://bugs.launchpad.net/bugs/442498 I have found a little HowTo, explaining how to populate the LDAP server under Ubuntu 9.10. See here: http://ubuntuforums.org/showpost.php?p=8161118&postcount=6 Please consider this problem solved. -- no prompt to enter the admin passwort upon package installation https://bugs.launchpad.net/bugs/468928 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 468928] [NEW] no prompt to enter the admin passwort upon package installation
Public bug reported: Binary package hint: slapd I'm running Ubuntu 9.10 x86_64 with package slapd version 2.4.18-0ubuntu1. Upon first installation of slapd, the user is not prompted to enter the admin password as described for Ubuntu 9.04 (see: https://help.ubuntu.com/9.04/serverguide/C/openldap-server.html) This is either a bug or the procedure of setting the password has changed. Neither "apt-get install slapd" nor "dkpg-reconfigure slapd" is prompting the user to enter the admin password. ** Affects: openldap (Ubuntu) Importance: Undecided Status: New -- no prompt to enter the admin passwort upon package installation https://bugs.launchpad.net/bugs/468928 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
Re: [Bug 176380] Re: Black Screen after Login with Asus P5K/Intel E4500/NVidia 8600GTS
Michael Nagel wrote: > is this still an issue? > > ** Changed in: linux-restricted-modules (Ubuntu) >Status: New => Incomplete > I do not have this motherboard and graphics card anymore, so I cannot tell if the problem still persists. Regards. André -- Black Screen after Login with Asus P5K/Intel E4500/NVidia 8600GTS https://bugs.launchpad.net/bugs/176380 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 281202] Re: e-mail redirect doesn't work correctly
Hi Sebastien, I've used Evolutioin 2.24.2 and it working fine now. Thanks for your help. Bob -- e-mail redirect doesn't work correctly https://bugs.launchpad.net/bugs/281202 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 281202] Re: e-mail redirect doesn't work
the receiver will reply to your e-mail address, and not to the address it originated from. -- e-mail redirect doesn't work https://bugs.launchpad.net/bugs/281202 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 281202] Re: e-mail redirect doesn't work
* Is this reproducible? Yes, it is reproducible. * If so, what specific steps should we take to recreate this bug? 1) open the mailbox, 2) double click on the email and a new windows appears 3) Click on "Message" and choose "Forward as" en choose "redirect" 4) Enter the new email adres and click "send" -- e-mail redirect doesn't work https://bugs.launchpad.net/bugs/281202 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 281202] Re: e-mail redirect doesn't work
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/18391317/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/18391318/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/18391319/ProcStatus.txt -- e-mail redirect doesn't work https://bugs.launchpad.net/bugs/281202 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 281202] [NEW] e-mail redirect doesn't work
Public bug reported: Binary package hint: evolution Hi, I'm trying to redirect an email i received in my inbox. The email was intended for our customer-ticket system. When I redirect the e-mail to the system with evolution, it looks like the e-mail is sent from my account in stead of the original sender. So the email is being forwarded instead of being redirected. ProblemType: Bug Architecture: i386 Date: Fri Oct 10 11:02:04 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/evolution NonfreeKernelModules: nvidia Package: evolution 2.22.3.1-0ubuntu1 PackageArchitecture: i386 ProcEnviron: PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution Uname: Linux 2.6.24-19-generic i686 ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- e-mail redirect doesn't work https://bugs.launchpad.net/bugs/281202 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 211892] Re: control modifier gets lost in hardy
I can confirm this bug too. with this bug, the whole system nearly unusable.. -- control modifier gets lost in hardy https://bugs.launchpad.net/bugs/211892 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 60475] Re: Problem with deleting files in amarok from within gnome.
Sarah is right, install kdebase-kio-plugins can fix this problem -- Problem with deleting files in amarok from within gnome. https://bugs.launchpad.net/bugs/60475 You received this bug notification because you are a member of Kubuntu Team, which is subscribed to amarok in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 208125] Re: wink: error while loading shared libraries: libexpat.so.0
after sudo ln -s /usr/lib/libexpat.so /usr/lib/libexpat.so.0 wink can launch, but seems its function not working. new a project and press the hotkeys no screenshot being done -- wink: error while loading shared libraries: libexpat.so.0 https://bugs.launchpad.net/bugs/208125 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 208125] [NEW] wink: error while loading shared libraries: libexpat.so.0
Public bug reported: Binary package hint: wink ubuntu: 8.04 [code] $ wink /usr/lib/wink/wink: error while loading shared libraries: libexpat.so.0: cannot open shared object file: No such file or directory [/code] can fix by: [code] sudo ln -s /usr/lib/libexpat.so /usr/lib/libexpat.so.0 [/code] ** Affects: wink (Ubuntu) Importance: Undecided Status: New -- wink: error while loading shared libraries: libexpat.so.0 https://bugs.launchpad.net/bugs/208125 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 207508] [NEW] no way to stop empathy startup with session
Public bug reported: Binary package hint: empathy ubuntu: 8.04 empathy: 0.22.0-1 after install empathy and launch it one time, now when i login gnome session, empathy will start too( i exit the empathy program before last logout) ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: empathy -- no way to stop empathy startup with session https://bugs.launchpad.net/bugs/207508 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 176380] Black Screen after Login with Asus P5K/Intel E4500/NVidia 8600GTS
Public bug reported: I installed Ubuntu 7.10 x86_64 on an Asus P5K with 2G RAM , Intel E4500, NVidia 8600GTS and a 250GB "SAMSUNG HD250HJ" HDD. After installation Gnome was working fine, but after installing the nvidia-glx-new driver(plus enabling) and rebooting, the screen went all black after logging in. dmesg noch shows the following: I could log on via SSH and set the display variable to ":0". I did that and started the restricted-manager. I unchecked the box and the desktop is almost back to normal. For some reason the desktop remains empty and dmesg shows the following: [ 2958.776056] gnome-panel[7756]: segfault at 2b39253f2c4c rip 2b391a09849e rsp 7fff923f44b0 error 4 [ 2958.941844] gnome-settings-[7748]: segfault at 2aab96cae8ff rip 2b4d7b2075b0 rsp 7fff3380ddd8 error 4 [ 2959.368031] nm-applet[7817]: segfault at 2ba548951eff rip 2ba4558c15b0 rsp 7fff5c33e5f8 error 4 [ 2959.486122] gnome-panel[7819]: segfault at 2aeb8cef8a18 rip 2aeb82ae77d9 rsp 7fff299a7210 error 4 [ 2959.738788] gnome-panel[7862]: segfault at 2ba67e9f7a18 rip 2ba6745e67d9 rsp 7fff37ea48c0 error 4 [ 2959.968660] gnome-panel[7926]: segfault at 2b0c2002ba18 rip 2b0c15c1a7d9 rsp 7fff968720e0 error 4 [ 2960.159160] gnome-panel[7983]: segfault at 2b10ecc87c4c rip 2b10e283d49e rsp 7fffc9c51cd0 error 4 [ 2960.436369] gnome-panel[8003]: segfault at 2b9c27439a18 rip 2b9c1d0287d9 rsp 7fff8f465cd0 error 4 [ 2960.709757] gnome-panel[8007]: segfault at 2b2ae75d7c4c rip 2b2add18d49e rsp 7fffcf301380 error 4 [ 2961.010446] gnome-panel[8010]: segfault at 2ba225bc6a18 rip 2ba21b7b57d9 rsp 7fff90cd64d0 error 4 [ 2961.213906] gnome-panel[8013]: segfault at 2b1480ceea18 rip 2b14768dd7d9 rsp 7fff35baf200 error 4 [ 2961.431945] gnome-panel[8016]: segfault at 2b4b81d75a18 rip 2b4b779647d9 rsp 7fff34b26180 error 4 [ 2961.540060] update-notifier[7799]: segfault at 2b5c4079bb3c rip 2b5c37ac77d9 rsp 7fff75df4110 error 4 [ 2961.616672] gnome-panel[8020]: segfault at 2b0eaf065c4c rip 2b0ea4c1b49e rsp 7fff078738f0 error 4 [ 2965.316531] gnome-settings-[8028]: segfault at 2b488c84 rip 2aeffc1457d9 rsp 7fffb006b7c0 error 4 [ 2965.548047] gnome-settings-[8035]: segfault at 2b488c84 rip 2b2e8c4fd7d9 rsp 7fff1fcb6400 error 4 [ 2965.745410] gnome-settings-[8043]: segfault at 2b488c84 rip 2ae0235a77d9 rsp 7fff88c0a360 error 4 [ 2965.913701] gnome-settings-[8050]: segfault at 2b488c84 rip 2abca2a8a7d9 rsp 7fff09728e70 error 4 [ 2966.133622] gnome-settings-[8057]: segfault at 2b488c84 rip 2b1b65c557d9 rsp 7fff4655bcb0 error 4 [ 2966.302847] gnome-settings-[8064]: segfault at 2b488c84 rip 2b826dd447d9 rsp 7fff3e46cbc0 error 4 [ 2966.471197] gnome-settings-[8071]: segfault at 2b488c84 rip 2ad06429d7d9 rsp 7fff47f16660 error 4 [ 2966.640074] gnome-settings-[8078]: segfault at 2b488c84 rip 2b32780657d9 rsp 7fff3414b8a0 error 4 [ 2966.815494] gnome-settings-[8085]: segfault at 2b488c84 rip 2b76475d37d9 rsp 7fff64bde330 error 4 [ 2967.119531] gnome-settings-[8093]: segfault at 2b488c84 rip 2ac16f1147d9 rsp 7fff3d09e7f0 error 4 Can those segfaults be related to the black screen problem? Or could this be the result of the update I ran today? I installed the machine today from CD and Gnome looked good before I updated the system. Thanks a lot for looking into it. ** Affects: ubuntu Importance: Undecided Status: New -- Black Screen after Login with Asus P5K/Intel E4500/NVidia 8600GTS https://bugs.launchpad.net/bugs/176380 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
