[Bug 1973064] Re: Missing python3-dbus dependency for ubuntu-release-upgrader-core
Additional info: This was on a fully updated minimal Ubuntu 20.04 (running on WSL2). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973064 Title: Missing python3-dbus dependency for ubuntu-release-upgrader-core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1973064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973064] [NEW] Missing python3-dbus dependency for ubuntu-release-upgrader-core
Public bug reported: do-release-upgrade failed with "ModuleNotFoundError: No module named 'dbus'". Installing python3-dbus resolved the issue. This should be a package dependency for ubuntu-release-upgrader-core. ** Affects: ubuntu-release-upgrader (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/1973064 Title: Missing python3-dbus dependency for ubuntu-release-upgrader-core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1973064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923196] [NEW] Background noise when intel hd audio enters power save
Public bug reported: There is a very high noise level whenever the audio driver doesn't get used for a while (after 5-10 seconds). The problem goes away whenever any sound plays, even a completely silent video. There is a solution online that sets two values to prevent the audio driver going into power save state, but the solution isn't permanent and isn't a real solution. That 'hacky' solution uses the following two commands: echo 0 | sudo tee /sys/module/snd_hda_intel/parameters/power_save_controller echo 0 | sudo tee /sys/module/snd_hda_intel/parameters/power_save Power save sounds like a good feature to have, but there should be an option to disable it or something when the motherboard/audio card has high noise levels when it enters power save... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: thomas 2761 F pulseaudio /dev/snd/pcmC1D0p: thomas 2761 F...m pulseaudio /dev/snd/controlC0: thomas 2761 F pulseaudio /dev/snd/timer: thomas 2761 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 9 14:34:09 2021 InstallationDate: Installed on 2021-02-09 (58 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.20 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock 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.:bvrP4.20:bd06/18/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr: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: 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. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923196 Title: Background noise when intel hd audio enters power save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1923196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909877] [NEW] Clock in top bar doesn't update
Public bug reported: When exiting fullscreen from chromium (YouTube), the clock widget in the top bar seems stuck and only updates after being updated from the mouse hovering over it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.45.01 Thu Nov 5 23:03:56 UTC 2020 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 2 21:56:27 2021 DistUpgraded: 2020-12-27 18:29:34,023 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 455.45.01, 5.4.0-58-generic, x86_64: installed nvidia, 455.45.01, 5.8.0-33-generic, x86_64: installed virtualbox, 6.1.14, 5.4.0-58-generic, x86_64: installed virtualbox, 6.1.14, 5.8.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:1264] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Ti Mobile] [1025:1265] InstallationDate: Installed on 2020-12-11 (22 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Nitro AN515-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic root=UUID=8753fbc2-cbcd-41b4-ad44-9e1a6f940ddf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-12-27 (6 days ago) dmi.bios.date: 08/05/2019 dmi.bios.release: 1.28 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:br1.28:efr1.26:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Acer Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909877 Title: Clock in top bar doesn't update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1909877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903391] Re: linux-cloud-tools and linux-cloud-tools-common disagree on file paths
** Package changed: ubuntu => linux-hwe-5.4 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903391 Title: linux-cloud-tools and linux-cloud-tools-common disagree on file paths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1903391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903391] [NEW] linux-cloud-tools and linux-cloud-tools-common disagree on file paths
Public bug reported: Situation: (focal) ubuntu-minimal + linux-virtual-hwe-20.04 + linux-cloud-tools-virtual-hwe-20.04 Running as a Gen-2 Hyper-V guest on Windows 10. 1) Ubuntu release Description:Ubuntu 20.04.1 LTS Release:20.04 2) package versions linux-cloud-tools-5.4.0-52: Installed: 5.4.0-52.57 linux-cloud-tools-common: Installed: 5.4.0-52.57 3) expected behavior hv_kvp_daemon should work out of the box, providing information to the Hyper-V host. 4) actual behavior hv_kvp_daemon logs errors about not finding files it needs to provide the information: hv_kvp_daemon[276209]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dns_info: not found hv_kvp_daemon[276211]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dhcp_info: not found 5) anasysis The actual hv_kvp_daemon binary is hardcoded with a path to the sub- utilities it uses (I don't think it is runtime configurable). $ strings /usr/lib/linux-tools-5.4.0-52/hv_kvp_daemon | grep libexec /usr/libexec/hypervkvpd/%s /usr/libexec/hypervkvpd/%s %s These binaries are instead located at: $ locate hv_get_dns_info /usr/sbin/hv_get_dns_info Suggested solution: either compile hv_kvp_daemon so it uses /usr/sbin instead of /usr/libexec/hypervkvpd, or (probably easier) make linux- cloud-tools-common install the scripts in /usr/libexec/hypervkvpd instead of in /usr/sbin, or (easiest) install an extra symlink as in the workaround below. 6) workaround $ sudo mkdir /usr/libexec $ sudo ln -s /usr/sbin /usr/libexec/hypervkvpd ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903391 Title: linux-cloud-tools and linux-cloud-tools-common disagree on file paths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1903391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872870] [NEW] Ubuntu 20.04 latest update mouse pointer leaves square trails on desktop
RE: mouse pointer leaves square trails-boxes Hello Christopher, Last week I moved to Ubuntu 20.04, and have the same distracting trails-boxes, that indeed disappear when Zoom is Off, but I absolutely need the Zoom. I have written a small script that toggles Zoom, and added it as a short-cut. Now, with a single key-press, I can toggle between Zoom On (for my eye sight) and Zoom Off (for a full desktop view, without the trails-boxes). If you are interested, I will email you the details, Som fransvandersom...@gmail.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872870 Title: Ubuntu 20.04 latest update mouse pointer leaves square trails on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/1872870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1668049] Re: lxd cannot shutdown container
I have no idea. I changed jobs and have no more access to the infrastructure where this issue showed up. Closing or rejecting this ticket is fine with me. Op maandag 1 juni 2020 18:31:17 CEST schreef Stéphane Graber <1668...@bugs.launchpad.net>: Is this still an issue? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1668049 Title: lxd cannot shutdown container Status in systemd package in Ubuntu: New Bug description: I found this issue when working with lxd and submitted a ticket there but the lxc people said it was related to systemd, not lxc. The issue is: I have a container running under lxc/lxd. lxc stop of the container does not work whereas if I execute "shutdown now" inside the container it does stop as expected. The associated lxd ticket is here: https://github.com/lxc/lxd/issues/2947 The output of journalctl -a is at the end of this message The syslog of that same run can be found here: http://paste.ubuntu.com/24071244/ and this is the output of ps aux: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.1 37808 4576 ? Ss 11:19 0:00 /sbin/init root 48 0.0 0.0 35276 3004 ? Ss 11:19 0:00 /lib/systemd/systemd-journald root 49 0.0 0.0 41724 1912 ? Ss 11:19 0:00 /lib/systemd/systemd-udevd message+ 514 0.0 0.0 42900 2460 ? Ss 11:19 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation root 704 0.0 0.0 18252 2508 ? Ss 11:55 0:00 bash root 720 0.0 0.0 34556 1992 ? R+ 11:59 0:00 ps aux Note that this may be timing related. If I stop the container immediately after starting things work. If I stop after a minute or so, the stop will not get through. (even not on a 2nd or 3rd attempt). However if I leave the container for a while then a new lxc stop will terminate the container. (this happened after an hour or so). The issue is reproducible but seems to be dependend on what is running inside the container. container runs ubuntu 16.04 on a 16.04 host. systemd --version says: systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN lxc sends SIGRTMIN+3 to systemd to stop. This was apparently discussed here: https://github.com/lxc/lxc/issues/1085 Let me know if more info is needed. Frans -- Logs begin at Sun 2017-02-26 11:19:12 UTC, end at Sun 2017-02-26 11:23:05 UTC. -- Feb 26 11:19:12 D-wan-61-1 systemd-journald[48]: Runtime journal (/run/log/journal/) is 8.0M, max 196.7M, 188.7M free. Feb 26 11:19:12 D-wan-61-1 systemd-journald[48]: Journal started Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '4 4 1 7' to 'kernel/printk', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '176' to 'kernel/sysrq', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '1' to 'fs/protected_symlinks', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '1' to 'net/ipv4/tcp_syncookies', ignoring: No such file or directory Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '1' to 'kernel/kptr_restrict', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '1' to 'fs/protected_hardlinks', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '1' to 'kernel/yama/ptrace_scope', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '65536' to 'vm/mmap_min_addr', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd[1]: systemd-sysctl.service: Main process exited, code=exited, status=1/FAILURE Feb 26 11:19:12 D-wan-61-1 systemd[1]: Failed to start Apply Kernel Variables. Feb 26 11:19:12 D-wan-61-1 systemd[1]: systemd-sysctl.service: Unit entered failed state. Feb 26 11:19:12 D-wan-61-1 systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'. Feb 26 11:19:12 D-wan-61-1 systemd-journald[48]: Forwarding to syslog missed 1 messages. Feb 26 11:19:12 D-wan-61-1 systemd[1]: Started Uncomplicated firewall. Feb 26 11:19:12 D-wan-61-1 systemd[1]: Failed to reset devices.list on /system.slice/ufw.service: Operation not permitted Feb 26 11:19:12 D-wan-61-1 systemd[1]: Started udev Kernel Device Manager. Feb 26 11:19:12 D-wan-61-1 mount[45]: mount: permission denied Feb 26 11:19:12 D-wan-61-1 systemd[1]: Started Nameserver information manager. Feb 26 11:19:12 D-wan-61-1 systemd[1]: dev-hugepages.mount: Mount process exited, code=exited status=32 Feb 26 11:19:12 D-wan-61-1 systemd[1]: Failed to mount Huge Pages File System. Feb 26 11:19:12 D-wa
[Bug 1870019] Re: HPLIP: SyntaxWarning, using is or is not, did you mean == or != ?
** Summary changed: - HPLIP: SyntaxWarning, using is, is not, did you mean == or != ? + HPLIP: SyntaxWarning, using is or is not, did you mean == or != ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870019 Title: HPLIP: SyntaxWarning, using is or is not, did you mean == or != ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1870019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870019] Re: HPLIP: SyntaxWarning, did you mean == or != ?
** Description changed: - While running python rtupdate hooks for python3.8 ... + While running python rtupdate hooks for python3.8, got these warnings + from hplip-data ... /usr/share/hplip/base/utils.py:2060: SyntaxWarning: "is" with a literal. Did you mean "=="? if weburl is "" or weburl is None: /usr/share/hplip/check-plugin.py:116: SyntaxWarning: "is" with a literal. Did you mean "=="? if log_level is 'debug': /usr/share/hplip/check.py:685: SyntaxWarning: "is not" with a literal. Did you mean "!="? if 'getfacl' not in g and '' is not g and 'file' not in g: /usr/share/hplip/installer/core_install.py:2037: SyntaxWarning: "is" with a literal. Did you mean "=="? if home_dir is "": /usr/share/hplip/ui5/devmgr_ext.py:15: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self.latest_available_version is not "": /usr/share/hplip/ui5/devmgr_ext.py:37: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self.latest_available_version is not "": ** Description changed: While running python rtupdate hooks for python3.8, got these warnings - from hplip-data ... + from hplip-data package ... /usr/share/hplip/base/utils.py:2060: SyntaxWarning: "is" with a literal. Did you mean "=="? if weburl is "" or weburl is None: /usr/share/hplip/check-plugin.py:116: SyntaxWarning: "is" with a literal. Did you mean "=="? if log_level is 'debug': /usr/share/hplip/check.py:685: SyntaxWarning: "is not" with a literal. Did you mean "!="? if 'getfacl' not in g and '' is not g and 'file' not in g: /usr/share/hplip/installer/core_install.py:2037: SyntaxWarning: "is" with a literal. Did you mean "=="? if home_dir is "": /usr/share/hplip/ui5/devmgr_ext.py:15: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self.latest_available_version is not "": /usr/share/hplip/ui5/devmgr_ext.py:37: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self.latest_available_version is not "": ** Description changed: While running python rtupdate hooks for python3.8, got these warnings - from hplip-data package ... + from the hplip-data package ... /usr/share/hplip/base/utils.py:2060: SyntaxWarning: "is" with a literal. Did you mean "=="? if weburl is "" or weburl is None: /usr/share/hplip/check-plugin.py:116: SyntaxWarning: "is" with a literal. Did you mean "=="? if log_level is 'debug': /usr/share/hplip/check.py:685: SyntaxWarning: "is not" with a literal. Did you mean "!="? if 'getfacl' not in g and '' is not g and 'file' not in g: /usr/share/hplip/installer/core_install.py:2037: SyntaxWarning: "is" with a literal. Did you mean "=="? if home_dir is "": /usr/share/hplip/ui5/devmgr_ext.py:15: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self.latest_available_version is not "": /usr/share/hplip/ui5/devmgr_ext.py:37: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self.latest_available_version is not "": ** Summary changed: - HPLIP: SyntaxWarning, did you mean == or != ? + HPLIP: SyntaxWarning, using is, is not, did you mean == or != ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870019 Title: HPLIP: SyntaxWarning, using is, is not, did you mean == or != ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1870019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870019] [NEW] HPLIP: SyntaxWarning, did you mean == or != ?
Public bug reported: While running python rtupdate hooks for python3.8, got these warnings from the hplip-data package ... /usr/share/hplip/base/utils.py:2060: SyntaxWarning: "is" with a literal. Did you mean "=="? if weburl is "" or weburl is None: /usr/share/hplip/check-plugin.py:116: SyntaxWarning: "is" with a literal. Did you mean "=="? if log_level is 'debug': /usr/share/hplip/check.py:685: SyntaxWarning: "is not" with a literal. Did you mean "!="? if 'getfacl' not in g and '' is not g and 'file' not in g: /usr/share/hplip/installer/core_install.py:2037: SyntaxWarning: "is" with a literal. Did you mean "=="? if home_dir is "": /usr/share/hplip/ui5/devmgr_ext.py:15: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self.latest_available_version is not "": /usr/share/hplip/ui5/devmgr_ext.py:37: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self.latest_available_version is not "": ** Affects: hplip (Ubuntu) Importance: Undecided Status: New ** Tags: focal ** Tags added: focal ** Description changed: + While running python rtupdate hooks for python3.8 ... + /usr/share/hplip/base/utils.py:2060: SyntaxWarning: "is" with a literal. Did you mean "=="? - if weburl is "" or weburl is None: + if weburl is "" or weburl is None: /usr/share/hplip/check-plugin.py:116: SyntaxWarning: "is" with a literal. Did you mean "=="? - if log_level is 'debug': + if log_level is 'debug': /usr/share/hplip/check.py:685: SyntaxWarning: "is not" with a literal. Did you mean "!="? - if 'getfacl' not in g and '' is not g and 'file' not in g: + if 'getfacl' not in g and '' is not g and 'file' not in g: /usr/share/hplip/installer/core_install.py:2037: SyntaxWarning: "is" with a literal. Did you mean "=="? - if home_dir is "": + if home_dir is "": /usr/share/hplip/ui5/devmgr_ext.py:15: SyntaxWarning: "is not" with a literal. Did you mean "!="? - if self.latest_available_version is not "": + if self.latest_available_version is not "": /usr/share/hplip/ui5/devmgr_ext.py:37: SyntaxWarning: "is not" with a literal. Did you mean "!="? - if self.latest_available_version is not "": + if self.latest_available_version is not "": ** Summary changed: - SyntaxWarning + hplib: SyntaxWarning, did you mean "=="? or "!="? ** Summary changed: - hplib: SyntaxWarning, did you mean "=="? or "!="? + HPLIP: SyntaxWarning, did you mean "=="? or "!="? ** Summary changed: - HPLIP: SyntaxWarning, did you mean "=="? or "!="? + HPLIP: SyntaxWarning, did you mean ==? or !=? ** Summary changed: - HPLIP: SyntaxWarning, did you mean ==? or !=? + HPLIP: SyntaxWarning, did you mean == or != ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870019 Title: HPLIP: SyntaxWarning, did you mean == or != ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1870019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855570] Re: [nouveau][conroe] No Gnome is showing up in Ubuntu 20.04
** Attachment added: "Ubuntu 20.04 Desktop after login by FvB" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855570/+attachment/5311664/+files/IMG_20191211_080948.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855570 Title: [nouveau][conroe] No Gnome is showing up in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855570] Re: [nouveau][conroe] No Gnome is showing up in Ubuntu 20.04
** Attachment added: "Ubuntu 20.04 gdm3 by FvB" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855570/+attachment/5311659/+files/IMG_20191211_073739.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855570 Title: [nouveau][conroe] No Gnome is showing up in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855570] Re: [nouveau][conroe] No Gnome is showing up in Ubuntu 20.04
Click on the cog wheel icon, there are three options, Gnome + Remmina Kiosk, Ubuntu and Ubuntu on Wayland. And Ubuntu is selected by default. Next after login, there is nothing on the screen, as in blank / black. Except the mouse pointer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855570 Title: [nouveau][conroe] No Gnome is showing up in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855570] Re: [nouveau][conroe] No Gnome is showing up in Ubuntu 20.04
After some time the screen i going to purple, the mouse pointer still there but no change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855570 Title: [nouveau][conroe] No Gnome is showing up in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855570] Re: [nouveau][conroe] No Gnome is showing up in Ubuntu 20.04
Sorry i wasn't clear about that. I am able to login with gdm3 with user frans as expected. But next i am getting a Desktop without any Gnome controls. I still can move the mouse over two screens. But even clicking on the mouse buttons, doesn't show up any menu, to open up a terminal for example. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855570 Title: [nouveau][conroe] No Gnome is showing up in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855570] Re: [nouveau][conroe] No Gnome is showing up in Ubuntu 20.04
** Attachment added: "Ubuntu 20.04 journal.txt by FvB" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855570/+attachment/5311628/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855570 Title: [nouveau][conroe] No Gnome is showing up in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855570] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1855570/+attachment/5311617/+files/ShellJournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855570 Title: [nouveau][conroe] No Gnome is showing up in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855570] Re: [nouveau][conroe] No Gnome is showing up in Ubuntu 20.04
apport information ** Tags added: apport-collected ** Description changed: Just freshly installed Ubuntu 20.04 on a bare metal Desktop disk partition (for testing purpose only): While booting there is no Gnome showing up. Checking syslog for error's there are these messages ... Dec 8 07:51:43 deblnxsrv100 xdg-desktop-por[1287]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Timeout was reached Dec 8 07:51:43 deblnxsrv100 at-spi-bus-launcher[1245]: X connection to :0 broken (explicit kill or server shutdown). Dec 8 07:51:44 deblnxsrv100 gsd-wacom[1522]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 gsd-xsettings[1538]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Main process exited, code=exited, status=1/FAILURE Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Failed with result 'exit-code'. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Triggering OnFailure= dependencies. Dec 8 07:51:44 deblnxsrv100 systemd[]: Stopped target GNOME XSettings. Dec 8 07:51:44 deblnxsrv100 systemd[]: Started GNOME Session Failed lockdown screen (user). Dec 8 07:51:44 deblnxsrv100 systemd[]: Reached target GNOME Session Failed. Dec 8 07:51:44 deblnxsrv100 update-notifier[1815]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu13 + Architecture: amd64 + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + GsettingsChanges: + + Package: gnome-shell 3.34.1+git20191024-1ubuntu1 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=en_US:en + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13 + RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1 + Tags: focal + Uname: Linux 5.3.0-25-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1855570/+attachment/5311615/+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/1855570 Title: [nouveau][conroe] No Gnome is showing up in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855570] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1855570/+attachment/5311616/+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/1855570 Title: [nouveau][conroe] No Gnome is showing up in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855570] Re: [nouveau][conroe] No Gnome is showing up in Ubuntu 20.04
Okay, tell me. How do i fire up a graphical terminal on a Desktop without Gnome controls? There is nothing on my screen now. I have access to the computer by ssh, truth. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855570 Title: [nouveau][conroe] No Gnome is showing up in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855570] Re: xdg-desktop-por: Could not get window list: Timeout was reached
** Attachment added: "Ubuntu 20.04 gpu-manager by FvB" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1855570/+attachment/5310648/+files/gpu-manager.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855570 Title: xdg-desktop-por: Could not get window list: Timeout was reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1855570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855570] [NEW] xdg-desktop-por: Could not get window list: Timeout was reached
Public bug reported: Just freshly installed Ubuntu 20.04 on a bare metal Desktop disk partition (for testing purpose only): While booting there is no Gnome showing up. Checking syslog for error's there are these messages ... Dec 8 07:51:43 deblnxsrv100 xdg-desktop-por[1287]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Timeout was reached Dec 8 07:51:43 deblnxsrv100 at-spi-bus-launcher[1245]: X connection to :0 broken (explicit kill or server shutdown). Dec 8 07:51:44 deblnxsrv100 gsd-wacom[1522]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 gsd-xsettings[1538]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Main process exited, code=exited, status=1/FAILURE Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Failed with result 'exit-code'. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Triggering OnFailure= dependencies. Dec 8 07:51:44 deblnxsrv100 systemd[]: Stopped target GNOME XSettings. Dec 8 07:51:44 deblnxsrv100 systemd[]: Started GNOME Session Failed lockdown screen (user). Dec 8 07:51:44 deblnxsrv100 systemd[]: Reached target GNOME Session Failed. Dec 8 07:51:44 deblnxsrv100 update-notifier[1815]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Ubuntu 20.04 syslog by FvB" https://bugs.launchpad.net/bugs/1855570/+attachment/5310647/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855570 Title: xdg-desktop-por: Could not get window list: Timeout was reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1855570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855570] Re: xdg-desktop-por: Could not get window list: Timeout was reached
** Attachment added: "Ubuntu 20.04 Xorg 0 log by FvB" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1855570/+attachment/5310649/+files/Xorg.0.log ** Description changed: - Just installed Ubuntu 20.04 (for testing purpose only): While booting - there is no Gnome showing up. Checking syslog there are these messages - ... + Just freshly installed Ubuntu 20.04 on a bare metal Desktop (for testing + purpose only): While booting there is no Gnome showing up. Checking + syslog there are these messages ... Dec 8 07:51:43 deblnxsrv100 xdg-desktop-por[1287]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Timeout was reached Dec 8 07:51:43 deblnxsrv100 at-spi-bus-launcher[1245]: X connection to :0 broken (explicit kill or server shutdown). Dec 8 07:51:44 deblnxsrv100 gsd-wacom[1522]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 gsd-xsettings[1538]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Main process exited, code=exited, status=1/FAILURE Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Failed with result 'exit-code'. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Triggering OnFailure= dependencies. Dec 8 07:51:44 deblnxsrv100 systemd[]: Stopped target GNOME XSettings. Dec 8 07:51:44 deblnxsrv100 systemd[]: Started GNOME Session Failed lockdown screen (user). Dec 8 07:51:44 deblnxsrv100 systemd[]: Reached target GNOME Session Failed. Dec 8 07:51:44 deblnxsrv100 update-notifier[1815]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. ** Description changed: - Just freshly installed Ubuntu 20.04 on a bare metal Desktop (for testing - purpose only): While booting there is no Gnome showing up. Checking - syslog there are these messages ... + Just freshly installed Ubuntu 20.04 on a bare metal Desktop disk + partition (for testing purpose only): While booting there is no Gnome + showing up. Checking syslog there are these messages ... Dec 8 07:51:43 deblnxsrv100 xdg-desktop-por[1287]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Timeout was reached Dec 8 07:51:43 deblnxsrv100 at-spi-bus-launcher[1245]: X connection to :0 broken (explicit kill or server shutdown). Dec 8 07:51:44 deblnxsrv100 gsd-wacom[1522]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 gsd-xsettings[1538]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Main process exited, code=exited, status=1/FAILURE Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Failed with result 'exit-code'. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Triggering OnFailure= dependencies. Dec 8 07:51:44 deblnxsrv100 systemd[]: Stopped target GNOME XSettings. Dec 8 07:51:44 deblnxsrv100 systemd[]: Started GNOME Session Failed lockdown screen (user). Dec 8 07:51:44 deblnxsrv100 systemd[]: Reached target GNOME Session Failed. Dec 8 07:51:44 deblnxsrv100 update-notifier[1815]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. ** Description changed: Just freshly installed Ubuntu 20.04 on a bare metal Desktop disk partition (for testing purpose only): While booting there is no Gnome - showing up. Checking syslog there are these messages ... + showing up. Checking syslog for error's there are these messages ... Dec 8 07:51:43 deblnxsrv100 xdg-desktop-por[1287]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Timeout was reached Dec 8 07:51:43 deblnxsrv100 at-spi-bus-launcher[1245]: X connection to :0 broken (explicit kill or server shutdown). Dec 8 07:51:44 deblnxsrv100 gsd-wacom[1522]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 gsd-xsettings[1538]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Main process exited, code=exited, status=1/FAILURE Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Failed with result 'exit-code'. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Triggering OnFailure= dependencies. Dec 8 07:51:44 deblnxsrv100 systemd[]: Stopped target GNOME XSettings. Dec 8 07:51:44 deblnxsrv100 systemd[]: Started GNOME Session Failed lockdown screen (user). Dec 8 07:51:44 deblnxsrv100 systemd[]: Reached target GNOME Session
[Bug 1822416] Re: resolve: do not hit CNAME or DNAME entry in NODATA cache
Extra question: is Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP, as pointed related? https://www.linode.com/community/questions/17384/error-server-returned- error-nxdomain-mitigating-potential-dns-violation-dve-2018 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822416 Title: resolve: do not hit CNAME or DNAME entry in NODATA cache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1822416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822416] [NEW] resolve: do not hit CNAME or DNAME entry in NODATA cache
Public bug reported: The question: DNS A record lookups fail to resolve due to cached CNAME NODATA lookups ... https://askubuntu.com/questions/1063462/18-04-server-systemd-resolve- returns-cached-cname-nodata-for-a-lookup Upstream at Github: Systemd issue 998 - Cached cname NODATA returned for A lookup ... https://github.com/systemd/systemd/issues/9833 Please patch ... https://github.com/systemd/systemd/commit/3740146a4cbd99883af79e375ee4836206dcea4e ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: 18.04 systemd-resolved ** Tags added: 18.04 ** Tags added: systemd-resolved -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822416 Title: resolve: do not hit CNAME or DNAME entry in NODATA cache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1822416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796447] [NEW] package libgles1 (not installed) failed to install/upgrade: poging tot overschrijven van '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', wat ook in pakket nvidia-340 340.106-0ubuntu
Public bug reported: E: /tmp/apt-dpkg-install-mc273t/57-libgles1_1.0.0-2ubuntu2.2_amd64.deb: poging tot overschrijven van '/usr/lib/x86_64-linux- gnu/libGLESv1_CM.so.1', wat ook in pakket nvidia-340 340.106-0ubuntu3 zit ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgles1 (not installed) ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_34_37_generic_44 nvidia ApportVersion: 2.20.9-0ubuntu7.4 AptOrdering: libgles1:amd64: Install libglvnd-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Oct 6 05:48:39 2018 DpkgTerminalLog: Uitpakken van .../libgles1_1.0.0-2ubuntu2.2_amd64.deb wordt voorbereid... Bezig met uitpakken van libgles1:amd64 (1.0.0-2ubuntu2.2) ... [1mdpkg:[0m fout bij verwerken van archief /var/cache/apt/archives/libgles1_1.0.0-2ubuntu2.2_amd64.deb (--unpack): poging tot overschrijven van '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', wat ook in pakket nvidia-340 340.106-0ubuntu3 zit ErrorMessage: poging tot overschrijven van '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', wat ook in pakket nvidia-340 340.106-0ubuntu3 zit InstallationDate: Installed on 2014-09-03 (1493 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libglvnd Title: package libgles1 (not installed) failed to install/upgrade: poging tot overschrijven van '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', wat ook in pakket nvidia-340 340.106-0ubuntu3 zit UpgradeStatus: Upgraded to bionic on 2018-09-16 (19 days ago) ** Affects: libglvnd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796447 Title: package libgles1 (not installed) failed to install/upgrade: poging tot overschrijven van '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', wat ook in pakket nvidia-340 340.106-0ubuntu3 zit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1796447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791095] [NEW] package keyboard-configuration 1.178ubuntu2.6 failed to install/upgrade: geïnstalleerd keyboard-configuration pakket post-installation script subproces meldde een fout afsluitstatu
Public bug reported: keyboard-configuration console-setup-linux console-setup libdvd-pkg: Package libdvdcss2-1.4.2-1 was removed, stop processing... E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: keyboard-configuration 1.178ubuntu2.6 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Thu Sep 6 15:10:31 2018 DpkgHistoryLog: Start-Date: 2018-09-06 15:10:30 Commandline: apt-get install Requested-By: frans (1000) DpkgTerminalLog: Instellen van keyboard-configuration (1.178ubuntu2.6) ... /var/lib/dpkg/info/keyboard-configuration.config: 13: /etc/default/keyboard: Syntax error: Unterminated quoted string dpkg: fout bij verwerken van pakket keyboard-configuration (--configure): geïnstalleerd keyboard-configuration pakket post-installation script subproces meldde een fout afsluitstatus 2 ErrorMessage: geïnstalleerd keyboard-configuration pakket post-installation script subproces meldde een fout afsluitstatus 2 InstallationDate: Installed on 2018-06-20 (77 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: console-setup Title: package keyboard-configuration 1.178ubuntu2.6 failed to install/upgrade: geïnstalleerd keyboard-configuration pakket post-installation script subproces meldde een fout afsluitstatus 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791095 Title: package keyboard-configuration 1.178ubuntu2.6 failed to install/upgrade: geïnstalleerd keyboard-configuration pakket post- installation script subproces meldde een fout afsluitstatus 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1791095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791094] [NEW] package keyboard-configuration 1.178ubuntu2.6 failed to install/upgrade: geïnstalleerd keyboard-configuration pakket post-installation script subproces meldde een fout afsluitstatu
Public bug reported: keyboard-configuration console-setup-linux console-setup libdvd-pkg: Package libdvdcss2-1.4.2-1 was removed, stop processing... E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: keyboard-configuration 1.178ubuntu2.6 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Thu Sep 6 15:10:31 2018 DpkgHistoryLog: Start-Date: 2018-09-06 15:10:30 Commandline: apt-get install Requested-By: frans (1000) DpkgTerminalLog: Instellen van keyboard-configuration (1.178ubuntu2.6) ... /var/lib/dpkg/info/keyboard-configuration.config: 13: /etc/default/keyboard: Syntax error: Unterminated quoted string dpkg: fout bij verwerken van pakket keyboard-configuration (--configure): geïnstalleerd keyboard-configuration pakket post-installation script subproces meldde een fout afsluitstatus 2 ErrorMessage: geïnstalleerd keyboard-configuration pakket post-installation script subproces meldde een fout afsluitstatus 2 InstallationDate: Installed on 2018-06-20 (77 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: console-setup Title: package keyboard-configuration 1.178ubuntu2.6 failed to install/upgrade: geïnstalleerd keyboard-configuration pakket post-installation script subproces meldde een fout afsluitstatus 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791094 Title: package keyboard-configuration 1.178ubuntu2.6 failed to install/upgrade: geïnstalleerd keyboard-configuration pakket post- installation script subproces meldde een fout afsluitstatus 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1791094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782320] Re: Braille display inoperable in GUI since polkit-update
Have tested the brltty package in bionic-proposed as instructed in comment #12: v5.5-4ubuntu2.0.1 It works as expected. After commenting out the "api-parameters Auth=keyfile" line in brltty.conf and restarting the machine (just to be sure), my braille display works completely in both text console as in my GUI desktop. Thanks for fixing this! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782320 Title: Braille display inoperable in GUI since polkit-update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1782320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782320] Re: Braille display inoperable in GUI since polkit-update
Thanks to a member of the BrlTTY mailing list, my problem is solved. It seems that the default authorization of BrltTTY under Ubuntu was no longer working. Providing it with a dummy key-file was enough to get it back to work - instantly. The display came back to life immediately after these steps: - edit /etc/brltty.conf, uncomment the line "api-parameters Auth=keyfile:/etc/brlapi.key" - sudo touch /etc/brlapi.key - sudo chmod 0644 /etc/brlapi.key For me, the issue is solved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782320 Title: Braille display inoperable in GUI since polkit-update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1782320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782320] Re: Braille display inoperable in GUI since polkit-update
Have just replayed the upgrade in a VirtualBox VM using a clean install of Ubuntu 18.04. Before the upgrade (of policy-kit), the braille display works (both output and input). After the upgrade and reboot, the same errors appear in /var/log/syslog: Jul 18 11:49:43 test-VirtualBox brltty[409]: BrlAPI connection fd=27 accepted: local Jul 18 11:49:43 test-VirtualBox brltty[409]: brltty: BrlAPI connection fd=27 accepted: local Jul 18 11:49:43 test-VirtualBox brltty[409]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 11:49:43 test-VirtualBox brltty[409]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 11:49:43 test-VirtualBox brltty[409]: BrlAPI connection fd=27 accepted: local Jul 18 11:49:43 test-VirtualBox brltty[409]: brltty: BrlAPI connection fd=27 accepted: local Jul 18 11:49:43 test-VirtualBox brltty[409]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 11:49:43 test-VirtualBox brltty[409]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 11:49:43 test-VirtualBox brltty[409]: BrlAPI connection fd=27 accepted: local Jul 18 11:49:43 test-VirtualBox brltty[409]: brltty: BrlAPI connection fd=27 accepted: local Jul 18 11:49:43 test-VirtualBox brltty[409]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 11:49:43 test-VirtualBox brltty[409]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 11:49:43 test-VirtualBox brltty[409]: BrlAPI connection fd=27 accepted: local Jul 18 11:49:43 test-VirtualBox brltty[409]: brltty: BrlAPI connection fd=27 accepted: local Jul 18 11:49:43 test-VirtualBox brltty[409]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 11:49:43 test-VirtualBox brltty[409]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782320 Title: Braille display inoperable in GUI since polkit-update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1782320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782320] [NEW] Braille display inoperable in GUI since polkit-update
Public bug reported: $ lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 $ apt-cache policy brltty brltty: Installed: 5.5-4ubuntu2 Candidate: 5.5-4ubuntu2 Version table: *** 5.5-4ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy policykit-1-gnome policykit-1-gnome: Installed: (none) Candidate: 0.105-6ubuntu2 Version table: 0.105-6ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Expected behavior: After a system upgrade, the braille display should function as before the upgrade. Actual behavior: Since the upgrade, the braille display only works in console mode (Ctrl+Alt+F3, -F4, etc.) In GUI mode, the display reads "Screen not in text mode". Restarting Orca (screenreader) has no effect. Restarting the system has no effect. This is the upgrade command, taken from /var/log/apt/history.log: Start-Date: 2018-07-17 07:47:02 Commandline: /usr/bin/unattended-upgrade Upgrade: libpolkit-gobject-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-agent-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-backend-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), policykit-1:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), gir1.2-polkit-1.0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1) End-Date: 2018-07-17 07:47:04 These are the error messages taken from /var/log/syslog: Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: brltty 5.5-4ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jul 18 11:03:27 2018 ExecutablePath: /bin/brltty InstallationDate: Installed on 2018-05-15 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LocalLibraries: /usr/local/lib/libgpg-error.so.0.24.2 /usr/local/lib/libgcrypt.so.20.2.2 SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.brltty.conf: 2018-05-16T09:36:35.497752 ** Affects: brltty (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic brltty local-libs policy-kit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782320 Title: Braille display inoperable in GUI since polkit-update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1782320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764643] Re: Logout after console use freezes GUI
I'm sorry, but I no longer have the crash-report. I performed a clean install of Ubuntu (now 18.04) and the bug is gone. Next to the release difference (17.10 to 18.04), I did not install the nVidia proprietary driver. For me, this problem's solved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764643 Title: Logout after console use freezes GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1764643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764643] Re: Logout after console use freezes GUI
Finally making some headway, I tried the following: 1. boot the system. 2. at the graphical login prompt, switch to another console (Ctrl+Alt+F2) 3. login 4. logout The screen displays the GUI login prompt but hangs. I can still login on this console using the braille display. 5. Log in from another machine using SSH 6. sudo killall -ABRT gdm-x-session The working GUI login prompt appears and lets me log in. I now have a crash report of this call to killall. Should I report it, and include its number here, as I did before? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764643 Title: Logout after console use freezes GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1764643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764643] Re: Logout after console use freezes GUI
Trying to reproduce on different system (laptop). Same Ubuntu release and GNOME/my desktop system, GDM packages. $ lsb_release -rd Description:Ubuntu 17.10 Release:17.10 $ apt-cache policy gdm3 gdm3: Installed: 3.26.1-3ubuntu3 Candidate: 3.26.1-3ubuntu3 Version table: *** 3.26.1-3ubuntu3 500 500 http://nl.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.26.1-3ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu artful/main amd64 Packages The bug is not present. I can switch to a console, log in and log out. I am returned to the text-only login prompt. On my desktop system (with the bug), GDM takes control of the screen at logout. I then have to reboot the system to get control again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764643 Title: Logout after console use freezes GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1764643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764643] Re: Logout after console use freezes GUI
Trying to pin this bug down, I deactivated nVIDIA's driver, reactivated nouveau and rebooted. Sadly, the problem still persists. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764643 Title: Logout after console use freezes GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1764643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764643] Re: Logout after console use freezes GUI
Thanks. I uninstalled LIRC, just to be on the safe side. Orca is necessary for my using the computer. I uncommented the line #WaylandEnable=false and rebooted. The problem still persists. Then, without logging in graphically, I switched to tty3 (Ctrl+Alt+F3). Logged in, executed a single command "who", then exited using Ctrl+D. GDM (or Gnome-shell?) shows the time and date. The mouse pointer sits in the center of the screen and can no longer move. The keyboard no longer does anything, except Ctrl+Alt+F1. When I do that, the screen goes black and the system freezes totally - or at least all inputs like keyboard, mouse and braille display do. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764643 Title: Logout after console use freezes GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1764643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764643] Re: Logout after console use freezes GUI
As requested, I killed both gdm3 and gnome-shell. The bug-ids are #1764672 and #1764674 respectively. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764643 Title: Logout after console use freezes GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1764643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764643] Re: Logout after console use freezes GUI
I followed your instructions; commented out the line in /etc/apport/crashdb.conf, reproduced the problem, but there are no crash-files in /var/crash. Sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764643 Title: Logout after console use freezes GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1764643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764643] [NEW] Logout after console use freezes GUI
Public bug reported:
Hello,
Ubuntu 17.10 64 bit
GNOME 3.26.2
nVIDIA GeForce GT620 driver 384.111
X-server 11.0, v1.19.5
Orca + braille enabled
$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
$ apt-cache policy gdm3
gdm3:
Installed: 3.26.1-3ubuntu3
Candidate: 3.26.1-3ubuntu3
Version table:
*** 3.26.1-3ubuntu3 500
500 http://nl.archive.ubuntu.com/ubuntu artful-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.26.1-3ubuntu2 500
500 http://nl.archive.ubuntu.com/ubuntu artful/main amd64 Packages
Every now and then, I use the console-terminals (Ctrl+Alt+F2-F6). When I'm done
there, I logout (exit or Ctrl+D). The problem I describe occurs both when
logged in graphically, or not. So it doesn't matter if there is a running GUI
session.
GDM then shows me a graphical screen with the clock and a mouse pointer.
The pointer does no longer move. On my braille display, I can read the
standard login prompt ("hostname-login:", then "password:"). I can login
using the keyboard and access the console this way (blind, without any
visual change).
What happens:
I can not get back to the standard GDM user selection, i.e. login form.
What would I expect:
I would like to be presented the GDM user selection form
If you need more info, please ask.
Kind regards,
FWieP
** Affects: gdm3 (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/1764643
Title:
Logout after console use freezes GUI
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1764643/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743379] [NEW] Installation failed late because of UEFI partition was not created during manual disk set up
Public bug reported: Fresh installation of Ubuntu 17.10.1. Apparently this new motherboard is configured in UEFI mode. Because wanting total control of the partitioning schema used, I chose manual partitioning in the beginning of the installation. When installing "grub-uefi-something-whatever-64" (cannot now verify the exact name of the package, because I cannot find how to start terminal application in this aborted installation), it failed due to missing UEFI system partition. When I acknowledged the failure there was also this crash. So I see two issues here: 1. abrupt crash of the installer 2. not warning of the missing UEFI partition before accepting the manually created partition table (in an earlier installation attempt there was a warning about swap not being encrypted and subsequent refusal to continue the installation, meaning there seems to be some other checks of similar nature in place). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubiquity 17.10.10 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CasperVersion: 1.387 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 15 21:03:40 2018 LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743379 Title: Installation failed late because of UEFI partition was not created during manual disk set up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1743379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743379] Re: Installation failed late because of UEFI partition was not created during manual disk set up
Calling 'apt-install grub-efi-amd64-signed' failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743379 Title: Installation failed late because of UEFI partition was not created during manual disk set up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1743379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1701851] [NEW] package phabricator 0~git20160124-1ubuntu1 failed to install/upgrade: subproces post-installation script geïnstalleerd gaf een foutwaarde 1 terug
Public bug reported: Set 'phabricator.base-uri' in local configuration. Set 'mysql.host' in local configuration. Set 'mysql.user' in local configuration. Set 'mysql.pass' in local configuration. MySQL Credentials Not Configured Unable to connect to MySQL using the configured credentials. You must configure standard credentials before you can upgrade storage. Run these commands to set up credentials: phabricator/ $ ./bin/config set mysql.host __host__ phabricator/ $ ./bin/config set mysql.user __username__ phabricator/ $ ./bin/config set mysql.pass __password__ These standard credentials are separate from any administrative credentials provided to this command with __--user__ or __--password__, and must be configured correctly before you can proceed. Raw MySQL Error: Attempt to connect to aklub@localhost failed with error #1698: Access denied for user 'aklub'@'localhost'. dpkg: fout bij verwerken van pakket phabricator (--configure): subproces post-installation script geïnstalleerd gaf een foutwaarde 1 terug Fouten gevonden tijdens verwerken van: phabricator E: Sub-process /usr/bin/dpkg returned an error code (1) aklub@aklub:~$ ^C ProblemType: Package DistroRelease: Ubuntu 16.10 Package: phabricator 0~git20160124-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-56.61-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.3 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Sat Jul 1 23:04:30 2017 DpkgHistoryLog: Start-Date: 2017-07-01 23:04:28 Commandline: apt-get autoremove Requested-By: aklub (1000) ErrorMessage: subproces post-installation script geïnstalleerd gaf een foutwaarde 1 terug InstallationDate: Installed on 2017-01-17 (165 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1.1 apt 1.3.5 SourcePackage: phabricator Title: package phabricator 0~git20160124-1ubuntu1 failed to install/upgrade: subproces post-installation script geïnstalleerd gaf een foutwaarde 1 terug UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: phabricator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701851 Title: package phabricator 0~git20160124-1ubuntu1 failed to install/upgrade: subproces post-installation script geïnstalleerd gaf een foutwaarde 1 terug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phabricator/+bug/1701851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687623] Re: linux-4.4.0-77.98 was a phased update in -updates only and may become partially installed (was: 4.4.0-77-generic breaks internet on 16.04.2)
I just ran Software Updater and after reboot I am now running kernel 4.8.0-53-generic without problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687623 Title: linux-4.4.0-77.98 was a phased update in -updates only and may become partially installed (was: 4.4.0-77-generic breaks internet on 16.04.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687623] Re: linux-4.4.0-77.98 was a phased update in -updates only and may become partially installed (was: 4.4.0-77-generic breaks internet on 16.04.2)
I just updated Ubuntu 16.04.2 kernel 4.4.0-75. New linux- image-4.4.0-77-generic was installed along with the corresponding linux- image-extra and linux-headers. After reboot both WiFi and ethernet work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687623 Title: linux-4.4.0-77.98 was a phased update in -updates only and may become partially installed (was: 4.4.0-77-generic breaks internet on 16.04.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop
4.4.0-75.96 works for me too with x64 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666421 Title: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop
Confirm 4.4.0-74.95 from xenial-proposed works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666421 Title: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop
Perhaps you forgot to install the corresponding linux-image-extra ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666421 Title: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop
Confirm 4.4.0-73.94 from proposed works. No freeze and good WiFi connection. ID 0b05:17ba ASUSTek Computer, Inc. N10 Nano 802.11n Network Adapter [Realtek RTL8192CU] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666421 Title: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1681128] [NEW] bug report
Public bug reported: grub not started Linux Mint Mate and Ubuntu Mate on the same system ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubiquity 16.10.14 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CasperVersion: 1.379 Date: Sat Apr 8 20:40:48 2017 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu-mate.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) ProcEnviron: LANGUAGE=nl_NL.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-16.10.14 ubuntu-mate yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1681128 Title: bug report To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1681128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678806] [NEW] package 389-admin 1.1.43-1 failed to install/upgrade: subproces post-installation script geïnstalleerd gaf een foutwaarde 1 terug
Public bug reported: not installed ProblemType: Package DistroRelease: Ubuntu 16.10 Package: 389-admin 1.1.43-1 ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17 Uname: Linux 4.8.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Mon Apr 3 08:59:30 2017 ErrorMessage: subproces post-installation script geïnstalleerd gaf een foutwaarde 1 terug InstallationDate: Installed on 2016-12-05 (118 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.5 SourcePackage: 389-admin Title: package 389-admin 1.1.43-1 failed to install/upgrade: subproces post-installation script geïnstalleerd gaf een foutwaarde 1 terug UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: 389-admin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678806 Title: package 389-admin 1.1.43-1 failed to install/upgrade: subproces post- installation script geïnstalleerd gaf een foutwaarde 1 terug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/389-admin/+bug/1678806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673687] [NEW] lx-ls crashes and dumps core
Public bug reported: See https://github.com/lxc/lxc/issues/1466 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.9-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-110.157-generic 3.13.11-ckt39 Uname: Linux 3.13.0-110-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Fri Mar 17 08:06:13 2017 KernLog: SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673687 Title: lx-ls crashes and dumps core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1673687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668049] Re: lxd cannot shutdown container
Sorry for the long message, I did reply from email and forgot to delete the old message (actually assumed that only new text would be uploaded to launchpad). Frans -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668049 Title: lxd cannot shutdown container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668049] Re: lxd cannot shutdown container
** Bug watch added: LXD bug tracker #2947 https://github.com/lxc/lxd/issues/2947 ** Bug watch added: LXC bug tracker #1085 https://github.com/lxc/lxc/issues/1085 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668049 Title: lxd cannot shutdown container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1668049] Re: lxd cannot shutdown container
Hi, "shutdown --halt now" stops the container as does "shutdown now" If I omit the now part and just do shutdown --halt I get: root@D-wan-61-1:~# shutdown --halt Failed to set wall message, ignoring: Refusing activation, D-Bus is shutting down. Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Refusing activation, D-Bus is shutting down and I get a prompt again Just running shutdowngives the same message. From: Dimitri John Ledkov <launch...@surgut.co.uk> To: fransmeulenbro...@yahoo.com Sent: Monday, 27 February 2017, 12:34 Subject: [Bug 1668049] Re: lxd cannot shutdown container `shutdown now` executes poweroff command which in systemd signals manpage documented as: SIGRTMIN+4 Powers off the machine, starts the poweroff.target unit. This is mostly equivalent to systemctl start poweroff.target. The logs indicate that lxc is sending SIGRTMIN+3 Halts the machine, starts the halt.target unit. This is mostly equivalent to systemctl start halt.target. Note that in addition to above, systemd have more immediate variants for these: SIGRTMIN+13 Immediately halts the machine. SIGRTMIN+14 Immediately powers off the machine. Could you please start the affected containter and try `shutdown --halt now` and check if that hangs as well? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1668049 Title: lxd cannot shutdown container Status in systemd package in Ubuntu: New Bug description: I found this issue when working with lxd and submitted a ticket there but the lxc people said it was related to systemd, not lxc. The issue is: I have a container running under lxc/lxd. lxc stop of the container does not work whereas if I execute "shutdown now" inside the container it does stop as expected. The associated lxd ticket is here: https://github.com/lxc/lxd/issues/2947 The output of journalctl -a is at the end of this message The syslog of that same run can be found here: http://paste.ubuntu.com/24071244/ and this is the output of ps aux: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.1 37808 4576 ? Ss 11:19 0:00 /sbin/init root 48 0.0 0.0 35276 3004 ? Ss 11:19 0:00 /lib/systemd/systemd-journald root 49 0.0 0.0 41724 1912 ? Ss 11:19 0:00 /lib/systemd/systemd-udevd message+ 514 0.0 0.0 42900 2460 ? Ss 11:19 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation root 704 0.0 0.0 18252 2508 ? Ss 11:55 0:00 bash root 720 0.0 0.0 34556 1992 ? R+ 11:59 0:00 ps aux Note that this may be timing related. If I stop the container immediately after starting things work. If I stop after a minute or so, the stop will not get through. (even not on a 2nd or 3rd attempt). However if I leave the container for a while then a new lxc stop will terminate the container. (this happened after an hour or so). The issue is reproducible but seems to be dependend on what is running inside the container. container runs ubuntu 16.04 on a 16.04 host. systemd --version says: systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN lxc sends SIGRTMIN+3 to systemd to stop. This was apparently discussed here: https://github.com/lxc/lxc/issues/1085 Let me know if more info is needed. Frans -- Logs begin at Sun 2017-02-26 11:19:12 UTC, end at Sun 2017-02-26 11:23:05 UTC. -- Feb 26 11:19:12 D-wan-61-1 systemd-journald[48]: Runtime journal (/run/log/journal/) is 8.0M, max 196.7M, 188.7M free. Feb 26 11:19:12 D-wan-61-1 systemd-journald[48]: Journal started Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '4 4 1 7' to 'kernel/printk', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '176' to 'kernel/sysrq', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '1' to 'fs/protected_symlinks', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '1' to 'net/ipv4/tcp_syncookies', ignoring: No such file or directory Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '1' to 'kernel/kptr_restrict', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '1' to 'fs/protected_hardlinks', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '1' to 'kernel/yama/ptrace_scope', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '65536' to 'vm/mmap_min_addr', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd[1]: systemd-sysctl.service: Main process e
[Bug 1668049] Re: lxd cannot shutdown container
I don't think systemd changed its shutdown signal as I have other 1604 based containers that stop as expected. To me it seems that systemd wants to stop a process and hangs waiting for it (whereas shutdown now does stop the system) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668049 Title: lxd cannot shutdown container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668049] [NEW] lxd cannot shutdown container
Public bug reported: I found this issue when working with lxd and submitted a ticket there but the lxc people said it was related to systemd, not lxc. The issue is: I have a container running under lxc/lxd. lxc stop of the container does not work whereas if I execute "shutdown now" inside the container it does stop as expected. The associated lxd ticket is here: https://github.com/lxc/lxd/issues/2947 The output of journalctl -a is at the end of this message The syslog of that same run can be found here: http://paste.ubuntu.com/24071244/ and this is the output of ps aux: USERPID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.1 37808 4576 ?Ss 11:19 0:00 /sbin/init root 48 0.0 0.0 35276 3004 ?Ss 11:19 0:00 /lib/systemd/systemd-journald root 49 0.0 0.0 41724 1912 ?Ss 11:19 0:00 /lib/systemd/systemd-udevd message+514 0.0 0.0 42900 2460 ?Ss 11:19 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation root704 0.0 0.0 18252 2508 ?Ss 11:55 0:00 bash root720 0.0 0.0 34556 1992 ?R+ 11:59 0:00 ps aux Note that this may be timing related. If I stop the container immediately after starting things work. If I stop after a minute or so, the stop will not get through. (even not on a 2nd or 3rd attempt). However if I leave the container for a while then a new lxc stop will terminate the container. (this happened after an hour or so). The issue is reproducible but seems to be dependend on what is running inside the container. container runs ubuntu 16.04 on a 16.04 host. systemd --version says: systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN lxc sends SIGRTMIN+3 to systemd to stop. This was apparently discussed here: https://github.com/lxc/lxc/issues/1085 Let me know if more info is needed. Frans -- Logs begin at Sun 2017-02-26 11:19:12 UTC, end at Sun 2017-02-26 11:23:05 UTC. -- Feb 26 11:19:12 D-wan-61-1 systemd-journald[48]: Runtime journal (/run/log/journal/) is 8.0M, max 196.7M, 188.7M free. Feb 26 11:19:12 D-wan-61-1 systemd-journald[48]: Journal started Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '4 4 1 7' to 'kernel/printk', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '176' to 'kernel/sysrq', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '1' to 'fs/protected_symlinks', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '1' to 'net/ipv4/tcp_syncookies', ignoring: No such file or directory Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '1' to 'kernel/kptr_restrict', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '1' to 'fs/protected_hardlinks', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '1' to 'kernel/yama/ptrace_scope', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd-sysctl[42]: Couldn't write '65536' to 'vm/mmap_min_addr', ignoring: Permission denied Feb 26 11:19:12 D-wan-61-1 systemd[1]: systemd-sysctl.service: Main process exited, code=exited, status=1/FAILURE Feb 26 11:19:12 D-wan-61-1 systemd[1]: Failed to start Apply Kernel Variables. Feb 26 11:19:12 D-wan-61-1 systemd[1]: systemd-sysctl.service: Unit entered failed state. Feb 26 11:19:12 D-wan-61-1 systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'. Feb 26 11:19:12 D-wan-61-1 systemd-journald[48]: Forwarding to syslog missed 1 messages. Feb 26 11:19:12 D-wan-61-1 systemd[1]: Started Uncomplicated firewall. Feb 26 11:19:12 D-wan-61-1 systemd[1]: Failed to reset devices.list on /system.slice/ufw.service: Operation not permitted Feb 26 11:19:12 D-wan-61-1 systemd[1]: Started udev Kernel Device Manager. Feb 26 11:19:12 D-wan-61-1 mount[45]: mount: permission denied Feb 26 11:19:12 D-wan-61-1 systemd[1]: Started Nameserver information manager. Feb 26 11:19:12 D-wan-61-1 systemd[1]: dev-hugepages.mount: Mount process exited, code=exited status=32 Feb 26 11:19:12 D-wan-61-1 systemd[1]: Failed to mount Huge Pages File System. Feb 26 11:19:12 D-wan-61-1 systemd[1]: dev-hugepages.mount: Unit entered failed state. Feb 26 11:19:12 D-wan-61-1 systemd-remount-fs[44]: mount: can't find LABEL=cloudimg-rootfs Feb 26 11:19:12 D-wan-61-1 systemd-remount-fs[44]: /bin/mount for / exited with exit status 1. Feb 26 11:19:12 D-wan-61-1 systemd[1]: systemd-remount-fs.service: Main process exited, code=exited, status=1/FAILURE Feb 26 11:19:12 D-wan-61-1 systemd[1]: Failed to start Remount Root and Kernel File Systems. Feb 26 11:19:12 D-wan-61-1 systemd[1]: systemd-remount-fs.service: Unit entered failed state. Feb 26 11:19:12 D-wan-61-1 systemd[1
[Bug 1663073] Re: this package installs nvidia-352 upto nvidia-367 and jumps to login forever
** Description changed: + After login, the screen turns black and jumps back to + the login screen + + I typed + sudo apt-get install nvidia-352 + the package installs all newer updates upto nvidia-367 + which I did not want to try + Ubuntu 16.04 LTS NV34 [GeForce FX 5200] Dell 8300 Pentium 4 - 2.6GHz 2x1GB DDR400 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1663073 Title: this package installs nvidia-352 upto nvidia-367 and jumps to login forever To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-352/+bug/1663073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1663073] [NEW] this package installs nvidia-352 upto nvidia-367 and jumps to login forever
Public bug reported: Ubuntu 16.04 LTS NV34 [GeForce FX 5200] Dell 8300 Pentium 4 - 2.6GHz 2x1GB DDR400 ** Affects: nvidia-graphics-drivers-352 (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/1663073 Title: this package installs nvidia-352 upto nvidia-367 and jumps to login forever To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-352/+bug/1663073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 344878] Re: file name too long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry)
Long too path error! "Long path tool" is very helpful for this problem. You can solve this problem like copy, delete, long path files by using this tool. I used to have similar problems too, but after using "long path tool" everything was solved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/344878 Title: file name too long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/344878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 344878] Re: file name too long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry)
Long too path error! "Long path tool" is very helpful for this problem. You can solve this problem like copy, delete, long path files by using this tool.I used to have similar problems too, but after using "long path tool" everything was solved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/344878 Title: file name too long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/344878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565985] Re: vagrant vb ubuntu/xenial64 cannot mount synced folders
** Changed in: cloud-images 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/1565985 Title: vagrant vb ubuntu/xenial64 cannot mount synced folders To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1565985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1562291] Re: Calibre starts and screws up the graphical user interface - problem solved
** Summary changed: - Calibre starts and screws up the graphical user interface + Calibre starts and screws up the graphical user interface - problem solved ** Summary changed: - Calibre starts and screws up the graphical user interface - problem solved + Calibre starts and screws up the graphical user interface - update dd. 20160505: problem solved -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1562291 Title: Calibre starts and screws up the graphical user interface - update dd. 20160505: problem solved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1562291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1562291] Re: Calibre starts and screws up the graphical user interface
I tried the following, inspired by one of the comments in another bug
report. In a terminal I ran the following commands:
sudo rm -fr /opt/calibre
sudo rm -fr ~/.config/calibre
After that I manually removed calibre from the desktop starter bar.
After that I did an install from the Calibre website https://calibre-
ebook.com/download_linux and ran the command headlined "binary install"
in a terminal:
sudo -v && wget -nv -O-
https://raw.githubusercontent.com/kovidgoyal/calibre/master/setup/linux-
installer.py | sudo python -c "import sys;
main=lambda:sys.stderr.write('Download failed\n');
exec(sys.stdin.read()); main()"
After that all seems fine now..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1562291
Title:
Calibre starts and screws up the graphical user interface
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1562291/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1562291] Re: Calibre starts and screws up the graphical user interface
** Attachment added: "Desktop screenshot with Calibre started." https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1562291/+attachment/4656458/+files/CAM00249.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1562291 Title: Calibre starts and screws up the graphical user interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1562291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1562291] Re: Calibre starts and screws up the graphical user interface
** Attachment added: "Desktop screenshot" https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1562291/+attachment/4656457/+files/CAM00250.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1562291 Title: Calibre starts and screws up the graphical user interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1562291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1562291] [NEW] Calibre starts and screws up the graphical user interface
Public bug reported: When starting Calibre from the sidebar by clicking on it, the splash screen is shown (a picture of a shelf of books) and the text loading user interface is displayed. After this, the user interface is corrupted. Not only for Calibre, but for other parts of the system as well. For instance the comments when hovering over the icons of the sidebar are displayed permanently, even when moving to hover over another sidebar icon. When right-clicking the Calibre icon on the sidebar and selecting Exit, the user interface seems to function normal again ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: calibre 2.48.0+dfsg-1build1 [modified: usr/bin/calibre usr/bin/calibre-customize usr/bin/calibre-debug usr/bin/calibre-parallel usr/bin/calibre-server usr/bin/calibre-smtp usr/bin/calibredb usr/bin/ebook-convert usr/bin/ebook-device usr/bin/ebook-edit usr/bin/ebook-meta usr/bin/ebook-polish usr/bin/ebook-viewer usr/bin/fetch-ebook-metadata usr/bin/lrf2lrs usr/bin/lrfviewer usr/bin/lrs2lrf usr/bin/markdown-calibre usr/bin/web2disk usr/share/applications/calibre-gui.desktop] ProcVersionSignature: Ubuntu 4.4.0-2.16-lowlatency 4.4.0 Uname: Linux 4.4.0-2-lowlatency i686 ApportVersion: 2.19.4-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Sat Mar 26 12:41:45 2016 InstallationDate: Installed on 2016-01-08 (77 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) PackageArchitecture: all SourcePackage: calibre UpgradeStatus: Upgraded to xenial on 2016-02-06 (48 days ago) ** Affects: calibre (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1562291 Title: Calibre starts and screws up the graphical user interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1562291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457776] Re: virtualbox-dkms 4.3.10-dfsg-1ubuntu5: virtualbox kernel module failed to build
Same story as Eduar: just installed Ubuntu 14.04.3 on a new ASUS N751IJ laptop. Through Ubuntu Software Centrum I installed VirtualBox 4.3.10 and get the following error: Loading new virtualbox-4.3.10 DKMS files... First Installation: checking all kernels... Building only for 3.19.0-25-generic Building initial module for 3.19.0-25-generic Error! Bad return status for module build on kernel: 3.19.0-25-generic (x86_64) Consult /var/lib/dkms/virtualbox/4.3.10/build/make.log for more information. * Stopping VirtualBox kernel modules [ OK ] * Starting VirtualBox kernel modules * No suitable module for running kernel found [fail] invoke-rc.d: initscript virtualbox, action restart failed. The make.log file contains the following errors: Loading new virtualbox-4.3.10 DKMS files... First Installation: checking all kernels... Building only for 3.19.0-25-generic Building initial module for 3.19.0-25-generic Error! Bad return status for module build on kernel: 3.19.0-25-generic (x86_64) Consult /var/lib/dkms/virtualbox/4.3.10/build/make.log for more information. * Stopping VirtualBox kernel modules [ OK ] * Starting VirtualBox kernel modules * No suitable module for running kernel found [fail] invoke-rc.d: initscript virtualbox, action restart failed. ... /var/lib/dkms/virtualbox/4.3.10/build/vboxnetadp/linux/VBoxNetAdp-linux.c: In function ‘vboxNetAdpOsCreate’: /var/lib/dkms/virtualbox/4.3.10/build/vboxnetadp/linux/VBoxNetAdp-linux.c:186:48: error: macro alloc_netdev requires 4 arguments, but only 3 given vboxNetAdpNetDevInit); ^ /var/lib/dkms/virtualbox/4.3.10/build/vboxnetadp/linux/VBoxNetAdp-linux.c:184:15: error: ‘alloc_netdev’ undeclared (first use in this function) pNetDev = alloc_netdev(sizeof(VBOXNETADPPRIV), ^ /var/lib/dkms/virtualbox/4.3.10/build/vboxnetadp/linux/VBoxNetAdp-linux.c:184:15: note: each undeclared identifier is reported only once for each function it appears in /var/lib/dkms/virtualbox/4.3.10/build/vboxnetadp/linux/VBoxNetAdp-linux.c: At top level: /var/lib/dkms/virtualbox/4.3.10/build/vboxnetadp/linux/VBoxNetAdp-linux.c:159:13: warning: ‘vboxNetAdpNetDevInit’ defined but not used [-Wunused-function] static void vboxNetAdpNetDevInit(struct net_device *pNetDev) ^ make[2]: *** [/var/lib/dkms/virtualbox/4.3.10/build/vboxnetadp/linux/VBoxNetAdp-linux.o] Error 1 make[1]: *** [/var/lib/dkms/virtualbox/4.3.10/build/vboxnetadp] Error 2 make: *** [_module_/var/lib/dkms/virtualbox/4.3.10/build] Error 2 make: Leaving directory `/usr/src/linux-headers-3.19.0-25-generic' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457776 Title: virtualbox-dkms 4.3.10-dfsg-1ubuntu5: virtualbox kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1457776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448500] Re: tftp-hpa doesn't accept IPv4 connections
It seems tftpd-hpa interprets option --address ::69 to mean that only listen on IPv6: 1. By default (with TFTP_ADDRESS=[::]:69) it is started as /usr/sbin/in.tftpd --listen --user tftp --address [::]:69 --secure --create /srv/tftp 2. netstat (command sudo netstat -anutp | grep '[:]69') shows: udp6 0 0 :::69 :::* 10681/in.tftpd I do not know and I am not interested to check the source code if there is way to explicitly tell tftpd-hpa to listen on all interfaces, both IPv4 and IPv6, but if you just omit the --address option, tftpd-hpa - per netstat output - listens on all interfaces both IPv4 and IPv6; when I start tftp-hpa as /usr/sbin/in.tftpd --listen --user tftp --secure --create /srv/tftp then netstat shows udp0 0 0.0.0.0:69 0.0.0.0:* 24607/in.tftpd udp6 0 0 :::69 :::* 24607/in.tftpd I accomplished this by hacking /etc/init.d/tftpd-hpa as follows: diff --git a/init.d/tftpd-hpa b/init.d/tftpd-hpa index 115ca4e..a4a5b60 100755 --- a/init.d/tftpd-hpa +++ b/init.d/tftpd-hpa @@ -52,9 +52,15 @@ do_start() fi done + if [ $TFTP_ADDRESS = [::]:69 ]; then# all interfaces + start-stop-daemon --start --quiet --oknodo --exec $DAEMON -- \ +--listen --user $TFTP_USERNAME \ + $TFTP_OPTIONS $TFTP_DIRECTORY + else start-stop-daemon --start --quiet --oknodo --exec $DAEMON -- \ --listen --user $TFTP_USERNAME --address $TFTP_ADDRESS \ $TFTP_OPTIONS $TFTP_DIRECTORY + fi } do_stop () -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448500 Title: tftp-hpa doesn't accept IPv4 connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/1448500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448500] Re: tftp-hpa doesn't accept IPv4 connections
NOTE: There is an obvious limitation in the above solution - if you want to listen on different port then you are back to square one. I wish this helps someone to bypass the problem while waiting for proper and complete fix. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tftp-hpa in Ubuntu. https://bugs.launchpad.net/bugs/1448500 Title: tftp-hpa doesn't accept IPv4 connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/1448500/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1448500] Re: tftp-hpa doesn't accept IPv4 connections
NOTE: There is an obvious limitation in the above solution - if you want to listen on different port then you are back to square one. I wish this helps someone to bypass the problem while waiting for proper and complete fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448500 Title: tftp-hpa doesn't accept IPv4 connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/1448500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448500] Re: tftp-hpa doesn't accept IPv4 connections
It seems tftpd-hpa interprets option --address ::69 to mean that only listen on IPv6: 1. By default (with TFTP_ADDRESS=[::]:69) it is started as /usr/sbin/in.tftpd --listen --user tftp --address [::]:69 --secure --create /srv/tftp 2. netstat (command sudo netstat -anutp | grep '[:]69') shows: udp6 0 0 :::69 :::* 10681/in.tftpd I do not know and I am not interested to check the source code if there is way to explicitly tell tftpd-hpa to listen on all interfaces, both IPv4 and IPv6, but if you just omit the --address option, tftpd-hpa - per netstat output - listens on all interfaces both IPv4 and IPv6; when I start tftp-hpa as /usr/sbin/in.tftpd --listen --user tftp --secure --create /srv/tftp then netstat shows udp0 0 0.0.0.0:69 0.0.0.0:* 24607/in.tftpd udp6 0 0 :::69 :::* 24607/in.tftpd I accomplished this by hacking /etc/init.d/tftpd-hpa as follows: diff --git a/init.d/tftpd-hpa b/init.d/tftpd-hpa index 115ca4e..a4a5b60 100755 --- a/init.d/tftpd-hpa +++ b/init.d/tftpd-hpa @@ -52,9 +52,15 @@ do_start() fi done + if [ $TFTP_ADDRESS = [::]:69 ]; then# all interfaces + start-stop-daemon --start --quiet --oknodo --exec $DAEMON -- \ +--listen --user $TFTP_USERNAME \ + $TFTP_OPTIONS $TFTP_DIRECTORY + else start-stop-daemon --start --quiet --oknodo --exec $DAEMON -- \ --listen --user $TFTP_USERNAME --address $TFTP_ADDRESS \ $TFTP_OPTIONS $TFTP_DIRECTORY + fi } do_stop () -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tftp-hpa in Ubuntu. https://bugs.launchpad.net/bugs/1448500 Title: tftp-hpa doesn't accept IPv4 connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/1448500/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1424013] Re: Compiz high CPU and UI freeze on NVIDIA after fix for #269904 in trusty-updates
After implementation of this change the system start OK but with a black screen, where only the mouse pointer is visible. The system has an NVIDIA video card. Implementation the change seems linked to changes for OpenGL, so I cannot install these without installing this one. The only solution was to restore the system and to not implement the Compiz and OpenGL updates, Although I do not know enough about Linux to be absolutely sure that this problem is caused by this update I do hope this can be solved. Kind regards, Frans Timmers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1424013 Title: Compiz high CPU and UI freeze on NVIDIA after fix for #269904 in trusty-updates To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1424013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400365] Re: Intel PRO/1000 network driver e1000e doesn't always regain connection
I'm still new to this Kubuntu bug fixing process and the preceding comment doesn't say whether this is directed at the reporter (me), but I went ahead and installed the 3.13.0-45 kernel packages from trusty-proposed yesterday. Tested on home and office LAN: booted with just Wifi, docked the laptop, and it acquired the wired connection without a hitch. Encountered no other issues either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400365 Title: Intel PRO/1000 network driver e1000e doesn't always regain connection To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1400365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384981] Re: system-settings transparent
I had som problem with my sound and tried to sudo apt-get remove --purge alsa-base pulseaudio indicator-sound then I saw that it was going to install some gnome stuff and after that the settings got transparent -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384981 Title: system-settings transparent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1384981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384981] Re: system-settings transparent
I run sudo apt-get remove gnome-settings-daemon and now everything works -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384981 Title: system-settings transparent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1384981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1411884] [NEW] not all CPU cores loaded during boot
Public bug reported: During boot, at dmesg timestamp 0, the kernel complains about fast TSC calibration failed. Then at around timestamp 7.9 the kernel complains about smpboot: CPU1: Not responding. After some more time, it will also say CPU2 and CPU3 aren't responding either. The computer proceeds to boot successfully, but only using 1 CPU core out of my quad core CPU (and as you might guess this makes it rather slow). According to /proc/cpuinfo my computer only recognizes a single core on my computer. Here's the output of uname -a Linux Hostname 3.16.0-29-generic #39-Ubuntu SMP Mon Dec 15 22:27:29 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux I'll attach dmesg and lspci outputs as well. I've also attached my /proc/cpuinfo file as it proves that my computer only recognizes one of my 4 cores. Also, this problem is absent on the 3.16.0-23 kernel. ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Attachment added: dmesg.log https://bugs.launchpad.net/bugs/1411884/+attachment/4300249/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1411884 Title: not all CPU cores loaded during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1411884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1411884] Re: not all CPU cores loaded during boot
** Attachment added: version.log https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1411884/+attachment/4300252/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1411884 Title: not all CPU cores loaded during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1411884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1411884] Re: not all CPU cores loaded during boot
** Attachment added: cpuinfo.log https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1411884/+attachment/4300250/+files/cpuinfo.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1411884 Title: not all CPU cores loaded during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1411884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1411884] Re: not all CPU cores loaded during boot
** Attachment added: lspci-vvnn.log https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1411884/+attachment/4300251/+files/lspci-vvnn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1411884 Title: not all CPU cores loaded during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1411884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400365] Re: Intel PRO/1000 network driver e1000e doesn't always regain connection
I had a laptop still on the vanilla 3.13.0-40-generic kernel which exhibited the problem: no wired connection (despite many retries) after plugging in the cable after a boot. With the linux-image and linux-image-extra packages above installed, the wired connection was established right away in the same test. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400365 Title: Intel PRO/1000 network driver e1000e doesn't always regain connection To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1400365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400365] Re: Intel PRO/1000 network driver e1000e doesn't always regain connection
Thanks for picking this up so promptly. I aim to test it this week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400365 Title: Intel PRO/1000 network driver e1000e doesn't always regain connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400365] [NEW] Intel PRO/1000 network driver e1000e doesn't always regain connection
Public bug reported: On our Dell E6440 laptops we found that the Wired network connection is sometimes not re-established when going from Wifi back to Ethernet, e.g. when booting without LAN and then putting the laptop back in its dock. The following upstream patch resolved this problem for us in Kubuntu 14.04 LTS kernels 3.13.0-34-generic and 3.13.0-40-generic: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/drivers/net/ethernet/intel/e1000e?id=b20a774495671f037e7160ea2ce8789af6b61533 Please incorporate this patch in the Kubuntu kernel so that the /lib/modules/3.13.0-XX- generic/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko module doesn't have to rebuilt manually every time we follow a kernel update. Thanks. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-40-generic 3.13.0-40.69 [modified: lib/modules/3.13.0-40-generic/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko] ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: homa 2299 F pulseaudio homa 2573 F pulseaudio /dev/snd/controlC0: homa 2299 F pulseaudio homa 2573 F pulseaudio CurrentDesktop: KDE Date: Mon Dec 8 16:22:48 2014 HibernationDevice: RESUME=UUID=df0741f0-a429-48cf-9eaf-0b9a31bb32ea InstallationDate: Installed on 2014-12-05 (3 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) MachineType: Dell Inc. Latitude E6440 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic root=UUID=63b4f79f-bbff-4166-9be1-3adf4ea9708b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-40-generic N/A linux-backports-modules-3.13.0-40-generic N/A linux-firmware 1.127.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0YX2X3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd02/18/2014:svnDellInc.:pnLatitudeE6440:pvr01:rvnDellInc.:rn0YX2X3:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400365 Title: Intel PRO/1000 network driver e1000e doesn't always regain connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396820] [NEW] Wireless stopped working after upgrade
Public bug reported: After upgrading to 14.04 connection to the wireless was hardly possible. After downgrading the wpasupplicant package to 1.0-3ubuntu2-mtrudel1 wireless connection was restored. System is Ubuntu 14.04.1 LTS on a HP Presario CQ71. Sorry I could only send the bug report from the 'repaired' system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: wpasupplicant 1.0-3ubuntu2~mtrudel1 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 27 00:25:52 2014 InstallationDate: Installed on 2014-01-12 (318 days ago) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) SourcePackage: wpa UpgradeStatus: Upgraded to trusty on 2014-04-19 (221 days ago) ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396820 Title: Wireless stopped working after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1396820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse from working
I too am having this issue (I think). The issue appears after I go to the activities section, either by pressing the windows key or by clicking activities. The issue seems to happen when im running games that manipulate the mouse, the main examples are minecraft which locks the mouse somewhere while playing and Civ 5 which hides the mouse and uses a custom pointer. The games work fine until I go to the application overview and back. Most of the time, the mouse can still be moved but clicks stop doing anything in any windows and no hover effects are shown. The mouse works fine on the menu bar in gnome though. Sometimes the issue can be fixed by clicking a window a few times, if that doesn't work, alt tabing in and out of the game fixes it ocationally. If that still doesn't work, closing the game usually does. Looking into the issue further, it seems like clicking on a window sevral times and moving the mouse will almost always fix the issue. Another way to solve the issue temporarily that I have found is to use the skype integration plugin and open a new skype window, then closing it. It's not related to skype since I have had the issue when not running it but it seems to be able to fix the issue. Looking into it some more, it seems like opening any window will work, for example using ctrl+alt+t. Also, if no game which uses the mouse is running, opening the activities tab and closing it again without clicking on a window will require one click to gain focus and then one to actually click. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181666 Title: gnome-shell randomly blocks mouse from working To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 231939] Re: package update-manager 1:0.87.27 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1)
** Changed in: flashplugin-nonfree (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/231939 Title: package update-manager 1:0.87.27 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/231939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1287664] [NEW] cannot login login screen
Public bug reported: When I start and I arrive in login screen, I cannot login. Cannot type password. But if I go hereafter to visitor and I login without password no problem. Then hereafter I logged out. And then I can login just with my username as mentioned in the first step. ** Affects: lightdm (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/1287664 Title: cannot login login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1287664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 861268] Re: text corruption in terminals (xterm, urxvt) and emacs
Just some additional info that might help narrowing down the cause. I see this same effect on a machine running Arch Linux. On this machine I use urxvt on top of the i3 window manager. (So not Gnome, KDE or Unity). It happens when text gets scrolled in the terminal window. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/861268 Title: text corruption in terminals (xterm, urxvt) and emacs To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/861268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1236656] [NEW] ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build
Public bug reported: none ProblemType: Package DistroRelease: Ubuntu 12.04 Package: ndiswrapper-dkms 1.57-1ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-31.46~precise1-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic i686 ApportVersion: 2.0.1-0ubuntu17.5 Architecture: i386 DKMSKernelVersion: 3.8.0-31-generic Date: Tue Oct 8 03:06:12 2013 InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release i386 (20130820.1) MarkForUpload: True PackageArchitecture: all PackageVersion: 1.57-1ubuntu1 SourcePackage: ndiswrapper Title: ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ndiswrapper (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1236656 Title: ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/1236656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181651] [NEW] ldconfig problem with 64-bit nvidia driver packages
Public bug reported: On Ubuntu 13.04 64-bit, this package as well as others (including nvidia-current and nvidia-current-updates from the main ubuntu package repositories) don't play nice with applications that use 32-bit OpenGL libraries. When such an application tries to load the nvidia 32-bit libGL.so library, they don't load the nvidia libGL.so but some other non-nvidia libGL.so. This means a 32-bit application running on Ubuntu Raring 64-bit will never use the nvidia libGL.so library. After a lot of monkey business, I figured out what the problem is. Which libGL.so a 32-bit application uses on a 64-bit system is controlled by the file /etc/ld.so.conf.d/i386-linux-gnu_GL.conf which is just a symlink to /etc/alternatives/i386-linux-gnu_gl_conf which is another symlink to /usr/lib/nvidia-319/alt_ld.so.conf or something similar for other versions of the nvidia drivers. This file is blank in a clean install, so ldconfig doesn't know that 32-bit applications asking for libGL.so should get linked with the version in /usr/lib32/nvidia-319, so it links them with some other version. This breaks 32-bit programs like Steam (which throws a warning about not using direct rendering when it starts up) and 32-bit games like Team Fortress 2 (which fails to start altogether). Of course, this isn't specific to Steam and Team Fortress 2 but will affect any 32-bit program trying to use libGL.so and its associated libraries on a 64-bit machine. fortunately, the fix for this is pretty simple: in the file /usr/lib/nvidia-319/alt_ld.so.conf in the nvidia-319 package add the lines: /usr/lib32/nvidia-319 /usr/lib/nvidia-319 This will tell ldconfig to use the nvidia libGL.so and associated libraries for 32-bit applications. For the other versions of the nvidia driver (such as nvidia-304 and nvidia-304-updates in the main ubuntu repositories) it's a simple matter of replacing nvidia-319 with nvidia-304, nvidia-304-updates, nvidia-313, etc. in the directory names. Although I reported this bug for the nvidia-319 package, I have checked and this bug applies at least to the nvidia-304 and nvidia-304-updates packages for Ubuntu 13.04 amd64 in the main ubuntu package repositories as well. It probably also applies to other nvidia driver packages as well, but I haven't checked those. I suppose all you'd have to look for is a blank /usr/lib/nvidia driver package name/alt_ld.so.conf file to check for the bug. The file I've included is the output of ldd (which prints the dynamic library dependencies of a program) when it's used on a 32-bit program that needs the 32-bit libGL.so on an Ubuntu 13.04 64-bit machine. In this case, the program I used ldd on is the 32-bit version of glxinfo from mesa-utils:i386. The nvidia driver version I had installed when I did this is nvidia-319. However, you will get a very similar result for other nvidia driver versions/packages. Also, I said I don't know for the package because 1.) it affects multiple packages and 2.) it didn't accept the package name nvidia-319. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: xorg-edgers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181651 Title: ldconfig problem with 64-bit nvidia driver packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1181651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181651] Re: ldconfig problem with 64-bit nvidia driver packages
** Description changed: - On Ubuntu 13.04 64-bit, this package as well as others (including - nvidia-current and nvidia-current-updates from the main ubuntu package + On Ubuntu 13.04 64-bit, nvidia-319 as well as others (including nvidia- + current and nvidia-current-updates from the main ubuntu package repositories) don't play nice with applications that use 32-bit OpenGL libraries. When such an application tries to load the nvidia 32-bit libGL.so library, they don't load the nvidia libGL.so but some other non-nvidia libGL.so. This means a 32-bit application running on Ubuntu Raring 64-bit will never use the nvidia libGL.so library. After a lot of monkey business, I figured out what the problem is. Which libGL.so a 32-bit application uses on a 64-bit system is controlled by the file /etc/ld.so.conf.d/i386-linux-gnu_GL.conf which is just a symlink to /etc/alternatives/i386-linux-gnu_gl_conf which is another symlink to /usr/lib/nvidia-319/alt_ld.so.conf or something similar for other versions of the nvidia drivers. This file is blank in a clean install, so ldconfig doesn't know that 32-bit applications asking for libGL.so should get linked with the version in /usr/lib32/nvidia-319, so it links them with some other version. This breaks 32-bit programs like Steam (which throws a warning about not using direct rendering when it starts up) and 32-bit games like Team Fortress 2 (which fails to start altogether). Of course, this isn't specific to Steam and Team Fortress 2 but will affect any 32-bit program trying to use libGL.so and its associated libraries on a 64-bit machine. fortunately, the fix for this is pretty simple: in the file /usr/lib/nvidia-319/alt_ld.so.conf in the nvidia-319 package add the lines: /usr/lib32/nvidia-319 /usr/lib/nvidia-319 This will tell ldconfig to use the nvidia libGL.so and associated libraries for 32-bit applications. For the other versions of the nvidia driver (such as nvidia-304 and nvidia-304-updates in the main ubuntu repositories) it's a simple matter of replacing nvidia-319 with nvidia-304, nvidia-304-updates, nvidia-313, etc. in the directory names. Although I reported this bug for the nvidia-319 package, I have checked and this bug applies at least to the nvidia-304 and nvidia-304-updates packages for Ubuntu 13.04 amd64 in the main ubuntu package repositories as well. It probably also applies to other nvidia driver packages as well, but I haven't checked those. I suppose all you'd have to look for is a blank /usr/lib/nvidia driver package name/alt_ld.so.conf file to check for the bug. The file I've included is the output of ldd (which prints the dynamic library dependencies of a program) when it's used on a 32-bit program that needs the 32-bit libGL.so on an Ubuntu 13.04 64-bit machine. In this case, the program I used ldd on is the 32-bit version of glxinfo from mesa-utils:i386. The nvidia driver version I had installed when I did this is nvidia-319. However, you will get a very similar result for other nvidia driver versions/packages. Also, I said I don't know for the package because 1.) it affects multiple packages and 2.) it didn't accept the package name nvidia-319. ** Description changed: - On Ubuntu 13.04 64-bit, nvidia-319 as well as others (including nvidia- - current and nvidia-current-updates from the main ubuntu package - repositories) don't play nice with applications that use 32-bit OpenGL - libraries. When such an application tries to load the nvidia 32-bit - libGL.so library, they don't load the nvidia libGL.so but some other - non-nvidia libGL.so. This means a 32-bit application running on Ubuntu - Raring 64-bit will never use the nvidia libGL.so library. + On Ubuntu 13.04 64-bit, the nvidia-319 package as well as others + (including nvidia-current and nvidia-current-updates from the main + ubuntu package repositories) don't play nice with applications that use + 32-bit OpenGL libraries. When such an application tries to load the + nvidia 32-bit libGL.so library, they don't load the nvidia libGL.so but + some other non-nvidia libGL.so. This means a 32-bit application running + on Ubuntu Raring 64-bit will never use the nvidia libGL.so library. After a lot of monkey business, I figured out what the problem is. Which libGL.so a 32-bit application uses on a 64-bit system is controlled by the file /etc/ld.so.conf.d/i386-linux-gnu_GL.conf which is just a symlink to /etc/alternatives/i386-linux-gnu_gl_conf which is another symlink to /usr/lib/nvidia-319/alt_ld.so.conf or something similar for other versions of the nvidia drivers. This file is blank in a clean install, so ldconfig doesn't know that 32-bit applications asking for libGL.so should get linked with the version in /usr/lib32/nvidia-319, so it links them with some other version. This breaks 32-bit programs like Steam (which throws a warning about not using direct
[Bug 1179133] [NEW] new upstream 4.0.5+dfsg1
Public bug reported: Debian samba4 is moving forward. They are migrated to git and working on upstream 4.0.5+dfsg1 now. http://anonscm.debian.org/gitweb/?p=pkg-samba/samba.git Let us see when it goes in experimental? ** Affects: samba4 (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/1179133 Title: new upstream 4.0.5+dfsg1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1179133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1153934] Re: Some radio streams which used to play OK don't play after updating to rhythmbox 2.98
I would also like to confirm the bug. The same behavior repeated on all streams: player pauses and stop responding. Killing the gvfsd-http did not help. I tried not using LastFM plugin without success. I was able to get things working by disabling crossfade altogether. I enabled it yesterday and today Rhythmbox stopped working. I did play some music, but did not restart streams or the player after enabling until today. Ubuntu 13.04 (raring) 64bit Rhythmbox 2.98 GCC 4.7 (x86_64-linux-gnu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1153934 Title: Some radio streams which used to play OK don't play after updating to rhythmbox 2.98 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1153934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096859] [NEW] launcher does not show open docs
Public bug reported: Fresh install of Ubuntu 12.04.1 LTS. After some time the Launcher does not show with arrows at the sides of the icons that docs are open for certain programs (certainly Libre Office programs), and once you switch to another application or doc, you cannot click on the launcher to get back to the open document. Instead a new document (in case of Write) is opened. Also Alt-tab does not show (all) programs with open files. The only way to get back to open files is through Dash. I repair this (temporarily) by command line command: unity -- reset. After that the Launcher works normal, until the next time it fails. This is the output of the Terminal after typing the command (please note that the program advices to report a bug): frans@frans-AO722:~$ unity --reset WARNING: Unity currently default profile, so switching to metacity while resetting the values Checking if settings need to be migrated ...no Checking if internal files need to be migrated ...no Backend : gconf Integration : true Profile : unity Adding plugins Initializing core options...done compiz (core) - Warn: failed to receive ConfigureNotify event on 0x184 compiz (core) - Warn: failed to receive ConfigureNotify event on 0x323 compiz (core) - Warn: failed to receive ConfigureNotify event on 0x38000ba compiz (core) - Warn: failed to receive ConfigureNotify event on 0x3c00064 Initializing composite options...done Initializing opengl options...done Initializing decor options...done Initializing vpswitch options...done Initializing snap options...done Initializing mousepoll options...done Initializing resize options...done Initializing place options...done Initializing move options...done Initializing wall options...done Initializing grid options...done Initializing session options...done Initializing gnomecompat options...done Initializing animation options...done Initializing fade options...done Initializing unitymtgrabhandles options...done Initializing workarounds options...done Initializing scale options...done compiz (expo) - Warn: failed to bind image to texture Initializing expo options...done Initializing ezoom options...done (compiz:3627): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed Initializing unityshell options...done compiz (core) - Warn: unhandled ConfigureNotify on 0x1a000a0! compiz (core) - Warn: this should never happen. you should probably file a bug about this. compiz (core) - Warn: unhandled ConfigureNotify on 0x1a000a3! compiz (core) - Warn: this should never happen. you should probably file a bug about this. compiz (core) - Warn: unhandled ConfigureNotify on 0x1a000a6! compiz (core) - Warn: this should never happen. you should probably file a bug about this. compiz (core) - Warn: unhandled ConfigureNotify on 0x1a000a6! compiz (core) - Warn: this should never happen. you should probably file a bug about this. compiz (core) - Warn: unhandled ConfigureNotify on 0x1a000a9! compiz (core) - Warn: this should never happen. you should probably file a bug about this. compiz (core) - Warn: unhandled ConfigureNotify on 0x1a000a9! compiz (core) - Warn: this should never happen. you should probably file a bug about this. WARN 2013-01-07 12:01:01 unity.libindicator unknown:0 Desktop file '/usr/share/applications/libreoffice-writer.desktop' is using a deprecated format for its actions that will be dropped soon. WARN 2013-01-07 12:01:01 unity.libindicator unknown:0 Desktop file '/usr/share/applications/libreoffice-calc.desktop' is using a deprecated format for its actions that will be dropped soon. WARN 2013-01-07 12:01:01 unity.libindicator unknown:0 Desktop file '/usr/share/applications/libreoffice-impress.desktop' is using a deprecated format for its actions that will be dropped soon. Initializing staticswitcher options...done ERROR 2013-01-07 12:01:05 unity.glib-gobject unknown:0 g_object_unref: assertion `G_IS_OBJECT (object)' failed Setting Update main_menu_key Setting Update run_key The terminal does not return to the command prompt and seems to be stuck; but meanwhile the screen is built up anew, and the launcher works for some time My computer is ACER AO722 Trying to find package name (as suggested by this site): frans@frans-AO722:~$ apt-cache policy pkgname N: Unable to locate package pkgname frans@frans-AO722:~$ But I know that this is Ubuntu 12.04.1 LTS. It happened also in 12.10, which I abandoned for having many other problems. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096859 Title: launcher does not show open docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1096859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096859] Re: launcher does not show open docs
** Package changed: ubuntu = compiz (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096859 Title: launcher does not show open docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1096859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 105458] Re: [needs-packaging] HandBrake
[2012-10-03] Accepted handbrake 0.9.8+dfsg1-1~19.gbpc8b9ba in Debian Experimental. All the good work is done by Rogério Brito Reinhard Tartler. This is an almost complete rework of the packaging included in previous iterations of handbrake. This changelog reflects only a fraction of the work that went into make it suitable for Debian and involved the work of many people. For the complete list of changes, we kindly refer you to the git repository for all the details. http://packages.qa.debian.org/h/handbrake.html Please package Ubuntu now. ** Description changed: HandBrake is an open-source, GPL-licensed, multiplatform, multithreaded video transcoder, available for MacOS X, Linux and Windows. URL: http://handbrake.fr/ License: GPL - The Debian Bug watch claims that there is a Fix Released in Debian - (i.e. it is packaged there) -- but it is not. On the contrary, they - decided not to package it for now. - - Handbrake PPA: https://edge.launchpad.net/~handbrake-ubuntu/+archive/ppa - PPA with a version working with Ubuntu Lucid/10.04: https://edge.launchpad.net/~stebbins/+archive/handbrake-snapshots + The Debian Bug watch claims that there is a Fix Released in Debian. + Accepted 0.9.8+dfsg1-1~19.gbpc8b9ba in experimental -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/105458 Title: [needs-packaging] HandBrake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/105458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 105458] Re: [needs-packaging] HandBrake
In Git they merged 'upstream' branch to debian/0.9.8+dfsg1-1_19.gbpc8b9ba, removed ccache from build-depends, added libdvdread4 to recommends, added man pages, added dbg package fixed debian/watch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/105458 Title: [needs-packaging] HandBrake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/105458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1061142] [NEW] upon upgrading ubuntu 12.04 to 12.10 not able to login
Public bug reported: I just upgrade from 12.04 to 12.10. I downloaded the beta 2 version of Ubuntu 12.10 few hours ago. with my username i cannot login. through remote i can go into system, but all my documents are gone. Meaning i cannot reach. Pls let me know what to do. Thanks in advance for your help. Kind regards Frans ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1061142 Title: upon upgrading ubuntu 12.04 to 12.10 not able to login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1061142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 987410] Re: filezilla crashes when closing site manager
For the KDE workaround in #7, make sure you have installed gtk2 -engines-qtcurve sudo apt-get install gtk2-engines-qtcurve -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/987410 Title: filezilla crashes when closing site manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/filezilla/+bug/987410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
