[Bug 1725322] Re: kernel 4.4.0.97.102 breaks DFS
** Bug watch added: Linux Kernel Bug Tracker #196891 https://bugzilla.kernel.org/show_bug.cgi?id=196891 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=196891 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/1725322 Title: kernel 4.4.0.97.102 breaks DFS To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1725322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1706284] Re: sssd fails to Update PTR if any A record update fails.
Tested sssd-1.13.4-1ubuntu1.8 Result: PASS - PTR update is attempted after response from previous A record update returned non-zero and PTR is created in AD. --- (Wed Sep 27 07:03:21 2017) [sssd[be[TESTDOMAIN.TLD]]] [be_nsupdate_create_fwd_msg] (0x0400): -- Begin nsupdate message -- Reply from update query: ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 22909 (Wed Sep 27 07:03:21 2017) [sssd[be[TESTDOMAIN.TLD]]] [child_sig_handler] (0x0020): child [8280] failed with status [2]. -- (Wed Sep 27 07:03:21 2017) [sssd[be[TESTDOMAIN.TLD]]] [be_nsupdate_create_ptr_msg] (0x0400): -- Begin nsupdate message -- Reply from update query: ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 27361 ;; flags: qr; ZONE: 1, PREREQ: 0, UPDATE: 1, ADDITIONAL: 1 ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial ** Tags removed: verification-needed xenial ** Tags added: verification ** Tags removed: verification ** Tags added: verification-needed xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706284 Title: sssd fails to Update PTR if any A record update fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1706284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1706284] Re: sssd fails to Update PTR if any A record update fails.
** Changed in: sssd (Ubuntu) Assignee: Keith Ward (kward) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706284 Title: sssd fails to Update PTR if any A record update fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1706284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430143] Re: sss_obfuscate breaks /etc/sssd/sssd.conf
I'm not able to reproduce this in the current Xenial release, which Ubuntu Release / Package version did this issue occur in? ** Changed in: sssd (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/1430143 Title: sss_obfuscate breaks /etc/sssd/sssd.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1430143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707133] Re: crash periscope
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: firefox (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/1707133 Title: crash periscope To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1707133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707198] Re: no idea
>From the looks of the output of the log files you attached it appears that a copy of windows is present on that machine, that copy of windows has been put into hibernate mode, and as a result grub-installer will refuse to mount those partitions. Please log back into the windows install on that machine and shut the Operating System down normally before trying again. Unfortunately, we are unable to work further on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: grub-installer (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/1707198 Title: no idea To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1707198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707167] [NEW] Kernel CIFS Module ignores USER_SESSION_DELETED PDUs and holds onto dead sessions.
Public bug reported: #Summary The cifs kernel module currently ignores the nt_status USER_SESSION_DELETED PDUs sent to it from remote SMB2+ peers and holds onto clearly dead SMB2+ sessions as a result. This is causing issues, as it appears that the kernel only reconnects after a delay period, during which time all IO to that network share (with that session id) results in an I/O error for the user; all the while the kernel is repeatedly resubmitting the requests in the background with the server just responding to each of them with yet more USER_SESSION_DELETED packets. This is contrasting to the behaviour on Windows clients - whereby if the response the client gets is USER_SESSION_DELETED, it drops that session and reconnects - transparently to the user. This causes massive issues multiuser mounts (as is the case for me), as if a users SMB session is deleted by the server for any reason, that user essentially loses all access to that share for extended periods, until the cifs module sees fit to treat that session as dead and renegotiate or an admin intervenes. # Reproducing Reproducing the issue is easily done, establish an SMB2+ mount to a Windows Server machine, open any directory on client to establish a session, then simply terminate that SMB session from the servers MMC console, if you then try and run any queries against that mountpoint on the client you will just end up with a string of I/O errors because its trying to use a session id which is dead. For reference I'm testing using the following mount options: vers=3.02,multiuser,sec=ntlmsspi,file_mode=0750,dir_mode=0755,cache=none,credentials=/etc/smb.credentials.conf # Affects This affects all kernel releases that I've tested(including the kernel mainline), and hence I've reported it upstream, however I'm recording it here as well for reference purposes. ## Additional Reference Info Current Version Sig: Ubuntu 4.4.0-78.99-generic 4.4.62 ** Affects: linux Importance: Unknown Status: Unknown ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Current lspci" https://bugs.launchpad.net/bugs/1707167/+attachment/4922945/+files/lspci-vnvn.log ** Bug watch added: Linux Kernel Bug Tracker #195817 https://bugzilla.kernel.org/show_bug.cgi?id=195817 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=195817 Importance: Unknown Status: Unknown ** Summary changed: - CIFS: Kernel ignores USER_SESSION_DELETED PDU and holds onto dead sessions. + Kernel CIFS Module ignores USER_SESSION_DELETED PDUs and holds onto dead sessions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707167 Title: Kernel CIFS Module ignores USER_SESSION_DELETED PDUs and holds onto dead sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1707167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1706284] Re: sssd fails to Update PTR if any A record update fails.
--Verification from myself-- UnPatched Version 1.6: [FAIL] - Showing from debug_level 7 (Thu Jul 27 13:19:15 2017) [sssd[be[TESTDOMAIN.TLD]]] [be_nsupdate_create_fwd_msg] (0x0400): -- Reply from update query: ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 36140 ;; UPDATE SECTION: KWARVM002.TESTDOMAIN.TLD. 3600 IN A 192.168.93.130 (Thu Jul 27 13:19:15 2017) [sssd[be[TESTDOMAIN.TLD]]] [nsupdate_child_handler] (0x0040): Dynamic DNS child failed with status [512] (Thu Jul 27 13:19:15 2017) [sssd[be[TESTDOMAIN.TLD]]] [be_nsupdate_done] (0x0040): nsupdate child execution failed [1432158232]: Dynamic DNS update failed Reason for Fail: No PTR update performed - nsupdate returned non-zero even though Update actually was NOERROR. == My Patched Version 1.7: [PASS] - Showing from debug_level 7 (Thu Jul 27 13:06:58 2017) [sssd[be[TESTDOMAIN.TLD]]] [be_nsupdate_create_fwd_msg] (0x0400): -- Reply from update query: ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 49642 ;; UPDATE SECTION: KWARVM002.TESTDOMAIN.TLD. 3600 IN A 192.168.93.130 (Thu Jul 27 13:06:58 2017) [sssd[be[TESTDOMAIN.TLD]]] [nsupdate_child_handler] (0x0040): Dynamic DNS child failed with status [512] (Thu Jul 27 13:06:58 2017) [sssd[be[TESTDOMAIN.TLD]]] [be_nsupdate_create_ptr_msg] (0x0400): -- Reply from update query: ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 13681 ;; UPDATE SECTION: 130.93.168.192.in-addr.arpa. 3600 INPTR KWARVM002.TESTDOMAIN.TLD. (Thu Jul 27 13:06:58 2017) [sssd[be[TESTDOMAIN.TLD]]] [nsupdate_child_handler] (0x0040): Dynamic DNS child failed with status [512] (Thu Jul 27 13:06:58 2017) [sssd[be[TESTDOMAIN.TLD]]] [be_nsupdate_done] (0x0040): nsupdate child execution failed [1432158232]: Dynamic DNS update failed Reason for Pass: PTR performed even though previous update was marked as failed (NOERROR). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706284 Title: sssd fails to Update PTR if any A record update fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1706284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1706284] Re: sssd fails to Update PTR if any A record update fails.
I've updated the test case on this, which from what people are saying, should make it easier to reproduce. I've yet to sort out the debdiff on this for yakkety, I'll be sorting that out later today. ** Description changed: sssd in both xenial and yakkety fails to update the PTR record of the current host on an active directory controller if any update for an A/AAA record returns a non-fatal error, this results in missing (and/or) mismatched Reverse DNS. This has already been fixed in 1.5.1 (which is present in Zesty and above), as failure to update any of the A/AAA should not affect updating the PTR as well, as not all servers in a given AD cluster may accept an A/AAA record update, especially if it would result in no update being made (NOERROR). See the attached conversation about this issue here: https://pagure.io/SSSD/sssd/issue/3227 for further information. I'll attach a debdiff against the relevant releases shortly, however for now I've attached the original patch which was used to fix the bug in 1.15.1 ### SRU Justification ### [Impact] Currently users find that sssd will not update the reverse (PTR) records of a given host if an AD server returns non-fatal error for an A/AAA update. This causes strange issues to occur where we can end up with hosts with proper functioning forward records but no reverse. I propose we backport the fix from 1.15.1 to both Xenial and Yakkety to resolve the issue so PTR updates get processed (or at least attempted). The patch attached removes the error check that occurs should the return code of the A/AAA nsupdates be non zero, and instead allows the PTR update to occur before checking for errors. This is the same patch taken from the fix for 1.15.1 [Test Case] - As per the original bug: + For the configuration of sssd, a basic configuration of the following + should suffice: - Steps to Reproduce: - 1. Setup 'nonsecure and secure' zones - 2. Start sssd + [sssd] + services = nss, pam + config_file_version = 2 + domains = YOURDOMAIN.TLD - Actual results: - A records will get updated but PTR records will fail as sssd does not try to - update them. + [domain/YOURDOMAIN.TLD] + id_provider=ad + auth_provider=ad + access_provider=ad + chpass_provider=ad + override_homedir=/home/%d/%u + cache_credentials = true + ad_gpo_access_control=permissive + default_shell=/bin/bash + ad_hostname = sssd-hostname.YOURDOMAIN.TLD + + In AD change the properties of the Forward zone Dynamic Updates to "Nonsecure and Secure" + Ensure a Reverse Zone is present in the AD DNS MMC. + Remove any existing A/ and PTR records from Active Directory DNS for the SSSD system + Restart SSSD to trigger the nsupdate call + Check the reverse zone in AD for PTR records, they do not get created but the A/ records do. Expected results: Both A and PTR records get updated. [Regression Potential] As this patch is already present in a future release it has been fairly well tested already however back-porting the fix will result in sssd attempting PTR updates whether the A/AAA updates succeeds or not. As per the original bug report where a quick note was made about failed updates; If forward updates fail the result will be inconsistent DNS should the reverse succeed (reverse but no forward), however in that case the admin needs to look into with why the update failed, the code should at least try to record all updates (both A, AAA and PTR) and not just ignore the PTR because the forward update (may or may not have) failed. There is also the possibility that the patch may not resolve the problem completely however as this patch just moves the error handling before the PTR attempt I can see no reason not to backport the patch to the older version for Xenial/Yakkety. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706284 Title: sssd fails to Update PTR if any A record update fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1706284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1706284] Re: sssd fails to Update PTR if any A record update fails.
Attaching debdiff against Xenial (Old version: 1.13.4-1ubuntu1.6 new: 1.13.4-1ubuntu1.7) ** Patch added: "Debdiff for Xenial" https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1706284/+attachment/4920977/+files/sssd_1.13.4-1ubuntu1.7.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706284 Title: sssd fails to Update PTR if any A record update fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1706284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1706284] [NEW] sssd fails to Update PTR if any A record update fails.
Public bug reported: sssd in both xenial and yakkety fails to update the PTR record of the current host on an active directory controller if any update for an A/AAA record returns a non-fatal error, this results in missing (and/or) mismatched Reverse DNS. This has already been fixed in 1.5.1 (which is present in Zesty and above), as failure to update any of the A/AAA should not affect updating the PTR as well, as not all servers in a given AD cluster may accept an A/AAA record update, especially if it would result in no update being made (NOERROR). See the attached conversation about this issue here: https://pagure.io/SSSD/sssd/issue/3227 for further information. I'll attach a debdiff against the relevant releases shortly, however for now I've attached the original patch which was used to fix the bug in 1.15.1 ### SRU Justification ### [Impact] Currently users find that sssd will not update the reverse (PTR) records of a given host if an AD server returns non-fatal error for an A/AAA update. This causes strange issues to occur where we can end up with hosts with proper functioning forward records but no reverse. I propose we backport the fix from 1.15.1 to both Xenial and Yakkety to resolve the issue so PTR updates get processed (or at least attempted). The patch attached removes the error check that occurs should the return code of the A/AAA nsupdates be non zero, and instead allows the PTR update to occur before checking for errors. This is the same patch taken from the fix for 1.15.1 [Test Case] As per the original bug: Steps to Reproduce: 1. Setup 'nonsecure and secure' zones 2. Start sssd Actual results: A records will get updated but PTR records will fail as sssd does not try to update them. Expected results: Both A and PTR records get updated. [Regression Potential] As this patch is already present in a future release it has been fairly well tested already however back-porting the fix will result in sssd attempting PTR updates whether the A/AAA updates succeeds or not. As per the original bug report where a quick note was made about failed updates; If forward updates fail the result will be inconsistent DNS should the reverse succeed (reverse but no forward), however in that case the admin needs to look into with why the update failed, the code should at least try to record all updates (both A, AAA and PTR) and not just ignore the PTR because the forward update (may or may not have) failed. There is also the possibility that the patch may not resolve the problem completely however as this patch just moves the error handling before the PTR attempt I can see no reason not to backport the patch to the older version for Xenial/Yakkety. ** Affects: sssd (Ubuntu) Importance: Undecided Assignee: Keith Ward (keithward) Status: In Progress ** Tags: patch xenial yakkety ** Patch added: "Patch from Upstream" https://bugs.launchpad.net/bugs/1706284/+attachment/4920917/+files/sssd_update-ptr.patch ** Changed in: sssd (Ubuntu) Status: New => In Progress ** Changed in: sssd (Ubuntu) Assignee: (unassigned) => Keith Ward (keithward) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706284 Title: sssd fails to Update PTR if any A record update fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1706284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1689670] Re: Programas instalados no aparecen
Thank you for taking the time to report this issue and helping to make Ubuntu better. We noticed that some of the sentences in this bug report are not in English. If they were translated to English they would be more understandable to triagers. Could you please translate them? Please also answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem. ** Changed in: budgie-desktop (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/1689670 Title: Programas instalados no aparecen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1689670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611816] Re: pam_cifscreds.so not supplied in package
** Changed in: cifs-utils (Ubuntu Xenial) Status: In Progress => Confirmed ** Changed in: cifs-utils (Ubuntu Yakkety) Status: In Progress => Confirmed ** Changed in: cifs-utils (Ubuntu Xenial) Assignee: Keith Ward (keithward) => (unassigned) ** Changed in: cifs-utils (Ubuntu Yakkety) Assignee: Keith Ward (keithward) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611816 Title: pam_cifscreds.so not supplied in package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1611816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611816] Re: pam_cifscreds.so not supplied in package
Subscribed Ubuntu-Sponsors as I don't have ability to upload directly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611816 Title: pam_cifscreds.so not supplied in package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1611816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611816] Re: pam_cifscreds.so not supplied in package
Attaching debdiff against Yakkety - 6.5-2ubuntu1 ** Patch added: "cifs-utils_6.5-2ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/yakkety/+source/cifs-utils/+bug/1611816/+attachment/4814012/+files/cifs-utils_6.5-2ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611816 Title: pam_cifscreds.so not supplied in package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1611816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611816] Re: pam_cifscreds.so not supplied in package
Attaching Debdiff against Xenial 6.4-1_ubuntu1 ** Patch added: "cifs-utils_6.4-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/xenial/+source/cifs-utils/+bug/1611816/+attachment/4814010/+files/cifs-utils_6.4-1ubuntu2.debdiff ** Changed in: cifs-utils (Ubuntu Yakkety) Status: New => In Progress ** Changed in: cifs-utils (Ubuntu Yakkety) Assignee: (unassigned) => Keith Ward (keithward) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611816 Title: pam_cifscreds.so not supplied in package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1611816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611816] Re: pam_cifscreds.so not supplied in package
** Changed in: cifs-utils (Ubuntu Xenial) Status: New => In Progress ** Changed in: cifs-utils (Ubuntu Xenial) Assignee: (unassigned) => Keith Ward (keithward) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611816 Title: pam_cifscreds.so not supplied in package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1611816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611816] Re: pam_cifscreds.so not supplied in package
** Description changed: The cifs-utils source package contains the pam_cifscreds.so PAM module; however, this is not built and supplied in a resulting binary package. This is necessary functionality for our local managed deployment. We have worked around this issue by building our own patched version of the package; however, this is liable to be clobbered by any future upstream updates. Hence, it would be valuable if our modifications, or some variant of them, could be adopted upstream. The changes required are minimal; simply add libpam0g-dev to Build- Depends, and add some appropriate flags to ./configure in debian/rules to ensure the requisite library is built and installed in the correct location. See attached patch. + + ## SRU Justification + + [Impact] + + As David has found, users are currently unable to use the cifscreds PAM + module to unlock credentials at login because existing package doesn't + compile the module along with the rest of the package. + + Davids patch adds libpam-0g-dev to the Build depends, and amends the + debian rules file so that the PAM module is built along with the rest of + the application and installed into the correct location. + + I'm requesting this to be backported to the existing releases, this change is a + feature which is highly desired in managed deployments, the changes are minimal and as this patch only adds functionality and is largely unobtrusive I see no reason for the Ubuntu community to benefit from its inclusion considering the regression potential is minimal. + + This feature has been added to Zesty already as part of the merge done + in LP: #1660372. + + [Test Case] + + Install the package and check for the existance of the PAM module at: + /lib/x86_64-linux-gnu/security/pam_cifscreds.so + + At present this file is missing as it isn't compiled along with the rest + of the package. + + [Regression Potential] + + I've been testing this myself on a number of systems and have discovered + no issues as yet, with this patch the supplied module is built and + placed into the correct location, as is the manpage, and both perform as + intended. + + This change has an overall low chance of regression as it's only adding + functionality should already be there. + + The only regression I could think of is that for some reason the patch + could result in some of the other binaries being linked against PAM (and + potentially have their behavior changed) as a result of the addition of + PAM, but I find this extremely unlikely, and I have verified that PAM + isn't linked to except for pam_cifscreds.so so I find the possibility of + this happening negligible. + + Documentation for the feature is provided as a manpage and is + distributed along with the updated package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611816 Title: pam_cifscreds.so not supplied in package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1611816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1538284] Re: Unescaped left brace in regex is deprecated
** Also affects: pam (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815595 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/1538284 Title: Unescaped left brace in regex is deprecated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1538284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 788167] Re: CUPS cannot print to Kerberos-authenticated SMB print queue
** Bug watch added: Debian Bug tracker #711341 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711341 ** Changed in: debian Importance: Undecided => Unknown ** Changed in: debian Status: New => Unknown ** Changed in: debian Remote watch: None => Debian Bug tracker #711341 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/788167 Title: CUPS cannot print to Kerberos-authenticated SMB print queue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/788167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1372120] Re: setcifsacl errors out, package missing idmap-plugin symlink
** Bug watch added: Debian Bug tracker #845532 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845532 ** Also affects: cifs-utils (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845532 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/1372120 Title: setcifsacl errors out, package missing idmap-plugin symlink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1372120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611816] Re: pam_cifscreds.so not supplied in package
** Bug watch added: Debian Bug tracker #848140 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848140 ** Also affects: cifs-utils (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848140 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/1611816 Title: pam_cifscreds.so not supplied in package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1611816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 800910] [NEW] Kernel Upgrade forces removal of grub-efi due to missing recommends entry
Public bug reported: I'm currently experiencing an issue with installing kernel updates on natty. It seems to want to force install grub-pc -- ignoring the fact that grub-efi is installed. Looking at the dsc for the kernels at present, it seems linux-image-* recommends grub , grub-pc or lilo, but omits grub-efi which means when a kernel upgrade happens it forces removal of it for a recommended bootloader - despite the fact that grub-efi-* is perfectly valid, and is required for EFI booting. keith@Jarvis:~$ uname -a Linux Jarvis 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux -Keith ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Description changed: I'm currently experiencing an issue with installing kernel updates on natty. It seems to want to force install grub-pc -- ignoring the fact that grub-efi is installed. Looking at the dsc for the kernels at present, it seems linux-image-* - recommends grub , grub-pc or lilo, but omits grub-efi which mean when a - kernel upgrade happens it forces removal of it, over a recommended + recommends grub , grub-pc or lilo, but omits grub-efi which means when a + kernel upgrade happens it forces removal of it for a recommended bootloader - despite the fact that grub-efi-* is perfectly valid, and is required for EFI booting. keith@Jarvis:~$ uname -a Linux Jarvis 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux -Keith -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/800910 Title: Kernel Upgrade forces removal of grub-efi due to missing recommends entry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/800910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 800910] Re: Kernel Upgrade forces removal of grub-efi due to missing recommends entry
keith@Jarvis:~$ dpkg -l linux-image-generic Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Description +++-=-=-== ii linux-image-generic 2.6.38.8.22 Generic Linux kernel image keith@Jarvis:~$ dpkg -l linux-image-2.6.38-8-generic Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Description +++-=-=-== ii linux-image-2.6.38-8-generic 2.6.38-8.42 Linux kernel image for version 2.6.38 on x86/x86_64 keith@Jarvis:~$ sudo apt-get install linux-image-2.6.38-10-generic Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: grub-gfxpayload-lists grub-pc Suggested packages: desktop-base fdutils linux-doc-2.6.38 linux-source-2.6.38 linux-tools The following packages will be REMOVED grub-efi grub-efi-amd64 The following NEW packages will be installed grub-gfxpayload-lists grub-pc linux-image-2.6.38-10-generic 0 upgraded, 3 newly installed, 2 to remove and 2 not upgraded. Need to get 37.4 MB of archives. After this operation, 148 MB of additional disk space will be used. Do you want to continue [Y/n]? ** Description changed: I'm currently experiencing an issue with installing kernel updates on natty. It seems to want to force install grub-pc -- ignoring the fact that grub-efi is installed. Looking at the dsc for the kernels at present, it seems linux-image-* recommends grub , grub-pc or lilo, but omits grub-efi which means when a kernel upgrade happens it forces removal of it for a recommended bootloader - despite the fact that grub-efi-* is perfectly valid, and is required for EFI booting. keith@Jarvis:~$ uname -a Linux Jarvis 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux + keith@Jarvis:~$ apt-cache show linux-image-2.6.38-10-generic | grep Recommends + Recommends: grub-pc | grub | lilo (= 19.1) + -Keith -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/800910 Title: Kernel Upgrade forces removal of grub-efi due to missing recommends entry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/800910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 423514] Re: miro.real crashed with TypeError in skip_backward()
Unfortunately Karmic was marked as EOL on April 29th 2011, This means that this bug is unlikely to get fixed, as official support ended on that date. I would advise you to upgrade to the next supported release (which is Lucid Lynx), and try again. Please note miro has been upgraded significantly in Lucid and above. Please see: https://help.ubuntu.com/community/EOLUpgrades and https://help.ubuntu.com/community/LucidUpgrades. ** Changed in: miro (Ubuntu) Status: New = Incomplete ** Changed in: miro (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/423514 Title: miro.real crashed with TypeError in skip_backward() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/miro/+bug/423514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 423514] Re: miro.real crashed with TypeError in skip_backward()
Once you have upgraded to Lucid, if you could please check to ensure this bug is fixed. Thanks. ** Changed in: miro (Ubuntu) Status: Invalid = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/423514 Title: miro.real crashed with TypeError in skip_backward() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/miro/+bug/423514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721576] Re: [natty] kernel panic on reboot with (U)EFI
All, I've discovered a note on: https://help.ubuntu.com/community/UEFIBooting#Kernel%20panic%20on%20Reboot regarding this. Apparently this is as a result of buggy Sandybridge UEFI firmware? -Keith -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721576 Title: [natty] kernel panic on reboot with (U)EFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/721576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721576] Re: [natty] kernel panic on reboot with (U)EFI
** Also affects: ubuntu-release-notes 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/721576 Title: [natty] kernel panic on reboot with (U)EFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/721576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721576] Re: [natty] kernel panic on reboot with (U)EFI
I've gone ahead and added an entry for the Ubuntu Release Notes Team, Ideally we need a mention of this in the natty release notes (especially as there is already 4 other duplicate bugs with regards to this issue). -Keith ** Bug watch added: Debian Bug tracker #626022 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626022 ** Also affects: linux-2.6 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626022 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/721576 Title: [natty] kernel panic on reboot with (U)EFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/721576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539814] Re: tar: futimens() with a bad file descriptor (AT_FDCWD) causes bootstrapping failure with kernels 2.6.22
** Summary changed: - tar/gnulib bug prevents bootstraping Lucid on Dapper, causes Lucid upgrade to abort on older linux kernels (e.g. in a chroot or Xen VM) + tar: futimens() with a bad file descriptor (AT_FDCWD) causes bootstrapping failure with kernels 2.6.22 -- tar: futimens() with a bad file descriptor (AT_FDCWD) causes bootstrapping failure with kernels 2.6.22 https://bugs.launchpad.net/bugs/539814 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 539814] Re: tar: futimens() with a bad file descriptor (AT_FDCWD) causes bootstrapping failure with kernels 2.6.22
Attached debfiff for tar-1.22 that fixes this. ** Description changed: Binary package hint: tar - Currently if you try to debootstrap Lucid on anything running a kernel - older than 2.6.22, (I've specifically tried on 2.6.18) it fails with - stuff like: + Bootstrapping Ubuntu Lucid with debootstrap is currently impossible with + any kernel 2.6.22, due to a bug in tar - specifically it fails because + of a change to eglibc. - # dpkg --force-depends --install var/cache/apt/archives/base-files_5.0.0ubuntu10_amd64.deb var/cache/apt/archives/base-passwd_3.5.22_amd64.deb - tar: ./postinst: Cannot utime: Bad file descriptor - tar: ./preinst: Cannot utime: Bad file descriptor - tar: ./conffiles: Cannot utime: Bad file descriptor - tar: ./md5sums: Cannot utime: Bad file descriptor - tar: ./control: Cannot utime: Bad file descriptor - tar: .: Cannot utime: Bad file descriptor - tar: Exiting with failure status due to previous errors - dpkg-deb: subprocess tar returned error exit status 2 - dpkg: error processing var/cache/apt/archives/base-files_5.0.0ubuntu10_amd64.deb (--install): - subprocess dpkg-deb --control returned error exit status 2 - tar: ./postinst: Cannot utime: Bad file descriptor - tar: ./md5sums: Cannot utime: Bad file descriptor - tar: ./control: Cannot utime: Bad file descriptor - tar: .: Cannot utime: Bad file descriptor - tar: Exiting with failure status due to previous errors - dpkg-deb: subprocess tar returned error exit status 2 - dpkg: error processing var/cache/apt/archives/base-passwd_3.5.22_amd64.deb (--install): - subprocess dpkg-deb --control returned error exit status 2 - Errors were encountered while processing: - var/cache/apt/archives/base-files_5.0.0ubuntu10_amd64.deb - var/cache/apt/archives/base-passwd_3.5.22_amd64.deb + According to the debian bug report It seems that before eglibc 2.10.2-3, + calls to futimens failed silently, however due to a patch made to eglibc + 2.10.2-3, if futimens is called without a valid file descriptor, it now + fails with an Bad File Descriptor error, because the corresponding + utimensat() syscall was not added until kernel 2.6.22 - From further investigation, this appears to be due to a bug in tar. + Test Case: + 1) Boot a kernel older than 2.6.22 + 2) Attempt to Bootstrap Ubuntu Lucid to any target. + The bootstrap will fail once it attempts to unpack packages with: tar: ./postinst: Cannot utime: Bad file descriptor + + A patch is available (attached in launchpad) originating from the associated debian bug, that ensures that futimens is only called with a valid file descriptor. + A debdiff for 1.22-2 ( changing to 1.22-2ubuntu1 ) will be attached shortly. ** Patch added: Debdiff for tar-1.22 with added tar-futimens patch from debian bug report. https://bugs.launchpad.net/ubuntu/lucid/+source/tar/+bug/539814/+attachment/1515914/+files/tar-1.22-2ubuntu1.debdiff -- tar: futimens() with a bad file descriptor (AT_FDCWD) causes bootstrapping failure with kernels 2.6.22 https://bugs.launchpad.net/bugs/539814 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 539814] Re: tar/gnulib bug prevents bootstraping Lucid on Dapper, causes Lucid upgrade to abort on older linux kernels (e.g. in a chroot or Xen VM)
Firstly, apologies to anyone if the following comment comes across as confrontational, but this bug has gone on far too long. I've gone ahead Subscribed SRU to this bug, as it is urgent, due to the fact it prevents any system with a kernel older than 2.6.22 from bootstrapping lucid - (which means it applies to dapper), as tar simply fails due to the previously mentioned utime errors. I'm surprised this hasn't been patched already especially as it was previously mentioned that debian patched it a long long time ago. I'm even more surprised that Lucid was released without this being fixed - especially as the patch has been available since at least march! Just to clarify this bug prevents any type of bootstrapping from Dapper or running of tar on any kernel 2.6.22, (this means you can't debootstrap lucid on the majority of Xen Hosts, as they run kernel 2.6.18! While I agree that it is not possible to support every kernel known to man, due to the fact this this applies to more than just dapper - there are a lot of hosts running .18 kernels, for various reasons: mostly xen hosts, and the fact a patch has been available since the beginning half of the year, and has been fixed in *both* Debian and fedora, just makes the whole situation we are now in, completely unbelievable. The resolution to this problem is to either use the patch I attached a few months ago from the debian bug, and push that for an SRU (It fixes this bug, and only this bug). Or to push the package from maverick into lucid as an SRU (this bug according to the debian information at debbugs is fixed in version 1.23-1). As to which option is preferred i shall leave up to the developers, personally if we're updating the package again, it may be an idea to push over the version from maverick as opposed to just creating a new -rev for 1.22. Regards, -- tar/gnulib bug prevents bootstraping Lucid on Dapper, causes Lucid upgrade to abort on older linux kernels (e.g. in a chroot or Xen VM) https://bugs.launchpad.net/bugs/539814 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 539814] Re: tar/gnulib bug prevents bootstraping Lucid on Dapper, causes Lucid upgrade to abort on older linux kernels (e.g. in a chroot or Xen VM)
Debian has released a patch, that fixes just this problem, in January? See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563726 for more details. - Specifically http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=563726#66. Patch attached. Keith ** Patch added: Patch from above debian bug, which fixes this. http://launchpadlibrarian.net/49944671/tar-futimens.patch ** Changed in: tar (Ubuntu Lucid) Status: New = Fix Released ** Changed in: tar (Ubuntu) Status: New = Fix Released -- tar/gnulib bug prevents bootstraping Lucid on Dapper, causes Lucid upgrade to abort on older linux kernels (e.g. in a chroot or Xen VM) https://bugs.launchpad.net/bugs/539814 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 539814] Re: tar/gnulib bug prevents bootstraping Lucid on Dapper, causes Lucid upgrade to abort on older linux kernels (e.g. in a chroot or Xen VM)
Apologies - set these to the wrong status. -Keith ** Changed in: tar (Ubuntu) Status: Fix Released = In Progress ** Changed in: tar (Ubuntu Lucid) Status: Fix Released = In Progress ** Changed in: tar (Ubuntu) Status: In Progress = Fix Released -- tar/gnulib bug prevents bootstraping Lucid on Dapper, causes Lucid upgrade to abort on older linux kernels (e.g. in a chroot or Xen VM) https://bugs.launchpad.net/bugs/539814 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 552816] Re: coreutils affected by Bad file descriptor error with new glibc on older kernel
** Also affects: coreutils (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563754 Importance: Unknown Status: Unknown -- coreutils affected by Bad file descriptor error with new glibc on older kernel https://bugs.launchpad.net/bugs/552816 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 569904] [NEW] mysql-server-5.0 from hardy conflicts with mysql-server-core in karmic
Public bug reported: Binary package hint: mysql-server-core-5.1 When upgrading from hardy to karmic, the upgrade fails once it hits mysql, because mysqld is listed in both mysql-server-core and mysql- server-5.0. Unpacking mysql-server-core-5.1 (from .../mysql-server-core-5.1_5.1.37-1ubuntu5.1_i386.deb) ... dpkg: error processing /var/cache/apt/archives/mysql-server-core-5.1_5.1.37-1ubuntu5.1_i386.deb (--unpack): trying to overwrite '/usr/sbin/mysqld', which is also in package mysql-server-5.0 0:5.0.51a-3ubuntu5.5 ** Affects: mysql-dfsg-5.1 (Ubuntu) Importance: Undecided Status: New -- mysql-server-5.0 from hardy conflicts with mysql-server-core in karmic https://bugs.launchpad.net/bugs/569904 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569904] [NEW] mysql-server-5.0 from hardy conflicts with mysql-server-core in karmic
Public bug reported: Binary package hint: mysql-server-core-5.1 When upgrading from hardy to karmic, the upgrade fails once it hits mysql, because mysqld is listed in both mysql-server-core and mysql- server-5.0. Unpacking mysql-server-core-5.1 (from .../mysql-server-core-5.1_5.1.37-1ubuntu5.1_i386.deb) ... dpkg: error processing /var/cache/apt/archives/mysql-server-core-5.1_5.1.37-1ubuntu5.1_i386.deb (--unpack): trying to overwrite '/usr/sbin/mysqld', which is also in package mysql-server-5.0 0:5.0.51a-3ubuntu5.5 ** Affects: mysql-dfsg-5.1 (Ubuntu) Importance: Undecided Status: New -- mysql-server-5.0 from hardy conflicts with mysql-server-core in karmic https://bugs.launchpad.net/bugs/569904 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
