[Bug 1780071] Re: Error in system information after logging in to your account
I can confirm that the issue is still there in Ubuntu 18.04.4 LTS. I'm not sure if it counts, but landscape-client is not installed on the affected system. Instead there is landscape-common installed. I tried to add the package to the affected packages list of the bug, but without any success. Launchpad does simply not find landscape-common in project Ubuntu. Welcome to Ubuntu 18.04.4 LTS (GNU/Linux 4.15.0-96-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage System information as of Wed Apr 29 13:19:28 UTC 2020 System load: 1.14 Swap usage:0% Usage of /: 6.8% of 228.23GB Users logged in: 0 Memory usage: 9% IP address for enp3s0: 192.168.0.3 => There were exceptions while processing one or more plugins. See /var/log/landscape/sysinfo.log for more information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780071 Title: Error in system information after logging in to your account To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1780071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661682] Re: light-locker-settings has a missing dependency to python-gi
Workaround: $ sudo apt install python-gi After installing python-gi the light-locker-settings starts without issues. I think there is a missing dependency from package light-locker-settings to python-gi. Adding this dependency should fix this issue. $ apt-cache policy light-locker-settings light-locker-settings: Installiert: 1.5.0-0ubuntu2 Installationskandidat: 1.5.0-0ubuntu2 Versionstabelle: *** 1.5.0-0ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic $ inxi -bz System:Host: idefix Kernel: 4.15.0-96-generic x86_64 bits: 64 Desktop: Xfce 4.12.3 Distro: Ubuntu 18.04.4 LTS Machine: Device: laptop System: Acer product: AOD270 v: V1.10 serial: N/A Mobo: Acer model: JE01_CT serial: N/A BIOS: Insyde v: V1.10 date: 07/23/2013 BatteryBAT1: charge: 18.7 Wh 100.0% condition: 18.7/48.8 Wh (38%) CPU: Dual core Intel Atom N2600 (-MT-MCP-) speed/max: 816/1600 MHz Graphics: Card: Intel Atom Processor D2xxx/N2xxx Integrated Graphics Controller Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting (unloaded: fbdev,vesa) Resolution: 1024x600@60.03hz OpenGL: renderer: llvmpipe (LLVM 9.0, 128 bits) version: 3.3 Mesa 19.2.8 Network: Card-1: Realtek RTL810xE PCI Express Fast Ethernet controller driver: r8169 Card-2: Broadcom and subsidiaries BCM4313 802.11bgn Wireless Network Adapter driver: wl Drives:HDD Total Size: 320.1GB (2.8% used) Info: Processes: 172 Uptime: 29 min Memory: 1061.6/1981.9MB Client: Shell (bash) inxi: 2.3.56 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661682 Title: light-locker-settings has a missing dependency to python-gi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker-settings/+bug/1661682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661682] Re: light-locker-settings has a missing dependency to python-gi
I can confirm that for XUbuntu 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661682 Title: light-locker-settings has a missing dependency to python-gi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker-settings/+bug/1661682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848394] Re: software properteries shows "open source" for proprietary nvidia driver
It's the same on Ubuntu 18.04. $ LANG=C apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.32.12 Candidate: 0.96.24.32.12 Version table: *** 0.96.24.32.12 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 0.96.24.32.1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu bionic/main i386 Packages $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848394 Title: software properteries shows "open source" for proprietary nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1848394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857994] [NEW] no keyboard and mouse after exit from virtual terminal
Public bug reported: What I expected to happen: When exiting from virtual terminal I expected to get back to gnome session with working keyboard and mouse. What happened instead: When exiting from virtual terminal I was switched automatically back to (locked) gnome session and keyboard and mouse do not work any more. Sequence to reproduce the issue: Hint: tty1 and tty2 are used by X for display manager and gnome session. 1) Ctrl + Alt + F3 to switch from X to virtual terminal tty3 2) Login 3) Exit (switching back to X is performed automatically) 4) Result: keyboard/mouse do not work any more (stuck with unusable system until power off) See also: https://askubuntu.com/questions/1099608/exiting-from-virtual- terminal-and-automatically-going-back-to-x-disables-keyboar ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.33 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 31 14:15:50 2019 InstallationDate: Installed on 2018-08-01 (516 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=bdf52b6d-d54e-44a0-b2d6-323550a872c4 ro SourcePackage: systemd SystemdDelta: [MASKED] /etc/systemd/system/samba-ad-dc.service → /lib/systemd/system/samba-ad-dc.service [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1001 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970 PRO GAMING/AURA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1001:bd06/07/2017:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rn970PROGAMING/AURA:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. mtime.conffile..etc.systemd.system.conf: 2019-12-30T17:49:07.187140 mtime.conffile..etc.systemd.user.conf: 2019-12-30T17:49:49.868572 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857994 Title: no keyboard and mouse after exit from virtual terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1857994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817441] [NEW] lirc ITE8713 not working
Public bug reported: On Zotac ZBOX NANO AQ01 remote control with in build ir receiver does not work. $ irw # gives not output at all $ mode2 -d /dev/lirc0 # gives output $ sudo dpkg-reconfigure lirc # Windows Media Center Transceivers/Remotes (all) chosen $ sudo systemctl status lirc ● lirc.service - LSB: Starts LIRC daemon. Loaded: loaded (/etc/init.d/lirc; generated) Active: active (running) since Sun 2019-02-24 00:48:21 CET; 17min ago Docs: man:systemd-sysv-generator(8) Process: 6693 ExecStart=/etc/init.d/lirc start (code=exited, status=0/SUCCESS) Tasks: 1 (limit: 3976) CGroup: /system.slice/lirc.service └─6706 /usr/sbin/lircd --output=/run/lirc/lircd --device=/dev/lirc0 Feb 24 00:48:21 keksdose systemd[1]: Starting LSB: Starts LIRC daemon Feb 24 00:48:21 keksdose lirc[6693]: * Loading LIRC modules Feb 24 00:48:21 keksdose lirc[6693]:...done. Feb 24 00:48:21 keksdose lirc[6693]: * Starting remote control daemon(s) : Feb 24 00:48:21 keksdose lircd-0.9.0[6706]: lircd(default) ready, using /run/lirc/lircd Feb 24 00:48:21 keksdose lirc[6693]:...done. Feb 24 00:48:21 keksdose systemd[1]: Started LSB: Starts LIRC daemon.. Feb 24 00:48:24 keksdose lircd-0.9.0[6706]: accepted new client on /run/lirc/lircd Feb 24 00:48:50 keksdose lircd-0.9.0[6706]: removed client $ sudo ir-keytable Found /sys/class/rc/rc0/ (/dev/input/event4) with: Name: ITE8713 CIR transceiver Driver: ite-cir, table: rc-rc6-mce lirc device: /dev/lirc0 Supported protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp Enabled protocols: lirc bus: 25, vendor/product: 1283:, version: 0x Repeat delay = 500 ms, repeat period = 125 ms ** Affects: lirc (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/1817441 Title: lirc ITE8713 not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1817441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791409] Re: LIRC not working on Ubuntu 18.04
I can confirm the issue on Ubuntu 18.04 Server. If there is a fixed upstream version, what is needed to see an updated package in Ubuntu? Is there anything I can help with? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791409 Title: LIRC not working on Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1791409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773024] Re: Errors at boot
I can confirm the issue with freshly installed Ubuntu Server 18.04. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic $ sudo apt-cache policy linux-image-4.15.0-33-generic linux-image-4.15.0-33-generic: Installiert: 4.15.0-33.36 Installationskandidat: 4.15.0-33.36 Versionstabelle: *** 4.15.0-33.36 500 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status ** Changed in: linux (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/1773024 Title: Errors at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788235] Re: lirc broken on 18.04
I've tried the workaround, and it worked for me as described. :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788235 Title: lirc broken on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788235] Re: lirc broken on 18.04
I can confirm the issue on a recently fresh installed Ubuntu Server 18.04. The goal was to transform the installation to a HTPC running kodi and tvheadend (hts). Here are some links to guys who had the same experience and offer a workaround until the fix of the package. Same experience: https://forum.kodi.tv/showthread.php?tid=333904 Workaround: https://twosortoftechguys.wordpress.com/2018/07/24/make-lirc-work-in-ubuntu-18-04/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788235 Title: lirc broken on 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710995] Re: mythbuntu 16.04 install - whoopsie not online
I've reinstalled network-manager and commented out all lines associated to eth0 in /etc/network/interfaces. Now whoopsie is able to see if the system is connected to the inter net again. perhaps one "quick" solution could be making the package network-manager a hard dependency for whoopsie package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710995 Title: mythbuntu 16.04 install - whoopsie not online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1710995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710995] Re: mythbuntu 16.04 install - whoopsie not online
Restarting networking does not bring whoopsie online. $ sudo systemctl restart networking $ sudo systemctl status whoopsie ● whoopsie.service - crash report submission daemon Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor preset: enabled) Active: active (running) since Fr 2017-08-18 19:16:28 CEST; 56min ago Main PID: 1320 (whoopsie) CGroup: /system.slice/whoopsie.service └─1320 /usr/bin/whoopsie -f Aug 18 20:04:57 obelix whoopsie[1320]: [20:04:57] Cannot reach: https://daisy.ubuntu.com Aug 18 20:04:57 obelix whoopsie[1320]: [20:04:57] Cannot reach: https://daisy.ubuntu.com Aug 18 20:05:55 obelix whoopsie[1320]: [20:05:55] Cannot reach: https://daisy.ubuntu.com Aug 18 20:07:58 obelix whoopsie[1320]: [20:07:58] Not online; processing later (/var/crash/_lib_systemd_systemd-udevd.0.crash). Aug 18 20:10:25 obelix whoopsie[1320]: [20:10:25] Cannot reach: https://daisy.ubuntu.com Aug 18 20:10:25 obelix whoopsie[1320]: [20:10:25] Cannot reach: https://daisy.ubuntu.com Aug 18 20:10:25 obelix whoopsie[1320]: [20:10:25] Cannot reach: https://daisy.ubuntu.com Aug 18 20:10:26 obelix whoopsie[1320]: [20:10:26] Cannot reach: https://daisy.ubuntu.com Aug 18 20:10:27 obelix whoopsie[1320]: [20:10:27] Cannot reach: https://daisy.ubuntu.com Aug 18 20:10:27 obelix whoopsie[1320]: [20:10:27] Cannot reach: https://daisy.ubuntu.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710995 Title: mythbuntu 16.04 install - whoopsie not online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1710995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710995] Re: whoopsie not online
Yes, mythbuntu. $ lsb_release --all LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description:Ubuntu 16.04.3 LTS Release:16.04 Codename: xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710995 Title: whoopsie not online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1710995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710995] Re: whoopsie not online
Sure, let me know if you need more information. $ journalctl -u whoopsie -- Logs begin at Mi 2017-08-16 19:20:23 CEST, end at Mi 2017-08-16 20:49:31 CEST. -- Aug 16 19:20:29 obelix systemd[1]: Started crash report submission daemon. Aug 16 19:20:29 obelix whoopsie[1332]: [19:20:29] Using lock path: /var/lock/whoopsie/lock Aug 16 19:20:29 obelix whoopsie[1332]: [19:20:29] Could not get the Network Manager state: Aug 16 19:20:29 obelix whoopsie[1332]: [19:20:29] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files Aug 16 19:20:30 obelix whoopsie[1332]: [19:20:30] offline -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710995 Title: whoopsie not online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1710995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710995] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1710995/+attachment/4933488/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710995 Title: whoopsie not online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1710995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710995] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1710995/+attachment/4933489/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710995 Title: whoopsie not online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1710995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710995] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1710995/+attachment/4933486/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710995 Title: whoopsie not online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1710995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710995] Re: whoopsie not online
apport information ** Tags added: apport-collected autoreport-false ** Description changed: Reporting crashes from /var/crash/* is not possible any more. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: whoopsie 0.2.52.5 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CrashReports: 640:1000:139:81264064:2017-08-12 10:41:39.397392016 +0200:2017-08-16 00:23:25.391175383 +0200:/var/crash/_usr_bin_mythwelcome.1000.crash 640:0:139:936170:2017-08-12 17:56:15.728615283 +0200:2017-08-16 00:34:15.013084038 +0200:/var/crash/_lib_systemd_systemd-udevd.0.crash 640:1000:139:1194610:2017-08-11 17:52:56.113431094 +0200:2017-08-11 17:55:44.737433966 +0200:/var/crash/_usr_bin_xfce4-power-manager.1000.crash 640:1000:139:60309601:2017-08-16 00:18:13.511184669 +0200:2017-08-16 00:18:13.515184669 +0200:/var/crash/_usr_lib_x86_64-linux-gnu_kodi_kodi.bin.1000.crash Date: Wed Aug 16 00:37:18 2017 RelatedPackageVersions: apport-noui 2.20.1-0ubuntu2.10 SourcePackage: whoopsie UpgradeStatus: Upgraded to xenial on 2016-08-06 (374 days ago) + --- + ApportVersion: 2.20.1-0ubuntu2.10 + Architecture: amd64 + CurrentDesktop: XFCE + DistroRelease: Ubuntu 16.04 + NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia + Package: whoopsie 0.2.52.5 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 + RelatedPackageVersions: apport-noui N/A + Tags: xenial autoreport-false + Uname: Linux 4.10.0-32-generic x86_64 + UpgradeStatus: Upgraded to xenial on 2016-08-06 (374 days ago) + UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin mythtv netdev plugdev sambashare scanner tape vboxusers video + _MarkForUpload: True ** Attachment added: "CrashReports.txt" https://bugs.launchpad.net/bugs/1710995/+attachment/4933485/+files/CrashReports.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710995 Title: whoopsie not online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1710995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710995] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1710995/+attachment/4933487/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710995 Title: whoopsie not online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1710995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710995] Re: whoopsie not online
I think so. Curl gets the following answer. $ curl https://daisy.ubuntu.com Invalid BSON. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710995 Title: whoopsie not online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1710995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710995] Re: whoopsie not online
sjuk@obelix:/var/crash$ sudo systemctl status whoopsie ● whoopsie.service - crash report submission daemon Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor preset: enabled) Active: active (running) since Di 2017-08-15 23:58:15 CEST; 1h 9min ago Main PID: 1327 (whoopsie) CGroup: /system.slice/whoopsie.service └─1327 /usr/bin/whoopsie -f Aug 16 00:31:44 obelix whoopsie[1327]: [00:31:44] Not online; processing later (/var/crash/_lib_systemd_systemd-udevd.0.crash). Aug 16 00:34:18 obelix whoopsie[1327]: [00:34:18] Not online; processing later (/var/crash/_lib_systemd_systemd-udevd.0.crash). Aug 16 00:58:31 obelix whoopsie[1327]: [00:58:31] Not online; processing later (/var/crash/_usr_bin_mythwelcome.1000.crash). Aug 16 00:58:31 obelix whoopsie[1327]: [00:58:31] Not online; processing later (/var/crash/_usr_bin_mythwelcome.1000.crash). Aug 16 00:58:31 obelix whoopsie[1327]: [00:58:31] Not online; processing later (/var/crash/_lib_systemd_systemd-udevd.0.crash). Aug 16 00:58:31 obelix whoopsie[1327]: [00:58:31] Not online; processing later (/var/crash/_lib_systemd_systemd-udevd.0.crash). Aug 16 00:58:31 obelix whoopsie[1327]: [00:58:31] Not online; processing later (/var/crash/_usr_bin_xfce4-power-manager.1000.crash). Aug 16 00:58:31 obelix whoopsie[1327]: [00:58:31] Not online; processing later (/var/crash/_usr_bin_xfce4-power-manager.1000.crash) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710995 Title: whoopsie not online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1710995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710995] [NEW] whoopsie not online
Public bug reported: Reporting crashes from /var/crash/* is not possible any more. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: whoopsie 0.2.52.5 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CrashReports: 640:1000:139:81264064:2017-08-12 10:41:39.397392016 +0200:2017-08-16 00:23:25.391175383 +0200:/var/crash/_usr_bin_mythwelcome.1000.crash 640:0:139:936170:2017-08-12 17:56:15.728615283 +0200:2017-08-16 00:34:15.013084038 +0200:/var/crash/_lib_systemd_systemd-udevd.0.crash 640:1000:139:1194610:2017-08-11 17:52:56.113431094 +0200:2017-08-11 17:55:44.737433966 +0200:/var/crash/_usr_bin_xfce4-power-manager.1000.crash 640:1000:139:60309601:2017-08-16 00:18:13.511184669 +0200:2017-08-16 00:18:13.515184669 +0200:/var/crash/_usr_lib_x86_64-linux-gnu_kodi_kodi.bin.1000.crash Date: Wed Aug 16 00:37:18 2017 RelatedPackageVersions: apport-noui 2.20.1-0ubuntu2.10 SourcePackage: whoopsie UpgradeStatus: Upgraded to xenial on 2016-08-06 (374 days ago) ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug autoreport-true xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710995 Title: whoopsie not online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1710995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665998] [NEW] mythwelcome hangs and crashes on shutdown event
Public bug reported: Normally when initiating a restart mythtv (mythfrontend/mythwelcome) shuts down the system fast and clean. But restarting (from mythfrontend) the system needs several minutes to shutdown. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: mythtv 2:0.28.0+fixes.20160413.15cf421-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .var.log.mythtv.mythavtest.log: .var.log.mythtv.mythccextractor.log: .var.log.mythtv.mythjobqueue.log: .var.log.mythtv.mythlcdserver.log: .var.log.mythtv.mythmediaserver.log: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Feb 19 12:18:54 2017 Installed_mythtv_dbg: 0.0 PackageArchitecture: all SourcePackage: mythtv UpgradeStatus: Upgraded to xenial on 2016-08-06 (197 days ago) ** Affects: mythtv (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665998 Title: mythwelcome hangs and crashes on shutdown event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/1665998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665994] [NEW] kodi crashes on exit about every second time
Public bug reported: On exit I normally expect kodi to close fast and clean. But about every second time kodi hangs on exit and crashes with core and log. It seems that it doesn't matter if I use any function of kodi. Because I tried to start and exit kodi several times without playing any media or even navigating around. $ lsb_release -rd Description:Ubuntu 16.04.2 LTS Release:16.04 $ apt-cache policy kodi kodi: Installiert: 15.2+dfsg1-3ubuntu1 Installationskandidat: 15.2+dfsg1-3ubuntu1 Versionstabelle: *** 15.2+dfsg1-3ubuntu1 500 500 http://ftp.hosteurope.de/mirror/archive.ubuntu.com xenial/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: kodi 15.2+dfsg1-3ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Feb 19 11:57:40 2017 SourcePackage: kodi UpgradeStatus: Upgraded to xenial on 2016-08-06 (197 days ago) ** Affects: kodi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "kodi_crashlog-20170212_232651.log" https://bugs.launchpad.net/bugs/1665994/+attachment/4821905/+files/kodi_crashlog-20170212_232651.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665994 Title: kodi crashes on exit about every second time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1665994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1561010] [NEW] Ctrl+Alt+Keypad-Plus and -Minus does not work any more
Public bug reported: The following Shortcut-Keys does not work any more in ubuntu. Description from "man xorg" Ctrl+Alt+Keypad-Plus Change video mode to next one specified in the configuration file. This can be disabled with the DontZoom xorg.conf(5) file option. Ctrl+Alt+Keypad-Minus Change video mode to previous one specified in the configuration file. This can be disabled with the DontZoom xorg.conf(5) file option. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 352.63 Sat Nov 7 21:25:42 PST 2015 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.1) ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 23 15:11:49 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8554] InstallationDate: Installed on 2014-09-03 (566 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-83-generic root=UUID=9d89fa93-817a-4aa1-a48a-d8079899c384 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A87TD EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd03/08/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A87TDEVO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Mar 23 15:10:35 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputov519KEYBOARD, id 8 inputCHICONY HP Basic USB Keyboard KEYBOARD, id 9 inputLogitech USB Optical Mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561010 Title: Ctrl+Alt+Keypad-Plus and -Minus does not work any more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1561010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511973] [NEW] nvidia depends on linux headers
Public bug reported: Package nvidia-346 does not depend on linux-headers-generic. But without linux-headers the nvidia kernel module does not start. Description:Ubuntu 14.04.3 LTS Release:14.04 nvidia-346: Installiert: 346.96-0ubuntu0.0.1 Installationskandidat: 346.96-0ubuntu0.0.1 Versionstabelle: *** 346.96-0ubuntu0.0.1 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/restricted amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu/ trusty-security/restricted amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-346 346.96-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27 Uname: Linux 3.13.0-66-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 31 17:27:34 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-03 (422 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: nvidia-graphics-drivers-346 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-346 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511973 Title: nvidia depends on linux headers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-346/+bug/1511973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606491] Re: start: Job is already running: anacron
It affects me too (mythbuntu thrusty x64). Description:Ubuntu 14.04.2 LTS Release:14.04 anacron: Installiert: 2.3-20ubuntu1 Installationskandidat: 2.3-20ubuntu1 Versionstabelle: *** 2.3-20ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status subject: Cron start -q anacron || : body: start: Job is already running: anacron -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606491 Title: start: Job is already running: anacron To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/606491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1080366] Re: mythshutdown --unlock does not function anymore
I fixed it with this script. I don't remember exactly where I found it. But I think it was on the mythtv users mailing list. #!/bin/bash mask=16 mythshutdown --status status=$? while (($status & $mask)) do mythshutdown --unlock mythshutdown --status status=$? done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1080366 Title: mythshutdown --unlock does not function anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/1080366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1179180] Re: Impossible to open Empathy contact list window if already started with '-h' option
The issue is still there in trusty (14.04). So I will use pidgin again :-( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1179180 Title: Impossible to open Empathy contact list window if already started with '-h' option To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/1179180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1236657] Re: tmdb3.py crashed with TMDBRequestInvalid in handle_status(): Invalid id - The pre-requisite id is invalid or not found.
package added ** Project changed: mythbuntu => mythtv (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1236657 Title: tmdb3.py crashed with TMDBRequestInvalid in handle_status(): Invalid id - The pre-requisite id is invalid or not found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/1236657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] Re: upstart needs more than 100 seconds to start a desktop
Please perform a Stable Release Update... [Impact] * Boot time in 12.04 (LTS) takes 100 % longer than in 13.10 * LTS Release users will think ubuntu is slower than windows [Test Case] * activate bootchart, reboot and take a look in /var/lob/bootchart: about 45 sec. is normal / about 90 sec. is too much time [Regression Potential] * I don't know which package(s) have to be changed to solve the problem, but I would think of upstart to be involved * As there is already a fix in 13.10 I can offer you to test the fix on my computer, before publication Thank you :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] Re: upstart needs more than 100 seconds to start a desktop
Yes. I only upgrade to long term support release on productive machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] Re: upstart needs more than 100 seconds to start a desktop
See attached the rest of the the bootchart information... ** Attachment added: "asterix-precise-20130905-1.tgz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+attachment/3804008/+files/asterix-precise-20130905-1.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] Re: upstart needs more than 100 seconds to start a desktop
Hello Christopher M. Penalver, I tested it with the latest development release. System was up in about 45 seconds. The 12.04 installation needs about 90 seconds to boot up (look at bootchart in the attachment for details). If there is something I can test. Only ask ;-) ** Attachment added: "asterix-precise-20130905-1.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+attachment/3804007/+files/asterix-precise-20130905-1.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()
mythlogserver crashes on on frontend-mythbuntobox and on front-/backend- mythbuntubox, and it does unpredictable. Perhaps there is some hint in the mythfrontend.log (see attachment). ** Attachment added: "mythfrontend.log" https://bugs.launchpad.net/mythbuntu/+bug/1101395/+attachment/3711312/+files/mythfrontend.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1101395 Title: mythlogserver crashed with SIGSEGV in QObject::disconnect() To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1101395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] Re: upstart needs more than 100 seconds to start a desktop
kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] Re: upstart needs more than 100 seconds to start a desktop
I tested with witch kernel v3.7-rc6. The problem persists and the boot time increased to about 140 seconds. ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1081329] [NEW] mythtv-frontend crashes in scan for changes
Public bug reported: Description:Ubuntu 12.04.1 LTS Release:12.04 mythtv-frontend: Installiert: 2:0.25.2+fixes.20120802.46cab93-0ubuntu1 Kandidat:2:0.25.2+fixes.20120802.46cab93-0ubuntu1 Versionstabelle: *** 2:0.25.2+fixes.20120802.46cab93-0ubuntu1 0 500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/multiverse amd64 Packages 100 /var/lib/dpkg/status 2:0.25.0+fixes.20120410.1f5962a-0ubuntu1 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/multiverse amd64 Packages *** mythtv-frontend crashes in scan for changes. Before the scan I have marked a video as seen. (After every marking, the focus jumps to the very left.) And Filter is set to to show only unseen videos. *** ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: mythtv-frontend 2:0.25.2+fixes.20120802.46cab93-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-33.52-generic 3.2.31 Uname: Linux 3.2.0-33-generic x86_64 .var.log.mythtv.mythavtest.log: .var.log.mythtv.mythccextractor.log: .var.log.mythtv.mythcommflag.log: .var.log.mythtv.mythjobqueue.log: .var.log.mythtv.mythlcdserver.log: .var.log.mythtv.mythmediaserver.log: .var.log.mythtv.mythutil.log: ApportVersion: 2.0.1-0ubuntu15 Architecture: amd64 Date: Tue Nov 20 22:45:17 2012 Installed_mythtv_dbg: 0.0 MarkForUpload: True SourcePackage: mythtv UpgradeStatus: Upgraded to precise on 2012-05-17 (187 days ago) mtime.conffile..etc.mythtv.session.settings: 2010-06-12T13:31:59 ** Affects: mythtv (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1081329 Title: mythtv-frontend crashes in scan for changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/1081329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] Re: upstart needs more than 100 seconds to start a desktop
I added the needed log-files by "apport-collect 1004975" and changed the status of the bug to "Confirmed". ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1004975/+attachment/3437737/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1004975/+attachment/3437735/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1004975/+attachment/3437736/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1004975/+attachment/3437734/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1004975/+attachment/3437733/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1004975/+attachment/3437732/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1004975/+attachment/3437731/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1004975/+attachment/3437730/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1004975/+attachment/3437729/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1004975/+attachment/3437728/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1004975/+attachment/3437727/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] Card1.Codecs.codec.3.txt
apport information ** Attachment added: "Card1.Codecs.codec.3.txt" https://bugs.launchpad.net/bugs/1004975/+attachment/3437726/+files/Card1.Codecs.codec.3.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] Card1.Codecs.codec.2.txt
apport information ** Attachment added: "Card1.Codecs.codec.2.txt" https://bugs.launchpad.net/bugs/1004975/+attachment/3437725/+files/Card1.Codecs.codec.2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] Card1.Codecs.codec.1.txt
apport information ** Attachment added: "Card1.Codecs.codec.1.txt" https://bugs.launchpad.net/bugs/1004975/+attachment/3437724/+files/Card1.Codecs.codec.1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] Card1.Codecs.codec.0.txt
apport information ** Attachment added: "Card1.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1004975/+attachment/3437723/+files/Card1.Codecs.codec.0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1004975/+attachment/3437721/+files/Card0.Codecs.codec.0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] Card1.Amixer.values.txt
apport information ** Attachment added: "Card1.Amixer.values.txt" https://bugs.launchpad.net/bugs/1004975/+attachment/3437722/+files/Card1.Amixer.values.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] Card0.Amixer.values.txt
apport information ** Attachment added: "Card0.Amixer.values.txt" https://bugs.launchpad.net/bugs/1004975/+attachment/3437720/+files/Card0.Amixer.values.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1004975/+attachment/3437719/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] AlsaDevices.txt
apport information ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/1004975/+attachment/3437717/+files/AlsaDevices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] AplayDevices.txt
apport information ** Attachment added: "AplayDevices.txt" https://bugs.launchpad.net/bugs/1004975/+attachment/3437718/+files/AplayDevices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] Re: upstart needs more than 100 seconds to start a desktop
apport information ** Tags added: apport-collected running-unity ** Description changed: When turning on my desktop I expect to wait from 25 to 30 seconds until the login screen appears. But I have to wait more than 100 seconds until the login screen appears (look at the bootchart attachment). Is there any I can do to improve the boot time? Thank you ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: upstart 1.5-0ubuntu7 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Sat May 26 21:58:36 2012 EcryptfsInUse: Yes SourcePackage: upstart UpgradeStatus: Upgraded to precise on 2012-05-15 (11 days ago) + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. + ApportVersion: 2.0.1-0ubuntu15 + Architecture: amd64 + ArecordDevices: + List of CAPTURE Hardware Devices + card 0: SB [HDA ATI SB], device 0: VT1818S Analog [VT1818S Analog] +Subdevices: 2/2 +Subdevice #0: subdevice #0 +Subdevice #1: subdevice #1 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: sjuk 3967 F pulseaudio + /dev/snd/controlC0: sjuk 3967 F pulseaudio + CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. + Card0.Amixer.info: + Card hw:0 'SB'/'HDA ATI SB at 0xfbcf4000 irq 16' +Mixer name : 'VIA VT1818S' +Components : 'HDA:11060440,10438417,0010' +Controls : 46 +Simple ctrls : 23 + Card1.Amixer.info: + Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' +Mixer name : 'Nvidia GPU 12 HDMI/DP' +Components : 'HDA:10de0012,10de0101,00100100' +Controls : 24 +Simple ctrls : 4 + DistroRelease: Ubuntu 12.04 + EcryptfsInUse: Yes + HibernationDevice: RESUME=UUID=f41ab4fa-62ec-4fee-8abf-d80b2d9f1401 + IwConfig: + lono wireless extensions. + + eth0 no wireless extensions. + MachineType: System manufacturer System Product Name + MarkForUpload: True + NonfreeKernelModules: nvidia + Package: linux (not installed) + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic root=UUID=2a7737e5-1a4f-4465-be2d-2a2107c9268e ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 + RelatedPackageVersions: + linux-restricted-modules-3.2.0-32-generic N/A + linux-backports-modules-3.2.0-32-generic N/A + linux-firmware1.79.1 + RfKill: + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no + Tags: precise running-unity + Uname: Linux 3.2.0-32-generic x86_64 + UpgradeStatus: Upgraded to precise on 2012-05-15 (187 days ago) + UserGroups: adm admin audio cdrom chipcard cyberjack dialout dip disk fax floppy fuse lpadmin mythtv netdev plugdev powerdev sambashare scanner tape video voice + WifiSyslog: + + dmi.bios.date: 03/08/2011 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 2001 + dmi.board.asset.tag: To Be Filled By O.E.M. + dmi.board.name: M4A87TD EVO + dmi.board.vendor: ASUSTeK Computer INC. + dmi.board.version: Rev 1.xx + dmi.chassis.asset.tag: Asset-1234567890 + dmi.chassis.type: 3 + dmi.chassis.vendor: Chassis Manufacture + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd03/08/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A87TDEVO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: + dmi.product.name: System Product Name + dmi.product.version: System Version + dmi.sys.vendor: System manufacturer ** Attachment added: "AcpiTables.txt" https://bugs.launchpad.net/bugs/1004975/+attachment/3437716/+files/AcpiTables.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1080366] [NEW] mythshutdown --unlock does not function anymore
Public bug reported: Description:Ubuntu 12.04.1 LTS Release:12.04 mythtv-common: Installiert: 2:0.25.2+fixes.20120802.46cab93-0ubuntu1 Kandidat:2:0.25.2+fixes.20120802.46cab93-0ubuntu1 Versionstabelle: *** 2:0.25.2+fixes.20120802.46cab93-0ubuntu1 0 500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/multiverse amd64 Packages 100 /var/lib/dpkg/status 2:0.25.0+fixes.20120410.1f5962a-0ubuntu1 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/multiverse amd64 Packages *** "mythshutdown --unlock" does not unlock anymore. *** $ mythshutdown --unlock --verbose all 2012-11-18 15:59:39.419946 C mythshutdown version: fixes/0.25 [v0.25.2-15-g46cab93] www.mythtv.org 2012-11-18 15:59:39.419966 C Qt version: compile: 4.8.1, runtime: 4.8.1 2012-11-18 15:59:39.419972 N Enabled verbose msgs: all 2012-11-18 15:59:39.419991 N Setting Log Level to LOG_INFO 2012-11-18 15:59:39.420035 I Added logging to the console 2012-11-18 15:59:39.420043 I Added database logging to table logging 2012-11-18 15:59:39.420140 N Setting up SIGHUP handler 2012-11-18 15:59:39.420195 N Using runtime prefix = /usr 2012-11-18 15:59:39.420210 N Using configuration directory = /home/sjuk/.mythtv 2012-11-18 15:59:39.420296 E (old)Settings::ReadSettings(settings.txt) - No such file settings.txt 2012-11-18 15:59:39.420362 I Assumed character encoding: de_DE.UTF-8 2012-11-18 15:59:39.421398 E (old)Settings::ReadSettings(settings.txt) - No such file settings.txt 2012-11-18 15:59:39.421455 E (old)Settings::ReadSettings(/usr/share/mythtv/mysql.txt) - No such file /usr/share/mythtv/mysql.txt 2012-11-18 15:59:39.421489 E (old)Settings::ReadSettings(/usr/etc/mythtv/mysql.txt) - No such file /usr/etc/mythtv/mysql.txt 2012-11-18 15:59:39.421751 E (old)Settings::ReadSettings(./mysql.txt) - No such file ./mysql.txt 2012-11-18 15:59:39.421833 N Empty LocalHostName. 2012-11-18 15:59:39.421852 I Using localhost value of obelix 2012-11-18 15:59:39.421875 I Clearing Settings Cache. 2012-11-18 15:59:39.422194 I DefaultUPnP() - No default UPnP backend 2012-11-18 15:59:39.41 I Testing network connectivity to '192.168.0.3' 2012-11-18 15:59:39.422879 I Starting process manager 2012-11-18 15:59:39.422972 I Starting process signal handler 2012-11-18 15:59:39.424820 I Managed child (PID: 4920) has started! * command=ping -t 3 -c 1 192.168.0.3 >/dev/null 2>&1, timeout=0 2012-11-18 15:59:39.425393 I Starting IO manager (read) 2012-11-18 15:59:39.425568 I Starting IO manager (write) 2012-11-18 15:59:39.523237 I Managed child (PID: 4920) has exited! command=ping -t 3 -c 1 192.168.0.3 >/dev/null 2>&1, status=0, result=0 2012-11-18 15:59:39.523598 I Clearing Settings Cache. 2012-11-18 15:59:39.544013 I Database connection created: DBManager0 2012-11-18 15:59:39.544098 I New DB connection, total: 1 2012-11-18 15:59:39.552598 I Connected to database 'mythconverg' at host: 192.168.0.3 2012-11-18 15:59:39.561461 I Closing DB connection named 'DBManager0' 2012-11-18 15:59:39.561680 I Clearing Settings Cache. 2012-11-18 15:59:39.561773 I Database connection created: DBManager1 2012-11-18 15:59:39.561813 I New DB connection, total: 1 2012-11-18 15:59:39.563579 I Connected to database 'mythconverg' at host: 192.168.0.3 2012-11-18 15:59:39.567230 N Setting QT default locale to de_DE 2012-11-18 15:59:39.567427 I Current locale de_DE 2012-11-18 15:59:39.567558 N Reading locale defaults from /usr/share/mythtv//locales/de_de.xml 2012-11-18 15:59:39.588657 I Enabling Settings Cache. 2012-11-18 15:59:39.588672 I Clearing Settings Cache. 2012-11-18 15:59:39.588710 I Mythshutdown: --unlock 2012-11-18 15:59:39.603945 I MythCoreContext: Connecting to backend server: 192.168.0.3:6543 (try 1 of 1) 2012-11-18 15:59:39.604836 I MythSocket(1d38180:13): IP is local, using loopback address instead 2012-11-18 15:59:39.604864 I MythSocket(1d38180:13): attempting connect() to (127.0.0.1:6543) 2012-11-18 15:59:39.604901 I MSocketDevice::connect: setting Protocol to IPv4 2012-11-18 15:59:39.604908 I MSocketDevice::connect: attempting to create new socket 2012-11-18 15:59:39.605120 I MythSocket(1d38180:13): write -> 13 30 MYTH_PROTO_VERSION 72 D78EFD6F 2012-11-18 15:59:39.605894 I MythSocket(1d38180:13): read <- 13 13 ACCEPT[]:[]72 2012-11-18 15:59:39.605923 I Using protocol version 72 2012-11-18 15:59:39.605958 I MythSocket(1d38180:13): write -> 13 21 ANN Playback obelix 0 2012-11-18 15:59:39.606595 I MythSocket(1d38180:13): read <- 13 2 OK 2012-11-18 15:59:39.606724 I MythSocket(1d36a20:14): IP is local, using loopback address instead 2012-11-18 15:59:39.606749 I MythSocket(1d36a20:14): attempting connect() to (127.0.0.1:6543) 2012-11-18 15:59:39.606771 I MSocketDevice::connect: setting Protocol to IPv4 2012-11-18 15:59:39.606778 I MSocketDevice::connect: attempting to create new socket 2012-11-18 15:59:39.606957 I MythSocket(1d36a20:14): w
[Bug 1048167] Re: brasero does not eject disk after burning
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1048167 Title: brasero does not eject disk after burning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1048167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1048167] [NEW] brasero does not eject disk after burning
Public bug reported: Description:Ubuntu 12.04.1 LTS Release:12.04 brasero: Installiert: 3.4.1-0ubuntu1 Kandidat:3.4.1-0ubuntu1 Versionstabelle: *** 3.4.1-0ubuntu1 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status When burning a disc (audio, data, or from iso-image) I always check the 'eject after burn' option, but it never does eject. I have to use the button on the drive to get my new disc out. The discs themselves are OK. In detail: After successfully burning a CD, brasero asked to "please eject the CD yourself" (or similar, I've it in german language). So I eject it. And the dialog doesn't disappear and the only option available remains the "Cancel" button. It should be "OK", to acknowledge that I've ejected the CD. I hesitated and didn't know exactly what it would cancel… Please see also bugs #474233 and #549184. It's a quite old issue. But it still remains :-( Please reopen #474233 and fix the issue for LTS Ubuntu 12.04. Thank you ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: brasero 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27 Uname: Linux 3.2.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 Date: Sun Sep 9 11:04:24 2012 EcryptfsInUse: Yes SourcePackage: brasero UpgradeStatus: Upgraded to precise on 2012-05-15 (116 days ago) ** Affects: brasero (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1048167 Title: brasero does not eject disk after burning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1048167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 474233] Re: brasero does not eject disk after burning
This bug is still present in Brasero 3.4.1 on Ubuntu 12.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/474233 Title: brasero does not eject disk after burning To manage notifications about this bug go to: https://bugs.launchpad.net/brasero/+bug/474233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000973] Re: Mencoder error: Error, Invalid timestamp=1, last=1, encoding to mpeg4
I do not know what the meaning of "LMDE" is. But sure is that one mencoder instruction fails with 64 bit package while 32 bit package does a good job. What can I do to get closer to the origin of the failure (mencoder/mplayer or some libs?!?). what should I test? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000973 Title: Mencoder error: Error, Invalid timestamp=1, last=1, encoding to mpeg4 To manage notifications about this bug go to: https://bugs.launchpad.net/medibuntu/+bug/1000973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000973] Re: Mencoder error: Error, Invalid timestamp=1, last=1, encoding to mpeg4
Thanks to thomlark, who delivered the proof that there is a problem with the 64-bit mencoder. Is there any one who can fix it? I can test the fixed package. Let me know i I should test something... ** Changed in: medibuntu Status: Incomplete => Confirmed ** Changed in: mplayer (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000973 Title: Mencoder error: Error, Invalid timestamp=1, last=1, encoding to mpeg4 To manage notifications about this bug go to: https://bugs.launchpad.net/medibuntu/+bug/1000973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000973] Re: Mencoder error: Error, Invalid timestamp=1, last=1, encoding to mpeg4
I use divxenc as frontend. Here is what it writes into it's batchfile. #!/bin/bash # Automatically generated by divxenc 1.6.4 on So 3. Jun 17:45:10 CEST 2012 ### START OF COMMANDS ### test -d "/home/sjuk" || mkdir -p "/home/sjuk" test -d "/home/sjuk/.divxenc/job15834" || mkdir -p "/home/sjuk/.divxenc/job15834" test -e "/home/sjuk/TORNADO.avi" && mv -f "/home/sjuk/TORNADO.avi" "/home/sjuk/TORNADO.avi.old" nice -n 10 /usr/bin/mencoder "dvd://12" -o "/home/sjuk/TORNADO.avi" -vc mpeg12 -dvd-device /home/sjuk/Desktop/test.iso -nosub -ffourcc DX50 -vf softskip,harddup -noodml -aid 128 -channels 6 -oac copy -ovc lavc -lavcopts vcodec=mpeg4:vqscale=3:vmax_b_frames=2:vme=4:mbd=2:bidir_refine=1:cmp=2:subcmp=2:dia=-1:trell:cbp:mv0:last_pred=2:preme=1:autoaspect:threads=2 sleep 2 rm -rf "/home/sjuk/.divxenc/job15834" END OF COMMANDS I upgraded ubuntu from 11.04 to 12.04 two weeks ago. On 11.04 divxenc/mencoder worked fine. I don't know about "avconv". What does it do and how can you use it to convert divx from an iso-file? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000973 Title: Mencoder error: Error, Invalid timestamp=1, last=1, encoding to mpeg4 To manage notifications about this bug go to: https://bugs.launchpad.net/medibuntu/+bug/1000973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000973] Re: Mencoder error 64 bit U12.04
I can confirm. And it's the same with the ubuntu mencoder-/mplayer- package on 64-bit. ** Also affects: mplayer (Ubuntu) Importance: Undecided Status: New ** Changed in: medibuntu Status: New => Confirmed ** Changed in: mplayer (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000973 Title: Mencoder error 64 bit U12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/medibuntu/+bug/1000973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005224] Re: Video frame buffering failed too many times
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005224 Title: Video frame buffering failed too many times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/1005224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005224] [NEW] Video frame buffering failed too many times
Public bug reported: While watching tv video freezes and falls back to main menu. I'm using a combination of front- and backend on one mythbuntu-box. Here you can see what mythfrontend wrote to its logfile: May 27 15:32:58 obelix mythfrontend[2860]: W Decoder ringbuffer.cpp:1022 (WaitForReadsAllowed) RingBuf(myth://192.168.0.3:6543/11301_2012052715200 0.mpg): Taking too long to be allowed to read.. May 27 15:32:58 mythfrontend[2860]: last message repeated 6 times May 27 15:32:58 obelix mythfrontend[2860]: N CoreContext mythplayer.cpp:2079 (PrebufferEnoughFrames) Player(0): Waited 8509ms for video buffers AA uUuUAULAUAuLAP May 27 15:32:58 obelix mythfrontend[2860]: W Decoder ringbuffer.cpp:1022 (WaitForReadsAllowed) RingBuf(myth://192.168.0.3:6543/11301_2012052715200 0.mpg): Taking too long to be allowed to read.. May 27 15:33:02 mythfrontend[2860]: last message repeated 3 times May 27 15:33:02 obelix mythfrontend[2860]: E Decoder avformatdecoder.cpp:4374 (GetFrame) decoding error#012#011#011#011eno: Eingabe-/Ausgabefehler (5) May 27 15:33:08 mythfrontend[2860]: last message repeated 338 times May 27 15:33:08 obelix mythfrontend[2860]: N CoreContext mythplayer.cpp:2079 (PrebufferEnoughFrames) Player(0): Waited 6874ms for video buffers AAUuAUALALAfAAUuUAAAUAUAAUAAUUAP May 27 15:33:08 obelix mythfrontend[2860]: E Decoder avformatdecoder.cpp:4374 (GetFrame) decoding error#012#011#011#011eno: Eingabe-/Ausgabefehler (5) May 27 15:33:26 mythfrontend[2860]: last message repeated 459 times May 27 15:33:26 obelix mythfrontend[2860]: W CoreContext mythplayer.cpp:2962 (PauseDecoder) Player(0): Waited 100ms for decoder to pause May 27 15:33:31 mythfrontend[2860]: last message repeated 52 times May 27 15:33:31 obelix mythfrontend[2860]: W CoreContext mythpainter.cpp:32 (~MythPainter) MythPainter: 23 images not yet de-allocated. May 27 15:33:31 obelix mythfrontend[2860]: I CoreContext audio/audiopulsehandler.cpp:320 (SuspendInternal) Pulse: PulseAudio resume OK May 27 15:33:32 obelix mythfrontend[2860]: I CoreContext tv_play.cpp:2358 (HandleStateChange) TV: Changing from WatchingLiveTV to None May 27 15:33:32 obelix mythfrontend[2860]: I CoreContext tv_play.cpp:380 (StartTV) TV: Exiting main playback loop. May 27 15:33:32 obelix mythfrontend[2860]: I CoreContext tv_play.cpp:2121 (HandleStateChange) TV: Attempting to change from None to WatchingLiveTV May 27 15:33:32 obelix mythfrontend[2860]: I CoreContext mythcorecontext.cpp:371 (ConnectCommandSocket) MythCoreContext: Connecting to backend server: 192.168.0.3:6543 (try 1 of 1) May 27 15:33:32 obelix mythfrontend[2860]: I CoreContext mythcorecontext.cpp:1178 (CheckProtoVersion) Using protocol version 72 May 27 15:33:32 obelix mythfrontend[2860]: N CoreContext tv_play.cpp:2186 (HandleStateChange) TV: Spawning LiveTV Recorder -- begin May 27 15:33:32 obelix mythfrontend[2860]: N CoreContext tv_play.cpp:2193 (HandleStateChange) TV: Spawning LiveTV Recorder -- end May 27 15:33:32 obelix mythfrontend[2860]: I CoreContext tv_play.cpp:2214 (HandleStateChange) TV: playbackURL(myth://192.168.0.3:6543/11301_20120527153332.mpg) cardtype(DUMMY) May 27 15:33:32 obelix mythfrontend[2860]: E CoreContext tv_play.cpp:2231 (HandleStateChange) TV: LiveTV not successfully started May 27 15:33:32 obelix mythfrontend[2860]: I CoreContext tv_play.cpp:2449 (HandleStateChange) TV: Main UI disabled. May 27 15:33:32 obelix mythfrontend[2860]: I CoreContext tv_play.cpp:378 (StartTV) TV: Entering main playback loop. May 27 15:33:32 obelix mythfrontend[2860]: I CoreContext screensaver-x11.cpp:161 (RestoreDPMS) ScreenSaverX11Private: DPMS Reactivated 1 May 27 15:33:33 obelix mythfrontend[2860]: I CoreContext screensaver-x11.cpp:149 (DisableDPMS) ScreenSaverX11Private: DPMS Deactivated 1 May 27 15:33:33 obelix mythfrontend[2860]: I CoreContext tv_play.cpp:380 (StartTV) TV: Exiting main playback loop. May 27 15:33:33 obelix mythfrontend[2860]: N CoreContext mythmainwindow.cpp:2583 (PauseIdleTimer) Suspending idle timer Pleas help Thank you ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: mythtv 2:0.25.0+fixes.20120410.1f5962a-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 .var.log.mythtv.mythavtest.log: .var.log.mythtv.mythccextractor.log: .var.log.mythtv.mythcommflag.log: .var.log.mythtv.mythfilldatabase.log: .var.log.mythtv.mythjobqueue.log: .var.log.mythtv.mythlcdserver.log: .var.log.mythtv.mythmediaserver.log: .var.log.mythtv.mythutil.log: ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Sun May 27 18:49:14 2012 Installed_mythtv_dbg: 0.0 PackageArchitecture: all ProcEnviron: LANGUAGE=de_DE:de TERM=xterm PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: mythtv UpgradeStatus: Upgraded to precise on 2012-05-17 (10 days ago) ** Affects: mythtv (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You
[Bug 1004975] Re: upstart needs more than 100 seconds to start a desktop
And the upstart logs ** Attachment added: "upstart logs" https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1004975/+attachment/3164717/+files/upstart_logs.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] Re: upstart needs more than 100 seconds to start a desktop
Here the logs from bootchart... ** Attachment added: "bootchart logs" https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1004975/+attachment/3164716/+files/asterix-precise-20120526-4.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] Re: upstart needs more than 100 seconds to start a desktop
Here is a recent bootchart picture... ** Attachment added: "bootchart" https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1004975/+attachment/3164701/+files/bootchart.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] Re: upstart needs more than 100 seconds to start a desktop
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004975] [NEW] upstart needs more than 100 seconds to start a desktop
Public bug reported: When turning on my desktop I expect to wait from 25 to 30 seconds until the login screen appears. But I have to wait more than 100 seconds until the login screen appears (look at the bootchart attachment). Is there any I can do to improve the boot time? Thank you ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: upstart 1.5-0ubuntu7 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Sat May 26 21:58:36 2012 EcryptfsInUse: Yes SourcePackage: upstart UpgradeStatus: Upgraded to precise on 2012-05-15 (11 days ago) ** Affects: upstart (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004975 Title: upstart needs more than 100 seconds to start a desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1004975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004973] Re: test sound in gnome-control-center does not work
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004973 Title: test sound in gnome-control-center does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1004973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004973] [NEW] test sound in gnome-control-center does not work
Public bug reported: The problem: When klicking in "gnome-control-center sound" -> "test sound" on button "test" I expect to here any sound, or at least a visual feedback that there was playing a sound. Instead of that I get nothing of the expected. Klicking on the button leads to nothing :-( The reason: After searching the net and playing around in synaptic I installed "libcanberra-pulse". After that both expected feedbacks (visual and audible) came along in the test-facility of gnome-control-center. The solution: Please add libcanberra-pulse as a "hard" dependency to package gnome- control-center. Thank you ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Sat May 26 21:26:13 2012 EcryptfsInUse: Yes SourcePackage: gnome-control-center UpgradeStatus: Upgraded to precise on 2012-05-15 (11 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup22.0-0ubuntu2 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu2 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004973 Title: test sound in gnome-control-center does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1004973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 933308] Re: cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer configuration
I can confirm $ sudo zcat cups.log.* cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer configuration cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer configuration cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer configuration cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer configuration cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer configuration cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer configuration cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer configuration cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer configuration -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933308 Title: cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/933308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 710077] Re: no mic with ATI HDA SBx00 Azalia (VT1818S)
Thank you for for your help. But I don't have the time to try this now. After the next update of ubuntu I will try the on board sound card again. For now I can live with the separate sound card. Never touch a running system ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/710077 Title: no mic with ATI HDA SBx00 Azalia (VT1818S) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/710077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 710077] Re: no mic with ATI HDA SBx00 Azalia (VT1818S)
Thank you for your hint. But I don't think that it will help. Now I'm using natty (11.04) and there is no linux-backports-modules- alsa-generic package any more. And the problems with the on board sound card persists in natty. Now I use a separate sound card to workaround the problems with the ATI HDA SBx00 Azalia (VT1818S) chip. Not elegant but practical :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/710077 Title: no mic with ATI HDA SBx00 Azalia (VT1818S) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/710077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 596539] Re: mythexport does not honor an existing cutlist
What a pity. In my opinion a "config" should be a what it is, and no "script". On the one hand it is a good thing that the mythexport-config can handle anything you want (cause of the fact that it is a perl module). But on the outher hand I would say end users should only have to decide which features to use or not, and how. For the normal end user it will be to difficult and error-prone to edit such a config. I recommend to move the perl-module into the feature-part of the code and provide "clean" config-file. Another Idea would be to merge mythtranscode and mythexport and provide an easy configuration over the ui of mythtv. Please think about it, or give this Information to the developers. thx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/596539 Title: mythexport does not honor an existing cutlist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythexport/+bug/596539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 596539] Re: mythexport does not honor an existing cutlist
** Changed in: mythexport (Ubuntu) Status: Invalid => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/596539 Title: mythexport does not honor an existing cutlist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythexport/+bug/596539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742017] Re: "readline() on closed filehandle FILES" warnings caused by multiarch
will there be a fix for natty? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742017 Title: "readline() on closed filehandle FILES" warnings caused by multiarch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/popularity-contest/+bug/742017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 772992] Re: quick-lounge-applet makes gnome-panel segfault on Ubuntu Natty
three different humans with nearly the same issue, that's confirmation enough for me ** Changed in: quick-lounge-applet (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/772992 Title: quick-lounge-applet makes gnome-panel segfault on Ubuntu Natty -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 772992] Re: quick-lounge-applet makes gnome-panel segfault on Ubuntu Natty
I can confirm this. The same behaviour as go4linux described for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/772992 Title: quick-lounge-applet makes gnome-panel segfault on Ubuntu Natty -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 710077] Re: no mic with ATI HDA SBx00 Azalia (VT1818S)
The problem is in pulseaudio not in alsa. After purging pulseaudio there was no problem with the mic. ** Package changed: alsa-driver (Ubuntu) => pulseaudio (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/710077 Title: no mic with ATI HDA SBx00 Azalia (VT1818S) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 596242] Re: mythvideo does not find files with german Umlaut (äöü)
The issue went gone with the mythbuntu weekly build (0.24). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/596242 Title: mythvideo does not find files with german Umlaut (äöü) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 302919] Re: lcdproc: Futaba dm-140gink VFD device needs driver
I've changed to another hardware cause my barbone got broken. So there is nothing I can help with this issue any more. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/302919 Title: lcdproc: Futaba dm-140gink VFD device needs driver -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 390158] Re: [MSI MS-7329] suspend/resume failure [non-free: nvidia]
Sorry but I had to buy new hardware cause the board gave up last summer. There is nothing I can help any more. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/390158 Title: [MSI MS-7329] suspend/resume failure [non-free: nvidia] -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 710077] Re: no mic with ATI HDA SBx00 Azalia (VT1818S)
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/710077 Title: no mic with ATI HDA SBx00 Azalia (VT1818S) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 710077] [NEW] no mic with ATI HDA SBx00 Azalia (VT1818S)
Public bug reported: Description:Ubuntu 10.10 Release:10.10 alsa-base: Installiert: 1.0.23+dfsg-1ubuntu4 Kandidat:1.0.23+dfsg-1ubuntu4 Versionstabelle: *** 1.0.23+dfsg-1ubuntu4 0 500 http://de.archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages 100 /var/lib/dpkg/status After update from lucid to maverick the capture capability of my soundcard went gone. I already tried package "linux-backports-modules-alsa-maverick-generic" or ppa "ubuntu-audio-dev" for workaround, but without any noticable effect. please help ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: alsa-base 1.0.23+dfsg-1ubuntu4 ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: VT1818S Analog [VT1818S Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sjuk 2137 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfbcf4000 irq 16' Mixer name : 'VIA VT1818S' Components : 'HDA:11060440,10438417,0010' Controls : 35 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 12 HDMI/DP' Components : 'HDA:10de0012,10de0101,00100100' Controls : 16 Simple ctrls : 4 CheckboxSubmission: 32491223ee41faae6bb961227749d0a5 CheckboxSystem: edda5d4f616ca792bf437989cb597002 Date: Sun Jan 30 10:45:02 2011 EcryptfsInUse: Yes PackageArchitecture: all ProcEnviron: LANGUAGE=de_DE:de:en_GB:en PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver dmi.bios.date: 08/24/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1005 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A87TD EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1005:bd08/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A87TDEVO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/710077 Title: no mic with ATI HDA SBx00 Azalia (VT1818S) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 664559] Re: VDPAU Error in mythfrontend.log although using radeon
Thanx for the information. When the Error-Message does not harm any function I can ignore it. But in my opinion it should be a warning instead of an error. In my case there is no nvidia card in the mythtv- box. Why could there be an VDPAU-Error? Please think about it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/664559 Title: VDPAU Error in mythfrontend.log although using radeon -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 664559] Re: VDPAU Error in mythfrontend.log although using radeon
-- VDPAU Error in mythfrontend.log although using radeon https://bugs.launchpad.net/bugs/664559 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 664559] [NEW] VDPAU Error in mythfrontend.log although using radeon
Public bug reported: Binary package hint: mythtv Description:Ubuntu 10.04.1 LTS Release:10.04 mythtv-frontend: Installiert: 0.23.0+fixes24158-0ubuntu2 Kandidat: 0.23.0+fixes24158-0ubuntu2 Versions-Tabelle: *** 0.23.0+fixes24158-0ubuntu2 0 500 http://de.archive.ubuntu.com/ubuntu/ lucid/multiverse Packages 100 /var/lib/dpkg/status Since I switched from an nvida-based platform to an ati/amd-based platform there is an annoying error Message in the mythfrontend.log (VDPAU Error). 2010-10-21 14:44:58.812 Marking recording as watched using offset 4 minutes 2010-10-21 14:44:58.812 TV: Attempting to change from WatchingVideo to None 2010-10-21 14:44:58.813 TV: Changing from WatchingVideo to None 2010-10-21 14:44:58.876 TV: Attempting to change from None to None 2010-10-21 14:47:25.985 TV: Attempting to change from None to WatchingVideo Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory 2010-10-21 14:47:26.605 VDPAU Error: Error at mythrender_vdpau.cpp:1448 (#1, Unknown) 2010-10-21 14:47:26.605 VDPAU Error: Failed to create VDPAU device. 2010-10-21 14:47:26.605 VDPAU Error: No VDPAU device 2010-10-21 14:47:26.605 VDPAU: Failed to create dummy device. 2010-10-21 14:47:26.606 AFD: Opened codec 0xb5a3900, id(MPEG4) type(Video) 2010-10-21 14:47:26.606 AFD: codec MP2 has 2 channels 2010-10-21 14:47:26.606 AFD: Opened codec 0xb2f4860, id(MP2) type(Audio) 2010-10-21 14:47:26.709 Opening audio device 'default'. ch 2(2) sr 48000 (reenc 0) 2010-10-21 14:47:26.709 Opening ALSA audio device 'default'. 2010-10-21 14:47:26.834 VideoOutputXv: XVideo Adaptor Name: 'Radeon Textured Video' 2010-10-21 14:47:26.878 OSD Theme Dimensions W: 1280 H: 720 2010-10-21 14:47:26.946 The realtime priority setting is not enabled. YadifDeint: In-Pixformat = 1 Out-Pixformat=1 YadifDeint: size changed from 0 x 0 -> 720 x 576 2010-10-21 14:47:26.948 TV: Changing from None to WatchingVideo YadifDeint: Using existing thread. 2010-10-21 14:47:26.962 Video timing method: DRM 2010-10-21 15:08:44.822 Marking recording as watched using offset 4 minutes 2010-10-21 15:08:44.822 TV: Attempting to change from WatchingVideo to None 2010-10-21 15:08:44.822 TV: Changing from WatchingVideo to None 2010-10-21 15:08:44.885 TV: Attempting to change from None to None ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: mythtv-frontend 0.23.0+fixes24158-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic x86_64 Architecture: amd64 Date: Thu Oct 21 16:47:00 2010 Installed_mythplugins-dbg: 0.0 Installed_mythtv-dbg: 0.0 ProcEnviron: LANGUAGE=de_DE:de PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: mythtv ** Affects: mythtv (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- VDPAU Error in mythfrontend.log although using radeon https://bugs.launchpad.net/bugs/664559 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 596543] Re: mythexport does not handle specia l german characters (äüöß) correctly
Yes it does. For example a file like "Singen ist schön.avi" will be like this "Singen_ist_sch_n.avi". When there is more then one special german character it gets more difficult get back the real meaning. ** Changed in: mythexport (Ubuntu) Status: Incomplete => New -- mythexport does not handle special german characters (äüöß) correctly https://bugs.launchpad.net/bugs/596543 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 596242] Re: mythvideo does not find files wit h german Umlaut (äöü)
Hello pjw, here is the information from my mythbuntu-box you requested. ii libqtcore44:4.6.2-0ubuntu5.1Qt 4 core module ii linux-image-2.6.32-25-generic 2.6.32-25.44 Linux kernel image for version 2.6.32 on x86/x86_64 ii mythtv-frontend 0.23.0+fixes24158-0ubuntu2A personal video recorder application (client) ii mythvideo 0.23.0+fixes24104-0ubuntu2A generic video player frontend module for MythTV LANG=de_DE.UTF-8 LANGUAGE=de_DE:de LC_CTYPE="de_DE.UTF-8" ... LC_IDENTIFICATION="de_DE.UTF-8" LC_ALL=The problem is still there, and I didn't try the "LC_ALL"-workaround, because of the side-effects it will have. -- mythvideo does not find files with german Umlaut (äöü) https://bugs.launchpad.net/bugs/596242 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 596251] Re: mythexport reports start and finish of jobs at the same second
I try it again: The job runs and finishes correctly, if mythshutdown does not shutdown automatically. So how should there something wrong with the ffmpeg lines? (see attached mythexport_settings.cfg and above you can see the log.) In my opinion a mythexport job should stay in status "running" until it is finished. But it doesn't. It gets reported started and finished at the same second (see above). What do you need exactly? Which logfile or something? ** Attachment added: "mythexport_settings.cfg" https://bugs.launchpad.net/ubuntu/+source/mythexport/+bug/596251/+attachment/1498116/+files/mythexport_settings.cfg -- mythexport reports start and finish of jobs at the same second https://bugs.launchpad.net/bugs/596251 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 571444] Re: Boot hangs and unable to continue when automount disk in fstab is not available (Off or Disconnected)
Hi folks, I have the same problem with mounting nfs-shares on my working machine to my htpc in the living room. There are 4 mount points for my mythtv home entertainment and backup strategy. /etc/fstab: obelix:/var/lib/mythtv/music /var/lib/mythtv/music nfs _netdev,auto 0 0 obelix:/var/lib/mythtv/mythexport /var/lib/mythtv/mythexport nfs _netdev,auto 0 0 obelix:/var/lib/mythtv/pictures /var/lib/mythtv/pictures nfs _netdev,auto 0 0 obelix:/var/lib/mythtv/videos /var/lib/mythtv/videos nfs _netdev,auto 0 0 When obelix (htpc) is down my working machine does not boot! Is there any workaround? Is there anything I can do to help? -- Boot hangs and unable to continue when automount disk in fstab is not available (Off or Disconnected) https://bugs.launchpad.net/bugs/571444 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 581378] Re: display turns on and off and on and off...
I switched to the nouveau driver. After that I had resolution problems (only 800x600 instead of 1280x1024). I found out that the kvm swich cannot handle edid (ddc). So I substituted the kvm switch from "Belkin Switch2 USB" (Model # F1DG102U-USB) to Digitus DC-11403. In the end the issue of this bug was gone. I think the major problem is the new autoconfiguration way of lucid in association with the edid-blocking of the kvm switch. Perhaps anyone can post a hint to the lucid release notes to point out the new behavior and problems with some kvm switches. -- display turns on and off and on and off... https://bugs.launchpad.net/bugs/581378 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
