Re: [Bug 1860824] Re: IMAP with STARTTLS on port 143 is broken
Gotit - thanks! On Fri, 2020-07-17 at 15:36 +, Kai Kasurinen wrote: > This bug report is being closed due to your last comment regarding this > being fixed. For future reference you can manage the status of your own > bugs by clicking on the current status in the yellow line and then > choosing a new status in the revealed drop down box. You can learn more > about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you > again for taking the time to report this bug and helping to make Ubuntu > better. Please submit any future bugs you may find. > > ** Changed in: evolution (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/1860824 Title: IMAP with STARTTLS on port 143 is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860824] Re: IMAP with STARTTLS on port 143 is broken
Dug further on this and the issue is an ancient TLS version being used on the server, so this bug can be closed. BTW is there any way for me to close the bug myself since I filed it? Thnx - -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860824 Title: IMAP with STARTTLS on port 143 is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880018] Re: Notifications unreadable due to dark on dark text
Indeed it was - 20.10 does not have this issue. Hopefully we can get a backport to focal... Anyway thanks a ton! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880018 Title: Notifications unreadable due to dark on dark text To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arc-theme/+bug/1880018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880018] [NEW] Notifications unreadable due to dark on dark text
Public bug reported:
Upon upgrade to focal notifications are black text on very dark grey
background, rendering them unreadable. I've attached a screenshot of
how it looks after the upgrade.
Hovering over the notification in the popup makes the text turn the
correct light color.
To make it readable, was able to change the CSS at line #1631 in this
file:
/usr/share/themes/Arc-Dark/gnome-shell/gnome-shell.css
...to make the notifications background lighter, like so:
[...]
.notification-banner,
.notification-banner:hover,
.notification-banner:focus {
font-size: 10pt;
width: 34em;
margin: 10px;
padding: 6px 4px;
color: #D3DAE3;
/* background-color: #383C4A; */
background-color: #636883;
...not great but makes it readable at least.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: arc-theme 20190917-1ubuntu1 [modified:
usr/share/themes/Arc-Dark/gnome-shell/gnome-shell.css]
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu May 21 12:22:08 2020
InstallationDate: Installed on 2019-07-19 (307 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
PackageArchitecture: all
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: arc-theme
UpgradeStatus: Upgraded to focal on 2020-05-14 (7 days ago)
** Affects: arc-theme (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
** Attachment added: "screenshot"
https://bugs.launchpad.net/bugs/1880018/+attachment/5375325/+files/Screenshot%20from%202020-05-21%2012-20-32.png
** Description changed:
Upon upgrade to focal notifications are black text on very dark grey
- background, rendering them unreadable. I've attached a couple
- screenshots of how it looks after the upgrade.
+ background, rendering them unreadable. I've attached a screenshot of
+ how it looks after the upgrade.
Hovering over the notification in the popup makes the text turn the
correct light color.
- To make it bearable, was able to change the CSS at line #1631 in this
+ To make it readable, was able to change the CSS at line #1631 in this
file:
/usr/share/themes/Arc-Dark/gnome-shell/gnome-shell.css
- ...to be a bit lighter, like so:
+ ...to make the notifications background lighter, like so:
[...]
.notification-banner,
.notification-banner:hover,
.notification-banner:focus {
- font-size: 10pt;
- width: 34em;
- margin: 10px;
- padding: 6px 4px;
- color: #D3DAE3;
+ font-size: 10pt;
+ width: 34em;
+ margin: 10px;
+ padding: 6px 4px;
+ color: #D3DAE3;
/* background-color: #383C4A; */
- background-color: #636883;
+ background-color: #636883;
+
+ ...not great but makes it readable at least.
+
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: arc-theme 20190917-1ubuntu1 [modified:
usr/share/themes/Arc-Dark/gnome-shell/gnome-shell.css]
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu May 21 12:22:08 2020
InstallationDate: Installed on 2019-07-19 (307 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
PackageArchitecture: all
ProcEnviron:
- PATH=(custom, no user)
- XDG_RUNTIME_DIR=
- LANG=en_US.UTF-8
- SHELL=/bin/bash
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
SourcePackage: arc-theme
UpgradeStatus: Upgraded to focal on 2020-05-14 (7 days ago)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880018
Title:
Notifications unreadable due to dark on dark text
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/arc-theme/+bug/1880018/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849156] Re: systemd-timesyncd.service broken on upgrade to 19.10 if ntp was installed
Got bit by this as well, recall fixing it a few years ago but must have clobbered my changes on upgrade bionic -> eoan? Having VirtualBox installed broke it, fix was to comment out this line in /lib/systemdd/system/systemd-timesyncd.service.d and restart systemd: ConditionFileIsExecutable=!/usr/sbin/VBoxService Don't recall being asked about a config file change during upgrade although maybe it did and didn't remember. Further info here: https://askubuntu.com/questions/940311/time-in-ubuntu-16-04-not- updating-from-internet#1005355 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849156 Title: systemd-timesyncd.service broken on upgrade to 19.10 if ntp was installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1849156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860827] Re: [snap] chromium does not open
You can close this, after recent updates it is now opening fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860827 Title: [snap] chromium does not open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1860827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860827] [NEW] chromium does not open
Public bug reported:
Just upgraded to fossa. When clicking chromium-browser, title bar
switches to "Chromium Web Browser", spins for awhile and then disappears
nothing opens.
If it helps, running 'chromium-browser' at CLI is:
mark@zynxps:~$ chromium-browser
Failed to move to new namespace: PID namespaces supported, Network namespace
supported, but failed: errno = Operation not permitted
Trace/breakpoint trap (core dumped)
mark@zynxps:~$
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser 79.0.3945.79-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 24 15:55:10 2020
InstallationDate: Installed on 2018-10-06 (475 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Snap.Changes:
ID Status Spawn Ready Summary
55 Done2020-01-24T12:55:57-08:00 2020-01-24T12:56:26-08:00 Install
"chromium" snap
56 Done2020-01-24T14:30:02-08:00 2020-01-24T14:30:02-08:00 Connect
chromium:password-manager-service to core:password-manager-service
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.117
(04f0a055010adab4484f7497fbfdbf312c307f1d-refs/branch-heads/3945@{#1019})
Snap.ChromiumVersion: Chromium 79.0.3945.117 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago)
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal third-party-packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860827
Title:
chromium does not open
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1860827/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860824] [NEW] IMAP with STARTTLS on port 143 is broken
Public bug reported: Just upgraded from eoan -> fossa to test. Incoming mail is configured to use STARTTLS over port 143 and works fine in eoan and bionic. But in fossa, upon startup IMAP immediately fails with error message: 'The reported error was "Error performing TLS handshake: An unexpected TLS packet was received."' ...no incoming mail and none of the folders will open. Workaround: Switch account configuration to use TLS directly over dedicated port 993 Then everything works as normal. But users for whom port 993 is not an option, no incoming mail or access to their mailfolders. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evolution 3.34.1-2build1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 15:34:28 2020 InstallationDate: Installed on 2018-10-06 (475 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860824 Title: IMAP with STARTTLS on port 143 is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860823] Re: IMAP with STARTTLS is broken
I went ahead and properly filed but 1860824 so this one can be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860823 Title: IMAP with STARTTLS is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-exchange/+bug/1860823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860823] [NEW] IMAP with STARTTLS is broken
Public bug reported: Just upgraded from eoan -> fossa to test. Incoming mail is configured to use STARTTLS over port 143 and works fine in eoan and bionic. But in fossa, upon startup IMAP immediately fails with error message: The reported error was “Error performing TLS handshake: An unexpected TLS packet was received.”. ...no incoming mail and none of the folders will open. Workaround: Switch account configuration to use TLS directly over dedicated port 993 Then everything works as normal. Users for whom port 993 is not an option, however, will have no incoming mail or access to any of their existing mail folders. ** Affects: evolution-exchange (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/1860823 Title: IMAP with STARTTLS is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-exchange/+bug/1860823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860823] Re: IMAP with STARTTLS is broken
Somehow this went the the wrong package; hopefully someone can reassign it was intended to go to the 'evolution' package directly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860823 Title: IMAP with STARTTLS is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-exchange/+bug/1860823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841646] Re: White text on white background for HTML e-mail
When av LTS is relkeased, is is considered according to it's promise: 6 years. But yet, after 3.5 years, here we are. Someone else said it works fine in Eoan. ...who approved this SRU? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841646 Title: White text on white background for HTML e-mail To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1841646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841646] Re: White text on white background for HTML e-mail
Thanks, was really surprised to see this happen in an LTS release. Any Ubuntu devs reading this, can we get a backport? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841646 Title: White text on white background for HTML e-mail To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1841646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841646] Re: White text on white background for HTML e-mail
Same behavior here, after unattended upgrade. This renders Evolution pretty much unusable with dark theme. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841646 Title: White text on white background for HTML e-mail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1841646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813662] Re: Cannot build VM
Hilko, you probably know this but it looks like in the original thread
here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725
...that this could be fixed thusly:
To have this automatically happen with each new kernel, create
/etc/kernel/postinst.d/statoverride:
#!/bin/sh
version="$1"
# passing the kernel version is required
[ -z "${version}" ] && exit 0
dpkg-statoverride --add root root 0644 /boot/vmlinux-${version} --update
...can libguestfs package ship that script? Or would that be a policy
violation of some sort?
It looks like if upon installation short script could be placed in
/etc/kernel/postinst.d/statoverride, along with a "chmod 0644
/boot/vmlinuz*", then all those annoying bugreports from ubuntu users
should go away.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813662
Title:
Cannot build VM
To manage notifications about this bug go to:
https://bugs.launchpad.net/libguestfs/+bug/1813662/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765726] Re: Optional dependencies are missing for Shutter in Ubuntu 18.04
Absolutely baffling that it is allowed for stuff like this to be removed without anyone considering the ramifications for the users... what is software without usefulness to its users? Anyway maybe the solution to this is an AppImage? Compile a binary with all dependent libs in the same folder and run the script. Run it directly regardless of what dist anyone is using. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765726 Title: Optional dependencies are missing for Shutter in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/shutter/+bug/1765726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576187] Re: backuppc/smb: BackupPC failes to backup SMB shares after smbclient update
Tested against a win2012 server, readonly SMB share. Working here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576187 Title: backuppc/smb: BackupPC failes to backup SMB shares after smbclient update To manage notifications about this bug go to: https://bugs.launchpad.net/backuppc/+bug/1576187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576187] Re: backuppc/smb: BackupPC failes to backup SMB shares after smbclient update
Thanks much - once PPA is up I can try spinning up a vanilla xenial and test this week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576187 Title: backuppc/smb: BackupPC failes to backup SMB shares after smbclient update To manage notifications about this bug go to: https://bugs.launchpad.net/backuppc/+bug/1576187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576187] Re: backuppc/smb: BackupPC failes to backup SMB shares after smbclient update
This is fixed in Bionic 18.04, however the parameter
"$Conf{BackupZeroFilesIsFatal} = 0" parameter for SMB Xfer, needs to be
changed for upgrading hosts that had it previously set to 1.
Relevant post at Debian bug #820693:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820963#82
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576187
Title:
backuppc/smb: BackupPC failes to backup SMB shares after smbclient
update
To manage notifications about this bug go to:
https://bugs.launchpad.net/backuppc/+bug/1576187/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576187] Re: backuppc/smb: BackupPC failes to backup SMB shares after smbclient update
This is still an issue in Bionic. It has been fixed upstream in 3.3.2 (Bionic currently is 3.3.1), see last post by upstream here: https://github.com/backuppc/backuppc/issues/21 Patch is here: https://github.com/backuppc/backuppc/pull/22 Looks like smbclient output was changed, which broke some regexes in BackupPC checking for success. ** Bug watch added: github.com/backuppc/backuppc/issues #21 https://github.com/backuppc/backuppc/issues/21 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576187 Title: backuppc/smb: BackupPC failes to backup SMB shares after smbclient update To manage notifications about this bug go to: https://bugs.launchpad.net/backuppc/+bug/1576187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1546108] Re: Latest Vagrant box for Ubuntu Xenial is failing to boot
Same, getting hard lockups on boot. Images from everywhere else work beautifully. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1546108 Title: Latest Vagrant box for Ubuntu Xenial is failing to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1546108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1315834] Re: 1002:983d [Acer Aspire V5-122P] Unable to adjust screen brightness using Radeon driver
Also Confirmed - vendor issue, not Ubuntu - BIOS upgrade fixed brightness / suspend issues as well for me. Everything now works flawlessly. A bit OT but in case others arrive here via google: the V5-122P BIOS updates *require* you to be running Windows 8 or newer. If you aren't dual booting into Windows, Acer forcing a Windows 8 binary in order to update the BIOS makes for a *very* bad day. FreeDOS does not work, not even WindowsPE on 32-bit works - it has to be Windows 8. Note being, when looking to buy hardware in the future not only will be googling linux compatability, but also checking to make sure the vendor is releasing BIOS patches which are easily installed using Linux as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315834 Title: 1002:983d [Acer Aspire V5-122P] Unable to adjust screen brightness using Radeon driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 540645] Re: no fsck messages shown in details mode (no splash on cmdline)
Fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/540645 Title: no fsck messages shown in details mode (no splash on cmdline) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/540645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 765735] Re: mountall should cause fsck to show progress on text console
Thanks Steve for taking the time to explain. This is exactly it - people think that plymouth is only annoying graphical stuff without realizing that upstart is replacing the System-V init entirely - already has for the symlinks in /etc/init.d. And the way upstart communicates with the display (text or graphical - does not matter) is through plymouth. Which is why if you do a hacked removal of plymouth, upstart jobs don't show up on the boot messages - only the old System-V jobs do. I have only ubuntu servers here but will take a look at desktop this week. If desktop has a progress bar during fscks, then I guess one approach might be to merge that with details so that we can toggle between them using esc? I don't think anybody would mind that much, so long as we have at least some way to get the progress info (graphical or otherwise). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/765735 Title: mountall should cause fsck to show progress on text console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/765735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 765735] mountall should cause fsck to show progress on text console
On Oct 9, 2012, at 2:46 PM, Steve Langasek steve.langa...@canonical.com wrote: On Tue, Oct 09, 2012 at 09:03:00PM -, Michael Neuffer wrote: Could you perhaps update your package to version 2.41? 2.42 now. Surprise, surprise. @Steve: Would you then consider picking up the change developped by Mark? I don't think this is the right way to address this issue. This really needs to happen transparently, without having to change any config files. I think the best way to address this would be a change to the plymouth details theme, to make it process fsck progress information the way the ubuntu theme does. I've browsed other bug reports and can responibly say that unless plymouth is removed as a a strong dependency from the mountall - it is HARMFUL TOWARD FREE _ FREE _ SOFTWARE. Admit it. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/765735 Title: mountall should cause fsck to show progress on text console Status in “mountall” package in Ubuntu: Triaged Bug description: Binary package hint: mountall mountall should cause fsck to show progress information (-C 0). Especially on large FS that take very long to fsck (sometimes many hours) it is very important to know that the fsck isn't actually hanging and still working. It is not possible to log in via console or ssh to check the status even for filesystems that are not boot- essential. Plymouth splash screen is disabled as this machine is a server. This behaviour has caused trouble several times already as the system was believed to be hanging and unresponsive and got rebooted while the fsck was still running. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: mountall 2.25ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Apr 19 11:51:06 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 LANGUAGE=en_US:en SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/765735/+subscriptions You've failed to consider your userbase; nobody cares. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/765735 Title: mountall should cause fsck to show progress on text console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/765735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 765735] Re: mountall should cause fsck to show progress on text console
I read some other thread regarding Ubuntu making plymouth a too-strong dependency. et. al., so I guesss this is our bug. Most importantly, this: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/556372 ...to which you ignored your users? And this: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553285 ...to which It's increasingly possible that you have bug reporters who are capable of what they are doing, yet thwarted by best approach methods determined by people who are looking out for their own best interests. Although I might not question your take, if you would like this to go away then your users would greatly appreciate an explicitly sound explanation as to why you've decided to ram plymouth, which apparently ignores the console, our throats. I've browsed at least a half-dozen other bug reports, some of them very long, which do not exist in debian systems. Although debian is a pain too, at least they are open about everything and those of us wiling and capable of modifying C code, are not unilaterally thrown into the dustbin. If someone at Canonical is willing to get onto a con-call regarding your userbase, I am happy to do so. This is an Ubuntu-specific bug. Politically saying, that freedom should extend to new users. Hiding the boot process behind a compiled C program is a BAD THING. Our users should always have the option to understand and learn from the boot process from any terminal. And this should be an easy thing for them to do. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/765735 Title: mountall should cause fsck to show progress on text console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/765735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 765735] Re: mountall should cause fsck to show progress on text console
TL;DR please give your users an exact explanation as to why you made plymouth such a strong dependency. This is ridiculous to those of us who don't understand the specifics which must be happening here. Please fully explain this decision. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/765735 Title: mountall should cause fsck to show progress on text console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/765735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 765735] Re: mountall should cause fsck to show progress on text console
And BTW, there are *multiple* bugs regarding crypsetup. To wit: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/556372 Is this correct? I see similar complaints nestled within a myriad of other bug threads similar to this one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/765735 Title: mountall should cause fsck to show progress on text console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/765735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 556372] Re: Please remove the plymouth dependency from mountall / cryptsetup
*nod* ... after only four years (not even one LTS cycle), we have begun the upgrade process back to debian. Debian testing appears to be much more stable than ubuntu these days. Less updates too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/556372 Title: Please remove the plymouth dependency from mountall / cryptsetup To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/556372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 599555] Re: no fsck progress displayed when booting without 'splash'
*** This bug is a duplicate of bug 540645 *** https://bugs.launchpad.net/bugs/540645 It *is* true, we can tap esc but no fsck progress is given. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/599555 Title: no fsck progress displayed when booting without 'splash' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/599555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 599555] Re: no fsck progress displayed when booting without 'splash'
*** This bug is a duplicate of bug 540645 *** https://bugs.launchpad.net/bugs/540645 Rants aside, I'm willing to look at the sources again and send a diff to support /etc/defaults/rcS line. We already change files all over the place for ubuntu - another option is no big deal. It's only two lines of C code so if someone is willing to put it in to shut us up, let me know. :-) Best -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/599555 Title: no fsck progress displayed when booting without 'splash' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/599555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 765735] Re: mountall should cause fsck to show progress on text console
Does the desktop theme on Precise provide a progress bar? If anyone can chime in, please do otherwise I'll test it myself later this week in a VM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/765735 Title: mountall should cause fsck to show progress on text console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/765735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 765735] Re: mountall should cause fsck to show progress on text console
Regarding this, I rebuilt a mountall package that fixed this bug and uploaded it to my PPA about two years ago. I added the --fsck-console option to mountall, and then added the option to enable this at boot time by adding the line FSCKCONSOLE=yes to /etc/defaults/rcS. From the changelog: * Added --fsck-console parameter to use console progress bar. To enable, add FSCKCONSOLE=yes to /etc/defaults/rcS. My PPA package is still sitting on Launchpad here: https://launchpad.net/~mark-syminet/+archive/syminet/+packages If this seems a good approach, I'm willing to spend the time to take a look at this again but only if someone is willing to consider getting it into the distribution, since I only want to use distribution packages on servers for critical boot-things like this. This really is a particularly nasty bug because servers can run for a long time without a power cut, etc. - but then that fateful day arrives and we are stuck without any idea if the remote machine is even hung, while bosses and customers are screaming about downtime demanding ETA's. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/765735 Title: mountall should cause fsck to show progress on text console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/765735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 540645] Re: no fsck messages shown in details mode (no splash on cmdline)
Regarding this, I rebuilt a mountall package that fixed this bug and uploaded it to my PPA about two years ago. I added the --fsck-console option to mountall, and then added the option to enable this at boot time by adding the line FSCKCONSOLE=yes to /etc/defaults/rcS. From the changelog: * Added --fsck-console parameter to use console progress bar. To enable, add FSCKCONSOLE=yes to /etc/defaults/rcS. My PPA package is still sitting on Launchpad here: https://launchpad.net/~mark-syminet/+archive/syminet/+packages If this seems a good approach, I'm willing to spend the time to take a look at this again but only if someone is willing to consider getting it into the distribution, since I only want to use distribution packages on servers for critical boot-things like this. This really is a particularly nasty bug because servers can run for a long time without a power cut, etc. - but then that fateful day arrives and we are stuck without any idea if the remote machine is even hung, while bosses and customers are screaming about downtime demanding ETA's. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/540645 Title: no fsck messages shown in details mode (no splash on cmdline) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/540645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 797544] Re: grub2 waits forever for keystroke before booting default OS. headless server. hang.
Horrible. We do not see this idiocy on Debian Systems, it is an UBUNTU problem. Apparently they re-packaged it without knowing what they are doing. Mint exists because why. Please make your changes much miloder, and concern yourself with the source. If they aren't doing it, then your new ideas shouldn't either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/797544 Title: grub2 waits forever for keystroke before booting default OS. headless server. hang. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/797544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 797544] Re: grub2 waits forever for keystroke before booting default OS. headless server. hang.
*milder ... sorry for the rant too but I've been venting awhile. I think many people have. Stop reinventing the wheel please and follow your own upstream - they already do most of the work for you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/797544 Title: grub2 waits forever for keystroke before booting default OS. headless server. hang. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/797544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523896] Re: useradd: cannot lock /etc/passwd; try again later.
I suspect this is related to the mountall binary package? Which deserves to be condemned to all hell. How DARE the packagers INFECT a distribution with a binary upon startup, other than the kernel? The only binary code upon turning on any computer, should be the kernel. Everything else is utterly disgusting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/523896 Title: useradd: cannot lock /etc/passwd; try again later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/523896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 523896] Re: useradd: cannot lock /etc/passwd; try again later.
I could fix this myself if it wasn't for unbelievably ridiculous shit like this: On Ubuntu: root@38r8:~# set |wc -l 6705 …on standard Debian: 4r6s1:~# set | wc -l 50 4r6s1:~# …really? *Really*? On Sep 23, 2012, at 4:50 PM, Dmitrijs Ledkovs wrote: On 23 September 2012 23:43, larrycornutt larrycorn...@yahoo.com wrote: ** Changed in: shadow (Ubuntu Precise) Status: Fix Committed = Fix Released No, it was not. The package in precise-proposed and is still pending verification. If it passes verification that the bug will be fix released in precise, if verification will not be passed the package with this fixed will be removed from precise-proposed. Please help to verify this update as outlined in comment #30 above. URL: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/523896/comments/30 Regards, Dmitrijs. ** Changed in: shadow (Ubuntu Quantal) Status: Fix Released = Fix Committed -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/523896 Title: useradd: cannot lock /etc/passwd; try again later. Status in “shadow” package in Ubuntu: Fix Committed Status in “shadow” source package in Precise: Fix Released Status in “shadow” source package in Quantal: Fix Committed Bug description: Binary package hint: postfix Ubuntu 9.10, via Update Manager. SOLUTION: Look for /etc/group.lock, /etc/passwd.lock and /etc/shadow.lock files and remove them. Be careful to only remove the files ending in 'lock' or else you might damage your system. Please do not add comments just containing Me too, instead please provide any information that could indicate why the files were locked: * the list of locked files: ls /etc/passwd.lock /etc/shadow.lock /etc/group.lock /etc/gshadow.lock * check the /var/log/auth.log for any message that could indicate the failure of any other tool (prior to the failure which reported the locked file) * any abnormal operation on the machine (reset, shutdown while the computer is still running) == SRU template == [IMPACT] * Locked files prevent adding/removing/modifying system users groups * This can result in failure to upgrade/remove packages that use system user names * The applied fix is to clear the locks on booting. [TESTCASE] * $ sudo touch /etc/passwd.lock * $ sudo adduser testing523896 * FAIL * Upgrade to new package * $ sudo adduser testing523896 * FAIL * $ sudo reboot (or shutdown poweron machine in any other way) * $ sudo adduser testing523896 * PASS * Also you can touch the locks, check that they are there and run `$ sudo start passwd` to clear them. [Regression Potential] * We are adding an extra job which will always run at boot, which will have a tiny impact on boot performance * The new job can be mis-used directly via `$ sudo start passwd`, but root user could clear the locks in the exact same way as well, before introducing this upstart job. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/523896/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/523896 Title: useradd: cannot lock /etc/passwd; try again later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/523896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523896] Re: useradd: cannot lock /etc/passwd; try again later.
Just got bit by this one again, clean lucid install. The fix is to rm -f /etc/gshadow.lock. sudo do-release-upgrade finishes with this: The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). Setting up dbus (1.4.18-1ubuntu1) ... groupadd: cannot lock /etc/gshadow; try again later. adduser: `/usr/sbin/groupadd -g 112 messagebus' returned error code 10. Exiting. dpkg: error processing dbus (--configure): subprocess installed post-installation script returned error exit status 1 Setting up whoopsie (0.1.32) ... groupadd: cannot lock /etc/gshadow; try again later. adduser: `/usr/sbin/groupadd -g 112 whoopsie' returned error code 10. Exiting. dpkg: error processing whoopsie (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of language-selector-common: language-selector-common depends on dbus; however: Package dbus is not configured yet. dpkg: error processing language-selector-common (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of ubuntu-standard: ubuntu-standard depends on language-selector-common; however: Package language-selector-common is not configured yet. dpkg: error processing ubuntu-standard (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of accountsservice: accountsservice depends on dbus; however: Package dbus is not configured yet. dpkg: error processing accountsservice (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: dbus whoopsie language-selector-common ubuntu-standard accountsservice Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER] -- ...'x' to get out of it, then: root@asdf:~# cd /etc root@asdf:/etc# ls -l *lock ls: unrecognized prefix: hl ls: unparsable value for LS_COLORS environment variable -rw--- 1 root root 0 Aug 14 16:41 gshadow.lock root@asdf:/etc# lsof gshadow.lock root@asdf:/etc# rm -f gshadow.lock root@asdf:/etc# apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 5 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue [Y/n]? Setting up dbus (1.4.18-1ubuntu1) ... dbus start/running, process 4465 Setting up accountsservice (0.6.15-2ubuntu9.3) ... Setting up language-selector-common (0.79) ... Installing new version of config file /etc/fonts/conf.avail/69-language-selector-zh-tw.conf ... Installing new version of config file /etc/fonts/conf.avail/69-language-selector-ja-jp.conf ... Installing new version of config file /etc/fonts/conf.avail/30-cjk-aliases.conf ... Removing obsolete conffile /etc/fonts/conf.avail/69-language-selector-ko-kr.conf ... Removing obsolete conffile /etc/fonts/conf.avail/29-language-selector-ko-kr.conf ... Setting up whoopsie (0.1.32) ... whoopsie start/running, process 4562 Setting up ubuntu-standard (1.267) ... root@asdf:/etc# ...I've replicated this three times in a row now on kvm guests,happy to run any commands on this side and post results here if that would be useful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/523896 Title: useradd: cannot lock /etc/passwd; try again later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/523896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004606] Re: virsh create-snapshot fails to create external snapshot
Same exact errors here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004606 Title: virsh create-snapshot fails to create external snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1004606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 670526] Re: phpmyadmin broken after hardy - lucid upgrade
OK - thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common in Ubuntu. https://bugs.launchpad.net/bugs/670526 Title: phpmyadmin broken after hardy - lucid upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/670526/+subscriptions -- 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 670526] Re: phpmyadmin broken after hardy - lucid upgrade
OK - thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/670526 Title: phpmyadmin broken after hardy - lucid upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/670526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881079] Re: FIXED: spurious Waiting up to 60 more seconds for network configuration message at startup, but all network devices are up
Hello Clint, going to have to say user error on this one apologies for the false alarm - someone had a line in a script that was changing stuff in /etc/udev which bonked things. Did a fresh Precise reinstall from the mini.iso and no issues, also a Lucid - Precise upgrade to confirm and indeed... no issues. Apologies for the false alarm! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881079 Title: FIXED: spurious Waiting up to 60 more seconds for network configuration message at startup, but all network devices are up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-common/+bug/881079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 765735] Re: mountall should cause fsck to show progress on text console
Still no progress bar in Precise. This really is bad, particularly on server because we get stuck with very long fscks on large disks and the progress bar is critical during unexpected downtimes. We need to be able to provide at least rough ETA's for our bosses/customers, and have assurance the system isn't hung. I took a look at mountall.c and the following change restored the bar: 2247c2247 arg = NIH_MUST (nih_sprintf (NULL, -C%d, fds[1])); --- arg = NIH_MUST (nih_sprintf (NULL, -C, fds[1])); ...although I can see how this would obviously not work in the distribution, is there something we can do to restore the progress bar? Looking through the code, it shouldn't be hard to implament (e.g. a setting in /etc/default/rcS). ** Patch added: mountall.patch https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/765735/+attachment/2651043/+files/mountall.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/765735 Title: mountall should cause fsck to show progress on text console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/765735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 540645] Re: no fsck messages shown in details mode (no splash on cmdline)
Still no progress bar in Precise... possible xref bug 765735 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/540645 Title: no fsck messages shown in details mode (no splash on cmdline) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/540645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881079] Re: FIXED: spurious Waiting up to 60 more seconds for network configuration message at startup, but all network devices are up
I'm getting exactly these symptoms after a test upgrade from vanilla Lucid - Precise. Upon reboot, the iface is indeed reachable and I can ssh into it within about 10 seconds but on the monitor it says Waiting up to 60 more seconds for network configuration... error, and hangs there for a full minute. The /etc/network/interfaces contains all necessary info, worked perfectly fine in Lucid, and the interface is indeed reachable the whole time: root@19r8s12:/etc# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 54:52:00:08:ea:ee inet addr:192.168.1.181 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::5652:ff:fe08:eaee/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:377 errors:0 dropped:0 overruns:0 frame:0 TX packets:122 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:27347 (27.3 KB) TX bytes:16381 (16.3 KB) Interrupt:10 Base address:0x6000 root@19r8s12:/etc# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet static address 192.168.1.181 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.1 root@19r8s12:/etc# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881079 Title: FIXED: spurious Waiting up to 60 more seconds for network configuration message at startup, but all network devices are up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-common/+bug/881079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 847782] Re: installer writes a permanent ethernet entry in interfaces file
We have servers which are all automatically configured by adding simple static entries to /etc/network/interfaces. Upon reboot, it's network reachable within about ten seconds while the monitor is hung saying, Waiting 60 more seconds for network configuration... - but it is pingable and accepting ssh connections with no problems. Commenting out the sleep stanzas worked here also, but it would be far better if the test checked properly and didn't start sleeping when everything was up. Either that or maybe something in /etc/default to tell it not to check period, I will maintain my own interfaces file. Here's an example interfaces file, I think this is all syntactically correct?: root@19r8s12:/etc# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet static address 192.168.1.181 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.1 root@19r8s12:/etc# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/847782 Title: installer writes a permanent ethernet entry in interfaces file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/847782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 582145] Re: Virtual guests' console is unusably slow due to framebuffer usage
sorry, that should be add this line to /etc/modprobe.d/blacklist- framebuffer.conf : blacklist vga16fb ...superfast VM console now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/582145 Title: Virtual guests' console is unusably slow due to framebuffer usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/582145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 582145] Re: Virtual guests' console is unusably slow due to framebuffer usage
Same problem here. Workaround was to add the following line to /etc/modprobe.d/blacklist.conf: blacklist vga16fb reboot, and vnc works as it should. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/582145 Title: Virtual guests' console is unusably slow due to framebuffer usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/582145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 599342] Re: Temporary failure in name resolution
@Serge correct - for security (and portability) reasons, we've decided to run ssh only and nothing else on the hosts - all other services run on guests - so the host is using one of it's own guests as it's DNS server. It's backup nameservers are on different hosts which are usually up, so we never noticed this issue - but this time, they were not available at the moment we rebooted. The result was all guests failed to start. For now, we've just updated /etc/hosts on each machine to make sure they automatically resolve themselves even without nameservice - this seems to be a decent workaround for now. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/599342 Title: Temporary failure in name resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/599342/+subscriptions -- 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 599342] Re: Temporary failure in name resolution
@Serge correct - for security (and portability) reasons, we've decided to run ssh only and nothing else on the hosts - all other services run on guests - so the host is using one of it's own guests as it's DNS server. It's backup nameservers are on different hosts which are usually up, so we never noticed this issue - but this time, they were not available at the moment we rebooted. The result was all guests failed to start. For now, we've just updated /etc/hosts on each machine to make sure they automatically resolve themselves even without nameservice - this seems to be a decent workaround for now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/599342 Title: Temporary failure in name resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/599342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 599342] Re: Temporary failure in name resolution
But what if your DNS servers, are also your guests? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/599342 Title: Temporary failure in name resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/599342/+subscriptions -- 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 599342] Re: Temporary failure in name resolution
Might stand to rephrase: What if your DNS servers, are your guests? And btw? Thanks for all you do. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/599342 Title: Temporary failure in name resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/599342/+subscriptions -- 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 599342] Re: Temporary failure in name resolution
But what if your DNS servers, are also your guests? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/599342 Title: Temporary failure in name resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/599342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 599342] Re: Temporary failure in name resolution
Might stand to rephrase: What if your DNS servers, are your guests? And btw? Thanks for all you do. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/599342 Title: Temporary failure in name resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/599342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 604335] Re: grub-pc.postinst script fails to detect virtio vda disk in KVM guest
I can't believe you guys actually blackholed stdout during fsck... I updated the code for this to provide for a status bar, like it should be with e2fsck -C0 -y as its been since like, forever: https://launchpad.net/~mark-syminet/+archive/syminet ...not applying this to any machine, for obvious reasons but would like to see this option in /etc/default/grub for reasons which should be obvious. The diffs are simple two-liners. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/604335 Title: grub-pc.postinst script fails to detect virtio vda disk in KVM guest -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550028] Re: Dell Mini 9 Hibernate does not work
You can't cross reference and/or reassign this bug over to the proper place for them? I am having same issue here... back to google I go... -- Dell Mini 9 Hibernate does not work https://bugs.launchpad.net/bugs/550028 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 550028] Re: Dell Mini 9 Hibernate does not work
Possible cross reference bug #477106: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/477106 -- Dell Mini 9 Hibernate does not work https://bugs.launchpad.net/bugs/550028 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 670526] Re: phpmyadmin broken after hardy - lucid upgrade
OK thanks, the fix I posted worked easily enough over here. I might mention that I was using a /root/.my.cnf for auto-login to mysql. When being asked questions by dbconfig I leave the passwd blank and usually that seems to work just fine. So if you aren't hearing this from others, then maybe I chmodded the file or something while working and didn't realize. -- phpmyadmin broken after hardy - lucid upgrade https://bugs.launchpad.net/bugs/670526 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dbconfig-common 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 670526] Re: phpmyadmin broken after hardy - lucid upgrade
OK thanks, the fix I posted worked easily enough over here. I might mention that I was using a /root/.my.cnf for auto-login to mysql. When being asked questions by dbconfig I leave the passwd blank and usually that seems to work just fine. So if you aren't hearing this from others, then maybe I chmodded the file or something while working and didn't realize. -- phpmyadmin broken after hardy - lucid upgrade https://bugs.launchpad.net/bugs/670526 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 670541] Re: Upgrade mysql5.0 - 5.1 fails due to error on postrm script.
Hello, sure, here you go (I removed my exit 0; at the top):
=== snip ===
#!/bin/bash -e
# It is possible that Debconf has already been removed, too.
if [ -f /usr/share/debconf/confmodule ]; then
. /usr/share/debconf/confmodule
fi
if [ -n $DEBIAN_SCRIPT_DEBUG ]; then set -v -x; DEBIAN_SCRIPT_TRACE=1; fi
${DEBIAN_SCRIPT_TRACE:+ echo #42#DEBUG# RUNNING $0 $* 12 }
MYADMIN=/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf
# Try to stop the server in a sane way. If it does not success let the admin
# do it himself. No database directories should be removed while the server
# is running!
stop_server() {
set +e
if [ -x /usr/sbin/invoke-rc.d ]; then
invoke-rc.d mysql stop
else
/etc/init.d/mysql stop
fi
errno=$?
set -e
if [ $? != 0 ]; then
echo Trying to stop the MySQL server resulted in exitcode $?. 12
echo Stop it yourself and try again! 12
exit 1
fi
}
case $1 in
purge|remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
if [ -n `$MYADMIN ping 2/dev/null` ]; then
# stop_server
# sleep 2
fi
;;
*)
echo postrm called with unknown argument '$1' 12
exit 1
;;
esac
# Remove Debconf generated config files to allow clean upgrades to 5.1.
rm -f /etc/mysql/conf.d/old_passwords.cnf
#
# - Do NOT purge logs or data if another mysql-sever* package is installed
(#307473)
# - Remove the mysql user only after all his owned files are purged.
#
if [ $1 = purge -a ! \( -x /usr/sbin/mysqld -o -L /usr/sbin/mysqld \) ];
then
# we remove the mysql user only after all his owned files are purged
rm -f
[Bug 670541] Re: Upgrade mysql5.0 - 5.1 fails due to error on postrm script.
Hello, sure, here you go (I removed my exit 0; at the top):
=== snip ===
#!/bin/bash -e
# It is possible that Debconf has already been removed, too.
if [ -f /usr/share/debconf/confmodule ]; then
. /usr/share/debconf/confmodule
fi
if [ -n $DEBIAN_SCRIPT_DEBUG ]; then set -v -x; DEBIAN_SCRIPT_TRACE=1; fi
${DEBIAN_SCRIPT_TRACE:+ echo #42#DEBUG# RUNNING $0 $* 12 }
MYADMIN=/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf
# Try to stop the server in a sane way. If it does not success let the admin
# do it himself. No database directories should be removed while the server
# is running!
stop_server() {
set +e
if [ -x /usr/sbin/invoke-rc.d ]; then
invoke-rc.d mysql stop
else
/etc/init.d/mysql stop
fi
errno=$?
set -e
if [ $? != 0 ]; then
echo Trying to stop the MySQL server resulted in exitcode $?. 12
echo Stop it yourself and try again! 12
exit 1
fi
}
case $1 in
purge|remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
if [ -n `$MYADMIN ping 2/dev/null` ]; then
# stop_server
# sleep 2
fi
;;
*)
echo postrm called with unknown argument '$1' 12
exit 1
;;
esac
# Remove Debconf generated config files to allow clean upgrades to 5.1.
rm -f /etc/mysql/conf.d/old_passwords.cnf
#
# - Do NOT purge logs or data if another mysql-sever* package is installed
(#307473)
# - Remove the mysql user only after all his owned files are purged.
#
if [ $1 = purge -a ! \( -x /usr/sbin/mysqld -o -L /usr/sbin/mysqld \) ];
then
# we remove the mysql user only after all his owned files are purged
rm -f
[Bug 649591] Re: mountall spins eating cpu when 'nobootwait' option exists in fstab followed by a comma
What Ingo said - for servers, not having a console progress bar is *terrible*, since for servers we often aren't physically there. So even with e.g. remote VNC access we get nothing but a blank screen and have no idea if it's actually even doing a fsck, or locked up for some other reason. All of this while customers are calling frantically screaming at us because their server is down. As a stopgap we're now booting them into rescue mode from external media and running the fscks manually, but all of this causes unnecessary hassle, stress and increased downtime. Would be much nicer to have our progress bar back like we always had before. -- mountall spins eating cpu when 'nobootwait' option exists in fstab followed by a comma https://bugs.launchpad.net/bugs/649591 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 670541] [NEW] Upgrade mysql5.0 - 5.1 fails due to error on postrm script.
Public bug reported: Binary package hint: mysql-server-5.1 Hardy - Lucid upgrade, after which phpmyadmin warns about mysql-server5.0 whereas the php library is 5.1 and thus conflicts. OK, lets upgrade - but mysql upgrade fails due to what looks like a typo in the postrm script: === Preconfiguring packages ... (Reading database ... 40610 files and directories currently installed.) Removing mysql-server-5.0 ... * Stopping MySQL database server mysqld ...done. /var/lib/dpkg/info/mysql-server-5.0.postrm: line 38: syntax error near unexpected token `fi' dpkg: error processing mysql-server-5.0 (--remove): subprocess installed post-removal script returned error exit status 2 Removing mysql-client-5.0 ... Processing triggers for man-db ... Processing triggers for ureadahead ... ureadahead will be reprofiled on next reboot Errors were encountered while processing: mysql-server-5.0 E: Sub-process /usr/bin/dpkg returned an error code (1) r...@28r6s1:/etc/apache# === For me, the quick fix was to edit /var/lib/dpkg/info/mysql-server-5.0.postrm shellscript and simply make this the first line: exit 0; ...hopefully this didn't cause some sort of breakage that will bite us at some indeterminable point in the future. But it at least got the critical mysql service running again on that server. ** Affects: mysql-5.1 (Ubuntu) Importance: Undecided Status: New -- Upgrade mysql5.0 - 5.1 fails due to error on postrm script. https://bugs.launchpad.net/bugs/670541 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-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 670526] [NEW] phpmyadmin broken after hardy - lucid upgrade
Public bug reported: Binary package hint: phpmyadmin Lucid: 4:3.3.2-1 After upgrade hardy - lucid phpmyadmin complains that controluser is invalid and logins fail. These commands fixed it: dpkg --purge phpmyadmin apt-get install phpmyadmin However more bugs/errors/warnings after being able to login... will post those next. This has happened three times in a row on three different servers. ** Affects: phpmyadmin (Ubuntu) Importance: Undecided Status: New -- phpmyadmin broken after hardy - lucid upgrade https://bugs.launchpad.net/bugs/670526 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 670533] [NEW] Hardy - Lucid upgrade: Connection for controluser as defined in your configuration failed.
Public bug reported: Binary package hint: phpmyadmin Lucid: 4:3.3.2-1 Upgrade Hardy - Lucid. Try to restart with fresh install: dpkg --purge phpmyadmin drop phpmyadmin database apt-get install phpmyadmin But upon login this message appears at the bottom of the screen in glaring red banner which scares users of the server and makes them complain. Solution was to get the correct information from /etc/phpmyadmin/config-db.php and then mysql -u root mysql grant all on phpmyadmin.* to 'phpmyadmin'@'localhost' identified by 'MY_PASSWORD'; Query OK, 0 rows affected (0.00 sec) mysql flush permissions; ...error message disappeared. ** Affects: phpmyadmin (Ubuntu) Importance: Undecided Status: New -- Hardy - Lucid upgrade: Connection for controluser as defined in your configuration failed. https://bugs.launchpad.net/bugs/670533 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 670541] [NEW] Upgrade mysql5.0 - 5.1 fails due to error on postrm script.
Public bug reported: Binary package hint: mysql-server-5.1 Hardy - Lucid upgrade, after which phpmyadmin warns about mysql-server5.0 whereas the php library is 5.1 and thus conflicts. OK, lets upgrade - but mysql upgrade fails due to what looks like a typo in the postrm script: === Preconfiguring packages ... (Reading database ... 40610 files and directories currently installed.) Removing mysql-server-5.0 ... * Stopping MySQL database server mysqld ...done. /var/lib/dpkg/info/mysql-server-5.0.postrm: line 38: syntax error near unexpected token `fi' dpkg: error processing mysql-server-5.0 (--remove): subprocess installed post-removal script returned error exit status 2 Removing mysql-client-5.0 ... Processing triggers for man-db ... Processing triggers for ureadahead ... ureadahead will be reprofiled on next reboot Errors were encountered while processing: mysql-server-5.0 E: Sub-process /usr/bin/dpkg returned an error code (1) r...@28r6s1:/etc/apache# === For me, the quick fix was to edit /var/lib/dpkg/info/mysql-server-5.0.postrm shellscript and simply make this the first line: exit 0; ...hopefully this didn't cause some sort of breakage that will bite us at some indeterminable point in the future. But it at least got the critical mysql service running again on that server. ** Affects: mysql-5.1 (Ubuntu) Importance: Undecided Status: New -- Upgrade mysql5.0 - 5.1 fails due to error on postrm script. https://bugs.launchpad.net/bugs/670541 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 670549] [NEW] The additional features for working with linked tables have been deactivated. To find out why click here.
Public bug reported: Binary package hint: phpmyadmin Lucid: 4:3.3.2-1 Hardy - Lucid upgrade, tried a fresh install with dpkg --purge phpmyadmin drop database phpmyadmin apd-get install phpmyadmin But we are still greeted by a scary red warning banner at the bottom of the phpmyadmin login page: The additional features for working with linked tables have been deactivated. To find out why click here. The error message is a link, click it and all is OK except this: $cfg['Servers'][$i]['tracking'] ... not OK [ Documentation ] Tracking: Disabled ...looking at file /etc/phpmyadmin/config.inc.php: === /* Optional: Advanced phpMyAdmin features */ $cfg['Servers'][$i]['pmadb'] = $dbname; $cfg['Servers'][$i]['bookmarktable'] = 'pma_bookmark'; $cfg['Servers'][$i]['relation'] = 'pma_relation'; $cfg['Servers'][$i]['table_info'] = 'pma_table_info'; $cfg['Servers'][$i]['table_coords'] = 'pma_table_coords'; $cfg['Servers'][$i]['pdf_pages'] = 'pma_pdf_pages'; $cfg['Servers'][$i]['column_info'] = 'pma_column_info'; $cfg['Servers'][$i]['history'] = 'pma_history'; $cfg['Servers'][$i]['designer_coords'] = 'pma_designer_coords'; === ...looking at local phpmyadmin database and see that the table pma_tracking does indeed exist. The following line appears to be missing, so we add it: $cfg['Servers'][$i]['tracking'] = 'pma_tracking'; LOG OUT of phpmyadmin to make changes take effect, log back in and error message is gone. ** Affects: phpmyadmin (Ubuntu) Importance: Undecided Status: New -- The additional features for working with linked tables have been deactivated. To find out why click here. https://bugs.launchpad.net/bugs/670549 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 516684] Re: After upgrade from Karmic boot fails, mountall and udevd fail
Same problem here. If the newer kernel is required, then why isn't it a dependency when going from Hardy - Lucid? -- After upgrade from Karmic boot fails, mountall and udevd fail https://bugs.launchpad.net/bugs/516684 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 604335] Re: grub-pc.postinst script fails to detect virtio vda disk in KVM guest
Same here - switched a few kvm guests from ide - virtio disks. Ran apt-get upgrade and voila, broken packaging system. The patch provided by nutznboltz up there solved the issue. -- grub-pc.postinst script fails to detect virtio vda disk in KVM guest https://bugs.launchpad.net/bugs/604335 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 331944] Re: roundcube-core requires php-mdb2
What Sam said. php-mdb2 installed OK but it isn't enough - additional packages are required depending upon which DB you're using: php-mdb2 - PHP PEAR module to provide a common API for supported RDBMS php-mdb2-driver-mysql - PHP PEAR module to provide a MySQL driver for MDB2 php-mdb2-driver-pgsql - PHP PEAR module to provide a PostgreSQL driver for MDB2 php-mdb2-driver-sqlite - PHP PEAR module to provide a SQLite driver for MDB2 Since we're using mysql here, apt-get install php-mdb2-driver-mysql got it working - but the installer scripts should ask which DB is being used and include that as a dependency, otherwise the roundcube installs unusable. -- roundcube-core requires php-mdb2 https://bugs.launchpad.net/bugs/331944 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 331944] Re: roundcube-core requires php-mdb2
OK, so what's happening is that people are doing apt-get install roundcube. When they go through dbconfig-common to configure their database for mysql, it's implicit that roundcube knows it's supposed to be using mysql - but it wants to use sqlite. Looking closer, it's obvious now but not when installing without knowing any of this - it would be great if the postinst said You need to install one of these metapackages now:, or even a simple /usr/share/doc/roundcube/README.Debian that mentions this would have saved the day here. :-) Anyway problem solved - thanks much for the insight. -- roundcube-core requires php-mdb2 https://bugs.launchpad.net/bugs/331944 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 589307] Re: Wrong compilation of asterisk-mp3
shitty solution. WWhy are you7 here? -- Wrong compilation of asterisk-mp3 https://bugs.launchpad.net/bugs/589307 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 589307] Re: Wrong compilation of asterisk-mp3
Same error here, upgrading from karmic - lucid all of our music on hold files went silent. Worked around this here by converting the mp3's to .sln files: apt-get remove asterisk-mp3 apt-get install sox libsox-fmt-all mpg321 # convert mp3 to wav mpg321 -w myfile.mp3 myfile.wav # convert wav to sln sox myfile.wav -t raw -r 8000 -s -c1 myfile.sln The -c1 up there is important if your mp3 is stereo. If you care more about filesize than sound quality you can convert them to GSM instead: sox unknown.wav -r 8000 -c1 unknown.gsm Best -- Wrong compilation of asterisk-mp3 https://bugs.launchpad.net/bugs/589307 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 523896] Re: useradd: cannot lock /etc/passwd; try again later.
I had the same situation here, it turns out it was a stuck useradd process - destroying it got useradd working again, something like this: killall -9 userdel rm -f /etc/*lock In my case the stuck useradd was caused by a bug in my own script, but for the others, if it was caused by the package manager then I guess there might be a package out there with a bug in it's call to useradd. -- useradd: cannot lock /etc/passwd; try again later. https://bugs.launchpad.net/bugs/523896 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 429510] Re: package dahdi 1:2.2.0-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Same here. Installing dahdi-linux by hand first worked for me: apt-get install dahdi-linux ...then install asterisk and it was ok so seems to be something in the order in which it's installing packages. It's a different bug, no time to check but also had the following happen: r...@7r6s1:/var/log/asterisk# invoke-rc.d asterisk restart Stopping Asterisk PBX: asterisk. Asterisk PBX is already running. Use restart. r...@7r6s1:/var/log/asterisk# ...issuing the command again brought it up OK maybe it needs a sleep(1) or something. -- package dahdi 1:2.2.0-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/429510 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 429867] Re: runlevel arguments (none) do not match LSB Default-Start values (0 6)
Same here: Do you want to continue [Y/n]? Preconfiguring packages ... (Reading database ... 45584 files and directories currently installed.) Preparing to replace unattended-upgrades 0.52ubuntu1 (using .../unattended-upgrades_0.52ubuntu1_all.deb) ... Unpacking replacement unattended-upgrades ... Processing triggers for man-db ... Setting up unattended-upgrades (0.52ubuntu1) ... update-rc.d: warning: unattended-upgrades start runlevel arguments (none) do not match LSB Default-Start values (0 6) update-rc.d: warning: unattended-upgrades stop runlevel arguments (0 6) do not match LSB Default-Stop values (none) r...@3r6s1:/home/mark# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=9.10 DISTRIB_CODENAME=karmic DISTRIB_DESCRIPTION=Ubuntu 9.10 r...@3r6s1:/home/mark# -- runlevel arguments (none) do not match LSB Default-Start values (0 6) https://bugs.launchpad.net/bugs/429867 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
