[Bug 1798091] Re: thumbnailer cannot create tempfiles (with apparmor denials)

Hello Ralf, or anyone else affected, Accepted evince into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/evince/3.30.1-1ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1799053] Re: Update gedit to 3.30.2

Hello Jeremy, or anyone else affected, Accepted gedit into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gedit/3.30.2-0ubuntu0.18.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1796499] Re: Keyboard calculator button not working

Seb, this is missing an SRU template, including a discussion of regression-potential. I see that your patch is replacing the reference to gnome-calculator.desktop with gnome-calculator_gnome- calculator.desktop rather than supporting both, so if the user still has the deb installed, won't this

[Bug 1800542] [NEW] OpenVPN connection not stable after upgrade to 18.10 (udp, ipv6)

Public bug reported: After upgrade to Ubuntu 18.10, my connection to my employer's VPN server has become unstable. The server provides both ipv4 and ipv6 endpoints. Since I have global ipv6 at home, my client defaults to connecting over ipv6. The connection consistently drops after only a few

[Bug 1798481] Re: org.gnome.desktop.interface.cursor-blink-timeout not honored

Or perhaps such an addition wouldn't be appropriate because it only applies to GTK applications and the xfce team would only want to include such a control if it were universal? In any case, I'll try to bring this to the attention of the xfce maintainers (and add answers to askubuntu.com, etc).

[Bug 1798481] Re: org.gnome.desktop.interface.cursor-blink-timeout not honored

