[Bug 2059045] [NEW] Xfce xpanel double network panel icon

[Michael Lueck]

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 24.04
Package: xfce4-panel 4.18.4-1
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.494
CurrentDesktop: XFCE
Date: Mon Mar 25 21:04:51 2024
LiveMediaBuild: Xubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240325)
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: xfce4-panel
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xfce4-panel (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble

** Attachment added: "Screen shot of the Xubuntu Live Desktop with Double 
Network Icons in Top Panel"
   
https://bugs.launchpad.net/bugs/2059045/+attachment/5759343/+files/XubuntuLiveDesktop_DoubleNetworkIconsInTopPanel_2024-03-25.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059045

Title:
  Xfce xpanel double network panel icon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/2059045/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1944519] Re: Xubuntu shutdown prompt is missing

[Michael Lueck]

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, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944519

Title:
  Xubuntu shutdown prompt is missing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1944519/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054323] Re: Xubuntu Noble installer has no begin installation icon on desktop of Live Session

[Michael Lueck]

@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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054323

Title:
  Xubuntu Noble installer has no begin installation icon on desktop of
  Live Session

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2054323/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962470] Re: Jammy Live installer not producing booting gpt partition table / EFI partition hard drive installations

[Michael Lueck]

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 20 root root 0 Apr 23 12:58 memmap
xubuntu@xubuntu:/sys/firmware$ sudo dmesg | grep -i EFI
[0.078686] clocksource: refined-jiffies: mask: 0x max_cycles: 
0x, max_idle_ns: 7645519600211568 ns
[1.477833] tsc: Refined TSC clocksource calibration: 3166.306 MHz
[   80.771346] b43-phy0 ERROR: You must go to 
https://wireless.wiki.kernel.org/en/users/Drivers/b43#devicefirmware and 
download the correct firmware for this driver version. Please carefully read 
all instructions on this website.
xubuntu@xubuntu:/sys/firmware$


Booted to Xubuntu 22.04 LiveDVD
BIOS has UEFI enabled

xubuntu@xubuntu:/sys/firmware$ ls -al
total 0
drwxr-xr-x  5 root root 0 Apr 23 13:07 .
dr-xr-xr-x 13 root root 0 Apr 23 13:07 ..
drwxr-xr-x  5 root root 0 Apr 23 13:08 acpi
drwxr-xr-x  3 root root 0 Apr 23 13:08 dmi
drwxr-xr-x 20 root root 0 Apr 23 13:22 memmap
xubuntu@xubuntu:/sys/firmware$ sudo dmesg | grep -i EFI
[0.079762] clocksource: refined-jiffies: mask: 0x max_cycles: 
0x, max_idle_ns: 7645519600211568 ns
[1.522877] tsc: Refined TSC clocksource calibration: 3166.310 MHz
[   78.934879] b43-phy0 ERROR: You must go to 
https://wireless.wiki.kernel.org/en/users/Drivers/b43#devicefirmware and 
download the correct firmware for this driver version. Please carefully read 
all instructions on this website.
xubuntu@xubuntu:/sys/firmware$ 


Seems Xubuntu 22.04 release just cannot detect EFI / UEFI support within the 
BIOS.

The Ubuntu / Xubuntu ISO DVD's seem to be intelligent enough to boot if
the BIOS has only legacy support or new EFI / UEFI support. Perhaps that
is the area of Ubuntu that has the issue... that the EFI / UEFI detector
fails to detect, so boots in legacy support mode?

For this system, manually partitioning off the Live DVD with Gparted,
msdos partition table, one large xfs partition mounted as root.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962470

Title:
  Jammy Live installer not producing booting gpt partition table / EFI
  partition hard drive installations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1962470/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962470] Re: Jammy Live installer not producing booting gpt partition table / EFI partition hard drive installations

[Michael Lueck]

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 seems system specific that Xubuntu is unable to boot from the
internal disk on systems it is able to boot from the LiveDVD, install
without complaints.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962470

Title:
  Jammy Live installer not producing booting gpt partition table / EFI
  partition hard drive installations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1962470/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962470] Re: Jammy Live installer not producing booting gpt partition table / EFI partition hard drive installations

[Michael Lueck]

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 created the following partitions:

sda1  1MB  BIOS BOOT
sda2  500MB  EFI System
sda3  1TB  /  ext4

So, an additional partition my working Xubuntu 20.04.2 system did not
require... the 1MB BIOS BOOT partition. I had high hopes... Nope! Still
will not boot from the HDD. I mentioned in my failed installation test
results I would update this same defect case with the results of the
failed auto partition installation attempt.

The only way I can make Xubuntu 22.04 boot on this system is to manually
bring up Gparted, create a blank MSDOS partition table, and then a
single 1TB / xfs partition... it boots just fine with that legacy
configuration... which I do not install as the BIOS is new enough to
support UEFI Smart Boot... which I have that disabled.

Test system is based on a Intel DG33BU motherboard and Intel Core 2 Duo
E8500 CPU

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962470

Title:
  Jammy Live installer not producing booting gpt partition table / EFI
  partition hard drive installations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1962470/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1944519] Re: Xubuntu shutdown prompt is missing

[Michael Lueck]

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
shut down is text based.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944519

Title:
  Xubuntu shutdown prompt is missing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1944519/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962470] Re: Jammy Live installer not producing booting gpt partition table / EFI partition hard drive installations

[Michael Lueck]

** 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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962470

Title:
  Jammy Live installer not producing booting gpt partition table / EFI
  partition hard drive installations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1962470/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962470] Re: Jammy Live installer not producing booting EFI hard drive installations

[Michael Lueck]

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 from the installer.

Resulted in a non booting hard drive. :-(

Started over, wiped the disk, manually crated a msdos partition with
Gparted, then a single xfs partition. Installation warned about not
being able to boot the system... however this legacy way the hard drive
boots perfectly.

Major new defect with Xubuntu 22.04 that is not present in Xubuntu
20.04. I partition with gpt partition table, EFI / XFS as listed above
with perfect success. Something odd that 22.04 cannot handle a gpt
partition table.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962470

Title:
  Jammy Live installer not producing booting EFI hard drive
  installations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1962470/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962467] Re: Gparted off the LiveDVD wants package mtools added in order to display EFI partition correctly

[Michael Lueck]

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 file system 
support:  dosfstools, mtools.

xubuntu@xubuntu:~$ dpkg -l | grep dosfstools
ii  dosfstools4.2-1build2   
  amd64utilities for making and checking MS-DOS FAT filesystems
xubuntu@xubuntu:~$ dpkg -l | grep mtools
xubuntu@xubuntu:~$

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962467

Title:
  Gparted off the LiveDVD wants package mtools added in order to display
  EFI partition correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1962467/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1944519] Re: Xubuntu shutdown prompt is missing

[Michael Lueck]

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 of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944519

Title:
  Xubuntu shutdown prompt is missing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1944519/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962466] Re: Jammy Live installer does not display any "press a key" once it shuts down and ejects the DVD

[Michael Lueck]

*** 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 known / reported issue. Thank you for merging.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962466

Title:
  Jammy Live installer does not display any "press a key" once it shuts
  down and ejects the DVD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1962466/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962466] Re: Jammy Live installer does not display any "press a key" once it shuts down and ejects the DVD

[Michael Lueck]

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 notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962466

Title:
  Jammy Live installer does not display any "press a key" once it shuts
  down and ejects the DVD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1962466/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1964979] [NEW] Jammy server installer unable to set IPv4 static nor switch back to DHCP

[Michael Lueck]

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, or if I was entering incorrect input.

Unable to select manual IPv4 during attempted installation of 22.04 Jammy
https://ubuntuforums.org/showthread.php?t=2472852

The settings I put in for Manual IPv4 are as follows:

Subnet: 10.10.10.0/24
Address: 10.10.10.9
Gateway: 10.10.10.1
Name server: 10.10.10.10

Pushing Save blanked out the name server field, and it never finishes
the "Applying changes" step.

We have a Class C IPv4 subnet. Addresses 10.10.10.1 through 10.10.10.254

I tried adjusting back to DHCP vs manual... now it also no longer picks
up an address from our DHCP server. The spinning "Applying changes"
attempting to test DHCP again.

** Affects: live-build (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/1964979

Title:
  Jammy server installer unable to set IPv4 static nor switch back to
  DHCP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1964979/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962466] Re: Jammy Live installer does not display any "press a key" once it shuts down and ejects the DVD

[Michael Lueck]

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
remains, Ubuntu Server installer still displays the message which the
Xubuntu should also display. Borrow IP from there... ;-)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962466

Title:
  Jammy Live installer does not display any "press a key" once it shuts
  down and ejects the DVD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1962466/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1963768] [NEW] Gigolo back to not being able to connect to smb / CIFS / Samba servers again

[Michael Lueck]

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 Xubuntu 20.04 Focal Fossa.

Testing 22.04 Jammy Jellyfish, I get an error trying to use a brand new
smb bookmark. Trying in my Xubuntu 20.04 Focal Fossa system, now I get
the same error. So this impacts both Xubuntu releases.

Open Gigolo
Edit \ Bookmarks
Add
  Name the bookmark
  Service Type: Windows Share
  Server: hostname of Samba NT4 PDC
  Share: share name on the Samba NT4 PDC
  Domain: smb domain name of the Samba NT4 PDC
  User Name: my username on the Samba NT4 PDC
OK to save

Actions \ Bookmarks \ the newly created SMB bookmark
At the password box, enter my password for the Samba NT4 PDC, and select the 
radio button "Remember password until you logout"

Error pops up: Connecting to "smb://smb-domain;userid@hostname/-sharename" 
failed.
Failed to mount Windows Share: Software caused connection abort

So, is it really adding a "-" character between the Samba server
hostname, slash, and the sharename? That might be causing problems. I
did not type a dash there.

Same connection error occurs if I free hand type the connection string
into a Thunar window URL bar. Note I did not add the "-" in my free-hand
entered URL attempt.

The entry crated in ~/.config/gigolo/bookmarks looks perfect, no extra
unexpected characters.

I am able to create a Gigolo ssh connection to the same server and
connect successfully over that protocol.

** Affects: gigolo (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  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 Xubuntu 20.04 Focal Fossa.
  
  Testing 22.04 Jammy Jellyfish, I get an error trying to use a brand new
  smb bookmark. Trying in my Xubuntu 20.04 Focal Fossa system, now I get
  the same error. So this impacts both Xubuntu releases.
  
  Open Gigolo
  Edit \ Bookmarks
  Add
-   Name the bookmark
-   Service Type: Windows Share
-   Server: hostname of Samba NT4 PDC
-   Share: share name on the Samba NT4 PDC
-   Domain: smb domain name of the Samba NT4 PDC
-   User Name: my username on the Samba NT4 PDC
+   Name the bookmark
+   Service Type: Windows Share
+   Server: hostname of Samba NT4 PDC
+   Share: share name on the Samba NT4 PDC
+   Domain: smb domain name of the Samba NT4 PDC
+   User Name: my username on the Samba NT4 PDC
  OK to save
  
  Actions \ Bookmarks \ the newly created SMB bookmark
  At the password box, enter my password for the Samba NT4 PDC, and select the 
radio button "Remember password until you logout"
  
  Error pops up: Connecting to "smb://smb-domain;userid@hostname/-sharename" 
failed.
  Failed to mount Windows Share: Software caused connection abort
  
  So, is it really adding a "-" character between the Samba server
  hostname, slash, and the sharename? That might be causing problems. I
  did not type a dash there.
  
  Same connection error occurs if I free hand type the connection string
  into a Thunar window URL bar. Note I did not add the "-" in my free-hand
  entered URL attempt.
  
  The entry crated in ~/.config/gigolo/bookmarks looks perfect, no extra
  unexpected characters.
  
- I am able to create a ssh connection to the same server and connect
- successfully over that protocol.
+ I am able to create a Gigolo ssh connection to the same server and
+ connect successfully over that protocol.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963768

Title:
  Gigolo back to not being able to connect to smb / CIFS / Samba servers
  again

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gigolo/+bug/1963768/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962470] Re: Jammy Live installer not producing booting EFI hard drive installations

[Michael Lueck]

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 wrong with gpt partition tables all of a sudden. I use gpt
partition table with Xubuntu 20.04 perfectly fine... 500MB EFI
partition, the rest as root XFS. Not right that I must now revert to a
dos partition table in order to get a test system to boot.

There are the steps of me setting up the gpt trial this morning:

xubuntu@xubuntu:~$ sudo wipefs /dev/sda
DEVICE OFFSET TYPE UUID LABEL
sda0x1fe  dos   
xubuntu@xubuntu:~$ sudo wipefs -a -t dos -f /dev/sda
/dev/sda: 2 bytes were erased at offset 0x01fe (dos): 55 aa
xubuntu@xubuntu:~$ sudo wipefs /dev/sda
xubuntu@xubuntu:~$ sudo apt-get install mtools
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Suggested packages:
  floppyd
The following NEW packages will be installed:
  mtools
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 201 kB of archives.
After this operation, 413 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu jammy/main amd64 mtools amd64 
4.0.33-1+really4.0.32-1 [201 kB]
Fetched 201 kB in 1s (236 kB/s)
Selecting previously unselected package mtools.
(Reading database ... 161715 files and directories currently installed.)
Preparing to unpack .../mtools_4.0.33-1+really4.0.32-1_amd64.deb ...
Unpacking mtools (4.0.33-1+really4.0.32-1) ...
Setting up mtools (4.0.33-1+really4.0.32-1) ...
Processing triggers for install-info (6.8-4) ...
Processing triggers for man-db (2.10.1-1) ...

xubuntu@xubuntu:~$ sudo wipefs /dev/sda
DEVICE OFFSET   TYPE UUID LABEL
sda0x200gpt   
sda0xe8e0db5e00 gpt   
sda0x1fePMBR

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962470

Title:
  Jammy Live installer not producing booting EFI hard drive
  installations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1962470/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962470] Re: Jammy Live installer not producing booting EFI hard drive installations

[Michael Lueck]

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 UEFI enabled
gpt partition table
All the drive XFS partition

BIOS UEFI enabled
Let Xubuntu auto partition the entire drive... some sort of ext4 scheme, which 
also failed to boot.

Works - produces booting system
BIOS UEFI disabled
msdos partition table created in Gparted
All the drive XFS partition created in Gparted
The installer warned this may not produce a bootable system on the 
contrary, this finally does boot properly!

Shall next try:
BIOS UEFI disabled
gpt partition table
500MB EFI partition first
All the rest XFS partition?


I thought for sure I had success before enabling UEFI boot in the BIOS / having 
a gpt partition table and EFI partition... back in December. I am really 
puzzled why the configuration is now giving me a fight. Too late to go back now.

At least the test system boots again. I can continue on with other beta
testing. Please advise what combination you would like me to try to
modernize the drive partitioning beyond an msdos partition table.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962470

Title:
  Jammy Live installer not producing booting EFI hard drive
  installations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1962470/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962470] Re: Jammy Live installer not producing booting EFI hard drive installations

[Michael Lueck]

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 to have at least a small ext2 or ext3 (later) /boot partition,
and the rest could be XFS for the root partition.

Now with EFI systems, I have understood that it is back to having at
least two partitions... an EFI partition first, which then following may
be the main XFS partition.

As much as I have understood, this above is the state of Linux booting
from XFS currently.

As far as where I first booked this bug against... I had forgotten that
ubiquity was actually the package name for the installer. Please accept
my apologies.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962470

Title:
  Jammy Live installer not producing booting EFI hard drive
  installations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1962470/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962470] [NEW] Jammy Live installer not producing booting EFI hard drive installations

[Michael Lueck]

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 from the LiveDVD.

Check the partition table
sudo wipefs /dev/sda

Wipe the gpd partition table
sudo wipefs -a -t gpt -f /dev/sda

Double check that the wipe was successful with the first command, came
back empty / blank.

Next started the Xubuntu installer from the desktop icon.

Chose manual partitioning, created the following
sda1 500M Primary EFI Boot
sda2 remainder Primary xfs /

Once the installation got done, I opened Gparted to confirm the partitions.
The EFI partition was mounted to /target/boot/efi
The XFS partition was mounted to /target/

