** Attachment added: "history.log"
https://bugs.launchpad.net/ubuntu/+source/postgresql-11/+bug/1825501/+attachment/5258225/+files/history.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825501
** Attachment added: "apt-clone_system_state.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/postgresql-11/+bug/1825501/+attachment/5258229/+files/apt-clone_system_state.tar.gz
** Changed in: postgresql-11 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification
** Attachment added: "apt.log"
https://bugs.launchpad.net/ubuntu/+source/postgresql-11/+bug/1825501/+attachment/5258228/+files/apt.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825501
Title:
** Attachment added: "apt-term.log"
https://bugs.launchpad.net/ubuntu/+source/postgresql-11/+bug/1825501/+attachment/5258227/+files/apt-term.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "eipp.log.xz"
https://bugs.launchpad.net/ubuntu/+source/postgresql-11/+bug/1825501/+attachment/5258226/+files/eipp.log.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825501
Hello,
I'm attaching the relevant logs from /var/log/dist-upgrade
As you see, postgresql-10 was listed as Obsoleted and then in the
remove_candidates
Both boxes were updated on every release from utopic and experienced the
same behaviour.
** Attachment added: "main.log"
Tested on another cosmic machine and the upgrade, again, proposed the
removal of postgresql-10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825501
Title:
Upgrading the distro PURGED the previous
Public bug reported:
I did a do-release-upgrade as I usually do and I usually find the new
PostgreSQL package installed alongside with the previous, still working, one.
This time the upgrader PURGED the old package removing the cluster data
and configuration and everything!
Luckily I had a
Thank you Andreas, thank you Thomas, the workaround to depend on
network-online.target is fine for me.
I agree with Thomas that freebinding is not the appropriate way to cope
with binding to address that should deterministically be present on
start of the service.
You have surely made all the
Public bug reported:
Hello,
I have a Ubuntu cosmic box with static IPv4 and IPv6 addresses. It
noticed that on boot nginx is not able to bind to the explicit IPv6
address. However, trying few seconds after boot completed it starts
fine.
Mar 04 21:02:10 gems systemd[1]: Starting A high
Public bug reported:
Hello,
I have hosts with short-leaved DHCP leases.
Every time a lease is renewed systemd-resolved gets restarted and the
daemons attempting to resolve names get permanent errors.
gethostbyname returns NO_RECOVERY and that leads to more or less severe
failures.
That would
I wrote too soon, sorry, usbipd works fine, it's just that the working
binary is included in linux-tools-generic instead of usbip package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/900384
Title:
This issue seems to be still present on zesty.
The modules are present in the kernel and loaded, however usbipd fails
loading:
# usbipd -d -D
usbip err: stub_driver.c: 33 (open_sysfs_stub_driver) usbip_common_mod.ko and
usbip.ko must be loaded
** (process:3248): ERROR **: driver open failed
Sorry for the delay but I needed physical access to the host box.
I upgraded XenServer to 7.0 (fully patched) and the problem persists.
I tried with kernel 4.9-rc3 and the issue is still there.
I reverted to 4.4.0-45 and the issue disappears.
--
You received this bug notification because you
Public bug reported:
Hello,
I am experiencing a noticeable system slowdown since I upgraded from
Xenial to Yakkety on several VM under XenServer 6.5 (fully patched).
I understand it will be difficult for me to describe what is happening
and for you to troubleshoot this issue but I'll try to do
This issue is still present in latest wily beta.
I have a fairly big desktop with with ~15 konsole windows, browsers,
email client, ecc restoring the desktop takes a fairly big time.
This, plus the frequent issues in suspending and resuming the machine
(crash) make this a farily important
Christopher, I'm sorry but I don't have enough spare time to search for
the commit :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1498448
Title:
GUI failure when reinserting HDMI cable with Intel
The issue started when I upgraded from wily. Booting the previous kernel
solves the issue.
I tried with the latest 4.3 kernel and the problem seems to be fixed,
both the EDID messages and the X11/GUI processes are not crashing
anymore.
--
You received this bug notification because you are a
Christopher, I see you added a "bios-outdated" tag and I promptly
updated the BIOS to 0802 however this specific issue wasn't fixed by the
BIOS update.
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Addendum: This happens consistently using a KVM and switching from one
system to another.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1498448
Title:
GUI failure when reinserting HDMI cable with
Public bug reported:
Hello,
Removing the HDMI cable on my ASUS UN42 results in EDID failure which
might be only cosmetic, however inserting the cable again causes the
crash of the whole GUI segfaulting several KDE daemons.
Manually restarting SDDM restores the GUI.
[ 253.213048]
Thomas Lübking, your childish behaviour is an insult to everyone who is
affected by this bug, lost time, got frustrated and finally found out
this kind of consideration.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Importance is NORMAL?!?!
Whole session management is broken and this has NORMAL importance???
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446865
Title:
kwin does not remember on which desktop
Note that I'm working with vivid and network-manager 0.9.10.0-4ubuntu15
with systemd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445846
Title:
nm-online returns too early
To manage
Public bug reported:
I am setting up a totem system which mounts a remote file system at boot and
starts an application from it.
I found that randomly the boot fails because the mount fails due to
Network unreachable errors.
I made sure the mount unit waits for network-online.target to be
Just upgraded to oneiric, bug persists sigh
--
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/510587
Title:
Bind/named does not initialize on boot due to missing IPv6 address
Just upgraded to oneiric, bug persists sigh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/510587
Title:
Bind/named does not initialize on boot due to missing IPv6 address
To manage
** Changed in: bind9 (Ubuntu)
Status: Expired = New
--
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/510587
Title:
Bind/named does not initialize on boot due to missing IPv6
** Changed in: bind9 (Ubuntu)
Status: Expired = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/510587
Title:
Bind/named does not initialize on boot due to missing IPv6 address
--
This problem is still very present on Maverick
A notable fact might be that I explicitly bind to certain IPv6 addresses
instead of the default all interfaces
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in ubuntu.
This problem is still very present on Maverick
A notable fact might be that I explicitly bind to certain IPv6 addresses
instead of the default all interfaces
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Binary package hint: pure-ftpd
pure-ftpd-postgresql 1.0.28-2 on maverick on x86-64
(I'm actually using pure-ftpd-postgresql but it shouldn't be relevant.)
I'm using quota support. The issues shows up when a rename overwrites an
existing file.
# cat .ftpquota
0 0
put
This bug is still present in lucid release, just upgraded 4 boxes and
Bind didn't start at boot while it started when launched manually.
May 3 13:10:08 sid named[893]: starting BIND 9.7.0-P1 -u bind
May 3 13:10:08 sid named[893]: built with '--prefix=/usr'
'--mandir=/usr/share/man'
This bug is still present in lucid release, just upgraded 4 boxes and
Bind didn't start at boot while it started when launched manually.
May 3 13:10:08 sid named[893]: starting BIND 9.7.0-P1 -u bind
May 3 13:10:08 sid named[893]: built with '--prefix=/usr'
'--mandir=/usr/share/man'
Mark,
Attached you find a copy of /etc/network/interfaces.
Chuck,
1. the specific steps or actions you took that caused you to encounter the
problem,
rebooted the box
2. the behavior you expected, and
bind not failing
3. the behavior you actually encountered (in as much detail as
Yes, it could well be an issue in upstart or in some related-script,
unfortunately I'm not familiar with upstart, thus I'd have to spend some time
to figure out where the problem is (and at the moment the time is lacking...).
--
Bind/named does not initialize on boot due to missing IPv6
Mark,
Attached you find a copy of /etc/network/interfaces.
Chuck,
1. the specific steps or actions you took that caused you to encounter the
problem,
rebooted the box
2. the behavior you expected, and
bind not failing
3. the behavior you actually encountered (in as much detail as
Yes, it could well be an issue in upstart or in some related-script,
unfortunately I'm not familiar with upstart, thus I'd have to spend some time
to figure out where the problem is (and at the moment the time is lacking...).
--
Bind/named does not initialize on boot due to missing IPv6
Public bug reported:
Binary package hint: bind9
Hello,
After a reboot I noticed that named did not start. Starting it manually
worked fine.
In the log I found:
Jan 21 11:27:40 sid named[1315]: starting BIND 9.6.1-P2 -u bind
Jan 21 11:27:40 sid named[1315]: built with '--prefix=/usr'
Public bug reported:
Binary package hint: pure-ftpd-postgresql
This appears to be a regression in karmic as downgrading to jaunty's packages
solves the problem.
pure-ftpd, often but not always crashes during authentication.
Running pure-ftpd non-daemonized outputs a libc warning (attached)
** Attachment added: libc_warning
http://launchpadlibrarian.net/38001640/libc_warning
--
pure-ftpd with postgresql support in karmic crashes frequently during
authentication
https://bugs.launchpad.net/bugs/508768
You received this bug notification because you are a member of Ubuntu
Bugs,
Same on Asus T3-P5G31A
--
WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x7c/0x80()
https://bugs.launchpad.net/bugs/435877
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
42 matches
Mail list logo
