[Touch-packages] [Bug 1810439] Re: DNS/systemd-resolve: host1.foo.local cannot resolve host2.bar.local
Why isn't systemd-resolved forwarding my query for mirror1.eng.local to the configured upstream DNS server? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1810439 Title: DNS/systemd-resolve: host1.foo.local cannot resolve host2.bar.local Status in systemd package in Ubuntu: New Bug description: This is a fresh install of Ubuntu 18.04 (using the latest maas.io image). The system is in a DNS domain of "maas.local". There are other systems in this data center that are in the DNS domain "eng.local". Attempting to resolve the name of a system in the eng.local domain fails when run from the maas.local system (and vice versa, but we'll focus on the details of the former case). Details: ubuntu@kvm7246-vm009:~$ grep '^[^#]' /etc/resolv.conf nameserver 127.0.0.53 search maas.local tc82.local ubuntu@kvm7246-vm009:~$ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (ens6) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 172.23.4.4 DNS Domain: maas.local tc82.local ubuntu@kvm7246-vm009:~$ host maas1.maas.local maas1.maas.local has address 172.23.4.4 ubuntu@kvm7246-vm009:~$ systemd-resolve maas1.maas.local maas1.maas.local: 172.23.4.4 -- Information acquired via protocol DNS in 2.3ms. -- Data is authenticated: no ubuntu@kvm7246-vm009:~$ host mirror1.eng.local Host mirror1.eng.local not found: 2(SERVFAIL) ubuntu@kvm7246-vm009:~$ systemd-resolve mirror1.eng.local mirror1.eng.local: resolve call failed: No appropriate name servers or networks for name found ubuntu@kvm7246-vm009:~$ host mirror1.eng.local 172.23.4.4 Using domain server: Name: 172.23.4.4 Address: 172.23.4.4#53 Aliases: mirror1.eng.local has address 172.21.0.66 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1810439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1810439] [NEW] DNS/systemd-resolve: host1.foo.local cannot resolve host2.bar.local
Public bug reported: This is a fresh install of Ubuntu 18.04 (using the latest maas.io image). The system is in a DNS domain of "maas.local". There are other systems in this data center that are in the DNS domain "eng.local". Attempting to resolve the name of a system in the eng.local domain fails when run from the maas.local system (and vice versa, but we'll focus on the details of the former case). Details: ubuntu@kvm7246-vm009:~$ grep '^[^#]' /etc/resolv.conf nameserver 127.0.0.53 search maas.local tc82.local ubuntu@kvm7246-vm009:~$ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (ens6) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 172.23.4.4 DNS Domain: maas.local tc82.local ubuntu@kvm7246-vm009:~$ host maas1.maas.local maas1.maas.local has address 172.23.4.4 ubuntu@kvm7246-vm009:~$ systemd-resolve maas1.maas.local maas1.maas.local: 172.23.4.4 -- Information acquired via protocol DNS in 2.3ms. -- Data is authenticated: no ubuntu@kvm7246-vm009:~$ host mirror1.eng.local Host mirror1.eng.local not found: 2(SERVFAIL) ubuntu@kvm7246-vm009:~$ systemd-resolve mirror1.eng.local mirror1.eng.local: resolve call failed: No appropriate name servers or networks for name found ubuntu@kvm7246-vm009:~$ host mirror1.eng.local 172.23.4.4 Using domain server: Name: 172.23.4.4 Address: 172.23.4.4#53 Aliases: mirror1.eng.local has address 172.21.0.66 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: This is a fresh install of Ubuntu 18.04 (using the latest maas.io image). The system is in a DNS domain of "maas.local". There are other systems in this data center that are in the DNS domain "eng.local". Attempting to resolve the name of a system in the eng.local domain fails when run from the maas.local system (and vice versa, but we'll focus on the details of the former case). Details: - ubuntu@kvm7246-vm009:~$ grep '^[^#]' /etc/resolv.conf + ubuntu@kvm7246-vm009:~$ grep '^[^#]' /etc/resolv.conf nameserver 127.0.0.53 search maas.local tc82.local ubuntu@kvm7246-vm009:~$ systemd-resolve --status Global - DNSSEC NTA: 10.in-addr.arpa - 16.172.in-addr.arpa - 168.192.in-addr.arpa - 17.172.in-addr.arpa - 18.172.in-addr.arpa - 19.172.in-addr.arpa - 20.172.in-addr.arpa - 21.172.in-addr.arpa - 22.172.in-addr.arpa - 23.172.in-addr.arpa - 24.172.in-addr.arpa - 25.172.in-addr.arpa - 26.172.in-addr.arpa - 27.172.in-addr.arpa - 28.172.in-addr.arpa - 29.172.in-addr.arpa - 30.172.in-addr.arpa - 31.172.in-addr.arpa - corp - d.f.ip6.arpa - home - internal - intranet - lan - local - private - test + DNSSEC NTA: 10.in-addr.arpa + 16.172.in-addr.arpa + 168.192.in-addr.arpa + 17.172.in-addr.arpa + 18.172.in-addr.arpa + 19.172.in-addr.arpa + 20.172.in-addr.arpa + 21.172.in-addr.arpa + 22.172.in-addr.arpa + 23.172.in-addr.arpa + 24.172.in-addr.arpa + 25.172.in-addr.arpa + 26.172.in-addr.arpa + 27.172.in-addr.arpa + 28.172.in-addr.arpa +
[Touch-packages] [Bug 1754686] [NEW] libcurl4 Conflicts: libcurl3 - prevents install of 3rd party apps like slack-desktop
Public bug reported: Updating the curl package pulls in libcurl4, which for some reason forces libcurl3 to be removed. This prevents 3rd party apps that still build against libcurl3 from being installed. Isn't there a more graceful way to effect the transition from libcurl3 to libcurl4? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libcurl4 7.58.0-2ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 9 10:10:10 2018 EcryptfsInUse: Yes SourcePackage: curl UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago) ** Affects: curl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754686 Title: libcurl4 Conflicts: libcurl3 - prevents install of 3rd party apps like slack-desktop Status in curl package in Ubuntu: New Bug description: Updating the curl package pulls in libcurl4, which for some reason forces libcurl3 to be removed. This prevents 3rd party apps that still build against libcurl3 from being installed. Isn't there a more graceful way to effect the transition from libcurl3 to libcurl4? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libcurl4 7.58.0-2ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 9 10:10:10 2018 EcryptfsInUse: Yes SourcePackage: curl UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754186] [NEW] Night Light only affects a single monitor now
Public bug reported: The Display settings have a "Night Light" option which allows reducing blue light at night. In Ubuntu 17.10, this worked great, and the setting took effect on all 3 of my monitors. In Bionic, only the 1st monitor is affected; the other 2 remain at the default color temperature. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Wed Mar 7 17:51:02 2018 DistUpgraded: 2018-03-07 12:52:16,474 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Double D HD 7970 Black Edition [1682:3211] InstallationDate: Installed on 2014-08-21 (1294 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=98fea0b5-8fa6-4625-bae5-b85a70783a13 ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-03-07 (0 days ago) dmi.bios.date: 04/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1208 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX 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.:bvr1208:bd04/18/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX: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.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Oct 7 12:18:20 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.1 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic regression reproducible single-occurrence third-party-packages ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1754186 Title: Night Light only affects a single monitor now Status in xorg package in Ubuntu: New Bug description: The Display settings have a "Night Light" option which allows reducing blue light at night. In Ubuntu 17.10, this worked great, and the setting took effect on all 3 of my monitors. In Bionic, only the 1st monitor is affected; the other 2 remain at the default color temperature. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Wed Mar 7 17:51:02 2018 DistUpgraded: 2018-03-07 12:52:16,474 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Double D HD 7970 Black Edition [1682:3211] InstallationDate: Installed on 2014-08-21 (1294 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty
[Touch-packages] [Bug 1467695] [NEW] Alt-Grave (`) switcher has flickering/pulsing shadow artifacts
Public bug reported: 1. Hold down Alt and keep it held down. 2. Press and release the key above Tab (Grave, or `). Keep alt held down. While Alt is held down, the drop shadows for the window or windows of the current application will keep building up and then going back to normal and building up again. It's almost as though the windows are being redrawn may times per second into a buffer without clearing it first each time (but clearing it every second or so). While this is happening, I notice that the drop shadow for the top bar does the same thing. This can also be observed if one uses Alt-Tab to select an app that has multiple windows that then expand out into a similar display. I've observed this on systems with Intel, NVIDIA, and ATI display hardware, so I don't think it's hardware-specific. All my Ubuntu systems have 2 or 3 monitors. I suspect multiple monitors are needed to reproduce this. ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1467695 Title: Alt-Grave (`) switcher has flickering/pulsing shadow artifacts Status in unity package in Ubuntu: New Bug description: 1. Hold down Alt and keep it held down. 2. Press and release the key above Tab (Grave, or `). Keep alt held down. While Alt is held down, the drop shadows for the window or windows of the current application will keep building up and then going back to normal and building up again. It's almost as though the windows are being redrawn may times per second into a buffer without clearing it first each time (but clearing it every second or so). While this is happening, I notice that the drop shadow for the top bar does the same thing. This can also be observed if one uses Alt-Tab to select an app that has multiple windows that then expand out into a similar display. I've observed this on systems with Intel, NVIDIA, and ATI display hardware, so I don't think it's hardware-specific. All my Ubuntu systems have 2 or 3 monitors. I suspect multiple monitors are needed to reproduce this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1467695/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1267059] Re: Unattended-Upgrade::Remove-Unused-Dependencies does not work
This bug is serious (it causes filesystems to fill up on pretty much every production server that doesn't have a huge root fs). It has a reasonable looking patch that fixes the problem. I don't think there is anything to discuss other than: How do we get the fix into Ubuntu? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1267059 Title: Unattended-Upgrade::Remove-Unused-Dependencies does not work Status in unattended-upgrades package in Ubuntu: Triaged Bug description: I have a system that runs unattended-upgrades just fine. Now i want to automate removal of old kernels and kernel header packages that are accumulating otherwise. So i set 'Unattended-Upgrade::Remove-Unused- Dependencies true;'. But it doesn't work. Details: Lots of stuff pending autoremoval: $ apt-get --assume-no autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED linux-headers-3.2.0-38 linux-headers-3.2.0-38-generic linux-headers-3.2.0-39 linux-headers-3.2.0-39-generic linux-headers-3.2.0-40 linux-headers-3.2.0-40-generic linux-headers-3.2.0-41 linux-headers-3.2.0-41-generic linux-headers-3.2.0-43 linux-headers-3.2.0-43-generic linux-headers-3.2.0-44 linux-headers-3.2.0-44-generic linux-headers-3.2.0-45 linux-headers-3.2.0-45-generic linux-headers-3.2.0-48 linux-headers-3.2.0-48-generic linux-headers-3.2.0-51 linux-headers-3.2.0-51-generic linux-headers-3.2.0-52 linux-headers-3.2.0-52-generic linux-headers-3.2.0-53 linux-headers-3.2.0-53-generic linux-headers-3.2.0-54 linux-headers-3.2.0-54-generic linux-headers-3.2.0-55 linux-headers-3.2.0-55-generic linux-headers-3.2.0-56 linux-headers-3.2.0-56-generic linux-image-3.2.0-39-generic linux-image-3.2.0-40-generic linux-image-3.2.0-41-generic linux-image-3.2.0-43-generic linux-image-3.2.0-44-generic linux-image-3.2.0-45-generic linux-image-3.2.0-48-generic linux-image-3.2.0-51-generic linux- image-3.2.0-52-generic linux-image-3.2.0-53-generic linux-image-3.2.0-54-generic linux-image-3.2.0-55-generic linux-image-3.2.0-56-generic 0 upgraded, 0 newly installed, 41 to remove and 13 not upgraded. After this operation, 2,893 MB disk space will be freed. Do you want to continue [Y/n]? N Abort. Note that the majority of these packages have been installed by unattended-upgrades from precise-security. According to the comments within/etc/apt/apt.conf.d/50unattended- upgrades, this should automate autoremoval: // Do automatic removal of new unused dependencies after the upgrade // (equivalent to apt-get autoremove) Unattended-Upgrade::Remove-Unused-Dependencies true; but nothing happens (note the line Packages that are auto removed: '' : $ unattended-upgrades --debug --dry-run Initial blacklisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=precise-security'] adjusting candidate version: 'Version: package:'accountsservice' version:'0.6.15-2ubuntu9.6.1'' adjusting candidate version: 'Version: package:'libaccountsservice0' version:'0.6.15-2ubuntu9.6.1'' adjusting candidate version: 'Version: package:'libdrm-intel1' version:'2.4.43-0ubuntu0.0.3'' adjusting candidate version: 'Version: package:'libdrm-nouveau1a' version:'2.4.43-0ubuntu0.0.3'' adjusting candidate version: 'Version: package:'libdrm-radeon1' version:'2.4.43-0ubuntu0.0.3'' adjusting candidate version: 'Version: package:'libdrm2' version:'2.4.43-0ubuntu0.0.3'' Checking: bc ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: grub-common ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: grub-pc ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: grub-pc-bin ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: grub2-common ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: iproute ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: landscape-common ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) blacklist: [] Packages
[Touch-packages] [Bug 1301998] Re: Xorg freeze
Unfortunately, running Unity on this system makes doing my day job more or less impossible, so I've switched to using the Gnome fallback session. It's unlikely I'll have time to test this anytime soon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1301998 Title: Xorg freeze Status in xorg package in Ubuntu: Incomplete Bug description: Backtrace: https://launchpadlibrarian.net/171690059/XorgLogOld.txt ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8 Uname: Linux 3.13.0-21-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell] Date: Thu Apr 3 10:46:59 2014 DistUpgraded: 2014-01-22 19:30:50,196 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 [VGA controller]) Subsystem: BFG Tech Device [19f1:201f] ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-21-generic root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to trusty on 2014-01-23 (70 days ago) dmi.bios.date: 06/26/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: WBIBX10J.86A.0336.2012.0626.0141 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WB dmi.board.vendor: Intel Corporation dmi.board.version: AAE64798-207 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrWBIBX10J.86A.0336.2012.0626.0141:bd06/26/2012:svn:pn:pvr:rvnIntelCorporation:rnDP55WB:rvrAAE64798-207:cvn:ct2:cvr: version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 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 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Apr 3 10:38:37 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputSleep Button KEYBOARD, id 7 inputLogitech Optical USB Mouse MOUSE, id 8 inputBTC USB Multimedia Keyboard KEYBOARD, id 9 inputBTC USB Multimedia Keyboard KEYBOARD, id 10 xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu7 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1301998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1069964] Re: Unable to mount Blank CD-R disc. Location is already mounted.
This bug is pretty embarrassing for anyone trying to show parents or friends how easy Ubuntu is to use. Note: A workaround for the cannot burn any .iso files aspect of this issue (which doesn't require installing extra software) is to use wodim at the command line: wodim foo.iso -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1069964 Title: Unable to mount Blank CD-R disc. Location is already mounted. Status in OEM Priority Project: New Status in “glib2.0” package in Ubuntu: Confirmed Status in “unity-settings-daemon” package in Ubuntu: Confirmed Bug description: This error message comes up, while still able to burn, read/write etc. It occurs in quantal when inserting a CD/DVD into the drive, but it did not happen in precice. Screenshot: http://i47.tinypic.com/4v0aj6.png Burner: LG HL-DT-ST DVDRAM GH24NS90 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-settings-daemon 3.4.2-0ubuntu14 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 22 19:50:35 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1069964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp