[Bug 1959445] [NEW] DHCPD gets confused about what IPs should be handed out on what interfaces
Public bug reported: I had a device request an IP on one VLAN (one interface associated with the server -- ens256), and then I moved the device to a different VLAN (interface ens192 on the server), and was surprised when the DHCPD process continued to hand out the same IP on the new VLAN. Here are the associated syslog entries, and the IP interface settings: Jan 28 12:06:35 backup dhcpd[1020678]: DHCPREQUEST for 10.2.195.100 from ec:02:73:b8:4d:01 via ens256 Jan 28 12:06:35 backup dhcpd[1020678]: DHCPACK on 10.2.195.100 to ec:02:73:b8:4d:01 via ens256 Jan 28 12:08:43 backup dhcpd[1020678]: DHCPREQUEST for 10.2.195.100 from ec:02:73:b8:4d:01 via ens256 Jan 28 12:08:43 backup dhcpd[1020678]: DHCPACK on 10.2.195.100 to ec:02:73:b8:4d:01 via ens256 Jan 28 12:11:08 backup dhcpd[1024746]: DHCPREQUEST for 10.2.195.100 from ec:02:73:b8:4d:01 via ens192 Jan 28 12:11:08 backup dhcpd[1024746]: DHCPACK on 10.2.195.100 to ec:02:73:b8:4d:01 via ens192 Jan 28 12:11:23 backup dhcpd[1024746]: DHCPREQUEST for 10.2.195.100 from ec:02:73:b8:4d:01 via ens192 Jan 28 12:11:23 backup dhcpd[1024746]: DHCPACK on 10.2.195.100 to ec:02:73:b8:4d:01 via ens192 (I've trimmed out the IPv6 information): backup$ ip addr list ... 3: ens192: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:50:56:9e:8b:d8 brd ff:ff:ff:ff:ff:ff inet 10.7.32.2/21 brd 10.7.39.255 scope global ens192 valid_lft forever preferred_lft forever ... 5: ens256: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:50:56:9e:f2:e6 brd ff:ff:ff:ff:ff:ff inet 10.2.195.2/24 brd 10.2.195.255 scope global ens256 valid_lft forever preferred_lft forever ... When I rebooted the client, it went back to DHCPDISCOVER mode and then the DHCPD daemon correctly recognized that this client was on a new interface/VLAN and handed it a valid IP address for that interface/VLAN. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: isc-dhcp-server 4.4.1-2.1ubuntu5.20.04.2 [modified: usr/bin/omshell] ProcVersionSignature: Ubuntu 5.4.0-94.106-generic 5.4.157 Uname: Linux 5.4.0-94-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jan 28 12:24:05 2022 InstallationDate: Installed on 2021-06-29 (212 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: SHELL=/bin/bash TERM=xterm-color XDG_RUNTIME_DIR= PATH=(custom, user) SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.dhcp.dhcpd6.conf: [modified] mtime.conffile..etc.dhcp.dhcpd.conf: 2022-01-28T12:09:41.747865 mtime.conffile..etc.dhcp.dhcpd6.conf: 2019-01-03T15:05:49 ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959445 Title: DHCPD gets confused about what IPs should be handed out on what interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1959445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916931] Re: omshell returns inconsistent results or segfaults
I also noticed problems with omshell after upgrading to Ubuntu 20.04, and after finding this bug report I can confirm that compiling the ISC sources (w/o the Ubuntu/Debian patches) does resolve the problem(s) reported here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916931 Title: omshell returns inconsistent results or segfaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1916931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818881] Re: ath10k_pci crashing
** Attachment removed: "dmesg output after Wi-Fi crash" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818881/+attachment/5279667/+files/wifi-crash-2019-07-28.txt ** Attachment added: "dmesg output after Wi-Fi crash" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818881/+attachment/5279668/+files/wifi-crash-2019-07-28.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818881 Title: ath10k_pci crashing To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1818881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818881] Re: ath10k_pci crashing
I still hit this issue a few times per week, usually after resuming from suspend. I've attached the dmesg output from the most recent one (today). In this instance, although the Wi-Fi was not working, I was still able to interact with the system and shut it down cleanly. That's not always the case - sometimes the running system is corrupted and I can't even shutdown cleanly but have to do a hard power-off with the power button. This is with all the latest updates applied on 19.04. Kernel: Linux daniel-XPS-13-9380 5.0.0-21-generic #22-Ubuntu SMP Tue Jul 2 13:27:33 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Is there anything in the pipeline that will help with this? Any contacts at Dell, or Qualcomm / Atheros? This is after all a certified Ubuntu laptop. ** Attachment added: "dmesg output after Wi-Fi crash" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818881/+attachment/5279667/+files/wifi-crash-2019-07-28.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818881 Title: ath10k_pci crashing To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1818881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)
Hi Thomas, that sounds very similar to what we are seeing over in bug 1827790. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826125 Title: Dell XPS 13 9380 flickering (Whiskey Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827790] Re: Dell XPS 13 9380 - Screen flashes
On the basis of 3 of us deeming that the symptoms of the other bug are different to the ones described in this bug, I have removed the duplicate link. I hope that's OK. If it helps narrow it down, it seems that we all have the non-touch 1080p version, and all notice it much more when Night Light is enabled. ** This bug is no longer a duplicate of bug 1826125 Dell XPS 13 9380 flickering (Whiskey Lake) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827790 Title: Dell XPS 13 9380 - Screen flashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827790] Re: Dell XPS 13 9380 - Screen flashes
*** This bug is a duplicate of bug 1826125 *** https://bugs.launchpad.net/bugs/1826125 I agree with mactyr that this should not be a duplicate of that bug. The flaw that I see is not what is shown in those videos. There is no glitching, it is the whole screen flashing brighter, and is why I used the word "flashes" in the title, as opposed to "flickers" or "glitches". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827790 Title: Dell XPS 13 9380 - Screen flashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827791] Re: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily
In comment 28, the freeze happened just before taking the log, yet the last log entry was from ~1 minute earlier, so it doesn't look like there were any relevant log entries. However just now I had a freeze, and there are some messages in dmesg: [10980.231902] perf: interrupt took too long (2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500 [11986.082217] perf: interrupt took too long (3142 > 3140), lowering kernel.perf_event_max_sample_rate to 63500 [16384.901113] perf: interrupt took too long (3928 > 3927), lowering kernel.perf_event_max_sample_rate to 50750 Also in journalctl -b0: May 20 22:30:09 daniel-XPS-13-9380 kernel: perf: interrupt took too long (3928 > 3927), lowering kernel.perf_event_max_sample_rate to 50750 The previous journalctl message is from a few minutes prior. Searching for the error message suggests that perhaps these messages aren't any major cause for concern though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826219] Re: Input locks frequently/high CPU usage after 18.10->19.04 upgrade
Hi Paul, thanks for pointing me to this bug from https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827791. Is this also on a Dell XPS 13 9380? Your comment about Wayland made me curious, as I was using the default Xorg session. Testing with Wayland on 19.04 I also see the same problem (actually I think it's more prominent with Wayland than it was with Xorg). I also see lines like this in journalctl -b0: May 13 21:34:46 daniel-XPS-13-9380 org.gnome.Shell.desktop[1673]: Window manager warning: last_user_time (242191) is greater than comparison timestamp (242190). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... May 13 21:34:46 daniel-XPS-13-9380 org.gnome.Shell.desktop[1673]: Window manager warning: W1 appears to be one of the offending windows with a timestamp of 242191. Working around... And: May 13 21:41:21 daniel-XPS-13-9380 org.gnome.Shell.desktop[1673]: libinput error: event5 - DELL08AF:00 06CB:76AF Touchpad: kernel bug: Touch jump detected and discarded. May 13 21:41:21 daniel-XPS-13-9380 org.gnome.Shell.desktop[1673]: See https://wayland.freedesktop.org/libinput/doc/1.12.6/touchpad-jumping-cursors.html for details -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826219 Title: Input locks frequently/high CPU usage after 18.10->19.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727039] Re: Xorg crash
** Package changed: xorg (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727039 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1727039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727909] [NEW] Using Wayland
Public bug reported: When I've put my pendrive system just close session and I go back to log in screen. It happens in very different ways. Attached goes the logs file. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME Date: Thu Oct 26 23:55:20 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd HD Graphics 5500 [144d:c755] InstallationDate: Installed on 2017-10-19 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=b04e4fad-4a52-4169-9ba3-0786c9a0ab39 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06RCX.075.160311.JJ dmi.board.asset.tag: No Asset Tag dmi.board.name: NP370E4K-KW3BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8537A0C-C01-G001-S0001+10.0.10240 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06RCX.075.160311.JJ:bd03/11/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn370E4K:pvrP06RCX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370E4K-KW3BR:rvrSGL8537A0C-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 370E4K dmi.product.version: P06RCX dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful crash ubuntu wayland-session ** Attachment added: "Logs file" https://bugs.launchpad.net/bugs/1727909/+attachment/4997355/+files/error -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727909 Title: Using Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1727909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724738] Re: gnome-control-center crashed with SIGSEGV
*** This bug is a duplicate of bug 1720400 *** https://bugs.launchpad.net/bugs/1720400 Issue presented on a 17.10, a fresh install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724738 Title: gnome-control-center crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1724738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727039] [NEW] Xorg crash
Public bug reported: I got some messages in logs program. Message: "CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Erro ao chamar StartServiceByName para org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1" Message: "Unrecoverable failure in required component org.gnome.Shell.desktop" ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 BootLog: CompositorRunning: None CurrentDesktop: GNOME Date: Tue Oct 24 16:32:43 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd HD Graphics 5500 [144d:c755] InstallationDate: Installed on 2017-10-19 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=b04e4fad-4a52-4169-9ba3-0786c9a0ab39 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06RCX.075.160311.JJ dmi.board.asset.tag: No Asset Tag dmi.board.name: NP370E4K-KW3BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8537A0C-C01-G001-S0001+10.0.10240 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06RCX.075.160311.JJ:bd03/11/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn370E4K:pvrP06RCX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370E4K-KW3BR:rvrSGL8537A0C-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 370E4K dmi.product.version: P06RCX dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful crash ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727039 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1727039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726682] [NEW] Xorg freeze
Public bug reported: This problem occur: - when I input USB stick - When I have click about system (more details of Ubuntu) - Using normally, so open a video then system log off or freeze. I try Ctrl + Shft + F1 or Ctrl + Shift + F2 but it goes to the GDM login screen. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 BootLog: CompositorRunning: None CurrentDesktop: GNOME Date: Tue Oct 24 00:44:02 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd HD Graphics 5500 [144d:c755] InstallationDate: Installed on 2017-10-19 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=b04e4fad-4a52-4169-9ba3-0786c9a0ab39 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06RCX.075.160311.JJ dmi.board.asset.tag: No Asset Tag dmi.board.name: NP370E4K-KW3BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8537A0C-C01-G001-S0001+10.0.10240 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06RCX.075.160311.JJ:bd03/11/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn370E4K:pvrP06RCX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370E4K-KW3BR:rvrSGL8537A0C-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 370E4K dmi.product.version: P06RCX dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful freeze ubuntu wayland-session ** Attachment added: "System log" https://bugs.launchpad.net/bugs/1726682/+attachment/4990043/+files/Problems -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726682 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1726682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649700] [NEW] Sendmail 8.15.2 - hangs accepting e-mail with LDAP enabled
Public bug reported: Sendmail 8.15.2 seems to have a file descriptor bug/handling problem, which is exposed when the ldap_routing feature is enabled. I'm not certain I understand what you mean by "source package", but I assume what you're looking for is the 'sendmail' package. Distro: Ubuntu 16.04.1 LTS Package version: apt-cache policy sendmail sendmail: Installed: 8.15.2-3 Candidate: 8.15.2-3 Version table: *** 8.15.2-3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu xenial/universe i386 Packages 100 /var/lib/dpkg/status I expect e-mail received from a remote system to be processed and accepted by the local sendmail process. What happens is that the sendmail process hangs and never completes processing the e-mail message, so it does not get delivered. The configuration: When I add FEATURE(`ldap_routing', ...) to my sendmail.mc file and generate a new sendmail.cf file for sendmail to use, sendmail stops processing e-mail messages for delivery. Background: I initially developed my mc/cf files with ldap_routing on Ubuntu 14.04 systems. I had no problems with sendmail processing/delivery until I took the .cf file from my Ubuntu 14.04 system and used it with the Ubuntu 16.04 sendmail package (at which point I observed delivery problems). For troubleshooting, I used a stock Ubuntu 16.04 sendmail.mc file and slowly added things to it until I the problem reoccurred. I have found that adding FEATURE(`ldap_routing', ...) to the stock sendmail.mc file is sufficient to reproduce this problem under Ubuntu 16.04. Fuller problem report: The problem occurs when a (remote) SMTP host delivers e-mail over port 25 to the affected Ubuntu 16.04 system. Ubuntu's 16.04 sendmail process will report that it has accepted the e-mail message (over port 25), but the e-mail message is never delivered. Running 'ps auxwww | grep sendmail' on the Ubuntu 16.04 system after delivering an e-mail message to it, the sendmail child process reports that it's still accepting the message, like it hasn't finished processing it. This sendmail process hangs around indefinitely (I've waited days), and never finishes processing. If I kill the child sendmail process that was spawned to accept/process this message, at the next sendmail queue run interval the message is read from mqueue and properly delivered. When I run strace -p , it shows the sendmail process is waiting for input from FD 3 ( read(3, ...)). When I start the sendmail daemon as "strace -f /usr/sbin/sendmail-mta -Am -L sm-mta -bd -q10m", I still get the same behavior where the child process accepting the e-mail message will get hung up waiting for input on FD3. Examining /proc//fd/3 shows it to be a connection to a socket. When I backtrace through the strace output, it appears that FD3 is a socket to /dev/log, which strongly implies that sendmail isn't reading from the correct FD. If I start sendmail as "/usr/sbin/sendmail-mta -Am -L sm-mta -bd -q10m -D /tmp/log", then sendmail seems to work fine (it accepts messages and promptly delivers them). This makes me think a file descriptor leak/mixup bug is triggered when the LDAP code is enabled. The bug.apport output is included as a file attachment. ** Affects: sendmail (Ubuntu) Importance: Undecided Status: New ** Attachment added: "bug.apport" https://bugs.launchpad.net/bugs/1649700/+attachment/4791293/+files/bug.apport ** Description changed: Sendmail 8.15.2 seems to have a file descriptor bug/handling problem, which is exposed when the ldap_routing feature is enabled. I'm not certain I understand what you mean by "source package", but I assume what you're looking for is the 'sendmail' package. Distro: Ubuntu 16.04.1 LTS Package version: apt-cache policy sendmail sendmail: - Installed: 8.15.2-3 - Candidate: 8.15.2-3 - Version table: - *** 8.15.2-3 500 - 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages - 500 http://us.archive.ubuntu.com/ubuntu xenial/universe i386 Packages - 100 /var/lib/dpkg/status + Installed: 8.15.2-3 + Candidate: 8.15.2-3 + Version table: + *** 8.15.2-3 500 + 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages + 500 http://us.archive.ubuntu.com/ubuntu xenial/universe i386 Packages + 100 /var/lib/dpkg/status I expect e-mail received from a remote system to be processed and accepted by the local sendmail process. What happens is that the sendmail process hangs and never completes processing the e-mail message, so it does not get delivered. - - The configuration: When I add FEATURE(`ldap_routing', ...) to my sendmail.mc file and generate a new sendmail.cf file for sendmail to use, sendmail stops processing e-mail messages for delivery. + The configuration: When I add FEATURE(`ldap_routing', ...) to my + sendmail.mc file and
[Bug 1228567] Re: at-spi2 daemon error messages in .xsession-errors
@Colin: I'm experiencing the same issue. Installing updates to 14.04LTS on my laptop in early December has made the GUI on my computer unusable as well. It's a ThinkPad, I think with a stock Intel video chipset in it. Here is the output of my .xsession-errors file: Script for auto started at run_im. Script for default started at run_im. init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd respawning too fast, stopped init: gnome-session (Unity) main process (11515) terminated with status 1 init: logrotate main process (11404) killed by TERM signal init: update-notifier-crash (/var/crash/_usr_bin_nm-applet.104.crash) main process (11451) killed by TERM signal init: indicator-bluetooth main process (11638) killed by TERM signal init: indicator-power main process (11640) killed by TERM signal init: indicator-datetime main process (11641) killed by TERM signal init: indicator-session main process (11655) killed by TERM signal init: indicator-application main process (11671) killed by TERM signal init: Disconnected from notified D-Bus bus -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1228567 Title: at-spi2 daemon error messages in .xsession-errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1228567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1228567] Re: at-spi2 daemon error messages in .xsession-errors
Using the script that Marmuta suggested at the top generates two files. Here is the content of the user one: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry ** (at-spi2-registryd-:14335): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ** (at-spi2-registryd-:14335): WARNING **: Unable to register client with session manager SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry ** (at-spi2-registryd-:15092): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ** (at-spi2-registryd-:15092): WARNING **: Unable to register client with session manager --- Here is the lightdm one: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry ** (at-spi2-registryd-:14804): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ** (at-spi2-registryd-:14804): WARNING **: Unable to register client with session manager g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry ** (at-spi2-registryd-:15577): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ** (at-spi2-registryd-:15577): WARNING **: Unable to register client with session manager -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1228567 Title: at-spi2 daemon error messages in .xsession-errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1228567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1228567] Re: at-spi2 daemon error messages in .xsession-errors
One addendum: the permissions of my ~/.X* files are good (I own them and they're writeable), and the permissions on /tmp and /tmp/.X11* look correct as well. I moved ~/.config/dconf out of the way as well, and that didn't make a difference either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1228567 Title: at-spi2 daemon error messages in .xsession-errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1228567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429427] Re: Unexplainable time jumps in CRON
I'm seeing the same behavior out of rsyslogd. It shows up most frequently with CRON runs, but I've seen it on kernel syslog entries as well. I'm shipping my logs into ELK, and I was noticing that old indices kept getting updated. When I dug into the issue, I saw that this was happening on a relatively regular basis (at least once a day). It is/was one particular cron job that generated the vast majority of the incorrect timestamps: one that ran once a minute (e.g. * * * * * /bin/true) I've seen this happen on several Ubuntu hosts, mostly 14 LTS, but I think I've seen it in 12 LTS too. I've only recently started tracking this issue. The timestamp can be off by hours to days. When I see it happen, restarting rsyslogd makes the issue go away for a while. - Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1429427 Title: Unexplainable time jumps in CRON To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1429427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1038199] [NEW] Bind9 9.8.1 high CPU utilization
Public bug reported: I'm reporting this here to raise awareness of the bug. I suspect it's the same identical problem reported with Bind9 on Fedora, at: https://bugzilla.redhat.com/show_bug.cgi?id=709205 Basically, with DNSSEC enabled, and the managed-keys-directory option commented out in the config, named will sit at 100% cpu usage all of the time. It still answers queries, but it's using a lot of CPU over nothing. Description:Ubuntu 12.04.1 LTS Release:12.04 bind9: Installed: 1:9.8.1.dfsg.P1-4ubuntu0.2 Candidate: 1:9.8.1.dfsg.P1-4ubuntu0.2 Version table: *** 1:9.8.1.dfsg.P1-4ubuntu0.2 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status 1:9.8.1.dfsg.P1-4 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages - Daniel ** Affects: bind9 (Ubuntu) Importance: Undecided Status: New ** Affects: bind9 (Fedora) Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1038199 Title: Bind9 9.8.1 high CPU utilization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1038199/+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 1038199] Re: Bind9 9.8.1 high CPU utilization
I discovered this bug the hard way when I transferred over my named.conf from a Ubuntu 10.04 LTS system to 12.04. The managed-keys-directory option was not valid in 10.04 (Bind 9.7.0). ** Bug watch added: Red Hat Bugzilla #709205 https://bugzilla.redhat.com/show_bug.cgi?id=709205 ** Also affects: bind9 (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=709205 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1038199 Title: Bind9 9.8.1 high CPU utilization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1038199/+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 1038199] [NEW] Bind9 9.8.1 high CPU utilization
Public bug reported: I'm reporting this here to raise awareness of the bug. I suspect it's the same identical problem reported with Bind9 on Fedora, at: https://bugzilla.redhat.com/show_bug.cgi?id=709205 Basically, with DNSSEC enabled, and the managed-keys-directory option commented out in the config, named will sit at 100% cpu usage all of the time. It still answers queries, but it's using a lot of CPU over nothing. Description:Ubuntu 12.04.1 LTS Release:12.04 bind9: Installed: 1:9.8.1.dfsg.P1-4ubuntu0.2 Candidate: 1:9.8.1.dfsg.P1-4ubuntu0.2 Version table: *** 1:9.8.1.dfsg.P1-4ubuntu0.2 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status 1:9.8.1.dfsg.P1-4 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages - Daniel ** Affects: bind9 (Ubuntu) Importance: Undecided Status: New ** Affects: bind9 (Fedora) Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1038199 Title: Bind9 9.8.1 high CPU utilization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1038199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1038199] Re: Bind9 9.8.1 high CPU utilization
I discovered this bug the hard way when I transferred over my named.conf from a Ubuntu 10.04 LTS system to 12.04. The managed-keys-directory option was not valid in 10.04 (Bind 9.7.0). ** Bug watch added: Red Hat Bugzilla #709205 https://bugzilla.redhat.com/show_bug.cgi?id=709205 ** Also affects: bind9 (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=709205 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1038199 Title: Bind9 9.8.1 high CPU utilization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1038199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 672365] [NEW] Server failed to start during --configure: could not open file (pg_xlog): Invalid argument
Public bug reported: Binary package hint: postgresql-8.4 Upon installing postgresql-8.4, the server fails to start during --configure. The log shows: PANIC: could not open file pg_xlog/0001 (log file 0, segment 0): Invalid argument Steps to reproduce: -boot Ubuntu 10.10 livecd -run Update Manager: -click check -install everything except: linux-headers-2.6.35-22 linux-headers-2.6.35.22-generic linux-image-2.6.35.22-generic -open Terminal sudo apt-get update sudo apt-get install postgresql-8.4 I will attach complete logs momentarily ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: postgresql-8.4 8.4.5-0ubuntu10.10 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 Date: Mon Nov 8 00:55:34 2010 LiveMediaBuild: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: postgresql-8.4 ** Affects: postgresql-8.4 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- Server failed to start during --configure: could not open file (pg_xlog): Invalid argument https://bugs.launchpad.net/bugs/672365 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 672365] Re: Server failed to start: could not open file: Invalid argument
-- Server failed to start during --configure: could not open file (pg_xlog): Invalid argument https://bugs.launchpad.net/bugs/672365 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 672365] Re: Server failed to start: could not open file: Invalid argument
** Attachment added: /var/log/postgresql/postgresql-8.4-main.log https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/672365/+attachment/1726452/+files/postgresql-8.4-main.log -- Server failed to start during --configure: could not open file (pg_xlog): Invalid argument https://bugs.launchpad.net/bugs/672365 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 672365] Re: Server failed to start: could not open file: Invalid argument
** Attachment added: /var/log/apt/term.log https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/672365/+attachment/1726453/+files/term.log ** Summary changed: - Server failed to start: could not open file: Invalid argument + Server failed to start: could not open file (pg_xlog): Invalid argument ** Summary changed: - Server failed to start: could not open file (pg_xlog): Invalid argument + Server failed to start during --configure: could not open file (pg_xlog): Invalid argument -- Server failed to start during --configure: could not open file (pg_xlog): Invalid argument https://bugs.launchpad.net/bugs/672365 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 672365] Re: Server failed to start during --configure: could not open file (pg_xlog): Invalid argument
*** This bug is a duplicate of bug 658857 *** https://bugs.launchpad.net/bugs/658857 ** This bug has been marked a duplicate of bug 658857 package postgresql-8.4 8.4.5-0ubuntu10.10 failed to install/upgrade: el subproceso script post-installation instalado devolvió el código de salida de error 1 * You can subscribe to bug 658857 by following this link: https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/658857/+subscribe -- Server failed to start during --configure: could not open file (pg_xlog): Invalid argument https://bugs.launchpad.net/bugs/672365 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 672365] Re: Server failed to start during --configure: could not open file (pg_xlog): Invalid argument
*** This bug is a duplicate of bug 658857 *** https://bugs.launchpad.net/bugs/658857 ** Changed in: postgresql-8.4 (Ubuntu) Status: New = Confirmed ** Changed in: postgresql-8.4 (Ubuntu) Status: Confirmed = New -- Server failed to start during --configure: could not open file (pg_xlog): Invalid argument https://bugs.launchpad.net/bugs/672365 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 658857] Re: package postgresql-8.4 8.4. 5-0ubuntu10.10 failed to install/upgrade: el subproces o script post-installation instalado devolvió el c ódigo de salida de error 1
Interestingly enough, this appears to be a regression. I got the same results as you did on a 10.10 livecd. However, on a 10.04.1 livecd, postgresql-8.4 installs and starts successfully. ** Summary changed: - package postgresql-8.4 8.4.5-0ubuntu10.10 failed to install/upgrade: el subproceso script post-installation instalado devolvió el código de salida de error 1 + server fails to start, does not detect livecd filesystem's wal_sync_method ** Changed in: postgresql-8.4 (Ubuntu) Status: New = Confirmed -- server fails to start, does not detect livecd filesystem's wal_sync_method https://bugs.launchpad.net/bugs/658857 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 658857] Re: server fails to start, does not detect livecd filesystem's wal_sync_method
In particular http://www.piware.de/2010/09/postgresql-9-0-final- released/#comment-1083 and the comment below it highlight the issue. -- server fails to start, does not detect livecd filesystem's wal_sync_method https://bugs.launchpad.net/bugs/658857 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 663608] [NEW] Kernel update on livecd fails to symlink initrd.img: File exists
Public bug reported: Binary package hint: linux-image-2.6.35-22-generic Failed to symbolic-link /boot/initrd.img-2.6.35-22-generic to initrd.img: File exists ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: update-manager 1:0.142.20 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 CheckboxCommand: update-manager --check-dist-upgrades CheckboxData: The only installation failure was linux-image-2.6.35-22-generic, I'll attach the term.log CheckboxDescription: This test will execute Update Manager and check to see if there are any available updates for the system. Please follow the prompts and if updates are found, install them. When Update Manager has finished, please close the app by clicking the Close button in the lower right corner. CheckboxTest: update_manager_finds_updates Date: Wed Oct 20 00:00:36 2010 LiveMediaBuild: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 SourcePackage: update-manager ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug checkbox-bug i386 maverick -- Kernel update on livecd fails to symlink initrd.img: File exists https://bugs.launchpad.net/bugs/663608 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 663608] Re: Kernel update on livecd fails to symlink initrd.img:
** Summary changed: - Kernel update on livecd fails to symlink initrd.img: + Kernel update on livecd fails to symlink initrd.img: File exists -- Kernel update on livecd fails to symlink initrd.img: File exists https://bugs.launchpad.net/bugs/663608 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 663608] Re: Kernel update on livecd fails to symlink initrd.img: File exists
I'm not sure if this is expected behavior, feel free to close the bug if it is. I booted from a 10.10 livecd, ran Update Manager, and told it to install everything it found updates for. I'll attach the entire /var/log/apt/term.log, but here's the relevant piece: Setting up linux-image-2.6.35-22-generic (2.6.35-22.35) ... Running depmod. update-initramfs is disabled since running on read-only media Failed to symbolic-link /boot/initrd.img-2.6.35-22-generic to initrd.img: File exists dpkg: error processing linux-image-2.6.35-22-generic (--configure): subprocess installed post-installation script returned error exit status 17 This may actually be expected behavior following from update-initramfs being disabled. Besides, a kernel update on a livecd without any persistent storage won't actually accomplish anything. ** Attachment added: /var/log/apt/term.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/663608/+attachment/1702317/+files/term.log -- Kernel update on livecd fails to symlink initrd.img: File exists https://bugs.launchpad.net/bugs/663608 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 645700] Re: linux-image-2.6.32-24-generic 2.6.32-24.43 failed to upgrade
*** This bug is a duplicate of bug 562312 *** https://bugs.launchpad.net/bugs/562312 ** This bug is no longer a duplicate of bug 609932 package linux-image-2.6.32-24-generic 2.6.32-24.38 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 ** This bug has been marked a duplicate of bug 562312 package initramfs-tools 0.92bubuntu71 [modified: usr/sbin/update-initramfs] failed to install/upgrade: lzma: Encoder error: -2147467259 * You can subscribe to bug 562312 by following this link: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/562312/+subscribe -- linux-image-2.6.32-24-generic 2.6.32-24.43 failed to upgrade https://bugs.launchpad.net/bugs/645700 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562312] Re: package initramfs-tools 0.92bubuntu71 [modified: usr/sbin/update-initramfs] failed to install/upgrade: lzma: Encoder error: -2147467259
In my case ( bug #645700 ) there were over 700MB free, so presumably lzma did not run out of space. In my case, /vmlinuz does point to a valid file, but I have no idea if this was true before the update: ~$ ls -al /vmlinuz lrwxrwxrwx 1 root root 30 2010-09-17 00:28 /vmlinuz - boot/vmlinuz-2.6.32-24-generic ~$ sudo ls -al /boot/vmlinuz-2.6.32-24-generic -rw-r--r-- 1 root root 4034976 2010-09-16 18:14 /boot/vmlinuz-2.6.32-24-generic -- package initramfs-tools 0.92bubuntu71 [modified: usr/sbin/update-initramfs] failed to install/upgrade: lzma: Encoder error: -2147467259 https://bugs.launchpad.net/bugs/562312 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 645700] [NEW] linux-image-2.6.32-24-generic 2.6.32-24.43 failed to upgrade
Public bug reported: package linux-image-2.6.32-24-generic 2.6.32-24.43 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 I used Update Manager to attempt to update the following packages: -linux-image-2.6.32-24-generic -linux-headers-2.6.32-24 -linux-headers-2.6.32-24-generic This live-usb installation was created from a remastered ISO using UCK, so it is possible that this is my fault. However, when I remastered, I did not attempt to update any of the kernel packages. This is the first time I've attempted to update my kernel with this installation, so I have no idea whether this is reproducible. ~$ lsb_release -d Description:Ubuntu 10.04.1 LTS ~$ apt-cache policy linux-image-2.6.32-24-generic linux-image-2.6.32-24-generic: Installed: 2.6.32-24.43 Candidate: 2.6.32-24.43 Version table: *** 2.6.32-24.43 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid-security/main Packages 500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 100 /var/lib/dpkg/status ProblemType: Package DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-24-generic 2.6.32-24.43 Regression: Yes Reproducible: No ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 Architecture: i386 Date: Thu Sep 23 01:36:21 2010 ErrorMessage: subprocess installed post-installation script returned error exit status 2 LiveMediaBuild: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1) SourcePackage: linux Title: package linux-image-2.6.32-24-generic 2.6.32-24.43 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- linux-image-2.6.32-24-generic 2.6.32-24.43 failed to upgrade https://bugs.launchpad.net/bugs/645700 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 645700] Re: linux-image-2.6.32-24-generic 2.6.32-24.43 failed to upgrade
** Attachment added: /var/log/apt/history.log https://bugs.launchpad.net/bugs/645700/+attachment/1625324/+files/history.log ** Attachment added: AptOrdering.txt https://bugs.launchpad.net/bugs/645700/+attachment/1625325/+files/AptOrdering.txt ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/645700/+attachment/1625326/+files/Dependencies.txt ** Attachment added: Df.txt https://bugs.launchpad.net/bugs/645700/+attachment/1625327/+files/Df.txt ** Attachment added: Dmesg.txt https://bugs.launchpad.net/bugs/645700/+attachment/1625328/+files/Dmesg.txt ** Attachment added: DpkgTerminalLog.gz https://bugs.launchpad.net/bugs/645700/+attachment/1625329/+files/DpkgTerminalLog.gz -- linux-image-2.6.32-24-generic 2.6.32-24.43 failed to upgrade https://bugs.launchpad.net/bugs/645700 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 645700] Re: linux-image-2.6.32-24-generic 2.6.32-24.43 failed to upgrade
I can, in fact restart after this error. After restarting, Update Manager reports that the system is up to date. ~$ apt-cache policy linux-image-2.6.32-24-generic linux-image-2.6.32-24-generic: Installed: 2.6.32-24.43 Candidate: 2.6.32-24.43 Version table: *** 2.6.32-24.43 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid-security/main Packages 500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 100 /var/lib/dpkg/status ~$ uname -a Linux ubuntu 2.6.32-24-generic #39-Ubuntu SMP Wed Jul 28 06:07:29 UTC 2010 i686 GNU/Linux -- linux-image-2.6.32-24-generic 2.6.32-24.43 failed to upgrade https://bugs.launchpad.net/bugs/645700 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 645700] Re: linux-image-2.6.32-24-generic 2.6.32-24.43 failed to upgrade
*** This bug is a duplicate of bug 609932 *** https://bugs.launchpad.net/bugs/609932 My naive understanding is that this is not a duplicate of bug #609932. The relevant parts of my dpkg terminal log are: Preparing to replace linux-headers-2.6.32-24-generic 2.6.32-24.39 (using .../linux-headers-2.6.32-24-generic_2.6.32-24.43_i386.deb) ... Unpacking replacement linux-headers-2.6.32-24-generic ... Setting up linux-image-2.6.32-24-generic (2.6.32-24.43) ... Running depmod. update-initramfs: Generating /boot/initrd.img-2.6.32-24-generic lzma: Encoder error: -2147467259 Failed to create initrd image. dpkg: error processing linux-image-2.6.32-24-generic (--configure): subprocess installed post-installation script returned error exit status 2 Note the lzma encoder error. ** Tags added: initramfs linux-image-2.6.32-24-generic lzma -- linux-image-2.6.32-24-generic 2.6.32-24.43 failed to upgrade https://bugs.launchpad.net/bugs/645700 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 323570] Re: can't play avi video Movie player closes
*** This bug is a duplicate of bug 245213 *** https://bugs.launchpad.net/bugs/245213 I don't think this is a duplicate bug. I had the exact same problem in Ubuntu NBR 9.04. I fixed it through starting up in recovery mode (option in the grub boot loader), then selecting 'attempt to automatically fix graphics problems'... or words to that effect. After that everything was fine. D. -- can't play avi video Movie player closes https://bugs.launchpad.net/bugs/323570 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112039] Re: [needs-packaging] KScannerButtons
No, I just haven't logged on in a while. I'd still like to try :-) Thanks, Daniel -- [needs-packaging] KScannerButtons https://bugs.launchpad.net/bugs/112039 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112039] Re: [needs-packaging] KScannerButtons
I have read the guide to packaging in the ubuntu wiki and feel pretty confident. A mentor would be helpful but I don't need one that badly. I would be really interested in working on this package or another one like it. Thanks very much, Daniel -- [needs-packaging] KScannerButtons https://bugs.launchpad.net/bugs/112039 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53691] Re: Install Manual link on Alternate CD incorrect
Reassigned to installation-guide per mdke's suggestion. ** Changed in: ubuntu-docs (Ubuntu) Sourcepackagename: ubuntu-docs = installation-guide -- Install Manual link on Alternate CD incorrect https://launchpad.net/bugs/53691 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 19634] Re: after installing Ubuntu I can't access my rescue partition
ThinkWiki has some more information on this: http://thinkwiki.org/wiki/Predesktop_Area which links to http://thinkwiki.org/wiki/Hidden_Protected_Area http://thinkwiki.org/wiki/Rescue_and_Recovery The basic gist is that there's a hidden part of the hard drive (at the end) that can be booted into which contains backups and diagnostics. The tricky part is that the implementation has actually changed over time. Here's a summary of what I've been able to figure out. On older ThinkPads, this is implemented with the BIOS hiding that part of the hard drive (by reporting a smaller hard drive to the OS). In this case, the MBR contains a special ThinkPad bootloader which monitors the blue button. If the blue button is not pressed, it boots the first partition on the drive regardles of active bit. If the blue button is pressed, it does something magical to boot into the hidden part of the hard drive. On newer ThinkPads, the hidden part of the hard drive is a standard hidden partition, and the ThinkPad bootloader unhides it and boots into it when the button is pressed. In this case, it is possible to have GRUB replace the ThinkPad bootloader. Installing any bootloader into the MBR that is not the ThinkPad bootloader will result in difficulty booting into the predesktop area. Depending on your model, you may be able to configure grub to do the same thing. -- after installing Ubuntu I can't access my rescue partition https://launchpad.net/bugs/19634 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 21175] Re: Grub removes Windows boot option when NTFS partition needs recovery
While not a duplicate, the recovery partition accessibility problem is also discussed in Bug 19634. -- Grub removes Windows boot option when NTFS partition needs recovery https://launchpad.net/bugs/21175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