The EFI partition had boot, esp flags on it.

I restarted the system, shuts down, exhibits the usual with Jammy defect
1962466, I push a key to restart, system goes through BIOS screens, then
lands at a black screen with blinking cursor in the top left corner.

Getting systems to boot from the hard drive is very frustrating in the
era of EFI boot. :-(

** Affects: live-build (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/1962470

Title:
  Jammy Live installer not producing booting EFI hard drive
  installations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1962470/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962467] [NEW] Gparted off the LiveDVD wants package mtools added in order to display EFI partition correctly

[Michael Lueck]

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

Once that finishes, I restart Gparted, and no more error in the row
containing the EFI partition.

I just completed a load off a fresh boot of the same DVD, the same error
opening Gparted did not happen. Perhaps the Live installer added the
package dynamically since it was instructed to provision an EFI
partition? Not sure.

** Affects: live-build (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/1962467

Title:
  Gparted off the LiveDVD wants package mtools added in order to display
  EFI partition correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1962467/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962466] [NEW] Jammy Live installer does not display any "press a key" once it shuts down and ejects the DVD

[Michael Lueck]

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.

Pressing a key indeed correctly restarts the computer. Display defect
only... behaves operationally as expected.

** Affects: live-build (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/1962466

Title:
  Jammy Live installer does not display any "press a key" once it shuts
  down and ejects the DVD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1962466/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1834203] Re: Copying small files over CIFS doesn't close its window

[Michael Lueck]

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 away / close.

Please, may we get some traction on this regression defect as compared
with Xubuntu 16.04? That prior release of Xubuntu never had such a
defect.

-- 
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 small files over CIFS doesn't close its window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1834203/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956642] Re: convert crash during operation leaving partial output file

[Michael Lueck]

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   Area MemoryMap   Disk   Thread  Throttle   Time

   768   16.584GB  7.7226GiB  15.445GiB  unlimited2 0  unlimited
$


Xubuntu 20.04:
$ convert -list resource
Resource limits:
  Width: 16KP
  Height: 16KP
  List length: 18.446744EP
  Area: 128MP
  Memory: 256MiB
  Map: 512MiB
  Disk: 1GiB
  File: 768
  Thread: 12
  Throttle: 0
  Time: unlimited
$

Xubuntu 22.04:
$ convert -list resource
Resource limits:
  Width: 16KP
  Height: 16KP
  List length: unlimited
  Area: 128MP
  Memory: 256MiB
  Map: 512MiB
  Disk: 1GiB
  File: 768
  Thread: 2
  Throttle: 0
  Time: unlimited
$


So I can see that Memory and Disk are now far more constrained than when on 
Xubuntu 16.04.

All right, so I searched and found this page:
https://imagemagick.org/script/resources.php

Seems I am to make a policy.xml file in my home directory... I made:
~/.config/ImageMagick/policy.xml

Copied in the default per the site, uncommented lines for:
  
  


Saved, retested showing resources, no changes. Further suggestions please.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956642

Title:
  convert crash during operation leaving partial output file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/graphicsmagick/+bug/1956642/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956642] Re: convert crash during operation leaving partial output file

[Michael Lueck]

** 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.launchpad.net/bugs/1956642

Title:
  convert crash during operation leaving partial output file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/graphicsmagick/+bug/1956642/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956642] Re: convert crash during operation leaving partial output file

[Michael Lueck]

** 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.launchpad.net/bugs/1956642

Title:
  convert crash during operation leaving partial output file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/graphicsmagick/+bug/1956642/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956642] Re: convert crash during operation leaving partial output file

[Michael Lueck]

** 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.launchpad.net/bugs/1956642

Title:
  convert crash during operation leaving partial output file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/graphicsmagick/+bug/1956642/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956642] [NEW] convert crash during operation leaving partial output file

[Michael Lueck]

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 leaving partially
generated output files. Both the .GIF and .MP4 resulting file contain
the beginning part of the files, then end abruptly.

Xubuntu 16.04 system output:
.../AniGIF$ cat DownTheHillParkFavoriteTree.txt 

convert -resize 20% -delay 30 -loop 0 *.jpg
DownTheHillParkFavoriteTree.mp4

convert -resize 20% -delay 30 -loop 0 *.jpg
DownTheHillParkFavoriteTree.gif

.../AniGIF$ convert -resize 20% -delay 30 -loop 0 *.jpg 
DownTheHillParkFavoriteTree.mp4
.../AniGIF$ convert -resize 20% -delay 30 -loop 0 *.jpg 
DownTheHillParkFavoriteTree.gif
.../AniGIF$

This system produced complete .GIF and .MP4 files.


Xubuntu 20.04 system output:
.../AniGIF$ cat DownTheHillParkFavoriteTree.txt 

convert -resize 20% -delay 30 -loop 0 *.jpg
DownTheHillParkFavoriteTree.mp4

convert -resize 20% -delay 30 -loop 0 *.jpg
DownTheHillParkFavoriteTree.gif

.../AniGIF$ convert -resize 20% -delay 30 -loop 0 *.jpg 
DownTheHillParkFavoriteTree.mp4
convert-im6.q16: cache resources exhausted `IMG_20211026_130427643_HDR.jpg' @ 
error/cache.c/OpenPixelCache/4083.
convert-im6.q16: cache resources exhausted `IMG_20211027_134629172_HDR.jpg' @ 
error/cache.c/OpenPixelCache/4083.
convert-im6.q16: cache resources exhausted `IMG_20211101_125905455.jpg' @ 
error/cache.c/OpenPixelCache/4083.
convert-im6.q16: cache resources exhausted `IMG_20211102_125128024_HDR.jpg' @ 
error/cache.c/OpenPixelCache/4083.
convert-im6.q16: cache resources exhausted `IMG_20211104_124534882_HDR.jpg' @ 
error/cache.c/OpenPixelCache/4083.
convert-im6.q16: cache resources exhausted `IMG_20211105_130136284_HDR.jpg' @ 
error/cache.c/OpenPixelCache/4083.
convert-im6.q16: cache resources exhausted `IMG_20211106_161209515.jpg' @ 
error/cache.c/OpenPixelCache/4083.
convert-im6.q16: cache resources exhausted `IMG_20211107_120956962_HDR.jpg' @ 
error/cache.c/OpenPixelCache/4083.
convert-im6.q16: cache resources exhausted `IMG_20211108_130716503.jpg' @ 
error/cache.c/OpenPixelCache/4083.
convert-im6.q16: cache resources exhausted `IMG_20211109_131205937_HDR.jpg' @ 
error/cache.c/OpenPixelCache/4083.
convert-im6.q16: cache resources exhausted `IMG_2020_123923365_HDR.jpg' @ 
error/cache.c/OpenPixelCache/4083.
convert-im6.q16: cache resources exhausted `IMG_2022_124051555.jpg' @ 
error/cache.c/OpenPixelCache/4083.
.../AniGIF$ convert -resize 20% -delay 30 -loop 0 *.jpg 
DownTheHillParkFavoriteTree.gif
convert-im6.q16: cache resources exhausted `IMG_20211026_130427643_HDR.jpg' @ 
error/cache.c/OpenPixelCache/4083.
convert-im6.q16: cache resources exhausted `IMG_20211027_134629172_HDR.jpg' @ 
error/cache.c/OpenPixelCache/4083.
convert-im6.q16: cache resources exhausted `IMG_20211101_125905455.jpg' @ 
error/cache.c/OpenPixelCache/4083.
convert-im6.q16: cache resources exhausted `IMG_20211102_125128024_HDR.jpg' @ 
error/cache.c/OpenPixelCache/4083.
convert-im6.q16: cache resources exhausted `IMG_20211104_124534882_HDR.jpg' @ 
error/cache.c/OpenPixelCache/4083.
convert-im6.q16: cache resources exhausted `IMG_20211105_130136284_HDR.jpg' @ 
error/cache.c/OpenPixelCache/4083.
convert-im6.q16: cache resources exhausted `IMG_20211106_161209515.jpg' @ 
error/cache.c/OpenPixelCache/4083.
convert-im6.q16: cache resources exhausted `IMG_20211107_120956962_HDR.jpg' @ 
error/cache.c/OpenPixelCache/4083.
convert-im6.q16: cache resources exhausted `IMG_20211108_130716503.jpg' @ 
error/cache.c/OpenPixelCache/4083.
convert-im6.q16: cache resources exhausted `IMG_20211109_131205937_HDR.jpg' @ 
error/cache.c/OpenPixelCache/4083.
convert-im6.q16: cache resources exhausted `IMG_2020_123923365_HDR.jpg' @ 
error/cache.c/OpenPixelCache/4083.
convert-im6.q16: cache resources exhausted `IMG_2022_124051555.jpg' @ 
error/cache.c/OpenPixelCache/4083.
.../AniGIF$