I grepped for 463 against everything in my home directory and this was at the top of the list: .config/xfce4/xfconf/xfce-perchannel-xml/xsettings.xml: (Apparently I'm also not very familiar with the xfce ecosystem.) It seems there is some mechanism by which changes to properties in dconf

[Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (22s / no limit)"

The issue described in this bug, failure to shut down due to a 'Wait for Network' job, is believed to be resolved in the Ubuntu 18.04 final release and in later releases. I am therefore closing this bug. If someone can reproduce this failure with a currently-supported release image, please

[Bug 1798481] Re: org.gnome.desktop.interface.cursor-blink-timeout not honored

** Also affects: xfconf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1798481 Title:

[Bug 1798481] Re: org.gnome.desktop.interface.cursor-blink-timeout not honored

The blink time does seem to be a bit less than a half second. If I count the seconds out loud it blinks twice each second with a little time to spare. "dconf dump /" doesn't yield any instances of 463, but does show 1205 for cursor-blink-time (so it's in harmony with the dconf-editor GUI), and

[Bug 1798481] Re: org.gnome.desktop.interface.cursor-blink-timeout not honored

#2 Thanks for the comment. I'm accustomed to blinking following focus. The values I have in dconf are: cursor-blink: true cursor-blink-time: 1200 cursor-blink-timeout: 1 I built vte 0.54.1 and ran the test app with debugging messages on as you described. There is a line referring to "Cursor

[Bug 1798481] [NEW] org.gnome.desktop.interface.cursor-blink-timeout not honored

Public bug reported: Xubuntu desktop 18.04.1 $ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 gnome-terminal: 3.28.2-1ubuntu1~18.04.1 libgtk-3-0: 3.22.30-1ubuntu1 dconf-editor: 3.28.0-1 Per workaround instructions in comment #8 on bug 838381 (of which this is not a

[Bug 838381] Re: The cursor in active terminal window stops blinking after ten seconds.

I'd like to report that the workaround suggested in comment #8 has no effect in Xubuntu 18.04. It seems the native xfce4-terminal is also affected. I thought I'd solve the issue by switching to a terminal that isn't built on GTK so I installed Eterm, only to learn that not only does the cursor not

[Bug 1797543] Re: Unable to update software - Button Restart & Update, restarts no updates applied

Hello Tino, or anyone else affected, Accepted gnome-software into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.30.2-0ubuntu4 in a few hours, and then in the -proposed repository. Please help us by testing this new package.

[Bug 1794544] Re: [SRU] 2.56.3

What testing will be done of the resulting binary packages to guard against misbuilds not caught by the upstream testing? Please call this out explicitly in the bug description. (If the autopkgtests are sufficient, that's fine, please just call it out.) ** Changed in: glib2.0 (Ubuntu Bionic)

[Bug 1794544] Re: [SRU] 2.56.3

** Description changed: [ Description ] The third stable release in the 2.56 series. [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME - [ Regresison potential ] + [ Regression potential ] Various fixes

[Bug 1796434] Re: USB storage device does not finish ejecting

That would be a failed verification but not a regression. Removing the tag. ** Tags removed: regression-update -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1796434 Title: USB

[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

Hello Alberto, or anyone else affected, Accepted nvidia-settings into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia- settings/390.77-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this

[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

Hello Alberto, or anyone else affected, Accepted nvidia-prime into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia- prime/0.8.8.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-390 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-390/390.77-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please

[Bug 1778069] Re: [xfce] nautilus don't open files if set as default file manager

this effects a lot of users so please can you push the priority higher. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1778069 Title: [xfce] nautilus don't open files if set as

[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

Bug description says: > [Regression Potential] > Low, as hybrid graphics support does not work correctly, and the changes only > affect > this use case. Dropping the nvidia-fallback service means that any time the nvidia module has failed to be loaded, including if the nvidia module has failed

[Bug 1778011] Proposed package upload rejected

An upload of ubuntu-drivers-common to bionic-proposed has been rejected from the upload queue for the following reason: "contains change to systemd service with no bug reference; https://bugs.launchpad.net/ubuntu/+source/nvidia- prime/+bug/1778011/comments/10". -- You received this bug

[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

Reviewing ubuntu-drivers-common in the queue, I notice: +if (!match) { +free(match); Surely no good can come of this call to free() and it should be omitted? The change to start before oem-config.service seems correct but has no associated bug linked. This looks to me like

[Bug 1786046] Re: Bypass Login Screen by replugging in external monitors

** Summary changed: - Bypass Login Screen + Bypass Login Screen by replugging in external monitors ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu.

[Bug 1699388] Re: gdm3 crashed with SIGSEGV -- error after login using gdm3 greeter with Cinnamon Desktop using 4.12 rc 5 kernel. No symptoms so far besides error message

** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1699388 Title: gdm3 crashed with SIGSEGV -- error after login using gdm3 greeter

[Bug 1784514] Re: Update evolution-data-server to 3.28.5

Hello Jeremy, or anyone else affected, Accepted evolution-data-server into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /evolution-data-server/3.28.5-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by

[Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Triaged => In Progress ** Changed in: ubuntu-release-upgrader (Ubuntu Bionic) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to

[Bug 1784065] Re: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger

Hello Yan, or anyone else affected, Accepted glib2.0 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.48.2-0ubuntu4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1784065] Re: package libglib2.0-0 2.48.2-0ubuntu3 failed to install/upgrade: triggers ci file contains unknown directive `interest-await'

Unreproducible here in a xenial chroot w/ same versions of dpkg and libglib2.0-0. The format of the triggers file looks correct. Yan, is this problem reproducible if you run 'sudo dpkg --configure -a && sudo apt -f install && sudo apt install libglib2.0-0' in a terminal? Otherwise, my guess is

[Bug 1765401] Re: gtk+ toolbar style setting ignored in bionic?

Another thread relevant, at least for the gnucash aspect of this bug: https://lists.gnucash.org/pipermail/gnucash-user/2018-March/075769.html -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.

[Bug 1765401] Re: gtk+ toolbar style setting ignored in bionic?

Linking Jonathan's mailing list thread for reference: https://lists.gnucash.org/pipermail/gnucash-user/2018-April/076587.html -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1765401

[Bug 1781652] [NEW] should be possible to specify static routes on a dhcp-configured interface

Public bug reported: >From , a user wants to add a static route to a network interface where the gateway is known, but the interface's local address is configured via dhcp. This doesn't work with direct netplan

[Bug 1714989] Update Released

The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you

[Bug 1691675] Update Released

The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you

[Bug 1768786] Update Released

The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you

[Bug 1778703] Update Released

The verification of the Stable Release Update for mutter has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a

[Bug 1758528] Update Released

The verification of the Stable Release Update for mutter has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a

[Bug 1775145] Update Released

The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you

[Bug 1765261] Update Released

The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you

[Bug 1777956] Update Released

The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you

[Bug 1701047] Re: Renaming of conf file fails

Hello Gunnar, or anyone else affected, Accepted fonts-beng-extra into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fonts-beng- extra/1.0-6ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new

[Bug 1701047] Re: Renaming of conf file fails

Fix confirmed with the bionic-proposed version of fonts-guru-extra. ** Changed in: fonts-deva-extra (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to fonts-orya-extra in

[Bug 1701047] Please test proposed package

Hello Gunnar, or anyone else affected, Accepted fonts-deva-extra into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fonts-deva- extra/3.0-4ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new

[Bug 1701047] Please test proposed package

Hello Gunnar, or anyone else affected, Accepted fonts-gujr-extra into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fonts-gujr- extra/1.0-6ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new

[Bug 1701047] Please test proposed package

Hello Gunnar, or anyone else affected, Accepted fonts-orya-extra into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fonts-orya- extra/2.0-5ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new

Re: [Bug 1701047] Re: Renaming of conf file fails

On Thu, Jun 07, 2018 at 05:55:45PM -, Gunnar Hjalmarsson wrote: > OTOH, the issue is present for all the above packages for those > affected. Will try to fix them using the same method as you did for > fonts-guru-extra. It really isn't. I have all of these packages installed and

[Bug 1701047] Re: Renaming of conf file fails

Of these packages, fonts-guru-extra is the only one that in practice I see is affected by this bug on a continuously-upgraded system (16.04 -> 16.10 -> 17.04 -> 17.10 -> 18.04), so is the only package I am currently intending to SRU. -- You received this bug notification because you are a member

[Bug 1701047] Re: Renaming of conf file fails

** Description changed: - The fix of wasn't accomplished - properly. Renamings of conf files weren't addressed in maintainer - scripts, upgrades from previous versions fail in this respect, and the - package system generates warning messages. + [Impact] + The fix

[Bug 1701047] Re: Renaming of conf file fails

Fixed in 2.0-4ubuntu1 for cosmic. ** Changed in: fonts-guru-extra (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to fonts-guru-extra in Ubuntu. https://bugs.launchpad.net/bugs/1701047 Title:

[Bug 1771196] Re: daap plugin opens port by default

** Package changed: banshee (Ubuntu) => rhythmbox (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1771196 Title: daap plugin opens port by default To manage

[Bug 1772920] Re: package libgconf-2-4:amd64 3.2.6-4ubuntu1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross

[Bug 1771394] Re: gvfsd-mtp hoovers up all memory

I just experienced this too. If you don't need them, remove the adb files from ubuntu, if you're passing the USB device onto the guest OS, you don't need them anyway. FYI, I followed an install guide online, so just reversed the install line, e.g. sudo apt-get remove android-tools-adb

Re: [Bug 1767618] Re: system Brightness & Lock app ignores file permissions

Seth, thanks for the explanation. You learn something every day. I've been hacking away for almost 40 years now, and I hadn't considered how unlink() could be used to bypass access permissions. You had me ROTFL with your thoughts on apprenticeships in information security. :-) Steve Steve

Re: [Bug 1767618] Re: system Brightness & Lock app ignores file permissions

by the Brightness & Lock app eve@steve-laptop:~$ ls -l ~/.config/dconf/user -rw-r--r-- 1 steve eve 15965 Apr 28 10:37 /home/eve/.config/dconf/user ==> Alter lock settings using "Brightness & Lock" app eve@steve-laptop:~$ ls -l ~/.config/dconf/user -rw-rw-r-- 1 eve eve 15965 A

[Bug 1766575] Re: Drop libnss-myhostname recommends

Yes, I understand the reason for the Recommends. By "integrating with this", I meant that gnome-control-center's backend (which I believe is hostnamectl) should be updating /etc/hosts in addition to /etc/hostname. -- You received this bug notification because you are a member of Ubuntu Desktop

[Bug 1766575] Re: Drop libnss-myhostname recommends

Every Ubuntu system is installed with an entry in /etc/hosts pointing to 127.0.1.1 for the hostname. gnome-control-center should be integrating with this, and not just relying on either libnss-myhostname or systemd- resolved to resolve the hostname. The local hostname should be resolvable

[Bug 1751813] Re: Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L] [ipr]

** Changed in: debian-installer (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1751813 Title: Ubuntu 18.04 installer does not detect any

[Bug 1754422] Re: [MIR] volume-key

Override component to main volume-key 0.3.9-4 in bionic amd64: universe/utils/optional/100% -> main volume-key 0.3.9-4 in bionic arm64: universe/utils/optional/100% -> main volume-key 0.3.9-4 in bionic armhf: universe/utils/optional/100% -> main volume-key 0.3.9-4 in bionic i386:

[Bug 1764169] Re: error in gedit terminal can't edit a file

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross

[Bug 1765173] Re: networkd waits 10 seconds for ipv6 network discovery by default

The semantics of systemd-networkd-wait-online.service are that the service is ready when "the Internet" is reachable. In the past, the implementation of network-online.target has been less correct on Ubuntu, *because* ipv6 RA was handled asynchronously, and this target did not block waiting to

[Bug 1764216] Re: [regression] Unreadable stack traces since upgrading to gjs 1.52.1 and glib 2.56.1-2ubuntu1

'regression-update' is for regressions introduced in the -updates pocket of a stable release; removing the tag ** Tags removed: regression-update -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.

[Bug 1763878] Re: [regression] Many programs crashing at exit with assert failure: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertion `hash_table->live_entries == 0' failed. Called

** Tags removed: regression-update -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1763878 Title: [regression] Many programs crashing at exit with assert failure:

[Bug 1760598] Re: I/O Error after clicking "reboot now" - Ubuntu font missing from casper shutdown

** Changed in: ubiquity (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1760598 Title: I/O Error after clicking "reboot now" - Ubuntu

[Bug 1762899] Re: /etc/resolv.conf empty after upgrading from 16.04 to 18.40

I think we need to handle this via removal of the resolvconf package on upgrade. Removal (not purge) seems to be sufficient. Dimitri, is there any remaining reason for systemd to not conflict: with resolvconf? ** Changed in: resolvconf (Ubuntu) Status: Incomplete => Triaged ** Changed

[Bug 1761630] [NEW] journald takes over /dev/log in bionic, impacts usability of syslog querying

Public bug reported: In bionic, /dev/log is now owned by systemd-journald. $ sudo fuser -v /dev/log USERPID ACCESS COMMAND /run/systemd/journal/dev-log: root 1 F systemd root628 F systemd-journal $

[Bug 1717015] Re: libc resolver stops searching domain search list after getting back NSEC record

** Changed in: systemd (Ubuntu) Status: Expired => Won't Fix ** Changed in: systemd (Ubuntu) Status: Won't Fix => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu.

[Bug 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created

This is not an SRU-appropriate change and should not have been accepted into artful. Please revert this ASAP for artful. Marking 'wontfix' for xenial. ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Won't Fix -- You received this bug notification because you are a member

[Bug 1758438] [NEW] systemd can't be removed from a chroot

Public bug reported: The systemd package has the following code in its prerm: if [ "$1" = "remove" ] && [ -d /run/systemd/system ]; then echo "systemd is the active init system, please switch to another before removing systemd." exit 1 fi However, /run/systemd/system will exist even in

[Bug 1709688] Re: systemd package can't be removed from a chroot

The error message is correct, systemd is always the active init system and it will break your system to remove this package. It is not a bug in systemd that it prevents you from breaking your system and rendering it unbootable. ** Changed in: systemd (Ubuntu) Status: Confirmed => Triaged

[Bug 1758163] Re: Please remove xchat-gnome from Ubuntu (again)

Removing packages from bionic: xchat-gnome 1:0.30.0~git20141005.816798-0ubuntu12 in bionic xchat-gnome 1:0.30.0~git20141005.816798-0ubuntu12 in bionic amd64 xchat-gnome 1:0.30.0~git20141005.816798-0ubuntu12 in bionic arm64 xchat-gnome

[Bug 1662137] Re: 16.04 recovery shell works only for two minutes

** Also affects: systemd (Ubuntu Bionic) Importance: High Assignee: Dimitri John Ledkov (xnox) Status: Confirmed ** Tags removed: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu.

[Bug 1755949] Re: process-cpp FTBFS in bionic

Removing packages from bionic: dbus-cpp 5.0.0+18.04.20171031-1 in bionic dbus-cpp-bin 5.0.0+18.04.20171031-1 in bionic amd64 dbus-cpp-bin 5.0.0+18.04.20171031-1 in bionic arm64 dbus-cpp-bin 5.0.0+18.04.20171031-1 in bionic armhf

[Bug 1755949] Re: process-cpp FTBFS in bionic

Removing packages from bionic: process-cpp 3.0.1-0ubuntu5 in bionic libprocess-cpp-dev 3.0.1-0ubuntu5 in bionic amd64 libprocess-cpp-dev 3.0.1-0ubuntu5 in bionic arm64 libprocess-cpp-dev 3.0.1-0ubuntu5 in bionic armhf

[Bug 1755949] Re: process-cpp FTBFS in bionic

** No longer affects: mediascanner2 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1755949 Title: process-cpp FTBFS in bionic To manage notifications about this bug go

[Bug 1755949] [NEW] process-cpp FTBFS in bionic

Public bug reported: process-cpp fails to build with an inscrutable error from cmake about failing to find pthreads: Determining if the function pthread_create exists in the pthreads failed with the following output: Change Dir: /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp Run Build

[Bug 1753395] Re: Upgrade failure: dependency problems prevent configuration of gnome-session:

The regression-update tag is for regressions in SRUs. Removing this tag. You appear to be trying to install packages from bionic-proposed. This is unsupported. ** Tags removed: regression-update -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is

[Bug 1752722] Re: systemd 237 reports incorrect state when drop-in present

upstream fix: https://github.com/systemd/systemd/pull/8330 ** Changed in: systemd (Ubuntu) Status: Confirmed => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Also affects: systemd (Ubuntu Bionic) Importance: High Status: Triaged -- You received

[Bug 1751252] Re: ubiquity crashed with signal 5 in _XEventsQueued()

** Also affects: glib2.0 (Ubuntu Bionic) Importance: Medium Status: New ** Also affects: ubiquity (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: ubiquity (Ubuntu Bionic) Status: New => Triaged ** Changed in: ubiquity (Ubuntu Bionic) Importance:

[Bug 1532508] Update Released

The verification of the Stable Release Update for unity has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a

[Bug 1392012] Re: [MIR] libteam

Override component to main libteam 1.26-1 in bionic: universe/misc -> main libteam-dev 1.26-1 in bionic amd64: universe/libdevel/optional/100% -> main libteam-dev 1.26-1 in bionic arm64: universe/libdevel/optional/100% -> main libteam-dev 1.26-1 in bionic armhf: universe/libdevel/optional/100% ->

[Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR

** Also affects: glibc (Ubuntu Bionic) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Bionic) Importance: High Status: Invalid ** Also affects: systemd (Ubuntu Bionic) Importance: High Status: Triaged -- You received this bug notification

[Bug 1713803] Re: replacement of resolvconf with systemd needs integration

fetchmail integrates with resolvconf via /etc/resolvconf/update- libc.d/fetchmail; I think this warrants another look. ** Changed in: fetchmail (Ubuntu) Status: Won't Fix => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to

[Bug 1746765] Re: systemd FTBFS on arm64

** Bug watch added: Sourceware.org Bugzilla #22764 https://sourceware.org/bugzilla/show_bug.cgi?id=22764 ** Also affects: binutils via https://sourceware.org/bugzilla/show_bug.cgi?id=22764 Importance: Unknown Status: Unknown -- You received this bug notification because you are

[Bug 1746765] Re: systemd FTBFS on arm64

** Also affects: binutils (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gnu-efi (Ubuntu Bionic) Importance: Undecided Assignee: Julian Andres Klode (juliank) Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status:

[Bug 1737250] Re: systemd-resolved returns only short hostname when PTR record of local IP is requested

*** This bug is a duplicate of bug 1739672 *** https://bugs.launchpad.net/bugs/1739672 ** This bug has been marked a duplicate of bug 1739672 Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR -- You received this bug

[Bug 1676115] Re: systemd-resolved spams the system log with useless “Processing query...” messages

> This was fixed upstream in v233 by downgrading this message from log_info to log_debug: So this is fixed in Ubuntu 17.10 and later. ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop

[Bug 1661716] Re: Domain names not resolving on bootup

There were a number of bugs reported in the 16.10 timeframe about this issue. I believe these have all been resolved as of Ubuntu 17.04, so am closing this bug fix-released. If you are still seeing issues with systemd-resolved in a currently supported release of Ubuntu, please reopen this

[Bug 1650877] Re: systemd-resolved: resolve call failed: DNSSEC validation failed: failed-auxiliary

*** This bug is a duplicate of bug 1682499 *** https://bugs.launchpad.net/bugs/1682499 ** This bug has been marked a duplicate of bug 1682499 Disable DNSSEC by default -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in

[Bug 1663031] Re: cannot resolve www.facebook.com

*** This bug is a duplicate of bug 1682499 *** https://bugs.launchpad.net/bugs/1682499 ** This bug is no longer a duplicate of bug 1650877 systemd-resolved: resolve call failed: DNSSEC validation failed: failed-auxiliary ** This bug has been marked a duplicate of bug 1682499 Disable

[Bug 1659520] Re: openvpn network manager plugin dns server settings do not take effect in 16.10

I believe this was fixed in Ubuntu 17.04 and later. If you are still experiencing this problem with a currently supported Ubuntu release, please reopen this report. ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member

[Bug 1653495] Re: systemd-resolved breaks Steam

*** This bug is a duplicate of bug 1647031 *** https://bugs.launchpad.net/bugs/1647031 ** This bug has been marked a duplicate of bug 1647031 systemd-resolved’s 127.0.0.53 server does not follow CNAME records -- You received this bug notification because you are a member of Ubuntu

[Bug 1742310] Re: No network in recovery mode (systemd-resolved does not start)

** Package changed: systemd (Ubuntu) => friendly-recovery (Ubuntu) ** Changed in: friendly-recovery (Ubuntu) Importance: Undecided => High ** Changed in: friendly-recovery (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop

[Bug 1668296] Re: not failing back to IPv4 when AAAA returns SERVFAIL

I cannot reproduce this with the libnss-resolve in Ubuntu 17.04 or 17.10. The original problem was reported with systemd 231; 17.04 shipped with 232. It is possible that this has been fixed in systemd upstream (the linked upstream bug has been closed), or it's possible that the DNS configuration

[Bug 1731211] Re: systemd breaks interface configuration due to late resolv.conf

What exactly are the contents of /etc/network/interfaces.d/vlan0? I would not normally expect dnsmasq to be started as part of the network interface configuration via ifupdown. If there is a reason to configure it this way, then /lib/systemd/system/networking.service would need to be changed to

[Bug 1730744] Re: sudo is slow (10 seconds) when hostname is not resolvable

*** This bug is a duplicate of bug 1739672 *** https://bugs.launchpad.net/bugs/1739672 ** This bug has been marked a duplicate of bug 1739672 Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR -- You received this bug

[Bug 1731522] Re: systemd-resolved does not listen on TCP port, cannot serve large records (Cannot ping pod51041.outlook.com but can dig.)

According to https://github.com/systemd/systemd/issues/6520 this can be worked around by setting DNSStubListener=yes in /etc/systemd/resolved.conf. This is disabled by default due to . It is not ideal to have systemd-resolved conflict with other

[Bug 1729194] Re: Systemd-Resolvd Forgets to Resolv Request

127.0.1.1 is not the address of systemd-resolved, as you noted; it's the address used by dnsmasq. It sounds like your network-manager config is pointing to dnsmasq, which is no longer the default in 17.10, and should have been dropped from your config on upgrade from 16.10 to 17.04. Can you

[Bug 1738375] Re: Resolving DNS entry, answer too big to handle

$ ping www.ziggogo.tv PING www.ziggogo.tv(2001:730:3400:8000::14 (2001:730:3400:8000::14)) 56 data bytes 64 bytes from 2001:730:3400:8000::14 (2001:730:3400:8000::14): icmp_seq=1 ttl=52 time=176 ms 64 bytes from 2001:730:3400:8000::14 (2001:730:3400:8000::14): icmp_seq=2 ttl=52 time=178 ms ^C

[Bug 1632681] Re: SonicWall NetExteder broken by new nsswitch.conf configuration

In Ubuntu 17.10 and later, this is resolved by removing libnss-resolve from the default install and only using systemd-resolved via resolv.conf. ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu

[Bug 1628287] Re: systemd-resolved crashed with SIGABRT in log_assert_failed()

Thank you for reporting this issue and helping to improve Ubuntu. This bug was reported against the version of systemd in Ubuntu 16.10, which has reached End Of Life. As such, we will not be fixing bugs in this version of the package. If this problem is reproducible on later supported versions of

<    1   2   3   4   5   6   7   8   9   10   >