** Attachment added: "sigtest.cpp"
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1748597/+attachment/5052391/+files/sigtest.cpp
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunwind in Ubuntu.
Public bug reported:
https://bugs.debian.org/827015 was incorporated into the 1.2 package
(present on bionic); it would be really nice to backport that fix to all
prior releases (though I mostly care about trusty and xenial).
Without this fix, libunwind will corrupt the signal mask, which breaks
Here is the strace output for "eject -v -X sr0" for comparison
** Attachment added: "strace output for "eject -v -X sr0""
https://bugs.launchpad.net/ubuntu/+source/eject/+bug/1748503/+attachment/5052019/+files/sr0.trace
--
You received this bug notification because you are a member of
Public bug reported:
My machine has two CD/DVD drives. Entering "eject -v -X sr0" finds the
first drive. Entering "eject -v -X sr1" sorta finds the second drive but
not really. Here's the output for both.
$ eject -v -X sr0
eject: device name is `sr0'
eject: expanded name is `/dev/sr0'
eject:
Thanks Marc! Do you happen to know the answer to my other question?
"I'm also not an expert on NSEC/DNSSEC. Is this something that any
random app that uses DNS can be vulnerable too, or does it require a
program to specifically be trying to invoke DNSSEC somehow?"
--
You received this bug
@mdeslaur: Should I interpret the release of
https://usn.ubuntu.com/usn/usn-3558-1/ as saying that the answer to my
question in comment 19 is that yes, now we are getting the response?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
This bug is related to
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1725869 (and
https://sourceware.org/bugzilla/show_bug.cgi?id=22296). If gcc-4 is
rebuilt with a version of glibc with that bug fixed then this one is
fixed too.
** Bug watch added: Sourceware.org Bugzilla #22296
Public bug reported:
Summary:
On a device without build-in microphone, plug-unplug headset, on
gnome-control-center sound setting input tab, input level keeps going up and
down even without mic/headset attached.
Steps to reproduce:
1. Fresh install Ubuntu 17.10.1 image
2. Boot up the device
3.
** Changed in: zlib (Ubuntu)
Assignee: David Britton (davidpbritton) => Patricia Gaughen (gaughen)
** Changed in: ubuntu-power-systems
Assignee: David Britton (davidpbritton) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
apt does what it is told – appstream configures apt to download only the
files for the native architecture, so there is no sensible action to be
taken by apt and hence this task invalid.
If "$(NATIVE_ARCHITECTURE)" in the apt.conf file shipped by appstream is
changed to "$(ARCHITECTURE)" apt will
This problem still exists.
The problem is that these modules are listed in the blacklist files
provided with the kernel(/lib/modprobe.d/blacklist_linux-*.conf). Given
that these files aren't located in /etc they apparently are not
configuration files. Also very new kernel package you get a new
If it installs all of the language packages in other languages, except
for English-UK (and other non-US English locales), then it IS a bug.
The ubiquity installer could install every language pack when the user
chooses English-UK - it makes sense. The user wants English-UK, so
please install all
Public bug reported:
On boot, headset not listed in mixer list of audio outputs or inputs.
Upon unplugging, and plugging back in, the headset showed up and sound
began to play.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu
When the user selects a different language to English-US (e.g. English-
UK), all of the UK language packs should also be installed during
installation. Maybe ubiquity is the focus of the bug report?
When the user selects English-UK during Ubuntu installation, why don't
the related packages get
Just to follow up, i have done the upgrade to windows 10 version 17063,
and the bug is fixed, this should probably be marked as resolved by
Microsoft and the WSL team
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in
Been researching this issue, seems it's fixed in windows insider build
17046 and later
Reference issue:
https://github.com/Microsoft/WSL/issues/1878
Reference comment:
https://github.com/Microsoft/WSL/issues/1878#issuecomment-350325140
** Bug watch added: github.com/Microsoft/WSL/issues
Public bug reported:
Installing 18.07 on WSL using do-distribution-upgrade -d
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bash 4.3-14ubuntu1.2
ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
Uname: Linux 4.4.0-43-Microsoft x86_64
ApportVersion: 2.20.1-0ubuntu2.10
** Changed in: maas (Ubuntu)
Status: New => Won't Fix
** Changed in: maas (Ubuntu Trusty)
Status: New => Triaged
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
c 7 20:52:00 sydney systemd[1]: Started Session 379 of user david.
Dec 7 20:53:17 sydney gedit[511]: Error reading events from display: Broken
pipe
Dec 7 20:53:17 sydney tilix[4244]: Error reading events from display: Broken
pipe
Dec 7 20:53:17 sydney update-notifier[2795]: Error readin
ted service
'org.freedesktop.GeoClue2'
Dec 7 20:50:41 sydney systemd[1]: Started Location Lookup Service.
Dec 7 20:52:00 sydney systemd[1]: Started Session 379 of user david.
Dec 7 20:53:17 sydney gedit[511]: Error reading events from display: Broken
pipe
Dec 7 20:53:17 sydney tilix[4244]: Er
** No longer affects: init-system-helpers (Ubuntu Bionic)
** No longer affects: init-system-helpers (Ubuntu Artful)
** No longer affects: init-system-helpers (Ubuntu Zesty)
** No longer affects: init-system-helpers (Ubuntu Xenial)
** Changed in: init-system-helpers (Ubuntu)
Status:
** Changed in: util-linux (Ubuntu)
Assignee: David Britton (davidpbritton) => Patricia Gaughen (gaughen)
** Changed in: ubuntu-power-systems
Assignee: Canonical Server Team (canonical-server) => (unassigned)
--
You received this bug notification because you are a member of
** Changed in: iproute2 (Ubuntu)
Assignee: David Britton (davidpbritton) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1732032
Ti
I got some advice on mistakes in my update to changelog. This version
should be better.
** Patch added: "Second version with fixed changelog entries"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732803/+attachment/5012529/+files/Fix-journald-rate-limit-with-low-disk-space.debdiff
** Changed in: lxc (Ubuntu)
Assignee: David Britton (davidpbritton) => Stéphane Graber (stgraber)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1699759
Title:
This is my first attempt at a debdiff and an SRU. I'd love to know if
I've filed it properly!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1732803
Title:
Does anyone have an idea how to do a temp fix job on this? For us, this
happens on an off the shelf gitlab AWS image (Ubuntu 16.04) Because the
gitlab runners ssh into the gitlab server very many times, each one of
those ssh logins needs to timeout on the login1 hand off and sometimes
it crashes
Correction: I believe this occurs when the amount of remaining space
until journald hits its allocated limit is between 1 and 16MB, not when
the entire filesystem has that little space left. (This makes it much
more likely to occur: any system that is using logs enough for them to
be rotated due
** Patch added: "debdiff backporting fix from upstream"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732803/+attachment/5010237/+files/Fix-journald-rate-limit-with-low-disk-space.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
[Impact]
systemd-journald allows you to configure a per-service journal rate limit in
/etc/systemd/journald.conf via the RateLimitBurst parameter. systemd-journald
has
code that effectively increases the rate limit when there is a lot of disk
space available.
However, all
Same with Postman v5.3.2 64bits on ubuntu 17.10 (in VmwareWorkstation)
# /usr/bin/postman
/usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string
constant "murrine-scrollbar", expected valid string constant
Closed Window (id: 1)
--
You received this bug notification
Hi nalsubaie --
Please file a new bug report with ubuntu-bug systemd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1714301
Title:
systemd-networkd hangs my boot
Public bug reported:
When running Gnome 3 in Wayland mode (confirmed with XDG_SESSION_TYPE
env var) I see the following issues on this hardware:
* Jerky animations (glxgears stutters noticably)
* Mouse cursor sometimes updated at a reduced framerate, usualy when CPU is
under load, appearing to
Same problem on Ubuntu 17.10, I think it's a bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/1251178
Title:
qdbus and qdbusviewer crash with "No such file or
re: comment #14 (for future readers), please keep the discussion over
on:
https://bugs.launchpad.net/netplan/+bug/1729022
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
We manually enable systemd-resolved.service on xenial. It's installed
though it is not the default. Does that mean we are not going to get the
fix for this?
I'm also not an expert on NSEC/DNSSEC. Is this something that any
random app that uses DNS can be vulnerable too, or does it require a
Is systemd's sysv-generator prioritized over regular systemd unit files
? My question raises from this fix. It looks like unit files were
automatically created because of the existence of the wrong LSB
parameters in init files - by the generator - but at the same time
Xenial should be using
Public bug reported:
Ubuntu 17.10:
lscpu has the following fields of interest to this report:
Model name: Intel(R) Core(TM) i7-2700K CPU @ 3.50GHz
CPU MHz: 3499.996
CPU max MHz: 5900.
CPU min MHz: 1600.
The CPU MHz field is incorrect: At idle it
I tried to address the user issue part using the virtual machine version
of Ubuntu 17.10. It is still the same.
** Attachment added: "vokoscreen-2017-10-24_11-42-07.mkv"
I got this instead though...
** Attachment added: "Screenshot from 2017-10-24 11-20-30.png"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1725064/+attachment/4990023/+files/Screenshot%20from%202017-10-24%2011-20-30.png
--
You received this bug notification because you are a member
I wish that the effect here in Ubuntu 7.10 GNOME Shell search is the
same as this when it is integrated in the files. I upgraded to Ubuntu
7.10 expecting for this.
** Attachment added: "Selection_009.png"
If that could be the case, I updated the bug report to NetworkManager
component of GNOME instead.
https://bugzilla.gnome.org/show_bug.cgi?id=789341
** Attachment added: "Selection_008.png"
I think this error report had a similar problem, the bug report said it
is not GNOME problem: https://bugzilla.gnome.org/show_bug.cgi?id=773163
On the other hand, I created this same bug report to GNOME:
https://bugzilla.gnome.org/show_bug.cgi?id=789341 with a video to
express clearly what the
I think this error report had a similar problem, the bug report said it
is not GNOME problem: https://bugzilla.gnome.org/show_bug.cgi?id=773163
On the other hand, I created this same bug report to GNOME:
https://bugzilla.gnome.org/show_bug.cgi?id=789341 with a video to
express clearly what the
While that sounds reasonable at first in simple situations, if I follow
that argument, I can find no reason why we are doing complex metapackage
handling, keeping many providers and a lot of other things, so we should
get right of all those, too, should we?
In reality we have to deal with many
Public bug reported:
I used to search a file and access it immediately using Ubuntu 16.04 LTS
and some other distributions of GNOME. However, this time, almost only
folders are shown in the file search.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.26.0-0ubuntu1
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Also affects: network-manager-applet (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Verifying...
http://pastebin.ubuntu.com/25753116/
After using -proposed version:
http://paste.ubuntu.com/25753146/
Considering this fixed. Verified!
** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty
--
You received this
** Changed in: libnl3 (Ubuntu)
Assignee: Rafael David Tinoco (inaddy) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1312419
Title:
nl_cache_ref
After fixing this BUG (for canonical-livepatch snap to work, but being
affected by broken systemd in Trusty due to the lack of systemd-
fsck@.service unit file, I'm facing the following opened BUG:
https://bugs.launchpad.net/snapd/+bug/1721518 for canonical-livepatch
(or any other snap) to work).
I tested the fix from ppa:inaddy/lp1718966 and I am now able to install
snaps on my two test systems without using the /etc/fstab workaround,
one with LVM and one without. Both systems have /var isolated. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch
** Description changed:
[Impact]
Installing snaps is not possible on Ubuntu 14.04 when having /var on its
own partition, whether its LVM or not.
The issue is with the core snap being unable to mount:
The error with /var isolated and using LVM:
root@ubuntu:~# snap install
Solved?
Thanks for this forum Ubuntu. I'm a Fedora user, but I frequently find
solutions here
I have an XPS 9550 along with the issue of the headphone microphone not
working. I changed /etc/modprobe.d/alsa.conf from:
options snd-hda-intel single_cmd=1 probe_mask=1 model=dell-headset-multi
Meanwhile I have created a PPA containing the fix for all those affected
users:
https://launchpad.net/~inaddy/+archive/ubuntu/lp1718966
$ sudo add-apt-repository ppa:inaddy/lp1718966
$ sudo apt-get update
$ sudo apt-get dist-upgrade
Is likely enough for you to have a temporary fix.
--
You
I've made a small change creating a unit file slightly different from
the one already present in systemd-204, considering different
dependencies for this usage (mounting/umounting volumes when upstart has
already taken part on it).
The result is here: http://pastebin.ubuntu.com/25663762/
As you
had the same problem and could only fix it by removing the line
load-module module-switch-on-connect
from
/etc/pulse/default.pa
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
I just saw this via the USN. I'm having trouble evaluating the urgency
of this fix.
Is the issue:
- Without this, connecting to some sites will fail because of
missing/lapsed CAs
or
- Without this, you'll probably get MITMed because you're trusting some
insecure hacked CAs
?
--
You received
Okay, so another quick workaround, now keeping the fsck enabled for the
volumes:
Create a file called "/lib/systemd/upstart/systemd-fsck@.service" with:
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU
I confirm the workaround works for me:
Before:
root@ubuntu:~# cat /etc/fstab
/dev/mapper/vg00-rootvol / ext4errors=remount-ro 0 1
/dev/mapper/vg00-varvol /varext4defaults0 2
/dev/mapper/vg00-swap noneswapsw 0
Ok so in systemd-204, in TRUSTY, you will find the following logic to
create the mount units:
- manager_loop
- process-event (WATCH_MOUNT)
- mount_fd_event
- mount_load_proc_self_mountinfo
- mount_add_one (if load_extras == true)
- mount_add_extras
-
** Changed in: systemd (Ubuntu Trusty)
Assignee: (unassigned) => Rafael David Tinoco (inaddy)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1718966
Title:
Can
18.4ubuntu1.2
>apt 1.2.24
> SourcePackage: util-linux
> Title: package util-linux 2.29-1ubuntu2.1 failed to install/upgrade:
> subprocess installed post-installation script returned error exit status 1
> UpgradeStatus: Upgraded to xenial on 2017-08-26 (0 days ago)
>
&g
roblem to be fixed IMO.
This case should be targeted to both: snapd (trusty) AND systemd
(trusty)
** Changed in: snapd
Assignee: (unassigned) => Rafael David Tinoco (inaddy)
** Changed in: snapd
Status: New => Confirmed
** Also affects: systemd (Ubuntu)
Importance: Undecided
Public bug reported:
Description:Ubuntu Artful Aardvark (development branch)
Release:17.10
Instalados: 1.8.2-1ubuntu8
Candidato: 1.8.2-1ubuntu8
Tabla de versión:
*** 1.8.2-1ubuntu8 500
500 http://es.archive.ubuntu.com/ubuntu artful/main amd64 Packages
500
Ahah, this bug from 2011 is still valid in 2017 with Zesty!
Extract from `ps axf` today:
27019 ?Sl 0:00 \_ gdm-session-worker [pam/gdm-password]
27029 tty2 Ssl+ 0:00 \_ /usr/lib/gdm3/gdm-x-session --run-script
gnome-session --session=gnome
27031 tty2 Sl+1:05
Public bug reported:
graphics frame-rate is choppy in chrome, both stills and video, no
problems before recent-ish update(s)
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-33-generic
Public bug reported:
not much to say.
feel free to ask for info as nec.
PC-SUmmery:
HP-Z800 with dual Xeon -=- 96Ram
Boot SSD - Samsung evo 256
HD2 - SSD - Samsung evo 512
HD3-6 - WD Black 6tb each
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
#82 Helped me as well. And I'm 17.04...
It'd be nice to see this fixed...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1624317
Title:
systemd-resolved breaks
Unrelated to systemd. Related to open-iscsi systemd unit files and
kernel iscsi transport logout during shutdown.
** Changed in: open-iscsi (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: open-iscsi (Ubuntu Xenial)
Status: New => In Progress
** Changed in: open-iscsi
## SUMMARY 1
Affects open-iscsi (NOT systemd):
* ISCSID NEEDS TO BE UP & RUNNING (AND LOGGED TO PORTAL) FOR THE LOGOUT
TO WORK
https://pastebin.canonical.com/197359/
Daemon shutdown documentation in iscsiadm command says (about stopping iscsid
daemon with iscsiadm -k):
""" ... This will
** Also affects: open-iscsi (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
I keep gettin an error that I am out of space on /boot
This is a default Ubuntu install, so I'd figure y'all would have the default
/boot partition be the proper size.
I executed:
sudo apt-get autoremove linux-image-4.4.0.66-generic
And this error popped up.
There has got
Okay, I removed almost everything out of equation:
- removed networking interfaces from systemd
- removed open-iscsi login/logout logic from systemd
- used a single network interface for the logins, on a single iscsi portal
was still able to reproduce the issue by:
- doing a simple login after
Public bug reported:
?
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: util-linux 2.29-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Fri
For now, the workaround for this bug is this:
inaddy@iscsihang:~$ sudo su -
# disconnect what iscsid has mapped
root@iscsihang:~$ iscsiadm -m node --logoutall=all
# disconnect all leftovers
root@iscsihang:~$ for file in `find /sys/devices -name *delete`; do echo 1 >
$file; done
# shutdown
This is what I discovered:
This systemd issue is caused because there are iscsi connections still
logged in (not because of multipath, bonding, vlans, etc). One way of
reproducing this is by simply editing the open-iscsi.service unit and
disabling the logout script. It will, for me in all times,
47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1757 F pulseaudio
Date: Wed Dec 7 08:18:48 2016
ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited wi
Only a single device connected, the connection might have been
unreliable while I plugged a headphone. dmesg says:
[ 566.417496] firewire_core :15:00.1: created device fw1: GUID
0005950400400fc2, S400
[ 567.712261] firewire_core :15:00.1: BM lock failed (timeout), making
local node
Okay, besides all crap I posted - which are definitely right and will
possibly be addressed in other bugs, and also show other problems that
could make systemd to hang because of iscsi disks - I was able to cause
the same symptom of this bug:
[ OK ] Stopped LSB: ebtables ruleset management.
[
ure: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1757 F pulseaudio
Date: Wed Dec 7 08:18:48 2016
ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with
return code 2
HibernationDevice: RESUME=UUID=8d4566d4-7212
7.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1757 F pulseaudio
Date: Wed Dec 7 08:18:48 2016
ErrorMessage: run-parts: /etc/kernel/
pportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1757 F pulseaudio
Date: Wed Dec 7 08:18:48 2016
ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with
return code 2
Hibernatio
name: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1757 F pulseaudio
Date: Wed Dec 7 08:18:48 2016
ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal
Might be unrelated, but I discovered that:
## root namespace
root@iscsihang:~$ mount | egrep -E "sd.*(xfs|ext4)"
/dev/sda1 on /ext4 type ext4 (rw,relatime,stripe=32,data=ordered,_netdev)
/dev/sdb1 on /xfs type xfs (rw,relatime,attr2,inode64,noquota,_netdev)
## specific mnt namespace
Hypothesis,
Test (2) - The error is propagated to upper layers after X seconds.
In this case I'm testing:
$ sudo iscsiadm -m node -o show | grep node.session.timeo.replac
node.session.timeo.replacement_timeout = 60
node.session.timeo.replacement_timeout = 60
And same "locking" behavior is
Hypothesis,
Test (1) - The error is NEVER propagated to upper layers:
# xfs and ext4 mounted automatically
inaddy@iscsihang:~$ mount | grep _netde
/dev/sda1 on /ext4 type ext4 (rw,relatime,stripe=32,data=ordered,_netdev)
/dev/sdb1 on /xfs type xfs (rw,relatime,attr2,inode64,noquota,_netdev)
#
Hello Matt,
Good to read your feedback. When you have multipath AND iscsi, the error
propagation timeout can be given by one or both, that is why I explained
both. This issue is not an iscsi or multipath problem, it is a systemd
problem related to the fact that the network is removed before the
** Changed in: systemd (Ubuntu Xenial)
Assignee: (unassigned) => Rafael David Tinoco (inaddy)
** Changed in: systemd (Ubuntu Xenial)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
ure: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1757 F pulseaudio
Date: Wed Dec 7 08:18:48 2016
ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with
return code 2
HibernationDevice: RESUME=UUID=8d4566d4-7212-4261-963c-93
6_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1757 F pulseaudio
Date: Wed Dec 7 08:18:48 2016
ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with
return code 2
ing using ucaresystem-core. It left me at linux
4.4.0.21-generic and seems to be running fine.
Thanks for your interest.
David Ploen
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/b
** Also affects: apt (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872334
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
I believe this issue also affects apt-ftparchive in Debian, so have raised a
bug there:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872334
** Bug watch added: Debian Bug tracker #872334
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872334
--
You received this bug notification
juliank: From what I can see, cache files generated by apt-ftparchive do
not contain versioned entries. They can also be located anywhere on a
machine's filesystem, depending on how the sysadmin chose to apply the
utility; there isn't one canonical file that can be automatically
refreshed on
Public bug reported:
Release: 16.04
Version: 1.2.19
apt-ftparchive is a utility for, among other things, generating a
Packages file from a set of .deb packages.
Because generating Packages files for a large directory tree of .deb
packages is expensive, it can cache the properties of .deb
Another thing. Please check for containers referencing the filesystems
in question. When you have _netdev filesystems, it is possible that the
"mount --shared" characteristics of containers (different mount
namescapes) are holding references to the filesystem in question.
A good test is to test
Anyone facing this..
Could you please make sure to propagate I/O errors properly to
filesystem in order for it to call its automatically shutdown procedure.
After that, the mount won't reference the super block in kernel and that
will allow the device mapper to be destroyed (this can be seen by
Anyone facing this..
Could you please make sure to propagate I/O errors properly to
filesystem in order for it to call its automatically shutdown procedure.
After that, the mount won't reference the super block in kernel and that
will allow the device mapper to be closed/destroyed (this can be
Sorry, what does this mean? I do not understand.
Looking forward to your reply.
Have a great day
2017-08-11 6:11 GMT+08:00 Pat Ferrel :
> Just installed Xenial with all updates and can't install zlib1g-dev. It
> does not exist in proposed (tried from there) so I assume
Public bug reported:
Daisy-chained devices, trying to select one for operation.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: jackd2 1.9.10+20150825git1ed50c92~dfsg-2ubuntu2
ProcVersionSignature: Ubuntu 4.11.0-10.15-lowlatency 4.11.8
Uname: Linux 4.11.0-10-lowlatency x86_64
601 - 700 of 2291 matches
Mail list logo