[Bug 1971739] Re: [MIR] iwd
Using IWD wouldn't obviate the use of wpa_supplicant, since the latter is used for more than Wi-Fi security. 802.1x authentication can be used for physical networks as well as VPNs and other things, so NetworkManager will use wpa_supplicant for those scenarios. IWD is pretty much only for Wi-Fi, so you'd wind up needing both in main if you decided to go down the road of using IWD. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971739 Title: [MIR] iwd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iwd/+bug/1971739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968228] Re: RTD collision with opcache
** Bug watch added: bugs.php.net/ #79603 http://bugs.php.net/bug.php?id=79603 ** Also affects: php via http://bugs.php.net/bug.php?id=79603 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/1968228 Title: RTD collision with opcache To manage notifications about this bug go to: https://bugs.launchpad.net/php/+bug/1968228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966800] Re: systemd locks up due to incorrect handling of time zone changes
** Bug watch added: Red Hat Bugzilla #1941335 https://bugzilla.redhat.com/show_bug.cgi?id=1941335 ** Also affects: systemd (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1941335 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/1966800 Title: systemd locks up due to incorrect handling of time zone changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867775] Re: Sync pagure 5.8.1+dfsg-3 (universe) from Debian sid (main)
Thanks Jeremy! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867775 Title: Sync pagure 5.8.1+dfsg-3 (universe) from Debian sid (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pagure/+bug/1867775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867775] [NEW] Sync pagure 5.8.1+dfsg-3 (universe) from Debian sid (main)
Public bug reported: Please sync pagure 5.8.1+dfsg-3 (universe) from Debian sid (main) Changelog entries since current focal version 5.8.1+dfsg-1: pagure (5.8.1+dfsg-3) unstable; urgency=medium * Correct mistake and make sure we create HOME under /var/lib/pagure. In my last commit, I forgot to update the postinst files and make sure that the new HOME is /var/lib/pagure, and not /srv/pagure. * Add libjs-highlight.js as a dependency. This was a thinko; the dependency should have been added since the beginning. * Perform user/group replacement on service files on dh_installsystemd. There is no reason for us to keep various postinst scripts around just to perform the user/group adjustment on systemd service files when we can easily do that under the dh_installsystemd rule. -- Sergio Durigan Junior Wed, 04 Mar 2020 21:31:12 -0500 pagure (5.8.1+dfsg-2) unstable; urgency=medium * Mention pagure/utils.py in d/copyright. * Remove override_dh_installinit from d/rules. * Mark test B-D as "!nocheck". Also, reorganize a few dependencies, and add "python3-bs4" to the list. * Add Vcs-* fields. * Depend on httpd-wsgi3, instead of the Apache-specific package. Thanks to Michael Fladischer (Closes: #952708) * Depend on mariadb | postgres | sqlite3. * Enable the testsuite, but make it always pass, for now. The testsuite unfortunately contains several problems that need to be fixed before we are able to run it "for real". Hopefully, these problems will all be addressed in the next release. * Use /var/lib/pagure instead of /srv/pagure as HOME. This is needed because Debian Policy explicitly says that /srv should be reserved to the user, and no package must install files there. -- Sergio Durigan Junior Wed, 04 Mar 2020 12:26:22 -0500 ** Affects: pagure (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867775 Title: Sync pagure 5.8.1+dfsg-3 (universe) from Debian sid (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pagure/+bug/1867775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824245] Re: Can't create a bootable disk by doing image creation on a loop device
cjwatson, I've updated the patch accordingly... ** Patch added: "Patch to debian packaging to fix this (v2)" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1824245/+attachment/5289052/+files/grub2-ubuntu-pkg-support-partitioned-loops-v2.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824245 Title: Can't create a bootable disk by doing image creation on a loop device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1824245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824245] Re: Can't create a bootable disk by doing image creation on a loop device
cyphermox, if this helps, I've created a patch that directly applies on top of the existing grub2 sources reconstructed with `dpkg-source -x` that I've tested locally to work. ** Patch added: "Patch to debian packaging to fix this" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1824245/+attachment/5281704/+files/grub2-ubuntu-pkg-support-partitioned-loops.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824245 Title: Can't create a bootable disk by doing image creation on a loop device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1824245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824245] Re: Can't create a bootable disk by doing image creation on a loop device
cyphermox, could you please backport the fix for Ubuntu 16.04? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824245 Title: Can't create a bootable disk by doing image creation on a loop device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1824245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824245] Re: Can't create a bootable disk by doing image creation on a loop device
Bump? What about Ubuntu 16.04? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824245 Title: Can't create a bootable disk by doing image creation on a loop device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1824245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824245] Re: Can't create a bootable disk by doing image creation on a loop device
I've verified locally that this does fix my issue when I patch grub myself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824245 Title: Can't create a bootable disk by doing image creation on a loop device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1824245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824245] Re: Can't create a bootable disk by doing image creation on a loop device
I'll note that this configuration is loop images on a disk that was created as a disk image file mounted as a loop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824245 Title: Can't create a bootable disk by doing image creation on a loop device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1824245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824245] [NEW] Can't create a bootable disk by doing image creation on a loop device
Public bug reported:
I'm trying to create a bootable disk image using an image file mounted
as a loop device with partx.
While the grub-install succeeds, when I attempt to boot in KVM or
VMware, it fails with the following error:
error: no such device: 92136917-76ff-4115-9eed-9caa20529682.
Entering rescue mode...
grub rescue> _
The grub boot configuration entry my process creates is pretty simple:
"""
menuentry 'Ubuntu LTS (v16.04)' {
search --set=root --no-floppy --fs-uuid 92136917-76ff-4115-9eed-9caa20529682
loopback loop /images/16.04.img
linux (loop)/vmlinuz root=UUID=92136917-76ff-4115-9eed-9caa20529682
rootdelay=120 rw quiet panic=5 vga=791 consoleblank=0 max_loop=256 splash
loop=/images/16.04.img net.ifnames=0 nomdmonisw nomdmonddf bootdegraded=true
audit=1
initrd (loop)/initrd.img
}
"""
I think it's because this commit is missing from Ubuntu 16.04's grub2
package:
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=35f2d96c0d68772c831952b2ee4eba6519d6ea1b
Could this get fixed in some way?
I'm using Ubuntu 16.04.6. The current grub2 package version is
"2.02~beta2-36ubuntu3.21".
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824245
Title:
Can't create a bootable disk by doing image creation on a loop device
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1824245/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824245] Re: Can't create a bootable disk by doing image creation on a loop device
I'll also note that it sometimes works with UEFI, but I've never gotten it to work with BIOS... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824245 Title: Can't create a bootable disk by doing image creation on a loop device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1824245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776761] Re: targetcli aborts with the error message "NameError: name 'readline' is not defined" when running in interactive shell mode
** Also affects: python-configshell-fb (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901484 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/1776761 Title: targetcli aborts with the error message "NameError: name 'readline' is not defined" when running in interactive shell mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-configshell-fb/+bug/1776761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756566] Re: FFe: Sync rpm 4.14.1+dfsg1-2 (universe) from Debian sid (main)
Sweet, thanks Adam! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756566 Title: FFe: Sync rpm 4.14.1+dfsg1-2 (universe) from Debian sid (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpm/+bug/1756566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756566] [NEW] FFe: Sync rpm 4.14.1+dfsg1-2 (universe) from Debian sid (main)
Public bug reported: Please sync rpm 4.14.1+dfsg1-2 (universe) from Debian sid (main) Explanation of FeatureFreeze exception: RPM v4.14 introduces support for packages compressed with zstd, and distributions are starting to consider/use it. However, for Ubuntu to be able to be useful for building packages targeting these distributions, RPM needs to have zstd support enabled. RPM 4.14.1 is a bugfix release on top of RPM 4.14.0 including several bug fixes for package builds and processing large packages. More details on RPM 4.14.1: http://rpm.org/wiki/Releases/4.14.1 Changelog entries since current bionic version 4.14.0+dfsg1-2: rpm (4.14.1+dfsg1-2) unstable; urgency=medium * Build with libzstd-dev (Closes: #892759). -- Michal Čihař Wed, 14 Mar 2018 11:34:01 +0100 rpm (4.14.1+dfsg1-1) unstable; urgency=medium * New upstream release. * Remove old package replaces/conflicts from debian/control. * Bump standards to 4.1.3. -- Michal Čihař Tue, 23 Jan 2018 13:24:30 +0100 ** Affects: rpm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756566 Title: FFe: Sync rpm 4.14.1+dfsg1-2 (universe) from Debian sid (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpm/+bug/1756566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750382] Re: please roll back to 0.10.x stable branch or confirm use of 0.11.x for bionic
> I'm also trying to get some clarifications around why fedora 26/27 ship 0.10.X vs 0.11.X, I wonder if it was just the simplest thing to do with the document portal move in 0.11.X. If I get any reasoning I'll update this bug. Fedora 26 and 27 started out with flatpak 0.9.x, so they transitioned to 0.10.x in the updates process. Fedora 28 will ship with flatpak 0.11.x, and will likely transition to 0.12.x post-GA if it doesn't release before GA in May. There is a switch in 0.10.4 to disable building the desktop portal in flatpak itself (--disable-document-portal) so that you can use xdg- desktop-portal 0.10's implementation. As the maintainer of the Flatpak stack in Mageia, I shipped 0.9.x in Mageia 6 GA and will be shipping an update to 0.10.x to Mageia 6 shortly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750382 Title: please roll back to 0.10.x stable branch or confirm use of 0.11.x for bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1750382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292324] Re: Support non-root X
** Bug watch added: Red Hat Bugzilla #1078808 https://bugzilla.redhat.com/show_bug.cgi?id=1078808 ** Also affects: lightdm (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1078808 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/1292324 Title: Support non-root X To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1292324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641121] [NEW] Switch packaging to "3.0 (quilt)"
Public bug reported: The packaging for Mir is in the legacy 1.0 format. Please switch to "3.0 (quilt)" format. Thanks in advance. ** Affects: mir (Ubuntu) Importance: Undecided Status: New ** Tags: packaging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641121 Title: Switch packaging to "3.0 (quilt)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1641121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573275] Re: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom'
Yes. Actually, it might be more useful to diff between 15.10[1] and 16.04[2]. That lets you see all the differences that were required to get it working. [1]: https://build.opensuse.org/project/prjconf/Ubuntu:15.10 [2]: https://build.opensuse.org/project/prjconf/Ubuntu:16.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573275 Title: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573275] Re: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom'
Paul: Unfortunately not, but you can see how the configuration is set up on build.opensuse.org[1]. Details about the prjconf format is available on the openSUSE Wiki[2]. [1]: https://build.opensuse.org/project/prjconf/Ubuntu:16.04 [2]: https://en.opensuse.org/openSUSE:Build_Service_prjconf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573275 Title: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573275] Re: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom'
This is no longer a problem on the Open Build Service, as we're now ignoring the ifupdown dependency from upstart. Thus, Ubuntu 16.04 LTS build environments now work, as seen by this example[1]. [1]: https://build.opensuse.org/package/live_build_log/home:Pharaoh_Atem:u1604_stuff /php-libvirt/xUbuntu_16.04/x86_64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573275 Title: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573275] Re: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom'
** Package changed: ubuntu => ifupdown (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573275 Title: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573275] Re: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom'
Hey all, I'm the one who discovered the problem. As indicated in my LP profile, I can be reached on Freenode as "Conan_Kudo", "Pharaoh_Atem", or "Son_Goku". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573275 Title: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1573275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573275] Re: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom'
Err, because LP is awesome and I can't edit my own comment, I'm primarily available through Pharaoh_Atem (my workstation) or Son_Goku (my laptop). Alternatively, I can be reached by email. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573275 Title: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1573275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1560578] Re: /usr/bin/lldb-server symlink to /usr/bin/lldb-server-3.8 is missing
** Description changed: Applications that expect the unversioned binary for lldb-server to exist in /usr/bin will be bitterly disappointed, as the lldb package does not - provide that currently (though it is there for lldb). + provide that currently (though it provides /usr/bin/lldb). - Please add the missing symlink, otherwise lldb itself can't debug + Please add the missing symlink, otherwise lldb itself can't function properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1560578 Title: /usr/bin/lldb-server symlink to /usr/bin/lldb-server-3.8 is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-defaults/+bug/1560578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1560578] [NEW] /usr/bin/lldb-server symlink to /usr/bin/lldb-server-3.8 is missing
Public bug reported: Applications that expect the unversioned binary for lldb-server to exist in /usr/bin will be bitterly disappointed, as the lldb package does not provide that currently (though it is there for lldb). Please add the missing symlink, otherwise lldb itself can't debug properly. ** Affects: llvm-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: defaults lldb symlinks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1560578 Title: /usr/bin/lldb-server symlink to /usr/bin/lldb-server-3.8 is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-defaults/+bug/1560578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1391192] Re: php5-fpm init(.d) scripts don't report status
Could you please provide more information? Please report back at least the version of php5-fpm package installed, which version of Ubuntu you were using, and which architecture this was running on. ** Changed in: php5 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1391192 Title: php5-fpm init(.d) scripts don't report status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1391192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537757] Re: PHP modules removed when upgrading apache2 to 2.2.11-2ubuntu2.6
This issue is quite old, and I cannot reproduce it on current Ubuntu systems. If this is still an issue, please re-open and set the status to "New" with details on what the problem is. ** Changed in: php5 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/537757 Title: PHP modules removed when upgrading apache2 to 2.2.11-2ubuntu2.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/537757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1083824] Re: php5 UTF-8 bug
There's been no information received for several years on this issue. If this is still a problem, please provide the requested information and set it back to "New". ** Changed in: php5 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1083824 Title: php5 UTF-8 bug To manage notifications about this bug go to: https://bugs.launchpad.net/php-fpm/+bug/1083824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1059272] Re: php5-fpm init.d script does not return any output when php5-fpm is started or stopped
This is not a valid bug anymore (if it ever was), as with the move to systemd, sysv calls redirect to systemd, and systemd captures the information in the journal, which can be viewed by looking at /var/log/syslog, using "journalctl -u php5-fpm" (php7.0-fpm for Xenial), or any other mechanism for reading the syslog/journal. ** Changed in: php5 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059272 Title: php5-fpm init.d script does not return any output when php5-fpm is started or stopped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1059272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548442] Re: php7.0: segmentation fault running twig test suite
After working with Remi Collet to track down the issue, we've identified
the problem to be with PCRE support, specifically with PCRE JIT. We
reached this suspicion after Remi was able to run the tests successfully
with his PHP7 SCL for Fedora 23 just fine with the JIT enabled, but it
broke on CentOS 7.2 and Ubuntu Xenial.
I tested on Ubuntu Xenial php7.0-7.0.3-9 (from xenial-proposed) and
CentOS 7.2 php70-php-7.0.3-1.el7.remi SCL (from Remi's repository).
On both systems, I did the following:
0. Installed the required php7 packages.
** Ubuntu Xenial: php7.0-{cli,json,xml,mbstring}
** CentOS 7.2 php70 scl: php70-php-{cli,json,xml,mbstring}
1. Downloaded Twig 1.24.0 tarball from GitHub
(https://github.com/twigphp/Twig/archive/v1.24.0/Twig-1.24.0.tar.gz)
2. Untarred it and changed into the new Twig-1.24.0 directory.
3. Downloaded composer.phar ( https://getcomposer.org/composer.phar ) and
phpunit.phar ( https://phar.phpunit.de/phpunit.phar )
4. Run composer to set up the Twig sources.
** Ubuntu Xenial: php7.0 composer.phar install
** CentOS 7.2 php70 scl: php70 composer.phar install
5. Run phpunit on the Twig sources.
** Ubuntu Xenial: php7.0 phpunit.phar -v
** CentOS 7.2 php70 scl: php70 phpunit.phar -v
With the default configuration, these both fail with a segmentation
fault.
However, if I add "pcre.jit=0" to php.ini (/etc/php/7.0/cli/php.ini on
Ubuntu Xenial, /etc/opt/remi/php70/php.ini for CentOS 7.2 php70 scl) and
re-run the tests, they pass completely.
There are two solutions here:
1) Identify what Fedora's pcre package has that fixes it vs the Debian/Ubuntu
package (Fedora sources available here:
http://pkgs.fedoraproject.org/cgit/rpms/pcre.git/tree/?h=f23), as both are
using pcre 8.38, though I don't know why the soversion differs...
2) Add "pcre.jit=0" to the php configuration.
I don't consider solution 2 to be valid unless we're okay with disabling
PCRE JIT across the board.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1548442
Title:
php7.0: segmentation fault running twig test suite
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1548442/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547738] Re: Request: Sync with Debian to get upstream fixes for autopkgtests
It looks good to me, but I'm curious as to why libmcrypt isn't in main (and consequently able to be used as a PHP build dependency)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547738 Title: Request: Sync with Debian to get upstream fixes for autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1547738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547738] Re: Request: Sync with Debian to get upstream fixes for autopkgtests
Ondřej seems to have made some fixes and the current git HEAD is at php7.0-7.0.3-7, so please pull that in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547738 Title: Request: Sync with Debian to get upstream fixes for autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1547738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547738] Re: Request: Sync with Debian to get upstream fixes for autopkgtests
My patches have been merged into the git master for pkg-php[1] for Debian. Please pull in the current git master (noted as git hash: 65566bc2c31fd96f29c1327cd42c0e86682b3a52). This is the php7.0-7.0.3-6 package with everything properly generated. [1]: http://anonscm.debian.org/cgit/pkg-php/php.git/log/?h=master-7.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547738 Title: Request: Sync with Debian to get upstream fixes for autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1547738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547738] Re: Request: Sync with Debian to get upstream fixes for autopkgtests
The patches above are the ones I've submitted to Ondřej Surý for Debian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547738 Title: Request: Sync with Debian to get upstream fixes for autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1547738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547738] [NEW] Request: Sync with Debian to get upstream fixes for autopkgtests
Public bug reported: I've submitted patches to Ondřej Surý to fix the failing tests for the php7.0 package. Please sync with the version that will be released with these patches, so that Ubuntu will not need to carry a delta for test fixes. The patches have not yet been applied, and I will notify via this bug report when they have. ** Affects: php7.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547738 Title: Request: Sync with Debian to get upstream fixes for autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1547738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547738] Re: Request: Sync with Debian to get upstream fixes for autopkgtests
** Patch added: "Patch that has regenerated tests for the package" https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1547738/+attachment/4576062/+files/0003-Regenerate-d-tests.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547738 Title: Request: Sync with Debian to get upstream fixes for autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1547738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547738] Re: Request: Sync with Debian to get upstream fixes for autopkgtests
** Patch added: "Patch to fix the tests" https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1547738/+attachment/4576061/+files/0002-Fix-the-tests-to-pass-and-handle-conditions-that-sho.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547738 Title: Request: Sync with Debian to get upstream fixes for autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1547738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547738] Re: Request: Sync with Debian to get upstream fixes for autopkgtests
** Patch added: "Patch to ensure php-fpm httpd config is properly installed" https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1547738/+attachment/4576060/+files/0001-Ensure-php-fpm-apache-httpd-config-is-prepared-and-i.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547738 Title: Request: Sync with Debian to get upstream fixes for autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1547738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267255] Re: [MIR] php5 (php5-fpm binary)
@Robie: I can certainly take a look through them. Where can I see them? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267255 Title: [MIR] php5 (php5-fpm binary) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1267255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267255] Re: [MIR] php5 (php5-fpm binary)
Of course, I realize it means that for httpd, it would need to have mod_proxy_fcgi enabled by default for the php-fpm configuration I contributed to be useful in an out-of-the-box scenario. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267255 Title: [MIR] php5 (php5-fpm binary) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1267255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267255] Re: [MIR] php5 (php5-fpm binary)
So, I'd like to chime in here a bit. As Ondřej mentioned earlier, php-fpm is known to be a more secure alternative to mod_php, and is recommended for secure setups. I recently contributed a decent default configuration for php-fpm for PHP 7.0, and I would support flipping libapache2-mod-php7.0 to universe and keep php7.0-fpm in main. Critically, php-fpm can be used with any web server that supports FastCGI, whereas mod_php is Apache httpd specific. There is, of course, php-cgi, but it isn't recommended either, and I would suggest that it should be in universe as well. I don't pretend to know the difficulty of maintaining the PHP stack, but I think that perhaps moving these two particular methods of using PHP from main to universe in exchange for php-fpm should be considered. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267255 Title: [MIR] php5 (php5-fpm binary) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1267255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1325142] Re: failure to update libpam-systemd in 14.04 due to missing logind init script
I'm also being bitten by this issue. I can't create chroots or VM images based on trusty due to polkit-1 bringing in libpam-systemd, which breaks as other commenters have described earlier... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325142 Title: failure to update libpam-systemd in 14.04 due to missing logind init script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1325142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1325142] Re: failure to update libpam-systemd in 14.04 due to missing logind init script
This is very clearly not fixed on Ubuntu trusty, and the changelog of the package in trusty does not indicate any fix was applied. Please remove the incorrect designation of "Fix Committed" for trusty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325142 Title: failure to update libpam-systemd in 14.04 due to missing logind init script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1325142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569803] Re: upgrade 8.04LTS to 10.4LTS RC results in no keyboard available
A fresh installation of Ubuntu 10.04 Beta 2 or RC will result in this too. It worked in Beta 1. -- upgrade 8.04LTS to 10.4LTS RC results in no keyboard available https://bugs.launchpad.net/bugs/569803 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 412647] Re: Firefox is not able to play mp4 tags
** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=422540 Importance: Unknown Status: Unknown -- Firefox is not able to play mp4 tags https://bugs.launchpad.net/bugs/412647 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
Re: [Bug 284408] Re: r3xx Hardware does not work with fglrx [EPR#257839]
On Sun, Mar 22, 2009 at 5:35 AM, F-3582 wrote: > I read that on Heise a month ago, just prior to those announcements that > AMD were to drop support for those chips entirely. Then it looks like we will be leaving them out cold as far as OpenGL 2.1 support then. None of the existing FOSS drivers support OpenGL 2.1, and as far as I know, everybody is focused on bringing Gallium3D in to offer that support, but it seems it won't be ready before April distro release. Really, that leaves two options, either use Git Mesa code with Gallium3D and hope for the best, or hold back Xserver to version 1.5, which I doubt will happen. However, something DOES need to be done about this. -- r3xx Hardware does not work with fglrx [EPR#257839] https://bugs.launchpad.net/bugs/284408 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
Re: [Bug 284408] Re: r3xx Hardware does not work with fglrx [EPR#257839]
I would suggest that if possible we could hold in catalyst 9.3 for r300-r500 support, since those were dropped in 9.4. On Wed, Mar 18, 2009 at 5:06 PM, Hanno Meyer-Thurow wrote: > I wonder if it is too hard to do name-version packages like for nvidia > packages. :) > See: > http://packages.ubuntu.com/search?keywords=nvidia&searchon=names&suite=intrepid§ion=all > > -- > r3xx Hardware does not work with fglrx [EPR#257839] > https://bugs.launchpad.net/bugs/284408 > You received this bug notification because you are a direct subscriber > of the bug. > -- r3xx Hardware does not work with fglrx [EPR#257839] https://bugs.launchpad.net/bugs/284408 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
Re: [Bug 284408] Re: r3xx Hardware does not work with fglrx [EPR#257839]
On Tue, Feb 24, 2009 at 2:10 AM, Noiano wrote: > stomlin wrote: > > 9.2 fixed the problem for me. I have a Asus z80k with a mobile 9700 pro > (rv350) > > I installed them manually using the install method here... > http://wiki.cchtml.com/index.php/Ubuntu_Intrepid_Installation_Guide > > Hooorraaay! > > Everything is ok also with ati radeon 9500 pro. One little problem: the > intial login screen has a resolution of 1600x1200 which is out of the > range of my lcd screen. How do I set as default resolution 1024x768? > > thanks > > -- > r3xx Hardware does not work with fglrx [EPR#257839] > https://bugs.launchpad.net/bugs/284408 > You received this bug notification because you are a direct subscriber > of the bug. > Make a subsection in the Screen section and insert only modes that you want it to be able to access, setting it from highest to lowest. Alternatively, use aticonfig to do it. -- r3xx Hardware does not work with fglrx [EPR#257839] https://bugs.launchpad.net/bugs/284408 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 284408] Re: r3xx Hardware does not work with fglrx [EPR#257839]
Besides, Catalyst 9.2 finally fixes this issue, however, it will not work without a screen configuration set in xorg.conf. So in a future Ubuntu update, a screen configuration MUST be saved into xorg.conf for it to work... -- r3xx Hardware does not work with fglrx [EPR#257839] https://bugs.launchpad.net/bugs/284408 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 284408] Re: r3xx Hardware does not work with fglrx [EPR#257839]
Nope. Its a target of stupidity at most, and target of problems at least. None of the FOSS drivers support OpenGL 2(.1) or OpenGL 3.0. The ATI FOSS drivers do not support FBOs, which are needed by quite a few OpenGL-based games, especially emulators of game consoles. If you can bring up full OpenGL 2.1 + GLSL support by Jaunty for the FOSS driver, THEN it would be a target of opportunity. Otherwise you are just damning ATI card users. Besides, it seems that the FOSS driver is horribly unoptimized on OpenGL with Wine. fglrx has wonderful OpenGL/WineD3D performance. -- r3xx Hardware does not work with fglrx [EPR#257839] https://bugs.launchpad.net/bugs/284408 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