Xubuntu 22.04 system output:
.../AniGIF$ cat DownTheHillParkFavoriteTree.txt

convert -resize 20% -delay 30 -loop 0 *.jpg
DownTheHillParkFavoriteTree.mp4

convert -resize 20% -delay 30 -loop 0 *.jpg
DownTheHillParkFavoriteTree.gif

.../AniGIF$ convert -resize 20% -delay 30 -loop 0 *.jpg 
DownTheHillParkFavoriteTree.mp4
convert-im6.q16: cache resources exhausted `IMG_20211026_130427643_HDR.jpg' @ 
error/cache.c/OpenPixelCache/4095.
convert-im6.q16: cache resources exhausted `IMG_20211027_134629172_HDR.jpg' @ 
error/cache.c/OpenPixelCache/4095.
convert-im6.q16: cache resources exhausted `IMG_20211101_125905455.jpg' @ 
error/cache.c/OpenPixelCache/4095.
convert-im6.q16: cache resources exhausted `IMG_20211102_125128024_HDR.jpg' @ 
error/cache.c/OpenPixelCache/4095.
convert-im6.q16: cache resources exhausted `IMG_20211104_124534882_HDR.jpg' @ 
error/cache.c/OpenPixelCache/4095.
convert-im6.q16: cache resources exhausted 

[Bug 1938645] Re: Ubuntu 20.04.2 getting kernel I/O errors connecting to Sony Walkman over USB using MTP protocol

[Michael Lueck]

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 because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938645

Title:
  Ubuntu 20.04.2 getting kernel I/O errors connecting to Sony Walkman
  over USB using MTP protocol

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938645/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938645] Re: Ubuntu 20.04.2 getting kernel I/O errors connecting to Sony Walkman over USB using MTP protocol

[Michael Lueck]

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 I was seeing traces of recordings I had deleted yet in the playlist.
Some of the letters in the listings were missing, but the content would
still play properly. That told me deletes were not being completed
properly.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938645

Title:
  Ubuntu 20.04.2 getting kernel I/O errors connecting to Sony Walkman
  over USB using MTP protocol

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938645/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938645] Re: Ubuntu 20.04.2 getting kernel I/O errors connecting to Sony Walkman over USB using MTP protocol

[Michael Lueck]

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.launchpad.net/bugs/1938645

Title:
  Ubuntu 20.04.2 getting kernel I/O errors connecting to Sony Walkman
  over USB using MTP protocol

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1938645/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938645] [NEW] Ubuntu 20.04.2 getting kernel I/O errors connecting to Sony Walkman over USB using MTP protocol

[Michael Lueck]

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 some errors I believe are related:

Aug  1 10:39:54 jaakob kernel: [ 8079.675644] mtp[10045]: segfault at 8a ip 
7f2754d6f623 sp 7f274cbb2f20 error 4 in 
libglib-2.0.so.0.6400.6[7f2754d1b000+84000]
Aug  1 10:39:54 jaakob kernel: [ 8079.675648] Code: 0f 1f 80 00 00 00 00 48 c1 
e8 04 4c 8b 3b 8d 48 ff 48 89 c5 49 89 ce 49 c1 e6 04 4d 01 f7 4d 8b 27 4d 85 
e4 0f 84 cd 00 00 00 <49> 8b 44 24 08 48 85 c0 74 43 48 8b 10 49 89 54 24 08 49 
89 c4 49
Aug  1 10:40:13 jaakob kernel: [ 8098.630114] usb 1-11.2: USB disconnect, 
device number 6
Aug  1 10:41:34 jaakob kernel: [ 8179.600470] usb 1-5: new high-speed USB 
device number 8 using xhci_hcd
Aug  1 10:41:34 jaakob kernel: [ 8179.749115] usb 1-5: New USB device found, 
idVendor=054c, idProduct=0385, bcdDevice= 0.01
Aug  1 10:41:34 jaakob kernel: [ 8179.749121] usb 1-5: New USB device strings: 
Mfr=1, Product=2, SerialNumber=5
Aug  1 10:41:34 jaakob kernel: [ 8179.749124] usb 1-5: Product: WALKMAN
Aug  1 10:41:34 jaakob kernel: [ 8179.749127] usb 1-5: Manufacturer: Sony
Aug  1 10:41:34 jaakob kernel: [ 8179.749130] usb 1-5: SerialNumber: 
10FA1355316092
Aug  1 10:41:34 jaakob kernel: [ 8179.750689] usb-storage 1-5:1.0: USB Mass 
Storage device detected
Aug  1 10:41:34 jaakob kernel: [ 8179.751175] scsi host14: usb-storage 1-5:1.0
Aug  1 10:41:35 jaakob kernel: [ 8180.761332] scsi 14:0:0:0: Direct-Access 
SONY WALKMAN  1.00 PQ: 0 ANSI: 4
Aug  1 10:41:35 jaakob kernel: [ 8180.761875] sd 14:0:0:0: Attached scsi 
generic sg3 type 0
Aug  1 10:41:35 jaakob kernel: [ 8180.762889] sd 14:0:0:0: [sdb] 1917952 
2048-byte logical blocks: (3.93 GB/3.66 GiB)
Aug  1 10:41:35 jaakob kernel: [ 8180.763062] sd 14:0:0:0: [sdb] Write Protect 
is off
Aug  1 10:41:35 jaakob kernel: [ 8180.763066] sd 14:0:0:0: [sdb] Mode Sense: 3e 
00 00 00
Aug  1 10:41:35 jaakob kernel: [ 8180.763200] sd 14:0:0:0: [sdb] No Caching 
mode page found
Aug  1 10:41:35 jaakob kernel: [ 8180.763206] sd 14:0:0:0: [sdb] Assuming drive 
cache: write through
Aug  1 10:41:36 jaakob kernel: [ 8180.809779]  sdb: sdb1
Aug  1 10:41:36 jaakob kernel: [ 8180.811198] sd 14:0:0:0: [sdb] Attached SCSI 
removable disk
Aug  1 10:41:36 jaakob Thunar[7060]: Working directory "/home/mdlueck/[Invalid 
UTF-8]" does not exist. It won't be used when spawning "exo-open".Working 
directory "/home/mdlueck/[Invalid UTF-8]" does not exist. It won't be used when 
spawning "exo-open".
Aug  1 10:41:36 jaakob Thunar[10184]: thunar-volman: Unknown block device type 
"disk".
Aug  1 10:41:42 jaakob kernel: [ 8186.793656] FAT-fs (sdb1): Volume was not 
properly unmounted. Some data may be corrupt. Please run fsck.
Aug  1 10:41:42 jaakob systemd[1]: Created slice 
system-clean\x2dmount\x2dpoint.slice.
Aug  1 10:41:42 jaakob systemd[1]: Finished Clean the /media/mdlueck/WALKMAN 
mount point.
Aug  1 10:41:42 jaakob udisksd[813]: Mounted /dev/sdb1 at 
/media/mdlueck/WALKMAN on behalf of uid 1000
Aug  1 10:41:42 jaakob dbus-daemon[1546]: [session uid=1000 pid=1546] 
Activating service name='org.freedesktop.thumbnails.Thumbnailer1' requested by 
':1.83' (uid=1000 pid=7060 comm="/usr/bin/Thunar --daemon " label="unconfined")
Aug  1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: 
Registered thumbnailer atril-thumbnailer -s %s %u %o
Aug  1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: 
Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o
Aug  1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: 
Registered thumbnailer gnome-thumbnail-font --size %s %u %o
Aug  1 10:41:42 jaakob org.freedesktop.thumbnails.Thumbnailer1[10238]: 
Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o
Aug  1 10:41:42 jaakob dbus-daemon[1546]: [session uid=1000 pid=1546] 
Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1'
Aug  1 10:43:07 jaakob kernel: [ 8272.638815] blk_update_request: I/O error, 
dev sdb, sector 32 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
Aug  1 10:43:07 jaakob kernel: [ 8272.638818] Buffer I/O error on dev sdb1, 
logical block 1, lost async page write
Aug  1 10:43:07 jaakob kernel: [ 8272.638822] blk_update_request: I/O error, 
dev sdb, sector 2176 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
Aug  1 10:43:07 jaakob kernel: [ 8272.638823] Buffer I/O error on dev sdb1, 
logical block 537, lost async page write
Aug  1 10:43:07 jaakob kernel: [ 8272.638839] blk_update_request: I/O error, 
dev sdb, sector 793984 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
Aug  1 10:43:07 jaakob kernel: [ 8272.638839] Buffer I/O error on dev sdb1, 
logical block 198489, lost async page write
Aug  1 10:43:07 jaakob kernel: [ 8272.638842] 

[Bug 1937128] Re: package nvidia-dkms-470 (not installed) failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10

[Michael Lueck]

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 kernel on still
successfully runs VirtualBox. This system I applied the 5.8.0-63-generic
kernel to has both the nvidia driver issue and no longer will run
VirtualBox. I will not update the kernel on that still working system.

I tried booting this impacted system back to the 5.8.0-59-generic
kernel. VirtualBox still work not work... complains its kernel drivers
will not load.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937128

Title:
  package nvidia-dkms-470 (not installed) failed to install/upgrade:
  installed nvidia-dkms-470 package post-installation script subprocess
  returned error exit status 10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1937128/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1937128] Re: package nvidia-dkms-470 (not installed) failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10

[Michael Lueck]

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: [2170748.708122] NVRM: make sure that this 
kernel module and all NVIDIA driver
Jul 31 10:51:25 jaakob kernel: [2170748.708122] NVRM: components have the same 
version.

How best to get assistance in recovering from the upgrade damage? I am
thinking to try to fall back to the 460 version. The 465 package seems
to now be a meta package pointed at version 470.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937128

Title:
  package nvidia-dkms-470 (not installed) failed to install/upgrade:
  installed nvidia-dkms-470 package post-installation script subprocess
  returned error exit status 10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1937128/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1937128] Re: package nvidia-dkms-470 (not installed) failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10

[Michael Lueck]

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.net/bugs/1937128

Title:
  package nvidia-dkms-470 (not installed) failed to install/upgrade:
  installed nvidia-dkms-470 package post-installation script subprocess
  returned error exit status 10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1937128/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1934926] Re: Add a music player

[Michael Lueck]

+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/ubuntu/+source/xubuntu-meta/+bug/1934926/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1934932] Re: Add useful disk utilities

[Michael Lueck]

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.net/ubuntu/+source/xubuntu-meta/+bug/1934932/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 42178] Re: synaptic: ‘Lock Version’ is broken; use dpkg hold

[Michael Lueck]

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 20.04.2.

I inquired about the trouble here:
"20.04.2 system - Will not respect Synaptic package lock at a specific version"
https://ubuntuforums.org/showthread.php?t=2464498=14047839

The workaround I found is:

$ sudo apt-mark hold firefox-esr-mozilla-build
$ sudo apt-mark hold firefox-mozilla-build
$ apt-mark showhold
firefox-esr-mozilla-build
firefox-mozilla-build

When I started, apt-mark did not see the lock on the two packages the
Synaptic UI still recognized.

Now Synaptic no longer tries to update the packages from the versions I
want maintained.

So Synaptic appears not to leverage the same flag that apt-mark is
using? That seems odd and incorrect if that is the case. I would think
to be dpkg compatible, Synaptic should use the same flag as other dpkg /
apt tools, no?

Anyway, for us this is a definite new break moving from 16.04 to 20.4.2
versions.

-- 
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/42178

Title:
  synaptic: ‘Lock Version’ is broken; use dpkg hold

To manage notifications about this bug go to:
https://bugs.launchpad.net/synaptic/+bug/42178/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1834203] Re: Copying small files over CIFS doesn't close its window

[Michael Lueck]

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 small files over CIFS doesn't close its window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1834203/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1834203] Re: Copying small files over CIFS doesn't close its window

[Michael Lueck]

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 regularly "hangs" copying files with
Thunar involving the SAMBA mounted shares.

I would rather not install Dolphin as it is KDE based.

This was reported back on: Date: Tue Jun 25 13:03:59 2019

Could we get some traction to resolve this defect and roll out the
needed update?

I am thankful,
Michael

-- 
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 small files over CIFS doesn't close its window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1834203/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1912276] UbiquitySyslog.txt

[Michael Lueck]

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/1912276

Title:
  Ubuntu Server 20.04 installation to drive with BIOS set to legacy mode
  results in non-booting drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1912276/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1912276] Re: Ubuntu Server 20.04 installation to drive with BIOS set to legacy mode results in non-booting drive

[Michael Lueck]

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=14015093
  
  I suspect there might be a defect in Ubuntu Server 20.04 ISO. I was
  loading it onto a ThinkPad to test out the new Ubuntu Server LTS
  release. I had the ThinkPad BIOS set to boot from legacy mode disks, all
  UEFI disabled.
  
  The partitions Ubuntu Server 20.04 created for me were as follows:
  
  Disklabel Type: gpt
  sda1 BIOS Boot
  sda2 Linux filesystem (which I selected xfs)
  
  The system failed to boot from the HDD. When trying to boot from the
  system's HDD, I only am able to get the ThinkPad "Boot Menu /
  Application Menu" screen to come up. Selecting ATA HDD0 loops back
  around to the same menu.
  
  It was suggested that Ubuntu 20.04 really prefers to boot from drives in
  UEFI mode. I changes the BIOS settings, wiped the disk during another
  test installation. This time the partitions the installer created were
  as follows:
  
  Disklabel Type: gpt
  sda1 EFI System
  sda2 Linux filesystem (which I selected xfs)
  
  And the system does boot from the HDD now.
  
  So is this a defect in the installer for Ubuntu Server 20.04 that it
  does not produce a bootable drive when the computer BIOS is set to
  legacy boot mode?
  
  I was expecting to see the legacy boot partition table type not be a gpt
  partition table. Might that have something to do with the failure to
  boot?
  
  I think the fact that for the legacy boot installation, Ubuntu Server
  did at least create a first partition of type "BIOS boot".
  
  <><><><>
  
  I tried the same installation on the same ThinkPad from the
  ubuntu-20.04.1-live-server-amd64.iso disk. Same results as before.
  
  Looks like Ubuntu Server has a defect booting from disks where the BIOS
  is set to legacy mode.
  
  This is not broken in Xubuntu 20.04 installation.
  
  Logging an Ubuntu Server installer defect.
  
  <><><><>
  
- Xubuntu 20.04 does NOT have this same defect. Xubuntu 20.04 boots
- properly when installed to systems with the BIOS set to legacy mode for
- the hard drive access setting.
+ Xubuntu 20.04 does NOT have this same defect. Xubuntu 20.04 boots properly 
when installed to systems with the BIOS set to legacy mode for the hard drive 
access setting.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ DistroRelease: Ubuntu 20.04
+ InstallCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=468b6f29-36bc-4b5f-b089-3f3ad0f91cf4 ro
+ InstallationDate: Installed on 2021-01-18 (0 days ago)
+ InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
+ Package: ubiquity (not installed)
+ ProcEnviron:
+  TERM=linux
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
+ SourcePackage: ubiquity
+ Tags:  focal uec-images
+ Uname: Linux 5.4.0-26-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lxd plugdev sudo
+ _MarkForUpload: True

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1912276/+attachment/5454515/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912276

Title:
  Ubuntu Server 20.04 installation to drive with BIOS set to legacy mode
  results in non-booting drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1912276/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1912276] [NEW] Ubuntu Server 20.04 installation to drive with BIOS set to legacy mode results in non-booting drive

[Michael Lueck]

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=14015093

I suspect there might be a defect in Ubuntu Server 20.04 ISO. I was
loading it onto a ThinkPad to test out the new Ubuntu Server LTS
release. I had the ThinkPad BIOS set to boot from legacy mode disks, all
UEFI disabled.

The partitions Ubuntu Server 20.04 created for me were as follows:

Disklabel Type: gpt
sda1 BIOS Boot
sda2 Linux filesystem (which I selected xfs)

The system failed to boot from the HDD. When trying to boot from the
system's HDD, I only am able to get the ThinkPad "Boot Menu /
Application Menu" screen to come up. Selecting ATA HDD0 loops back
around to the same menu.

It was suggested that Ubuntu 20.04 really prefers to boot from drives in
UEFI mode. I changes the BIOS settings, wiped the disk during another
test installation. This time the partitions the installer created were
as follows:

Disklabel Type: gpt
sda1 EFI System
sda2 Linux filesystem (which I selected xfs)

And the system does boot from the HDD now.

So is this a defect in the installer for Ubuntu Server 20.04 that it
does not produce a bootable drive when the computer BIOS is set to
legacy boot mode?

I was expecting to see the legacy boot partition table type not be a gpt
partition table. Might that have something to do with the failure to
boot?

I think the fact that for the legacy boot installation, Ubuntu Server
did at least create a first partition of type "BIOS boot".

<><><><>

I tried the same installation on the same ThinkPad from the
ubuntu-20.04.1-live-server-amd64.iso disk. Same results as before.

Looks like Ubuntu Server has a defect booting from disks where the BIOS
is set to legacy mode.

This is not broken in Xubuntu 20.04 installation.

Logging an Ubuntu Server installer defect.

<><><><>

Xubuntu 20.04 does NOT have this same defect. Xubuntu 20.04 boots
properly when installed to systems with the BIOS set to legacy mode for
the hard drive access setting.

** Affects: ubiquity (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/1912276

Title:
  Ubuntu Server 20.04 installation to drive with BIOS set to legacy mode
  results in non-booting drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1912276/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1854137] Re: Gigolo trys to use port 21 for SMB/CIFS connect

[Michael Lueck]

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 resolved.

-- 
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 connect

To manage notifications about this bug go to:
https://bugs.launchpad.net/gigolo/+bug/1854137/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1279557] Re: Support ntfs partition type for brand new blank hard drives

[Michael Lueck]

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
installer would still properly detect the NTFS partitions, allow mount
points to be assigned to the ntfs partitions. It already was working
that way six years ago when I opened this enhancement request ticket.

Again, the use-case to request this enhancement would be to produce
dual-boot Linux/Windows configurations.

No progress / changes... please leave open to be addressed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1279557

Title:
  Support ntfs partition type for brand new blank hard drives

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1279557/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1834203] Re: Copying small files over CIFS doesn't close its window

[Michael Lueck]

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 Windows drive letter shares.

Using Thunar to transfer/copy files across the SAMBA mount... the
operation gets started, then the progress stalls, and canceling the copy
progress box never goes away. I close the windows, logoff the SAMBA
server, reboot.

Logged into SAMBA and copying at a terminal window is successful. So I
know it is not an issue with the underlying SAMBA mounts. I can
successfully copy both ways (client to server / server to client) in a
terminal window.

Again, this is a new defect since Xubuntu 16.04. Present in the beta of
Xubuntu 20.04.

-- 
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 small files over CIFS doesn't close its window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1834203/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1861937] Re: synaptic dialog boxes too tall with empty space for screen to display

[Michael Lueck]

** 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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861937

Title:
  synaptic dialog boxes too tall with empty space for screen to display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1861937/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1861937] [NEW] synaptic dialog boxes too tall with empty space for screen to display

[Michael Lueck]

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 height
seems to be fixed.

The only option available to get past this dialog box is to push the
corner X to close the dialog.

** Affects: synaptic (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Error resulting from a repository key not being properly 
installed"
   
https://bugs.launchpad.net/bugs/1861937/+attachment/5325427/+files/SynapticDialogBoxTooTallIssue2.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861937

Title:
  synaptic dialog boxes too tall with empty space for screen to display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1861937/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1854137] Re: Gigolo trys to use port 21 for SMB/CIFS connect

[Michael Lueck]

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 connect

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gigolo/+bug/1854137/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1759450] Re: Raleigh theme has hardly visible controls

[Michael Lueck]

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 any good. "Bug / defect"

-- 
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 has hardly visible controls

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1759450/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1759450] Re: Raleigh theme has hardly visible controls

[Michael Lueck]

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 has hardly visible controls

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1759450/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1759450] [NEW] Raleigh theme has hardly visible controls

[Michael Lueck]

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_assembled_attractive_dark_blue_theme_for_Xfce_with_Raleigh_Adwaita_and_Moheli_on_Xubuntu_16.04

1) First set the window style and icons as follows:
Settings Manager \ Appearance \ Style tab \ select Raleigh
Settings Manager \ Appearance \ Icons tab \ select Adwaita

Click the button labeled "All Settings" to go back to the main Settings
Manager

2) Next set the window manager as follows:
Settings Manager \ Window Manager \ Style tab \ select Moheli

And #4

4) Finally, edit the ~/.gtkrc-2.0 configuration file:
# Custom styles

style "default"
{
  bg[SELECTED] = "#3B5998" #Active Window Title Bar
}

style "entry" = "default"
{
  text[SELECTED] = "#FF" #Input control selected text
}

class "GtkWidget" style "default"
class "GtkEntry" style "entry"

# End custom styles


The text field of the password box is invisible. The buttons on the
password box are invisible.

Results of the Synaptic screen are also provided.

The issue seems to be in the Raleigh Style. Switching to the Greybird
Style at least fixes the invisible controls.

What has happened to the Raleigh Style?

** Affects: xubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Authentication Is Required Dialog Box"
   
https://bugs.launchpad.net/bugs/1759450/+attachment/5093028/+files/AuthenticationIsRequired-Versions.png

-- 
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 has hardly visible controls

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1759450/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1759450] Re: Raleigh theme has hardly visible controls

[Michael Lueck]

** 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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759450

Title:
  Raleigh theme has hardly visible controls

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1759450/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1735431] [NEW] Not possible to navigate into hidden directories with file selector dialog box

[Michael Lueck]

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 Application
Launchers for Wine programs. Wine defaults to building its "C:\ Drive"
in an hidden (. leading) directory off the user's profile/home
directory. This makes it extremely difficult to navigate into that
directory when setting up an Application Launcher for a Wine program.

Please see attached screen shot of a clean setup of Xubuntu 18.04.

I end up needing to locate the Application Launcher on disk in a
terminal window, then edit it directly in a text editor. Sample edits of
a couple of Wine Application Launchers via grep:

Application Launchers located under this directory:

~/.config/xfce4/panel/

launcher-20/13563769951.desktop:Exec=/usr/bin/wine c:notesnotes.exe
launcher-20/13563769951.desktop:Icon=/home/mdlueck/.wine/drive_c/notes/notes64.png
launcher-20/13563769951.desktop:Icon[en_US]=/home/mdlueck/.wine/drive_c/notes/notes64.png


launcher-48/14782179451.desktop:Exec=/usr/bin/wine 'c:Program Files 
(x86)PMViewPMView.exe'
launcher-48/14782179451.desktop:Icon=/home/mdlueck/.wine/drive_c/Program Files 
(x86)/PMView/PMViewPro64.png
launcher-48/14782179451.desktop:Icon[en_US]=/home/mdlueck/.wine/drive_c/Program 
Files (x86)/PMView/PMViewPro64.png
launcher-48/14782179451.desktop:Name=PMView Pro
launcher-48/14782179451.desktop:Name[en_US]=PMView Pro

Two enhancement requests to facilitate not having to drop down to
terminal level:

1) Put a UI field to manually enter / paste in a physical path.
2) Add option to hide/show hidden files.

** Affects: xfdesktop4 (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Screenshot example of the issue"
   
https://bugs.launchpad.net/bugs/1735431/+attachment/5016579/+files/CreateLauncherIconSelectionNotPossibleToSelect.wineDirectoryFromHomeDirectory.png

** Summary changed:

- Nort possible to navigate into hidden directories with file selector dialog 
box
+ Not possible to navigate into hidden directories with file selector dialog box

** Description changed:

  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 Application
  Launchers for Wine programs. Wine defaults to building its "C:\ Drive"
  in an hidden (. leading) directory off the user's profile/home
  directory. This makes it extremely difficult to navigate into that
  directory when setting up an Application Launcher for a Wine program.
  
  Please see attached screen shot of a clean setup of Xubuntu 18.04.
  
  I end up needing to locate the Application Launcher on disk in a
  terminal window, then edit it directly in a text editor. Sample edits of
  a couple of Wine Application Launchers via grep:
  
+ Application Launchers located under this directory:
+ 
+ ~/.config/xfce4/panel/
+ 
  launcher-20/13563769951.desktop:Exec=/usr/bin/wine c:notesnotes.exe
  
launcher-20/13563769951.desktop:Icon=/home/mdlueck/.wine/drive_c/notes/notes64.png
  
launcher-20/13563769951.desktop:Icon[en_US]=/home/mdlueck/.wine/drive_c/notes/notes64.png
+ 
  
  launcher-48/14782179451.desktop:Exec=/usr/bin/wine 'c:Program Files 
(x86)PMViewPMView.exe'
  launcher-48/14782179451.desktop:Icon=/home/mdlueck/.wine/drive_c/Program 
Files (x86)/PMView/PMViewPro64.png
  
launcher-48/14782179451.desktop:Icon[en_US]=/home/mdlueck/.wine/drive_c/Program 
Files (x86)/PMView/PMViewPro64.png
  launcher-48/14782179451.desktop:Name=PMView Pro
  launcher-48/14782179451.desktop:Name[en_US]=PMView Pro
  
  Two enhancement requests to facilitate not having to drop down to
  terminal level:
  
  1) Put a UI field to manually enter / paste in a physical path.
  2) Add option to hide/show hidden files.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735431

Title:
  Not possible to navigate into hidden directories with file selector
  dialog box

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1735431/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1281329] Re: Sync up 14.04 release with latest avaiable version from project

[Michael Lueck]

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 release with latest avaiable version from project

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sql-ledger/+bug/1281329/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1662550] Re: After LTS upgrade to 16.04, no more emails come from apt-listchanges

[Michael Lueck]

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 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 emails come from apt-listchanges

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt-listchanges/+bug/1662550/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

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 smart
enough to detect/differentiate between Ubuntu Server vs Ubuntu LTS
upgrades and select the correct value.

-- 
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 Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1662550] Re: After LTS upgrade to 16.04, no more emails come from apt-listchanges

[Michael Lueck]

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 +0100

I spot in the conf which=news so what exactly is not being done when set
to 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 emails come from apt-listchanges

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt-listchanges/+bug/1662550/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1662550] Re: After LTS upgrade to 16.04, no more emails come from apt-listchanges

[Michael Lueck]

[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 emails come from apt-listchanges

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt-listchanges/+bug/1662550/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

@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/1656605

Title:
  No server console display after Grub screen until fully booted and
  pressing Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

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 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 Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1615318] Re: package daemontools-run 1:0.76-6ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Michael Lueck]

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-installation script returned error exit status 1
Setting up dialog (1.3-20160209-1) ...

== DuplicateSignature =
package:daemontools-run: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-installation script returned error exit status 1


== ErrorMessage =
subprocess installed post-installation script returned error exit status 1

== Package =
daemontools-run 1:0.76-6ubuntu1

== PackageArchitecture =
all

== ProblemType =
Package

== ProcVersionSignature =
Ubuntu 3.13.0-110.157-generic 3.13.11-ckt39

== RelatedPackageVersions =
dpkg 1.18.4ubuntu1.1
apt  1.2.19

== SourcePackage =
daemontools

== Tags =
 xenial

== Title =
package daemontools-run 1:0.76-6ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1

== Uname =
Linux 3.13.0-110-generic i686

== UpgradeStatus =
Upgraded to xenial on 2017-02-25 (0 days ago)


What would you like to do? Your options are:
  S: Send report (419.6 KB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): 


Issue still present with the 16.04 package being installed over top of the 
14.04 package.

Package dnscache-run was not downloaded during the LTS upgrade process,
only daemontools-run.

$ ls -al | grep dnscache-run
$ ls -al | grep daemontools-run
-rw-r--r-- 1 root root 6454 Jan  7  2015 
daemontools-run_1%3a0.76-6ubuntu1_all.deb

The "usual" uninstall / IPL / reinstall per #4 again was the work-
around.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615318

Title:
  package daemontools-run 1:0.76-6ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/daemontools/+bug/1615318/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

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_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""


So we had value: "quiet splash"

I tried your suggested value: ""  That worked, not quite the old user
experience, however.

I tried value: "splash" to see if that would bring back the "Ubuntu
" start-up splash screen. Nadda.

I next moved to value: "quiet"  That at least shows IPL progress, and
successfully lands at TTY1 login screen. We will run with this new
setting for now.

So question, was it intentional to no longer have "Ubuntu " IPL
'splash screen' during which Esc may be pressed to see the actual IPL
steps on the server console?

-- 
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 Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656605

Title:
  No server console display after Grub screen until fully booted and
  pressing Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

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://bugs.launchpad.net/bugs/1656605

Title:
  No server console display after Grub screen until fully booted and
  pressing Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

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 until fully booted and
  pressing Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

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 Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1662550] [NEW] After LTS upgrade to 16.04, no more emails come from apt-listchanges

[Michael Lueck]

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 available on the upgraded 16.04
server, I applied them, and apt-listchanges still sent no email.

More information, including output from both the 14.04 and 16.04 systems
located here:

"apt-listchanges no longer sending emails after 16.04 LTS upgrade"
https://ubuntuforums.org/showthread.php?t=2351236

** Affects: apt-listchanges (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/1662550

Title:
  After LTS upgrade to 16.04, no more emails come from apt-listchanges

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt-listchanges/+bug/1662550/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

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 until fully booted and
  pressing Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

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.13 and 3.19 appears to be where the damage
was done. Perhaps do a build of 3.16ish to begin a binary search method?

-- 
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 Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

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 after Grub screen until fully booted and
  pressing Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

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 console display after Grub screen until fully booted and
  pressing Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

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 which is causing this issue?

-- 
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 Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

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 advise what you need me to test next.

-- 
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 Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

... 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
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 Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

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 running the i386 kernel.

-- 
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 Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

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 plan to you, Joseph?

-- 
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 Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

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
kernel, in this case?

I am thinking to stay booted to the v4.4-wily kernel 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/1656605

Title:
  No server console display after Grub screen until fully booted and
  pressing Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

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 from applying it:

mdlueck@ldslnx01:/srv/shares/data/Download/OpenSource/Ubuntu/Xenial/Bugs/1656605_ServerNoConsoleDisplay/v4.5-wily$
 sudo dpkg -i 
linux-image-4.5.0-040500-generic_4.5.0-040500.201603140130_i386.deb 
Selecting previously unselected package linux-image-4.5.0-040500-generic.
(Reading database ... 59100 files and directories currently installed.)
Preparing to unpack 
linux-image-4.5.0-040500-generic_4.5.0-040500.201603140130_i386.deb ...
Done.
Unpacking linux-image-4.5.0-040500-generic (4.5.0-040500.201603140130) ...
Setting up linux-image-4.5.0-040500-generic (4.5.0-040500.201603140130) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
4.5.0-040500-generic /boot/vmlinuz-4.5.0-040500-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 
4.5.0-040500-generic /boot/vmlinuz-4.5.0-040500-generic
update-initramfs: Generating /boot/initrd.img-4.5.0-040500-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 
4.5.0-040500-generic /boot/vmlinuz-4.5.0-040500-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.5.0-040500-generic 
/boot/vmlinuz-4.5.0-040500-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.10.0-041000rc4-generic
Found initrd image: /boot/initrd.img-4.10.0-041000rc4-generic
Found linux image: /boot/vmlinuz-4.5.0-040500-generic
Found initrd image: /boot/initrd.img-4.5.0-040500-generic
Found linux image: /boot/vmlinuz-4.4.0-59-generic
Found initrd image: /boot/initrd.img-4.4.0-59-generic
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
done

I will stay booted to this kernel version.

Please let me know if I may be of further assistance.

-- 
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 Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

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 Linux Kernel
4.8 either.

Anyway, do you need any further input from me? And can this be resolved
with the Linux Kernel 4.4 version? I would rather not have to apply a
hardware compatibility kernel to be able to run Ubuntu 16.04 on server
hardware from 2009.

-- 
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 Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1615318] Re: package daemontools-run 1:0.76-6ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Michael Lueck]

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

Then reinstalled them from the raw .deb files I had downloaded to the
server.

$sudo dpkg -i daemontools-run_0.76-6ubuntu1_all.deb
$sudo dpkg -i dnscache-run_1.05-8ubuntu1_all.deb

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615318

Title:
  package daemontools-run 1:0.76-6ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/daemontools/+bug/1615318/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

** 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
  pressing Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

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.201701152031_i386.deb 
[sudo] password for mdlueck: 
Selecting previously unselected package linux-image-4.10.0-041000rc4-generic.
(Reading database ... 57910 files and directories currently installed.)
Preparing to unpack 
linux-image-4.10.0-041000rc4-generic_4.10.0-041000rc4.201701152031_i386.deb ...
Done.
Unpacking linux-image-4.10.0-041000rc4-generic (4.10.0-041000rc4.201701152031) 
...
Setting up linux-image-4.10.0-041000rc4-generic (4.10.0-041000rc4.201701152031) 
...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
4.10.0-041000rc4-generic /boot/vmlinuz-4.10.0-041000rc4-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 
4.10.0-041000rc4-generic /boot/vmlinuz-4.10.0-041000rc4-generic
update-initramfs: Generating /boot/initrd.img-4.10.0-041000rc4-generic
W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_01.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915
run-parts: executing /etc/kernel/postinst.d/update-notifier 
4.10.0-041000rc4-generic /boot/vmlinuz-4.10.0-041000rc4-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 
4.10.0-041000rc4-generic /boot/vmlinuz-4.10.0-041000rc4-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.10.0-041000rc4-generic
Found initrd image: /boot/initrd.img-4.10.0-041000rc4-generic
Found linux image: /boot/vmlinuz-4.4.0-59-generic
Found initrd image: /boot/initrd.img-4.4.0-59-generic
Found linux image: /boot/vmlinuz-3.13.0-107-generic
Found initrd image: /boot/initrd.img-3.13.0-107-generic
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
done

** Tags added: kernel-fixed-upstream

-- 
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 Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1617691] Re: do-release-upgrade daemontools-run fatal error

[Michael Lueck]

@ 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 14.04 package, which was able to
update the 12.04 version during the LTS upgrade process.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1617691

Title:
  do-release-upgrade daemontools-run fatal error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1617691/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

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.

No option to move the Nvidia board to the impacted server machine as
there is no PCI-e slot on the server boards. They have only one card
slot which is in use for the RAID controller.

-- 
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 Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

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:/srv/shares/data/Download/OpenSource/Ubuntu/Xenial/Bugs/1656605_ServerNoConsoleDisplay$
 cat /proc/cmdline > cmdline.log
mdlueck@ldslnx01:/srv/shares/data/Download/OpenSource/Ubuntu/Xenial/Bugs/1656605_ServerNoConsoleDisplay$
 cat consoles.log 
tty0 -WU (EC p  )4:1
mdlueck@ldslnx01:/srv/shares/data/Download/OpenSource/Ubuntu/Xenial/Bugs/1656605_ServerNoConsoleDisplay$
 cat cmdline.log
BOOT_IMAGE=/vmlinuz-4.4.0-59-generic 
root=UUID=87ad7999-94fd-4004-b898-d6a943e5895e ro quiet splash vt.handoff=7

BTW: Another server, same config still on 14.04 LTS shows output:

mdlueck@cirlnx01:~$ cat /proc/consoles
tty0 -WU (EC p  )4:1

$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.13.0-107-generic 
root=UUID=b8d89557-1fb2-4748-8708-f6ca416b7a87 ro quiet splash vt.handoff=7

So looks quite similar output. (I do not detect any red flags, at
least.)

** Attachment added: "consoles.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+attachment/4804628/+files/consoles.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:
  No server console display after Grub screen until fully booted and
  pressing Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

** 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:
  No server console display after Grub screen until fully booted and
  pressing Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] [NEW] No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

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 Ctrl-Alt-F1/8, and indeed pressing those hotkeys
does toggle through the tty screens.

There is no boot process logged to the server console screen.

I did have the last 14.04 kernel yet installed, so selected that one
from the Grub menu. Booting that 14.04 kernel, then server console
display behaves normally.

So I suspected perhaps a bum install of the 16.04 kernel. I used the
following commands while booted to the 14.04 kernel to reinstall the
16.04 kernel:

$ sudo dpkg -P linux-image-4.4.0-59-generic linux-image-extra-4.4.0-59-generic 
linux-image-generic
$ sudo apt-get install linux-image-generic

Same results booting the 16.04 kernel after those steps.

Hardware spec is an Intel Atom D945GCLF2D boxed motherboard with Intel
Atom 330 Dual-Core processor and 2GB RAM. RAID is 3Ware SATA RAID.

** Affects: linux-meta (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/1656605

Title:
  No server console display after Grub screen until fully booted and
  pressing Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

** 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

Title:
  No server console display after Grub screen until fully booted and
  pressing Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

** 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

Title:
  No server console display after Grub screen until fully booted and
  pressing Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

** 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:
  No server console display after Grub screen until fully booted and
  pressing Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

** 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/1656605

Title:
  No server console display after Grub screen until fully booted and
  pressing Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8

[Michael Lueck]

** 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/1656605

Title:
  No server console display after Grub screen until fully booted and
  pressing Ctrl-Alt-F1/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1656605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1617691] Re: do-release-upgrade daemontools-run fatal error

[Michael Lueck]

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
$sudo dpkg -i dnscache-run_1.05-8ubuntu1_all.deb

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1617691

Title:
  do-release-upgrade daemontools-run fatal error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1617691/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1617691] Re: do-release-upgrade daemontools-run fatal error

[Michael Lueck]

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 this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1617691

Title:
  do-release-upgrade daemontools-run fatal error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1617691/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1643227] [NEW] Missing former files from package gnome-themes-extras in trusty

[Michael Lueck]

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 Trusty vs Xenial I observe:

1) No .theme files, which I believe is why I do not see any additional
entries showing up in: Settings Manager \ Appearance \ Icons

2) No Foxtrot or Gion files / directories.

Thus I do not see how package gnome-icon-theme-extras in Xenial is a
forward replacement for package gnome-themes-extras in Trusty.

What package are the Foxtrot or Gion icon sets supposed to be in for the
Xenial release?

** Affects: gnome-icon-theme-extras (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/1643227

Title:
  Missing former files from package gnome-themes-extras in trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme-extras/+bug/1643227/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1585614] Re: libc on 2016-05-25 causes Apache not to restart, libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

[Michael Lueck]

@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 are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585614

Title:
  libc on 2016-05-25 causes Apache not to restart, libm.so.6: symbol
  __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6
  with link time reference

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1585614/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1585614] Re: PHP Update on 2016-05-25 causes Apache not to restart, libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

[Michael Lueck]

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 on 2016-05-25 causes Apache not to restart, libm.so.6:
  symbol __strtold_nan, version GLIBC_PRIVATE not defined in file
  libc.so.6 with link time reference

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1585614/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1585614] Re: PHP Update on 2016-05-25 causes Apache not to restart, libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

[Michael Lueck]

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

Title:
  PHP Update on 2016-05-25 causes Apache not to restart, libm.so.6:
  symbol __strtold_nan, version GLIBC_PRIVATE not defined in file
  libc.so.6 with link time reference

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1585614/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1585614] Re: PHP Update on 2016-05-25 causes Apache not to restart, libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

[Michael Lueck]

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/1585614

Title:
  PHP Update on 2016-05-25 causes Apache not to restart, libm.so.6:
  symbol __strtold_nan, version GLIBC_PRIVATE not defined in file
  libc.so.6 with link time reference

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1585614/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs