Public bug reported:
Booted up the Live installer of today's build (20240325) and I see the
double network panel icon in the top panel. First time I have seen this
on a Live or clean installation. I have only seen it with LTS upgraded
Xubuntu installations.
ProblemType: Bug
DistroRelease: Ubuntu
Beta testing Xubuntu Noble currently, this defect still is present when
shutting down the Live DVD image. I am testing in a VirtualBox VM
instance.
Why is taking so much time (so many releases) to finally resolve this?
--
You received this bug notification because you are a member of Ubuntu
Bugs
@corrado
So how is it expected to launch the Xubuntu 24.04 installation? It is
expected to have to enter a command such as above into a Terminal?
We need further instructions from the Xubuntu team. Blocker defect for
now.
--
You received this bug notification because you are a member of Ubuntu
Thank you, Rod!
Booted to Xubuntu 22.04 LiveDVD
BIOS has UEFI disabled
xubuntu@xubuntu:/sys/firmware$ ls -al
total 0
drwxr-xr-x 5 root root 0 Apr 23 12:32 .
dr-xr-xr-x 13 root root 0 Apr 23 12:32 ..
drwxr-xr-x 5 root root 0 Apr 23 12:33 acpi
drwxr-xr-x 3 root root 0 Apr 23 12:33 dmi
drwxr-xr-x
Perhaps has the EFI / UEFI BIOS compatibility changed over time?
Finally boot success using a ThinkPad T540p model 20BE-CT01WW and the
Xubuntu 20220402 Daily jammy-desktop-2022-04-02-amd64.iso
Manual partitions as follows:
sda1 1MB BIOS BOOT
sda2 500MB EFI System
sda3 the rest / xfs
So se
With the same Xubuntu 20220402 Daily jammy-desktop-2022-04-02-amd64.iso
I thought to do an automatic partitioning installation. I knew I would
not end up with a XFS formatted root partition, but a booting system
with gpt partition table would be better than a non-booting system.
The installer crea
I just rechecked the behavior of Xubuntu 20.04.0 LTS. That LiveDVD
installer disk stayed in graphics mode as it shut down. There was an
Xubuntu logo in the middle of the screen, and the text displayed at the
bottom of the screen.
Contrasting with Xubuntu 22.04 on the same exact system, the LiveDVD
** Summary changed:
- Jammy Live installer not producing booting EFI hard drive installations
+ Jammy Live installer not producing booting gpt partition table / EFI
partition hard drive installations
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Still present in Xubuntu 20220402 Daily jammy-
desktop-2022-04-02-amd64.iso
This morning I pulled down the daily build, burned it to a DVD.
I began by wiping the previous partitions, allowed the installer to guide me
through creating:
500 MB EFI partition
The rest XFS mounted /
No complaints fr
Still present in Xubuntu 20220402 Daily jammy-
desktop-2022-04-02-amd64.iso
!Warning
Unable to read the contents of this file system!
Because of this some operations may be unavailable.
The cause might be a missing software package.
The following list of software packages is required for fat32 fil
I just pulled down Xubuntu jammy-desktop-2022-04-02-amd64.iso
Clean wiped drive installation, same behavior persists... blank screen
with blinking cursor, no "Please remove the installation medium, then
press ENTER:" text displayed.
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1944519 ***
https://bugs.launchpad.net/bugs/1944519
@Sean Davis, Nay no issue with Ubuntu Server. What I was saying is
Ubuntu Server correctly displays the text that Xubuntu used to have. Go
look at Ubuntu Server for a working example.
Good to know this is a
I managed to get to the end finally on a Jammy Server installation. So
the text there is as follows:
Please remove the installation medium, then press ENTER:
Unmounting /cdrom...
[FAILED] Failed unmounting /cdrom.
(But the drive actually ejected as expected.)
--
You received this bug notificati
Public bug reported:
I found that the jammy-live-server-2022-03-10-amd64.iso is not able to
set up the NIC to use IPv4 Static, nor be switched back to DHCP once
Static addressing has been attempted.
I started an UbuntuForums thread here to seek confirmation if it sounded
like there was a defect,
Confirmed that the current daily of Jammy Ubuntu Server does not share
this defect. Good!
Ubuntu Server properly displays the console text shutdown... and the
machine just up and rebooted itself as I was here trying to type exactly
what the message should be! Doh! Oh well, lost it for now. Point
r
Public bug reported:
A while ago we identified and had resolved an issue with Gigolo being
able to connect via bookmarks to a Samba server over smb / CIFS. That
was as follows:
Gigolo tries to use port 21 for SMB/CIFS connect
https://bugs.launchpad.net/bugs/1854137
So this was found working with
This morning I reloaded the computer again, selecting gpt versus dos for
the partition table. I made the EFI and XFS partitions. The installer
did not protest, and the resulting system will not boot. I reloaded it
back to a single xfs root partition on a dos partition table, that
boots.
Something
All right, significant more testing... about 10 drive wipe reloads of
this test system. Finally I got the Xubuntu DVD from this past weekend
to produce a bootable HDD.
Some of the failed attempts were:
BIOS UEFI enabled
gpt partition table
500MB EFI partition first
All the rest XFS partition
BIOS
Greetings Steve,
I prefer XFS filesystem. As much as I understand, the only way to get
Ubuntu / Xubuntu to use XFS is to do manual partitioning.
With legacy partitioning, then lately (past several versions) Ubuntu has
been able to boot directly from XFS. Back around 2004/5 range, it was
required
Public bug reported:
Starting up this weekend's Live DVD of Xubuntu, I am unable to produce a
system that will boot EFI mode from the hard disk.
The BIOS is configured to EFI boot mode for the disks.
This last attempt, I manually wiped the partitions from the drive before
launching the installer
Public bug reported:
Starting up this weekend's Live DVD of Xubuntu, trying to inspect the
partitions on the drive using Gparted, it complains it wants package
mtools added in order to display EFI partition correctly.
I exit Gparted, add it to the Live session via:
sudo apt-get install mtools
On
Public bug reported:
Beta testing the Xubuntu Jammy daily DVD this weekend, I find that it
still does not display any "press a key to continue" once the
installation finishes, it shuts down, ejects the DVD... instead left
with a completely black screen and blinking cursor in the top left
corner.
I confirmed this defect is still present in a test computer loaded with
the current nightly beta of Xubuntu 22.04. I copied with Thunar a small
178 byte shell script file between the local test machine's drive and
the Samba server over the usual Samba mount. The copy progress dialog
box will not go
Yes Bob, I knew convert is a part of ImageMagick. I was having
difficulty locating the correct package within this bug tracker.
Thanks for explaining how to show what resources convert is allowed to
use. Following is the output from my three systems:
Xubuntu 16.04:
$ convert -list resource
File
** Attachment added: "Output from Xubuntu 22.04 system"
https://bugs.launchpad.net/ubuntu/+source/graphicsmagick/+bug/1956642/+attachment/5552241/+files/Xubuntu_22.04.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Attachment added: "Output from Xubuntu 20.04 system"
https://bugs.launchpad.net/ubuntu/+source/graphicsmagick/+bug/1956642/+attachment/5552240/+files/Xubuntu_20.04.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Attachment added: "Output from Xubuntu 16.04 system"
https://bugs.launchpad.net/ubuntu/+source/graphicsmagick/+bug/1956642/+attachment/5552239/+files/Xubuntu_16.04.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Public bug reported:
I have three Xubuntu hard drives, loaded with 16.04 / 20.04 / 22.04 beta
I use ImageMagic convert binary to produce animated GIF and MP4 files of
leaves turning color and falling off. Convert performs flawlessly on the
16.04 system. It crashes on the 20.04 and 22.04 system le
The solution to this issue was documented in my #3 comment. The
misleading error messages coming from Linux were indicating that it was
time to fresh reformat the MP3 player and start over. Once done, no
issues.
This defect report may be close. Thank you.
--
You received this bug notification be
I decided to have the Sony WalkMan reformat itself. MTP over USB working
much better now.
Very odd that I could play MP3 recordings with the player without
issues... only issues was removing files, copying new files to it.
The thing that tipped me off to try reformatting the device with itself
is
syslog Sony WalkMan MTP over USB related errors
** Attachment added: "syslog.log"
https://bugs.launchpad.net/ubuntu/+bug/1938645/+attachment/5515138/+files/syslog.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Public bug reported:
I use package Rhythembox as my MP3 player software. I also use Rhythebox
to transfer audio to my Sony WalkMan MP3 player.
Since moving to Xubuntu 20.04.2, it has gotten much harder to
successfully transfer mp3 audio to the Sony WalkMan MP3 player. I
checked in syslog... I see
Did something go wrong in the latest kernel update that applied along
with the move to the 470 version of the Nvidia drivers? I use VirtualBox
on my computer... VirtualBox cites that it does not have its needed
kernel drivers loaded either.
Another system I have not updated the 5.8.0-59-generic ke
I found such entries in syslog:
#syslog entries
Jul 31 10:51:25 jaakob kernel: [2170748.708122] NVRM: API mismatch: the client
has the version 470.57.02, but
Jul 31 10:51:25 jaakob kernel: [2170748.708122] NVRM: this kernel module has
the version 465.27. Please
Jul 31 10:51:25 jaakob kernel: [2
I encountered a defect when Ubuntu updated from successfully working
nvidia-driver-465 to nvidia-driver-470.
I needed to purge all *nvidia* packages off my system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
+1 vote for rhythmbox to be added to Xubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934926
Title:
Add a music player
To manage notifications about this bug go to:
https://bugs.launchpad.net
Yes, looks like a useful tool. +1 vote
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934932
Title:
Add useful disk utilities
To manage notifications about this bug go to:
https://bugs.launchpad.ne
I find it very odd to see the defect I just found moving from Xubuntu
16.04 to Xubuntu 20.04.2 and Synaptic not respecting locked package
versions already reported as of 2006-04-29!
Synaptic, for us, had always respected when we would put a lock on a
certain package. That is no longer respected in
Would Nautilus, from GNOME desktop, be an alternate option? It looks
like that has a lighter weight dependency package footprint.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834203
Title:
Copying
So I finally moved to a new machine... loaded with Xubuntu 20.04.2...
upgraded from my reliable machine still running Xubuntu 16.04.
While on Xubuntu 16.04, I never had any issues with Thunar and copying
files either locally or involving SAMBA mounted shares.
Unfortunately Xubuntu 20.04.2 still r
apport information
** Attachment added: "UbiquitySyslog.txt"
https://bugs.launchpad.net/bugs/1912276/+attachment/5454516/+files/UbiquitySyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/191
apport information
** Tags added: apport-collected focal uec-images
** Description changed:
I opened a forum ticket about this observation here:
"Unable to boot from HDD 20.04 installed with BIOS in Legacy mode"
https://ubuntuforums.org/showthread.php?t=2455005&p=14015093
I suspect
Public bug reported:
I opened a forum ticket about this observation here:
"Unable to boot from HDD 20.04 installed with BIOS in Legacy mode"
https://ubuntuforums.org/showthread.php?t=2455005&p=14015093
I suspect there might be a defect in Ubuntu Server 20.04 ISO. I was
loading it onto a ThinkPad
Confirmed on my machine that now the behavior is Gigolo does not write a
port= entry when making SMB protocol bookmarks.
Using a newly created bookmark does successfully connect to the Samba
server.
Assuming leaving port= out completely was an intended change, then I
call this defect successfully
I just pulled down the daily ISO of focal. With a blank new drive, this
is still a design gap of the Ubuntu / Xubuntu installer. You cannot tag
a brand new partition as ntfs format and assign a Linux mount point to
it.
I assume if Windows NTFS partitions were present on the drive, the Linux
instal
I seem to have just bumped into this sort of issue beta testing Xubuntu
20.04. My Xubuntu 16.04 systems never did this. I did not have time to
upgraded to Xubuntu 18.04, so cannot comment about that LTS release.
I set up SAMBA mounts to our office SAMBA server... sort of the Linux
equivalent of Wi
** Attachment added: "Error resulting from not being connected to Internet"
https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1861937/+attachment/5325428/+files/SynapticDialogBoxTooTallIssue.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Public bug reported:
Synaptic has a bad habit of popping up informational dialog boxes which
are too tall for the screen, thus the buttons at the bottom are not
visible. It sizes the box much too tall for the amount of text to be
displayed. One cannot reduce the height of the dialog box... its hei
Confirmed in Xubuntu 20.04. Michael's suggestion in #3 gets around the
defect. Thanks Michael!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854137
Title:
Gigolo trys to use port 21 for SMB/CIFS co
Well since the legacy version of Raleigh is dead in 18.04 on account of
higher GTK version than it is compatible with, how do I go about
requesting for packaging the new GTK3 compatible version of the theme?
As-is, shipping a theme with an OS that will not work due to dependency
issues does no one
Thank you, Theo, for directing me to the new Raleigh.
Will this be included for Xubuntu in the main Ubuntu repositories?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759450
Title:
Raleigh theme h
Public bug reported:
Comparing Xubuntu 16.04 to 18.04, same theme settings... certain
controls are hardly visible on Xubuntu 18.04.
Please see the attached comparisons.
I configured the 18.04 system same as my 16.04 system, with the following
selections:
http://www.lueckdatasystems.com/Custom_a
** Attachment added: "Synaptic Package Manager comparison screen shot"
https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1759450/+attachment/5093029/+files/SynapticPackageManager-Versions.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Public bug reported:
Various file selection dialog boxes within the Xfce desktop environment
appear to be not enabled to navigate into . leading hidden directories.
There is no provided way to manually enter a specific filename / file
path.
One place I encountered this sharp spot is building Appl
Ubuntu 18.04 LTS will be coming soon... best try to get the latest
stable version of SQL Ledger before 18.04 code freezes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1281329
Title:
Sync up 14.04
So since it is stated that a fix is released for this issue... does that
mean that Ubuntu has agreed that it is incorrect to have to change the
configuration of this package from its installation default in order to
receive change log emails from apt?
--
You received this bug notification because
I just tested a Xubuntu 14.04 x64 LTS upgrade to Xubuntu 16.04. The value:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
is correct for Xubuntu. That is what causes the boot process to have the GUI
screen rather than text console messages.
So note to the upgrade package maintainers... it needs to be
Per the package's changelog:
apt-listchanges (2.85.14ubuntu1) xenial; urgency=medium
* Merge with Debian; remaining changes:
- apt-listchanges/DebianFiles.py: only use apt-get changelog if which is
changelogs or both, so not for news.
-- Matthias Klose Wed, 17 Feb 2016 14:53:58 +0
[apt]
frontend=pager
email_address=root
confirm=0
save_seen=/var/lib/apt/listchanges.db
which=news
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662550
Title:
After LTS upgrade to 16.04, no more em
@Joseph, Do you mean incomplete based on this bug report needing to
morph into an issue against the 14.04 to 16.04 LTS upgrade process?
How may I assist?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
We have now built brand new servers with Ubuntu Server 16.04 x64. The
initial state of the /etc/default/grub file is:
GRUB_CMDLINE_LINUX_DEFAULT=""
Must be that edit was missed in the LTS upgrade from 14.04 to 16.04.
I have modified our LTS upgraded 16.04 servers to this setting.
--
You receiv
During another 14.04->16.04 LTS upgrade:
Setting up daemontools (1:0.76-6ubuntu1) ...
Setting up daemontools-run (1:0.76-6ubuntu1) ...
Adding SV inittab entry...
start: Job is already running: svscan
dpkg: error processing package daemontools-run (--configure):
subprocess installed post-installat
Excellent find, Joseph!
Here are the lines of interest from our /etc/default/grub files:
GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LI
Correct, 3.13.0-9.29 boots with appropriate "Ubuntu " text, then
lands at a busybox type interface.
So looks like something happened bad in-between there.
Purged back off. Ready for the next test.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Looks like build 3.15.0-0.1 still has the issue. It also would not boot
correctly... landed the server at a busybox type interface.
Purged back off.
So, into the 3.14's next?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Build 3.16.0-0.1 has the reported defect. Purged back off.
Next build to evaluate, please...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
No server console display after Grub screen
There does not appear to be i386 files in that directory.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
No server console display after Grub screen until fully booted and
pressing C
Public bug reported:
We recently LTS upgraded our first server from 14.04 to 16.04. After
that upgrade, we are not seeing apt-listchanges attempt to send out
emails with the change log.
I have tried purging off package apt-listchanges, then reinstalled it.
Shortly apticron notified us of updates
Build 3.16.0-23 has the reported defect. Purged back off.
Next build to evaluate, please...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
No server console display after Grub screen
Yes that v3.13.0-108.155 kernel build boots up with the expected Ubuntu
splashscreen. Though would not boot up all the way cleanly... went
into busybox.
Received v4.4.0-62 via Xenial updates, so purging off both the
v3.13.0-108.155 and v4.4.0-59 kernel versions.
So yes, somewhere between 3.1
The 3.19.0-80 kernel build still has the defect. I purged it back off
our server. Booted back to 4.4.0-59.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
No server console display afte
Sorry... defect is yet persisting with the 4.2.0-16.19 kernel build. I
purged it back off our server. Booted back to 4.4.0-59.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
No server
Tested 4.2.0-19.23 kernel, same issue. Purging it off.
So, quick question... between "v4.4-wily" which worked and "linux-
image-4.4.0-1-generic", is the difference there the Ubuntu
customizations applied to the official Kernel build? Thus is something
in how Ubuntu customizes the Kernel source whi
Same defect with both the https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/11923303 and
https://launchpad.net/ubuntu/+source/linux/4.3.0-7.18 kernel builds.
I am back booted to linux-image-4.4.0-59-generic and all other kernels
have been purged back off the server.
Please
... and I was not suppose to be booting from a lower entry than the top
entry for the particular kernel build I am testing, was I? Top has no
suffix text, next one I believe was labeled "Upstart" and third was
"Recovery".
--
You received this bug notification because you are a member of Ubuntu
Bu
Wowsers... this bug is already present in linux-image-4.4.0-1-generic!
So was linux-image-4.4.0-1-generic the very next version after
v4.4-wily? Or do I need to test some additional versions?
The URL link you posted for the Yakkey(16.10) kernel leads directly to
amd64 specific... this system is r
Noted you want me to test the Yakkey(16.10) kernel specified.
About the Xenial kernels... I am thinking to walk the version list back
from 4.4.0-59 to land on one that does not have the error. Then post the
last one that was working, and the first one with the noted defect. Does
that sound like a
OK, I got the first kernel (v4.4-wily) validated that it works properly.
I IPL'ed back to the 4.4.0-59 to validate the problem had not suddenly
vanished, still there.
So:
4.4.0-59 bad / has the issue
v4.4-wily working / no issue
Do you still need me to install / test / validate the v4.5-rc1-wily
Excellent, first try lucky. I downloaded all three requested kernel
packages. Started with the:
4.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/
And this version already corrects the entire issue seen with the
4.4.0-59-generic official 16.04 version.
Here is the console output
Question: So is there hope of getting this fixed in the default kernel
version for the 16.04 release, or is it going to be addressed only with
the "Ubuntu 16.04.2 LTS Point Release Coming On Feb 2 With Linux Kernel
4.8" newer kernel?
No... Linux Kernel 4.4 vs Linux Kernel 4.10, so that is not Linu
I found a workaround to this issue and logged it here:
https://bugs.launchpad.net/ubuntu/+source/daemontools/+bug/1617691/comments/4
I got the package situation resolved that was caused due to performing a
14.04->16.04 LTS upgrade.
I removed the following packages:
dnscache-run
daemontools-run
T
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
No server console display after Grub screen until fully booted and
Yes, working perfectly! Trying to remember how I set tags. Here is the
output of applying the test kernel:
mdlueck@ldslnx01:/srv/shares/data/Download/OpenSource/Ubuntu/Xenial/Bugs/1656605_ServerNoConsoleDisplay/v4.10-rc4$
sudo dpkg -i
linux-image-4.10.0-041000rc4-generic_4.10.0-041000rc4.201701
@ the OP: "It's not clear where the bug is in this, but I was doing a
LTS release upgrade and svscan was already installed and running"
I would think the bug should be against the daemontools-run package,
that it is unable to apply an update to itself. Correct?
Seems to me a regression from the 1
Ah, a notable difference between the hardware spec of the test servers
and the real servers:
The test server is on a test machine which has a graphics board
installed in it: EVGA e-GeForce 8400 GS Graphics Card - 512 MB RAM
512-P3-1301-KR
The real servers are using the on-board Intel graphics.
N
A friend advised me to check two more outputs between a 14.04 server and
16.04 impacted server. Attaching the following additional outputs:
mdlueck@ldslnx01:/srv/shares/data/Download/OpenSource/Ubuntu/Xenial/Bugs/1656605_ServerNoConsoleDisplay$
cat /proc/consoles > consoles.log
mdlueck@ldslnx01:/
** Attachment added: "cmdline.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+attachment/4804629/+files/cmdline.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
Public bug reported:
Today I did our first production 14.04 to 16.04 LTS server upgrade. I
had done so a couple of times successfully on test server machines. Upon
booting up on the 16.04 system/kernel, after the Grub screen the server
console screen is completely blank.
Someone suggested using C
** Attachment added: "uname-a.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1656605/+attachment/4804496/+files/uname-a.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Ti
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1656605/+attachment/4804497/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Ti
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1656605/+attachment/4804494/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605
Title:
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1656605/+attachment/4804495/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16566
** Attachment added: "linux-images.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1656605/+attachment/4804498/+files/linux-images.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
I got the package situation resolved that was caused due to performing a
14.04->16.04 LTS upgrade.
I removed the following packages:
dnscache-run
daemontools-run
Then reinstalled them from the raw .deb files I had downloaded to the
server.
$sudo dpkg -i daemontools-run_0.76-6ubuntu1_all.deb
$sud
I went through the LTS upgrade on some Ubuntu Server machines w/o this
error from 12.04 to 14.04. Going through the LTS upgrade on the first of
the same systems from 14.04 to 16.04 I too am seeing this error.
I believe daemontools-run is used by djbdns, which our systems run.
--
You received thi
Public bug reported:
According to this page: https://launchpad.net/ubuntu/xenial/+source
/gnome-icon-theme-extras seems to suggest that package gnome-icon-
theme-extras in Xenial is a forward replacement for package gnome-
themes-extras in Trusty.
Between the list of files in the package for Tru
@Marc #12, perhaps so it was actually eglibc package. I tested
reapplying the PHP updates, IPL, and Apache stayed up. Evidently I
missed that eglibc and the subsequently required IPL.
We are now good with the latest packages for 12.04. Phew! :-)
--
You received this bug notification because you
For our servers (12.04) manually restarting the Apache service would
cause the same error. Apache would not manually restart.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585614
Title:
PHP Update
APT term.log
** Attachment added: "term.log"
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1585614/+attachment/4670188/+files/term.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585614
APT history.log
** Attachment added: "history.log"
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1585614/+attachment/4670187/+files/history.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
1 - 100 of 485 matches
Mail list logo
