[Bug 2058910] [NEW] package yaru-cinnamon-theme-icon 23.10.2 [modified: usr/share/icons/Yaru-cinnamon/icon-theme.cache] failed to install/upgrade: trying to overwrite '/usr/share/icons/Yaru-bark-dark/

[Gene Soo]

Public bug reported:

Crash occured during first boot after installing Cinnamon Daily Build
24.04.

ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: yaru-cinnamon-theme-icon 23.10.2 [modified: 
usr/share/icons/Yaru-cinnamon/icon-theme.cache]
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Sun Mar 24 20:38:33 2024
Dependencies:
 
DuplicateSignature:
 package:yaru-cinnamon-theme-icon:23.10.2 [modified: 
usr/share/icons/Yaru-cinnamon/icon-theme.cache]
 Unpacking yaru-cinnamon-theme-icon (24.04) over (23.10.2) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-SIIsV8/245-yaru-cinnamon-theme-icon_24.04_all.deb 
(--unpack):
  trying to overwrite '/usr/share/icons/Yaru-bark-dark/index.theme', which is 
also in package yaru-theme-icon 23.10.0-0ubuntu2
ErrorMessage: trying to overwrite 
'/usr/share/icons/Yaru-bark-dark/index.theme', which is also in package 
yaru-theme-icon 23.10.0-0ubuntu2
InstallationDate: Installed on 2024-02-07 (46 days ago)
InstallationMedia: Ubuntu-Cinnamon 24.04 LTS "Noble Numbat" - Daily amd64 
(20240207)
PackageArchitecture: all
Python3Details: /usr/bin/python3.12, Python 3.12.2, python3-minimal, 
3.12.1-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.22.4ubuntu5
 apt  2.7.12
SourcePackage: ubuntucinnamon-environment
Title: package yaru-cinnamon-theme-icon 23.10.2 [modified: 
usr/share/icons/Yaru-cinnamon/icon-theme.cache] failed to install/upgrade: 
trying to overwrite '/usr/share/icons/Yaru-bark-dark/index.theme', which is 
also in package yaru-theme-icon 23.10.0-0ubuntu2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntucinnamon-environment (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package noble package-conflict

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

Title:
  package yaru-cinnamon-theme-icon 23.10.2 [modified:
  usr/share/icons/Yaru-cinnamon/icon-theme.cache] failed to
  install/upgrade: trying to overwrite '/usr/share/icons/Yaru-bark-
  dark/index.theme', which is also in package yaru-theme-icon
  23.10.0-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntucinnamon-environment/+bug/2058910/+subscriptions


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

[Bug 1951708] [NEW] ubiquity installer crash ubuntu desktop daily build 22.04

[Gene Soo]

Public bug reported:

hard crash performing installation.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 21.10.10
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.465
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 20 17:29:52 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211120)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy ubiquity-21.10.10 ubuntu

** Summary changed:

- ubiquity installer crash ubunsutu desktop daily build 22.04
+ ubiquity installer crash ubuntu desktop daily build 22.04

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

Title:
  ubiquity installer crash ubuntu desktop daily build 22.04

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


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

[Bug 1950820] [NEW] installer failed kubuntu 22.04 daily buld ubiquity

[Gene Soo]

Public bug reported:

I received a hard installer failure during installation. No command
prompt was shown such that I could comply with the recommended action to
issue ubuntu-bug ubiquity to report the issue. I had to complete
termination of the installer and return back to live KDE to get a
terminal session to make this report.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 21.10.10
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.465
CurrentDesktop: KDE
Date: Fri Nov 12 14:09:31 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2022)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy kubuntu ubiquity-21.10.10

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

Title:
  installer failed kubuntu 22.04 daily buld ubiquity

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


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

[Bug 1943071] Re: ubuntustudio 21.10 daily build installation error

[Gene Soo]

The attachment contains a screenshot of the error received. The
installation stops with this error.

** Attachment added: "Screenshot Error Messages"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1943071/+attachment/5523919/+files/VirtualBox_U2110STUDLY_08_09_2021_13_04_30.png

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

Title:
  ubuntustudio 21.10 daily build installation error

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


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

[Bug 1943071] [NEW] ubuntustudio 21.10 daily build installation error

[Gene Soo]

Public bug reported:

Receiving Error Installation Failed Package Manager Error return error
code 100 during install of UbuntuStudio Daily Build 21.10. I will attach
a screenshot once this problem record is created.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: ubuntu-release-upgrader-core 1:21.10.7
ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1
Uname: Linux 5.13.0-14-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu68
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.465
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Wed Sep  8 13:26:48 2021
LiveMediaBuild: Ubuntu-Studio 21.10 "Impish Indri" - Alpha amd64 (20210907)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade impish

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

Title:
  ubuntustudio 21.10 daily build installation error

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


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

[Bug 1918034] [NEW] ubiquity crash installing Ubuntu 21.04 Desktop Daily Build

[Gene Soo]

Public bug reported:

Failure occurs on Pending version of Daily Build.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity 21.04.9
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.460
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar  7 00:25:29 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210306)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug hirsute ubiquity-21.04.9 ubuntu

** Summary changed:

- Failubiquity crash installing Ubuntu 21.04 Desktop Daily Build
+ ubiquity crash installing Ubuntu 21.04 Desktop Daily Build

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

Title:
  ubiquity crash installing Ubuntu 21.04 Desktop Daily Build

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

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

[Bug 1902406] Re: ubiquity kubuntu 20.10 install screens truncated

[Gene Soo]

Trying again with the current installation of Kubuntu 21.04 Daily Build.
The attached screenshots are from the Install process. I believe
Ubiquity is in complete control of the installation and any  problems
with kscreen are not applicable unless Ubiquity has its own version.
These screenshots are captured before Kubuntu is installed. Please note
the first few screens may look correct left-justified. Proceeding
through the screens, the first indication of truncation is on the lower
right when Continue buttons become truncated as off-screen right. To
remedy this situation, double clicking the top title bar will readjust
screen positioning for lower right to be visible which causes truncation
of left side due left side of screen being off-screen.

** Attachment added: "U2104KDEDLY.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1902406/+attachment/5453189/+files/U2104KDEDLY.tar.gz

** Summary changed:

- ubiquity kubuntu 20.10 install screens truncated
+ ubiquity kubuntu 20.10 21.04 install screens truncated

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

Title:
  ubiquity kubuntu 20.10 21.04 install screens truncated

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

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

[Bug 1902406] Re: ubiquity kubuntu 20.10 install screens truncated

[Gene Soo]

Trying again with the current installation of Kubuntu 21.04 Daily Build.
The attached screenshots are from the Install process. I believe
Ubiquity is in complete control of the installation and any  problems
with kscreen are not applicable unless Ubiquity has its own version.
These screenshots are captured before Kubuntu is installed. Please note
the first few screens may look correct left-justified. Proceeding
through the screens, the first indication of truncation is on the lower
right when Continue buttons become truncated as off-screen right. To
remedy this situation, double clicking the top title bar will readjust
screen positioning for lower right to be visible which causes truncation
of left side due left side of screen being off-screen.

** Attachment added: "U2104KDEDLY.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1902406/+attachment/5453188/+files/U2104KDEDLY.tar.gz

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

Title:
  ubiquity kubuntu 20.10 21.04 install screens truncated

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

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

[Bug 1903243] Re: package manpages 5.09-1 failed to install/upgrade: trying to overwrite '/usr/share/man/man3/queue.3.gz', which is also in package manpages-dev 5.08-1

[Gene Soo]

** Description changed:

  lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04
  
- Terminal Output from installation acript up to the point of failure:
- 
+ Terminal Output from installation script up to the point of failure:
  
  Selecting previously unselected package google-chrome-stable.
  (Reading database ... 169655 files and directories currently installed.)
  Preparing to unpack .../google-chrome-stable_current_amd64.deb ...
  Unpacking google-chrome-stable (86.0.4240.183-1) ...
  Setting up google-chrome-stable (86.0.4240.183-1) ...
  update-alternatives: using /usr/bin/google-chrome-stable to provide 
/usr/bin/x-www-browser (x-www-browser) in auto mode
  update-alternatives: using /usr/bin/google-chrome-stable to provide 
/usr/bin/gnome-www-browser (gnome-www-browser) in auto mode
  update-alternatives: using /usr/bin/google-chrome-stable to provide 
/usr/bin/google-chrome (google-chrome) in auto mode
  Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
  Processing triggers for desktop-file-utils (0.24-1ubuntu4) ...
  Processing triggers for mime-support (3.64ubuntu1) ...
  Processing triggers for man-db (2.9.3-2) ...
  Reading package lists... Done
- Building dependency tree   
+ Building dependency tree
  Reading state information... Done
  0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
  Hit:1 http://us.archive.ubuntu.com/ubuntu hirsute InRelease
  Get:2 http://dl.google.com/linux/chrome/deb stable InRelease [1,811 B]
  Hit:3 http://us.archive.ubuntu.com/ubuntu hirsute-updates InRelease
  Hit:4 http://us.archive.ubuntu.com/ubuntu hirsute-backports InRelease
  Ign:5 http://dl.google.com/linux/earth/deb stable InRelease
  Hit:6 http://us.archive.ubuntu.com/ubuntu hirsute-security InRelease
  Get:7 http://dl.google.com/linux/earth/deb stable Release [933 B]
  Get:8 http://dl.google.com/linux/earth/deb stable Release.gpg [819 B]
  Get:9 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages [1,093 
B]
  Get:10 http://dl.google.com/linux/earth/deb stable/main amd64 Packages [726 B]
  Fetched 5,382 B in 2s (2,553 B/s)
  Reading package lists... Done
- Building dependency tree   
+ Building dependency tree
  Reading state information... Done
  3 packages can be upgraded. Run 'apt list --upgradable' to see them.
  Reading package lists... Done
- Building dependency tree   
+ Building dependency tree
  Reading state information... Done
  E: Unable to locate package libgstreamer0.10-dev
  E: Couldn't find any package by glob 'libgstreamer0.10-dev'
  E: Unable to locate package libgstreamer-plugins-base0.10-dev
  E: Couldn't find any package by glob 'libgstreamer-plugins-base0.10-dev'
  E: Unable to locate package flashplugin-installer
  E: Unable to locate package libc6:i386
  --2020-11-05 22:53:12--  
http://archive.ubuntu.com/ubuntu/pool/main/l/lsb/lsb-security_4.1+Debian11ubuntu8_amd64.deb
  Resolving archive.ubuntu.com (archive.ubuntu.com)... 91.189.88.152, 
91.189.88.142, 2001:67c:1562::15, ...
  Connecting to archive.ubuntu.com (archive.ubuntu.com)|91.189.88.152|:80... 
connected.
  HTTP request sent, awaiting response... 404 Not Found
  2020-11-05 22:53:13 ERROR 404: Not Found.
  
  --2020-11-05 22:53:13--  
http://mirrors.kernel.org/ubuntu/pool/main/l/lsb/lsb-core_4.1+Debian11ubuntu6_amd64.deb
  Resolving mirrors.kernel.org (mirrors.kernel.org)... 149.20.37.36, 
2001:19d0:306:6:0:1994:3:14
  Connecting to mirrors.kernel.org (mirrors.kernel.org)|149.20.37.36|:80... 
connected.
  HTTP request sent, awaiting response... 301 Moved Permanently
  Location: 
http://mirrors.edge.kernel.org/ubuntu/pool/main/l/lsb/lsb-core_4.1+Debian11ubuntu6_amd64.deb
 [following]
  --2020-11-05 22:53:13--  
http://mirrors.edge.kernel.org/ubuntu/pool/main/l/lsb/lsb-core_4.1+Debian11ubuntu6_amd64.deb
  Resolving mirrors.edge.kernel.org (mirrors.edge.kernel.org)... 
147.75.197.195, 2604:1380:1:3600::1
  Connecting to mirrors.edge.kernel.org 
(mirrors.edge.kernel.org)|147.75.197.195|:80... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: 26244 (26K) [application/octet-stream]
  Saving to: ‘lsb-core_4.1+Debian11ubuntu6_amd64.deb’
  
  lsb-core_4.1+Debian 100%[===>]  25.63K  --.-KB/sin
  0.06s
  
  2020-11-05 22:53:13 (399 KB/s) - ‘lsb-
  core_4.1+Debian11ubuntu6_amd64.deb’ saved [26244/26244]
  
  --2020-11-05 22:53:13--  
http://archive.ubuntu.com/ubuntu/pool/main/l/lsb/lsb-invalid-mta_4.1+Debian11ubuntu8_all.deb
  Resolving archive.ubuntu.com (archive.ubuntu.com)... 91.189.88.142, 
91.189.88.152, 2001:67c:1562::18, ...
  Connecting to archive.ubuntu.com (archive.ubuntu.com)|91.189.88.142|:80... 
connected.
  HTTP request sent, awaiting response... 404 Not Found
  2020-11-05 22:53:13 ERROR 404: Not Found.
  
  Selecting previously unselected package lsb-core.
  (Reading database ... 169768 files and directories currently installed.)
  Preparing to unpack 

[Bug 1903243] [NEW] package manpages 5.09-1 failed to install/upgrade: trying to overwrite '/usr/share/man/man3/queue.3.gz', which is also in package manpages-dev 5.08-1

[Gene Soo]

Public bug reported:

lsb_release -rd
Description:Ubuntu Hirsute Hippo (development branch)
Release:21.04

Terminal Output from installation acript up to the point of failure:


Selecting previously unselected package google-chrome-stable.
(Reading database ... 169655 files and directories currently installed.)
Preparing to unpack .../google-chrome-stable_current_amd64.deb ...
Unpacking google-chrome-stable (86.0.4240.183-1) ...
Setting up google-chrome-stable (86.0.4240.183-1) ...
update-alternatives: using /usr/bin/google-chrome-stable to provide 
/usr/bin/x-www-browser (x-www-browser) in auto mode
update-alternatives: using /usr/bin/google-chrome-stable to provide 
/usr/bin/gnome-www-browser (gnome-www-browser) in auto mode
update-alternatives: using /usr/bin/google-chrome-stable to provide 
/usr/bin/google-chrome (google-chrome) in auto mode
Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
Processing triggers for desktop-file-utils (0.24-1ubuntu4) ...
Processing triggers for mime-support (3.64ubuntu1) ...
Processing triggers for man-db (2.9.3-2) ...
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Hit:1 http://us.archive.ubuntu.com/ubuntu hirsute InRelease
Get:2 http://dl.google.com/linux/chrome/deb stable InRelease [1,811 B]
Hit:3 http://us.archive.ubuntu.com/ubuntu hirsute-updates InRelease
Hit:4 http://us.archive.ubuntu.com/ubuntu hirsute-backports InRelease
Ign:5 http://dl.google.com/linux/earth/deb stable InRelease
Hit:6 http://us.archive.ubuntu.com/ubuntu hirsute-security InRelease
Get:7 http://dl.google.com/linux/earth/deb stable Release [933 B]
Get:8 http://dl.google.com/linux/earth/deb stable Release.gpg [819 B]
Get:9 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages [1,093 B]
Get:10 http://dl.google.com/linux/earth/deb stable/main amd64 Packages [726 B]
Fetched 5,382 B in 2s (2,553 B/s)
Reading package lists... Done
Building dependency tree   
Reading state information... Done
3 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree   
Reading state information... Done
E: Unable to locate package libgstreamer0.10-dev
E: Couldn't find any package by glob 'libgstreamer0.10-dev'
E: Unable to locate package libgstreamer-plugins-base0.10-dev
E: Couldn't find any package by glob 'libgstreamer-plugins-base0.10-dev'
E: Unable to locate package flashplugin-installer
E: Unable to locate package libc6:i386
--2020-11-05 22:53:12--  
http://archive.ubuntu.com/ubuntu/pool/main/l/lsb/lsb-security_4.1+Debian11ubuntu8_amd64.deb
Resolving archive.ubuntu.com (archive.ubuntu.com)... 91.189.88.152, 
91.189.88.142, 2001:67c:1562::15, ...
Connecting to archive.ubuntu.com (archive.ubuntu.com)|91.189.88.152|:80... 
connected.
HTTP request sent, awaiting response... 404 Not Found
2020-11-05 22:53:13 ERROR 404: Not Found.

--2020-11-05 22:53:13--  
http://mirrors.kernel.org/ubuntu/pool/main/l/lsb/lsb-core_4.1+Debian11ubuntu6_amd64.deb
Resolving mirrors.kernel.org (mirrors.kernel.org)... 149.20.37.36, 
2001:19d0:306:6:0:1994:3:14
Connecting to mirrors.kernel.org (mirrors.kernel.org)|149.20.37.36|:80... 
connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: 
http://mirrors.edge.kernel.org/ubuntu/pool/main/l/lsb/lsb-core_4.1+Debian11ubuntu6_amd64.deb
 [following]
--2020-11-05 22:53:13--  
http://mirrors.edge.kernel.org/ubuntu/pool/main/l/lsb/lsb-core_4.1+Debian11ubuntu6_amd64.deb
Resolving mirrors.edge.kernel.org (mirrors.edge.kernel.org)... 147.75.197.195, 
2604:1380:1:3600::1
Connecting to mirrors.edge.kernel.org 
(mirrors.edge.kernel.org)|147.75.197.195|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 26244 (26K) [application/octet-stream]
Saving to: ‘lsb-core_4.1+Debian11ubuntu6_amd64.deb’

lsb-core_4.1+Debian 100%[===>]  25.63K  --.-KB/sin
0.06s

2020-11-05 22:53:13 (399 KB/s) - ‘lsb-
core_4.1+Debian11ubuntu6_amd64.deb’ saved [26244/26244]

--2020-11-05 22:53:13--  
http://archive.ubuntu.com/ubuntu/pool/main/l/lsb/lsb-invalid-mta_4.1+Debian11ubuntu8_all.deb
Resolving archive.ubuntu.com (archive.ubuntu.com)... 91.189.88.142, 
91.189.88.152, 2001:67c:1562::18, ...
Connecting to archive.ubuntu.com (archive.ubuntu.com)|91.189.88.142|:80... 
connected.
HTTP request sent, awaiting response... 404 Not Found
2020-11-05 22:53:13 ERROR 404: Not Found.

Selecting previously unselected package lsb-core.
(Reading database ... 169768 files and directories currently installed.)
Preparing to unpack lsb-core_4.1+Debian11ubuntu6_amd64.deb ...
Unpacking lsb-core (4.1+Debian11ubuntu6) ...
dpkg: dependency problems prevent configuration of lsb-core:
 lsb-core depends on libncurses5; however:
  Package libncurses5 is not installed.
 lsb-core depends on lsb-invalid-mta (>= 4.1+Debian11ubuntu6) | 
mail-transport-agent; however:
  Package 

[Bug 1902406] Re: ubiquity kubuntu 20.10 install screens truncated

[Gene Soo]

I am a Kubuntu user and do not know all of the group responsibilities.
If anyone knows the proper group responsibility, I welcome that this
record is reassigned to the appropriate group.

I've experienced the issue reported by the record
https://bugs.kde.org/show_bug.cgi?id=407058#c9.

I would submit that this may be appropriate if you follow the navigation
"Try Kubuntu", attempt to change the display Resolution to higher than
800x600 which is not performed, and then Install Kubuntu. My impression
was that Ubiquity is responsible for the entire install process. If that
is not the case then please forward this to the correct group.

No matter which group is responsible, the user should not be forced to
change display resolutions during the install process and be exposed to
truncated information.

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

Title:
  ubiquity kubuntu 20.10 install screens truncated

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

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

[Bug 1902406] [NEW] ubiquity kubuntu 20.10 install screens truncated

[Gene Soo]

Public bug reported:

Performing the installation of Kubuntu 20.10 from kubuntu-20.10-desktop-
amd64.iso, the installation screens exceed the size of the available
window. In the initial windows, data is missing to the right while the
"Install Kubuntu" button is visible. Starting on the next screen
"keyboard Layout", the "Back" button is visible however the "Continue"
button is off-screen and requires the user to drag the window to the
left to see that button in order to proceed. This now positions the
window to possibly see subsequent buttons positioned on the lower right
of succeeding panes but now the Installation progress data in the
leftmost column of the panes is now not visible. The user will have to
scroll left to see that information. All of the other ubuntu
distributions ensure that local  scrolling is not required to navigate
through the install process.

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


** Tags: kubuntu ubiquity

** Attachment added: "Screenshots"
   
https://bugs.launchpad.net/bugs/1902406/+attachment/5429940/+files/U2010KDEGA%20Screenshots.zip

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

Title:
  ubiquity kubuntu 20.10 install screens truncated

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

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

[Bug 1885414] Re: on flavours ubiquity: bootloader failed on /dev/vda

[Gene Soo]

This problem seems to be corrected in the Xubuntu 20.10 Daily Build
effective 2020-10-19 running normal BIOS non-EFI mode.

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

Title:
  on flavours ubiquity: bootloader failed on /dev/vda

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

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

[Bug 1885414] Re: on flavours ubiquity: bootloader failed on /dev/vda

[Gene Soo]

As of 2020-10-03, this issue is still happening on both the 20.10
Xubuntu Daily Build and the recently released Xubuntu Beta 20.10
xubuntu-20.10-beta-desktop-amd64.iso.

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

Title:
  on flavours ubiquity: bootloader failed on /dev/vda

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

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

[Bug 1885414] Re: on flavours ubiquity: bootloader failed on /dev/vda

[Gene Soo]

I have been trying Xubuntu 20.10 Daily Build and as of today, this issue
seems to prevent it from being installed.

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

Title:
  on flavours ubiquity: bootloader failed on /dev/vda

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

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

Re: [Bug 1801408] Re: disco installer crashed with usr-merge

[Gene Soo]

Appreciate the feedback. I suspected as much. I did not see the failure in
any of the other daily builds.

Thanks

Gene

On Wed, Nov 7, 2018 at 2:56 PM Jeremy Bicha  wrote:

> vmc, please try tomorrow's ISO. The fixed ubiquity version wasn't
> released in time for today's Xubuntu iso build.
>
> You can see the specific ubiquity version if you look in the .manifest
> file provided in the same directory as the ISO.
>
> http://cdimage.ubuntu.com/xubuntu/daily-live/current/
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1801639).
> https://bugs.launchpad.net/bugs/1801408
>
> Title:
>   disco installer crashed with usr-merge
>
> Status in ubiquity package in Ubuntu:
>   Fix Released
> Status in ubiquity source package in Disco:
>   Fix Released
>
> Bug description:
>   disco installer crashed
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.04
>   Package: ubiquity 18.10.12
>   ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
>   Uname: Linux 4.18.0-10-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu14
>   Architecture: amd64
>   CasperVersion: 1.399
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Nov  2 19:28:27 2018
>   InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper
> initrd=/casper/initrd quiet splash --- maybe-ubiquity
>   LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181102)
>   ProcEnviron:
>LANGUAGE=en_GB.UTF-8
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_GB.UTF-8
>LC_NUMERIC=C.UTF-8
>   SourcePackage: ubiquity
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1801408/+subscriptions
>

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

Title:
  disco installer crashed with usr-merge

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

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

[Bug 1802175] [NEW] Crash during install

[Gene Soo]

Public bug reported:

Xubuntu Daily installer crash.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 18.10.12
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu14
Architecture: amd64
CasperVersion: 1.399
Date: Wed Nov  7 15:02:13 2018
InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
LiveMediaBuild: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco ubiquity-18.10.12 xubuntu

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

Title:
  Crash during install

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

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

[Bug 1801639] Re: Installation Crash 19.04 Budgie Daily

[Gene Soo]

After bug report completed, I got a Budgie environment to poke around. I
attempted an online install from the live session and got another error.
The error message referred to viewing /var/log/syslog. I have attached
that file for additional documentation.

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1801639/+attachment/5209199/+files/syslog

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

Title:
  Installation Crash 19.04 Budgie Daily

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

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

[Bug 1801639] [NEW] Installation Crash 19.04 Budgie Daily

[Gene Soo]

Public bug reported:

Possible dup of other Installer crashes for 19.04.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 18.10.12
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu14
Architecture: amd64
CasperVersion: 1.399
CurrentDesktop: Budgie
Date: Sun Nov  4 20:55:48 2018
InstallCmdLine: file=/cdrom/preseed/ubuntu-budgie.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
LiveMediaBuild: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20181104)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco ubiquity-18.10.12 ubuntu-budgie

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

Title:
  Installation Crash 19.04 Budgie Daily

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

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

[Bug 1761678] [NEW] Installer Crash

[Gene Soo]

Public bug reported:

.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.4
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CasperVersion: 1.392
Date: Fri Apr  6 02:08:25 2018
InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash ---
LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic lubuntu ubiquity-18.04.4

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

Title:
  Installer Crash

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

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

[Bug 1759692] [NEW] Lubuntu 18.04 Installer Crash

[Gene Soo]

Public bug reported:

N/A

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.3
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu1
Architecture: amd64
CasperVersion: 1.391
Date: Wed Mar 28 16:27:42 2018
InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash ---
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=err', '--lines=1000'] failed 
with exit code 1: Hint: You are currently not seeing messages from other users 
and the system.
   Users in groups 'adm', 'systemd-journal' can see all messages.
   Pass -q to turn off this notice.
 No journal files were opened due to insufficient permissions.
LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic lubuntu ubiquity-18.04.3

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

Title:
  Lubuntu 18.04 Installer Crash

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

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

[Bug 1756586] [NEW] crash on first boot of lubuntu after daily build install

[Gene Soo]

Public bug reported:

See summary.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.3
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.389
Date: Sat Mar 17 14:38:45 2018
InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash ---
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=err', '--lines=1000'] failed 
with exit code 1: Hint: You are currently not seeing messages from other users 
and the system.
   Users in groups 'adm', 'systemd-journal' can see all messages.
   Pass -q to turn off this notice.
 No journal files were opened due to insufficient permissions.
LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic lubuntu ubiquity-18.04.3

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

Title:
  crash on first boot of lubuntu after daily build install

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

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

[Bug 1756586] Re: crash on first boot of lubuntu after daily build install

[Gene Soo]

Correction to description. The install carshed before installation
completed.

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

Title:
  crash on first boot of lubuntu after daily build install

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

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

[Bug 1681108] [NEW] package grub-pc 2.02~beta3-4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10

[Gene Soo]

Public bug reported:

Summary descritipon does not mach list of reported issues.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: grub-pc 2.02~beta3-4ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
Uname: Linux 4.10.0-15-generic x86_64
ApportVersion: 2.20.4-0ubuntu3
Architecture: amd64
Date: Sat Apr  8 10:08:25 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 10
InstallationDate: Installed on 2017-04-08 (0 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170407)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-15-generic 
root=UUID=76d43fda-57e6-4526-8437-f28faa8ebb88 ro quiet splash
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.4
SourcePackage: grub2
Title: package grub-pc 2.02~beta3-4ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 10
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package grub-pc 2.02~beta3-4ubuntu2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 10

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

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

[Bug 1650720] [NEW] Ubiquity Crash

[Gene Soo]

Public bug reported:

Running KDE Daily Build and setting Display size to  one of the 1280
displays Ubiquity crashes. The Following traceback info was displayed in
a results window.


Traceback (most recent call last):
  File "/usr/lib/ubiquity/bin/ubiquity", line 655, in 
main(oem_config)
  File "/usr/lib/ubiquity/bin/ubiquity", line 639, in main
install(args[0], query=options.query)
  File "/usr/lib/ubiquity/bin/ubiquity", line 274, in install
ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 512, in run
if self.backup or self.dbfilter_handle_status():
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 857, in 
dbfilter_handle_status
QtWidgets.QMessageBox.Close)
TypeError: warning(QWidget, str, str, buttons: 
Union[QMessageBox.StandardButtons, QMessageBox.StandardButton] = 
QMessageBox.Ok, defaultButton: QMessageBox.StandardButton = 
QMessageBox.NoButton): too many arguments

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ubiquity 17.04.1
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
ApportVersion: 2.20.4-0ubuntu1
Architecture: amd64
CasperVersion: 1.379
CurrentDesktop: KDE
Date: Sat Dec 17 01:16:17 2016
InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
LiveMediaBuild: Kubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161216)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kubuntu ubiquity-17.04.1 zesty

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

Title:
  Ubiquity Crash

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

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

Re: [Bug 1595045] Re: Ubiquity Installer Crashes KDE Daily Build 16.10

[Gene Soo]

Sorry for the delay in replying. As far as I can tell, the problem is Not
happening in the Dailies any more.

On Thu, Jul 14, 2016 at 9:51 AM, Phillip Susi  wrote:

> Is this still happening with current daylies?
>
>
> ** Changed in: ubiquity (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1595045
>
> Title:
>   Ubiquity Installer Crashes KDE Daily Build 16.10
>
> Status in ubiquity package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Traceback (most recent call last):
> File "/usr/lib/ubiquity/bin/ubiquity", line 649, in 
>   main(oem_config)
> File "/usr/lib/ubiquity/bin/ubiquity", line 633, in main
>   install(args[0], query=options.query)
> File "/usr/lib/ubiquity/bin/ubiquity", line 268, in install
>   ret = wizard.run()
> File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 525, in run
>   self.start_slideshow()
> File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 641, in
> start_slideshow
>   webView = self._create_webview()
> File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 594, in
> _create_webview
>   from PyQt4.QtWebKit import QWebView
>   ImportError: No module named 'PyQt4.QtWebKit'
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.10
>   Package: ubiquity 16.10.2
>   ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13
>   Uname: Linux 4.4.0-25-generic x86_64
>   ApportVersion: 2.20.2-0ubuntu1
>   Architecture: amd64
>   CasperVersion: 1.376
>   Date: Wed Jun 22 00:45:00 2016
>   ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
>   InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper
> maybe-ubiquity initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
>   InterpreterPath: /usr/bin/python3.5
>   LiveMediaBuild: Kubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160621)
>   ProcEnviron:
>PATH=(custom, no user)
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: ubiquity
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1595045/+subscriptions
>

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

Title:
  Ubiquity Installer Crashes KDE Daily Build 16.10

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

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

[Bug 1595045] [NEW] Ubiquity Installer Crashes KDE Daily Build 16.10

[Gene Soo]

Public bug reported:

Traceback (most recent call last):
  File "/usr/lib/ubiquity/bin/ubiquity", line 649, in 
main(oem_config)
  File "/usr/lib/ubiquity/bin/ubiquity", line 633, in main
install(args[0], query=options.query)
  File "/usr/lib/ubiquity/bin/ubiquity", line 268, in install
ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 525, in run
self.start_slideshow()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 641, in 
start_slideshow
webView = self._create_webview()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 594, in 
_create_webview
from PyQt4.QtWebKit import QWebView
ImportError: No module named 'PyQt4.QtWebKit'

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubiquity 16.10.2
ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13
Uname: Linux 4.4.0-25-generic x86_64
ApportVersion: 2.20.2-0ubuntu1
Architecture: amd64
CasperVersion: 1.376
Date: Wed Jun 22 00:45:00 2016
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
InterpreterPath: /usr/bin/python3.5
LiveMediaBuild: Kubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160621)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kubuntu ubiquity-16.10.2 yakkety

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

Title:
  Ubiquity Installer Crashes KDE Daily Build 16.10

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

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

[Bug 1593258] [NEW] 16.10 KDE Daily Ubiquity Crash

[Gene Soo]

Public bug reported:

>From Exception Window upon error:

Traceback (most recent call last):
  File "/usr/lib/ubiquity/bin/ubiquity", line 649, in 
main(oem_config)
  File "/usr/lib/ubiquity/bin/ubiquity", line 633, in main
install(args[0], query=options.query)
  File "/usr/lib/ubiquity/bin/ubiquity", line 268, in install
ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 525, in run
self.start_slideshow()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 641, in 
start_slideshow
webView = self._create_webview()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 594, in 
_create_webview
from PyQt4.QtWebKit import QWebView
ImportError: No module named 'PyQt4.QtWebKit'

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubiquity 16.10.2
ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13
Uname: Linux 4.4.0-25-generic x86_64
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
CasperVersion: 1.376
Date: Thu Jun 16 09:31:43 2016
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
InterpreterPath: /usr/bin/python3.5
LiveMediaBuild: Kubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160616)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kubuntu ubiquity-16.10.2 yakkety

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

Title:
  16.10 KDE Daily Ubiquity Crash

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

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

[Bug 1591621] Re: ubiquity crash during install of kubuntu 16.10 daily

[Gene Soo]

Data from Error Popup:

Traceback (most recent call last):
  File "/usr/lib/ubiquity/bin/ubiquity", line 649, in 
main(oem_config)
  File "/usr/lib/ubiquity/bin/ubiquity", line 633, in main
install(args[0], query=options.query)
  File "/usr/lib/ubiquity/bin/ubiquity", line 268, in install
ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 525, in run
self.start_slideshow()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 641, in 
start_slideshow
webView = self._create_webview()
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 594, in 
_create_webview
from PyQt4.QtWebKit import QWebView
ImportError: No module named 'PyQt4.QtWebKit'

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

Title:
  ubiquity crash during install of kubuntu 16.10 daily

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

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

[Bug 1591621] [NEW] ubiquity crash during install of kubuntu 16.10 daily

[Gene Soo]

Public bug reported:

Hard crash of ubiquity during install process.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubiquity 16.10.2
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
CasperVersion: 1.376
Date: Sun Jun 12 01:52:27 2016
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
InterpreterPath: /usr/bin/python3.5
LiveMediaBuild: Kubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kubuntu ubiquity-16.10.2 yakkety

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

Title:
  ubiquity crash during install of kubuntu 16.10 daily

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

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

[Bug 1587555] Re: Installer crashed during installation

[Gene Soo]

I suspect there is something missing like needing to add Development
Repos to current GA Repos. I don't know what these are so if you have
that info, that would make the Workaround successful.

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

Title:
  Installer crashed during installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clock-setup/+bug/1587555/+subscriptions

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

[Bug 1587555] Re: Installer crashed during installation

[Gene Soo]

Tried KDE 16.04 LTS install and command above.
No Joy.

Command Results follow:
gene@U1610KDEDLYX:~$ sudo do-release-upgrade -d
Checking for a new Ubuntu release
No new release found
gene@U1610KDEDLYX:~$ uname -r
4.4.0-21-generic
gene@U1610KDEDLYX:~$ uname -a
Linux U1610KDEDLYX 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Installer crashed during installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clock-setup/+bug/1587555/+subscriptions

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

[Bug 1588427] [NEW] ubiquity crash Desktop 16.10 Daily

[Gene Soo]

Public bug reported:

Unknown Error.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubiquity 16.10.1
ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
Uname: Linux 4.4.0-23-generic x86_64
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
CasperVersion: 1.376
Date: Thu Jun  2 11:01:22 2016
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160601)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug third-party-packages ubiquity-16.10.1 ubuntu yakkety

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

Title:
  ubiquity crash Desktop 16.10 Daily

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

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

[Bug 1588419] [NEW] ubiquity crash during Mate 16.10 Daily Install

[Gene Soo]

Public bug reported:

Unknown Error Crashing ubiquity installer.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubiquity 16.10.1
ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
Uname: Linux 4.4.0-23-generic x86_64
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
CasperVersion: 1.376
Date: Thu Jun  2 10:35:29 2016
InstallCmdLine: file=/cdrom/preseed/ubuntu-mate.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
LiveMediaBuild: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20160602)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug ubiquity-16.10.1 ubuntu-mate yakkety

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

Title:
  ubiquity crash during Mate 16.10 Daily Install

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

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

[Bug 1588422] [NEW] ubiquity crash during Studio 16.10 Daily Install

[Gene Soo]

Public bug reported:

Unknown error.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubiquity 16.10.1
ProcVersionSignature: Ubuntu 4.4.0-23.41-lowlatency 4.4.10
Uname: Linux 4.4.0-23-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
CasperVersion: 1.376
Date: Thu Jun  2 10:41:14 2016
InstallCmdLine: file=/cdrom/preseed/ubuntustudio.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash ---
LiveMediaBuild: Ubuntu-Studio 16.10 "Yakkety Yak" - Alpha amd64 (20160601)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug ubiquity-16.10.1 ubuntustudio yakkety

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

Title:
  ubiquity crash during Studio 16.10 Daily Install

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

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

Re: [Bug 1578929] Re: UStudio 16.10 Daily Installation Fails ubi-console-setup exit code 1

[Gene Soo]

I downloaded and installed most of the Xenial Distros on the 22nd 2 days
after GA.
I just downloaded Ubuntu Desktop 64 from the URL you provided and it does
not have the problem.

On Fri, May 6, 2016 at 8:00 AM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> Is this only happening with the 16.10 daily images?  Can you see if it
> also happens with the Xenial image on the same setup?  It can be
> downloaded from:
>
> http://releases.ubuntu.com/xenial/
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> ** Tags added: kernel-da-key
>
> ** Also affects: linux (Ubuntu Yakkety)
>Importance: Medium
>Status: Confirmed
>
> ** Changed in: linux (Ubuntu Yakkety)
>Importance: Medium => High
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1578929
>
> Title:
>   UStudio 16.10 Daily Installation Fails ubi-console-setup exit code 1
>
> Status in linux package in Ubuntu:
>   Confirmed
> Status in linux source package in Yakkety:
>   Confirmed
>
> Bug description:
>   Hard Failure with this message during Choosing Keyboard "Continue".
>
>   Must cancel installation.
>
>   Received additional error
>   The Install encountered an error copying files to hard disk.
>
>   [Errno 2] No such file or directory:  '/target/usr/lib/x86_64-linux-
>   gnu/dri/vdpau_drv_video.so'
>
>   Rest of message directs you to possible faulty hard disk.
>
>   I am running under Virtualbox on solid hardware base so I strongly
>   doubt hardware is a problem.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.10
>   Package: linux-image-4.4.0-21-lowlatency 4.4.0-21.37
>   ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
>   Uname: Linux 4.4.0-21-lowlatency x86_64
>   ApportVersion: 2.20.1-0ubuntu2
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  ubuntu-studio   1887 F pulseaudio
>   CasperVersion: 1.376
>   CurrentDesktop: XFCE
>   Date: Fri May  6 01:05:34 2016
>   IwConfig:
>enp0s3no wireless extensions.
>
>lono wireless extensions.
>   LiveMediaBuild: Ubuntu-Studio 16.10 "Yakkety Yak" - Alpha amd64
> (20160505)
>   Lsusb:
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>   MachineType: innotek GmbH VirtualBox
>   ProcEnviron:
>TERM=xterm
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcFB:
>
>   ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed boot=casper
> only-ubiquity initrd=/casper/initrd.lz quiet splash ---
>   RelatedPackageVersions:
>linux-restricted-modules-4.4.0-21-lowlatency N/A
>linux-backports-modules-4.4.0-21-lowlatency  N/A
>linux-firmware   1.157
>   RfKill:
>
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/01/2006
>   dmi.bios.vendor: innotek GmbH
>   dmi.bios.version: VirtualBox
>   dmi.board.name: VirtualBox
>   dmi.board.vendor: Oracle Corporation
>   dmi.board.version: 1.2
>   dmi.chassis.type: 1
>   dmi.chassis.vendor: Oracle Corporation
>   dmi.modalias:
> dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
>   dmi.product.name: VirtualBox
>   dmi.product.version: 1.2
>   dmi.sys.vendor: innotek GmbH
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578929/+subscriptions
>

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

Title:
  UStudio 16.10 Daily Installation Fails ubi-console-setup exit code 1

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

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

[Bug 1578929] Re: UStudio 16.10 Daily Installation Fails ubi-console-setup exit code 1

[Gene Soo]

This error hits all of the GUI Distribution Installs. In other words the
only distribution not blown out of the water is Ubuntu Server.

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

Title:
  UStudio 16.10 Daily Installation Fails ubi-console-setup exit code 1

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

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

[Bug 1578929] [NEW] UStudio 16.10 Daily Installation Fails ubi-console-setup exit code 1

[Gene Soo]

Public bug reported:

Hard Failure with this message during Choosing Keyboard "Continue".

Must cancel installation.

Received additional error
The Install encountered an error copying files to hard disk.

[Errno 2] No such file or directory:  '/target/usr/lib/x86_64-linux-
gnu/dri/vdpau_drv_video.so'

Rest of message directs you to possible faulty hard disk.

I am running under Virtualbox on solid hardware base so I strongly doubt
hardware is a problem.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.4.0-21-lowlatency 4.4.0-21.37
ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
Uname: Linux 4.4.0-21-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ubuntu-studio   1887 F pulseaudio
CasperVersion: 1.376
CurrentDesktop: XFCE
Date: Fri May  6 01:05:34 2016
IwConfig:
 enp0s3no wireless extensions.
 
 lono wireless extensions.
LiveMediaBuild: Ubuntu-Studio 16.10 "Yakkety Yak" - Alpha amd64 (20160505)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:
 
ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed boot=casper 
only-ubiquity initrd=/casper/initrd.lz quiet splash ---
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-lowlatency N/A
 linux-backports-modules-4.4.0-21-lowlatency  N/A
 linux-firmware   1.157
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-bug yakkety

** Attachment added: "Log Files to Support Problem report"
   
https://bugs.launchpad.net/bugs/1578929/+attachment/4656905/+files/ubuntu-studio.tar.gz

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

Title:
  UStudio 16.10 Daily Installation Fails ubi-console-setup exit code 1

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

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

[Bug 1547297] Re: No auto login in Ubuntu GNOME Xenial

[Gene Soo]

Downloaded Daily Build for AMD64  4/8/16 15:59 at 4/8/16 15:49. Can't
explain why time stamp was 10 minutes ahead of current time.  This fix
does not seem to be incorporated with this build. Even though the fix
package accountsservice - 0.6.40-2ubuntu9 is available, it does no good
unless it is incorporated into the build.

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

Title:
  No auto login in Ubuntu GNOME Xenial

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

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

[Bug 1547297] Re: No auto login in Ubuntu GNOME Xenial

[Gene Soo]

I downloaded 4/7/16 15:37 Gnome AMD64 iso and this problem still exists.
I see that the issue was marked as Fixed. Is this drop supposed to
contain the fix or is there a delay in seeing this in the drop?

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

Title:
  No auto login in Ubuntu GNOME Xenial

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

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

[Bug 1558410] Re: Kubuntu 16.04 Daily Build Boot Stops at Desktop Folder

[Gene Soo]

I just performed a full download of cdimage.ubuntu.com/kubuntu/daily-
live/current/xenial-desktop-amd64.iso

Results were same stopping in Kubuntu Live Desktop with Desktop Folder
Open containing Icon to install same as first screenshot attached when
this incident opened.

If there is any additional commands I can issue to further prove this or
collect documentation then please supply instructions.

I am attaching with this update a Screenshot of 15.10 Install after the
boot, it leaves you in a Selection Window to choose Running Live Kubuntu
or Install Kubuntu,

** Attachment added: "Expected Installation Screen from 15.10"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1558410/+attachment/4624070/+files/VirtualBox_U1604KDEDLY_04_04_2016_22_32_49.png

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

Title:
  Kubuntu 16.04 Daily Build Boot Stops at Desktop Folder

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

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

[Bug 1566080] Re: Ubuntu Gnome Daily Build 16.04 Login No Password Does Not Work

[Gene Soo]

*** This bug is a duplicate of bug 1547297 ***
https://bugs.launchpad.net/bugs/1547297

** This bug has been marked a duplicate of bug 1547297
   No auto login in Ubuntu GNOME Xenial

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

Title:
  Ubuntu Gnome Daily Build 16.04 Login No Password Does Not Work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1566080/+subscriptions

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

[Bug 1566080] [NEW] Ubuntu Gnome Daily Build 16.04 Login No Password Does Not Work

[Gene Soo]

Public bug reported:

Selected option to suppress Password for Login. After installation completes. 
Password was required to signon.
Option to set this value is in All Settings , Users, My Account, Automatic 
Login.

Had to toggle from No to Yes.
This field should have been set during Install.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-shell 3.18.4-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Apr  4 19:39:14 2016
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'firefox.desktop', 
'evolution.desktop', 'empathy.desktop', 'rhythmbox.desktop', 
'org.gnome.Photos.desktop', 'libreoffice-writer.desktop', 
'org.gnome.Nautilus.desktop', 'yelp.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2016-04-05 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 (20160404)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  Ubuntu Gnome Daily Build 16.04 Login No Password Does Not Work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1566080/+subscriptions

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

Re: [Bug 1558410] Re: Kubuntu 16.04 Daily Build Boot Stops at Desktop Folder

[Gene Soo]

Please look at the attached screenshot.
I just tried to boot the KDE Daily Image from Last Night.
Boot leaves you at KDE Desktop with Desktop Folder Open and barely Visible
is the icon to Launch The Install Script.
I am running this under VirtualBox and Mouse Control is not synchronized.
In the past, I was able to use the mouse to launch the install process.

If you are running KickStart Scripted Install, please forgo that install
and try a manual install against the unmodified ISO.

On Tue, Mar 29, 2016 at 12:29 PM, Phillip Susi 
wrote:

> I am not able to reproduce this, are you?  If I don't touch anything to
> make the boot menu show, it boots up anyway and then you get the
> ubiquity welcome screen asking to choose your language and whether to
> try or install ubuntu.
>
>
> ** Changed in: ubiquity (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1558410
>
> Title:
>   Kubuntu 16.04 Daily Build Boot Stops at Desktop Folder
>
> Status in ubiquity package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Booting the Kubuntu  Daily Build 16.04, the boot stops showing the
>   Desktop Folder with an Icon to Install Kubuntu 16.04 LTS.
>
>   Formerly, the boot of the ISO would bring you to a screen that gave the
> Options to Try Kubuntu or Install Kubuntu.
>   This screen was consistent with all of the other Ubuntu Distributions.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: ubiquity 2.21.47
>   ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
>   Uname: Linux 4.4.0-11-generic x86_64
>   ApportVersion: 2.20-0ubuntu3
>   Architecture: amd64
>   CasperVersion: 1.367
>   Date: Thu Mar 17 07:04:31 2016
>   ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
>   InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper
> maybe-ubiquity initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
>   InterpreterPath: /usr/bin/python3.5
>   LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160310)
>   ProcEnviron:
>PATH=(custom, no user)
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: ubiquity
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1558410/+subscriptions
>


** Attachment added: "VirtualBox_U1604KDEDLY_29_03_2016_12_58_57.png"
   
https://bugs.launchpad.net/bugs/1558410/+attachment/4616189/+files/VirtualBox_U1604KDEDLY_29_03_2016_12_58_57.png

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

Title:
  Kubuntu 16.04 Daily Build Boot Stops at Desktop Folder

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

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

Re: [Bug 1556387] Re: Unity8 Login Hangs

[Gene Soo]

Attempted Remove and designated packages not found.

On Wed, Mar 16, 2016 at 4:47 PM, kevin gunn 
wrote:

> just double checking, can you
>
> $ sudo apt-get remove mir-client-platform-mesa3 mir-client-platform-
> mesa2 mir-client-platform-mesa1
>
> these are very old, if you have them hanging around they can cause
> problems.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1556387
>
> Title:
>   Unity8 Login Hangs
>
> Status in unity8 package in Ubuntu:
>   New
>
> Bug description:
>   Attempted to Install and Login using Unity8 on top of Ubuntu 16.04
> Desktop Build.
>   Am amble to Signon to Unity Desktop distributed by build however when I
> attempt to singon to Unity8, the password accepts but the Signon Screen
> does not go away. The only thing I can do is either shutdown the machine or
> Restart.
>
>   The following data is from my test image:
>   gene@U1604DSKDLYX:~$ uname -a
>   Linux U1604DSKDLYX 4.4.4-040404-generic #201603031931 SMP Fri Mar 4
> 00:34:16 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>   gene@U1604DSKDLYX:~$ sudo apt-get install unity8-desktop-session-mir
>   Reading package lists... Done
>   Building dependency tree
>   Reading state information... Done
>   unity8-desktop-session-mir is already the newest version
> (1.0.12+15.10.20150609-0ubuntu1).
>   0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1556387/+subscriptions
>

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

Title:
  Unity8 Login Hangs

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

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

[Bug 1558410] [NEW] Kubuntu 16.04 Daily Build Boot Stops at Desktop Folder

[Gene Soo]

Public bug reported:

Booting the Kubuntu  Daily Build 16.04, the boot stops showing the
Desktop Folder with an Icon to Install Kubuntu 16.04 LTS.

Formerly, the boot of the ISO would bring you to a screen that gave the Options 
to Try Kubuntu or Install Kubuntu.
This screen was consistent with all of the other Ubuntu Distributions.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.47
ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
Uname: Linux 4.4.0-11-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CasperVersion: 1.367
Date: Thu Mar 17 07:04:31 2016
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
InterpreterPath: /usr/bin/python3.5
LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160310)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kubuntu ubiquity-2.21.47 xenial

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

Title:
  Kubuntu 16.04 Daily Build Boot Stops at Desktop Folder

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

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

[Bug 1558479] [NEW] Installation Complete Restart Now Boot Hang

[Gene Soo]

Public bug reported:

Kubuntu 16.04 Daily Build. Installation Completes with Two Options.
Restart Now or Continue Testing. Selected Restart Now. Screen Goes black but 
machine fails to reboot.
Running as a VirtualBox Guest machine. Must Issue a restart in order to reboot 
machine.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.47 [modified: 
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
Uname: Linux 4.4.0-11-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CasperVersion: 1.367
Date: Thu Mar 17 10:22:29 2016
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
InterpreterPath: /usr/bin/python3.5
LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160310)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kubuntu ubiquity-2.21.47 xenial

** Attachment added: "ScreenShot of Installation Completion"
   
https://bugs.launchpad.net/bugs/1558479/+attachment/4601954/+files/VirtualBox_U1604KDEDLY_17_03_2016_04_46_30%20Install%20Complete.png

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

Title:
  Installation Complete Restart Now Boot Hang

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

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

[Bug 1558481] [NEW] Installation Complete Restart Now Boot Hang

[Gene Soo]

Public bug reported:

Kubuntu 16.04 Daily Build. Installation Completes with Two Options.
Restart Now or Continue Testing. Selected Restart Now. Screen Goes black but 
machine fails to reboot.
Running as a VirtualBox Guest machine. Must Issue a restart in order to reboot 
machine.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.47 [modified: 
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
Uname: Linux 4.4.0-11-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CasperVersion: 1.367
Date: Thu Mar 17 10:22:29 2016
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
InterpreterPath: /usr/bin/python3.5
LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160310)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kubuntu ubiquity-2.21.47 xenial

** Attachment added: "ScreenShot of Installation Completion"
   
https://bugs.launchpad.net/bugs/1558481/+attachment/4601964/+files/VirtualBox_U1604KDEDLY_17_03_2016_04_46_30%20Install%20Complete.png

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

Title:
  Installation Complete Restart Now Boot Hang

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

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

Re: [Bug 1556387] Re: Unity8 Login Hangs

[Gene Soo]

Attaching two screen shots. First is at Signon prompt waiting for Password.
Second is after password entered and "Enter" key depressed.
ieldI don't get another Signon Screen. I get a hung state with an
intermediate screen with No Password entry field. Seems like the signon
request is accepted and waiting for validation like from a server that is
offline.

On Mon, Mar 14, 2016 at 4:20 AM, Albert Astals Cid <
albert.ast...@canonical.com> wrote:

> Are you sure the problem is not that you get another sign on screen?
>
> Have you tried entering the password in the second sign on screen?
>
> ** Changed in: unity8 (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1556387
>
> Title:
>   Unity8 Login Hangs
>
> Status in unity8 package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Attempted to Install and Login using Unity8 on top of Ubuntu 16.04
> Desktop Build.
>   Am amble to Signon to Unity Desktop distributed by build however when I
> attempt to singon to Unity8, the password accepts but the Signon Screen
> does not go away. The only thing I can do is either shutdown the machine or
> Restart.
>
>   The following data is from my test image:
>   gene@U1604DSKDLYX:~$ uname -a
>   Linux U1604DSKDLYX 4.4.4-040404-generic #201603031931 SMP Fri Mar 4
> 00:34:16 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>   gene@U1604DSKDLYX:~$ sudo apt-get install unity8-desktop-session-mir
>   Reading package lists... Done
>   Building dependency tree
>   Reading state information... Done
>   unity8-desktop-session-mir is already the newest version
> (1.0.12+15.10.20150609-0ubuntu1).
>   0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1556387/+subscriptions
>


** Attachment added: "VirtualBox_U1604DSKDLY_14_03_2016_23_12_31.png"
   
https://bugs.launchpad.net/bugs/1556387/+attachment/4599508/+files/VirtualBox_U1604DSKDLY_14_03_2016_23_12_31.png

** Attachment added: "VirtualBox_U1604DSKDLY_14_03_2016_23_13_19.png"
   
https://bugs.launchpad.net/bugs/1556387/+attachment/4599509/+files/VirtualBox_U1604DSKDLY_14_03_2016_23_13_19.png

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

Title:
  Unity8 Login Hangs

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

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

[Bug 1556387] [NEW] Unity8 Login Hangs

[Gene Soo]

Public bug reported:

Attempted to Install and Login using Unity8 on top of Ubuntu 16.04 Desktop 
Build.
Am amble to Signon to Unity Desktop distributed by build however when I attempt 
to singon to Unity8, the password accepts but the Signon Screen does not go 
away. The only thing I can do is either shutdown the machine or Restart.

The following data is from my test image:
gene@U1604DSKDLYX:~$ uname -a
Linux U1604DSKDLYX 4.4.4-040404-generic #201603031931 SMP Fri Mar 4 00:34:16 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
gene@U1604DSKDLYX:~$ sudo apt-get install unity8-desktop-session-mir
Reading package lists... Done
Building dependency tree   
Reading state information... Done
unity8-desktop-session-mir is already the newest version 
(1.0.12+15.10.20150609-0ubuntu1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

** Affects: unity8 (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/1556387

Title:
  Unity8 Login Hangs

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

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

[Bug 1553652] Re: Ubiquity Install fails to create Swap Partition Erase and Install

[Gene Soo]

Correction on last comment. I thought I was installing to unused space
however I realized that I turned off the Machine Deletion/Reallocation
in my virtualbox scripting. The error appears to be that when the Erase
Disk and Install Ubuntu option is selected, the partition delete process
is not being performed hence an error occurs trying to create the swap
partition.

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

Title:
  Ubiquity Install fails to create Swap Partition Erase and Install

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

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

[Bug 1553652] [NEW] Ubiquity Install fails to create Swap Partition Erase and Install

[Gene Soo]

Public bug reported:

Attempting to install Daily Drop of Unity Desktop 16.04. Selecting
fourth install option to Erase Disk and Install Ubuntu. Receiving error
that Swap Partition creation failed. Unable to proceed with installation
and must reboot. This is a hard failure and also happens on the current
Gnome Daily 16.04 distribution.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.47
ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
Uname: Linux 4.4.0-9-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CasperVersion: 1.367
Date: Sun Mar  6 04:35:46 2016
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
InterpreterPath: /usr/bin/python3.5
LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug ubiquity-2.21.47 ubuntu xenial

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

Title:
  Ubiquity Install fails to create Swap Partition Erase and Install

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

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

[Bug 1553652] Re: Ubiquity Install fails to create Swap Partition Erase and Install

[Gene Soo]

i negkected to include that the target of the installation was freshly
allocated machine under virtualbox with no prior partitions in virtual
Disks being used.

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

Title:
  Ubiquity Install fails to create Swap Partition Erase and Install

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

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

[Bug 1552539] Re: Ubiquity Erase Disk and Install Fails to create Swap Space

[Gene Soo]

Additional information: If I select Try Ubuntu and use Gparted to delete
the existing partitions, the installation works when you restart the
installation.

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

Title:
  Ubiquity Erase Disk and Install Fails to create Swap Space

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

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

[Bug 1552539] [NEW] Ubiquity Erase Disk and Install Fails to create Swap Space

[Gene Soo]

Public bug reported:

Daily Build of Gnome 16.04 using installation option to Erase Disk and Install 
fails with following message:
"The creation of swap space in Partition #5 of SCSi3(0,0,0) (sda) failed.

This is a Virtualbox based install using virtual disks that had a prior 
installation of a daily build.
The installation process does not fail when I delete and recreate the Virtual 
Machine.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.47
ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
Uname: Linux 4.4.0-9-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CasperVersion: 1.367
Date: Thu Mar  3 04:26:59 2016
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/ubuntu-gnome.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
InterpreterPath: /usr/bin/python3.5
LiveMediaBuild: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160302)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug ubiquity-2.21.47 ubuntu-gnome xenial

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

Title:
  Ubiquity Erase Disk and Install Fails to create Swap Space

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

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

[Bug 1549155] Re: Nautilus does not set Allow Execution of File for Multiple Files

[Gene Soo]

Bug 762655  was created
to report the issue.

On Wed, Feb 24, 2016 at 2:48 AM, Sebastien Bacher 
wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. The issue you are reporting is an upstream one and it
> would be nice if somebody having it could send the bug to the developers
> of the software by following the instructions at
> https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
> tell us the number of the upstream bug (or the link), so we can add a
> bugwatch that will inform us about its status. Thanks in advance.
>
> ** Changed in: nautilus (Ubuntu)
>Importance: Undecided => Low
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1549155
>
> Title:
>   Nautilus does not set Allow Execution of File for Multiple Files
>
> Status in nautilus package in Ubuntu:
>   New
>
> Bug description:
>   using Nautilus and selecting Multiple files.
>   Under "Properties" attempting to set "allow executing file as a program"
>   Nautilus fails to assign proper execute attribute.
>   However Nautilus will  remove this same attribute from the group of
> selected files if you toggle the setting off .
>   Only recourse using Nautilus is to perform the activation on one file at
> a time.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu2
>   ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
>   Uname: Linux 4.4.0-6-generic x86_64
>   ApportVersion: 2.20-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Wed Feb 24 01:26:07 2016
>   ExecutablePath: /usr/bin/nautilus
>   GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry'
> b"'720x540+20+54'"
>   InstallationDate: Installed on 2016-02-23 (0 days ago)
>   InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64
> (20160222.1)
>   ProcEnviron:
>SHELL=/bin/bash
>XDG_RUNTIME_DIR=
>PATH=(custom, no user)
>LANG=en_US.UTF-8
>   SourcePackage: nautilus
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1549155/+subscriptions
>


** Bug watch added: GNOME Bug Tracker #762655
   https://bugzilla.gnome.org/show_bug.cgi?id=762655

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

Title:
  Nautilus does not set Allow Execution of File for Multiple Files

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

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

[Bug 1549155] [NEW] Nautilus does not set Allow Execution of File for Multiple Files

[Gene Soo]

Public bug reported:

using Nautilus and selecting Multiple files.
Under "Properties" attempting to set "allow executing file as a program"
Nautilus fails to assign proper execute attribute.
However Nautilus will  remove this same attribute from the group of selected 
files if you toggle the setting off .
Only recourse using Nautilus is to perform the activation on one file at a time.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
Uname: Linux 4.4.0-6-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Feb 24 01:26:07 2016
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'720x540+20+54'"
InstallationDate: Installed on 2016-02-23 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160222.1)
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Nautilus does not set Allow Execution of File for Multiple Files

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

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

[Bug 1544364] Re: GNOME Daily Build Install into existing drive Erase Not Working

[Gene Soo]

Went back and tried installation on top of completed install and the
Erase process worked. I suspect that this particular incident occurred
after a failed install. I had to hard boot out from under in progress
installs running under virtualbox after losing control of Mouse Input
and Window control. No matter what state the installation partition was
left in, I would still expect the Erase Partition function to still work
because the partition information should have been static. Hopefully the
documentation loaded would indicate where the problem is.

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

Title:
  GNOME Daily Build Install into existing drive Erase Not Working

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

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

[Bug 1544364] [NEW] GNOME Daily Build Install into existing drive Erase Not Working

[Gene Soo]

Public bug reported:

Running 1604 GNOME Daily Build.
Booted ISO pointing to install on HD with existing install.
Select options to Erase disk and Install.
Installation aborts failing to Allocate Swap Partition.
Seems as if the Erase Target is not occuring.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.43
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CasperVersion: 1.366
Date: Wed Feb 10 23:58:57 2016
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/ubuntu-gnome.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
InterpreterPath: /usr/bin/python3.5
LiveMediaBuild: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160209)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug ubiquity-2.21.43 ubuntu-gnome xenial

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

Title:
  GNOME Daily Build Install into existing drive Erase Not Working

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

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

[Bug 1543197] [NEW] Auto Login not set in SDDM during Install

[Gene Soo]

Public bug reported:

Current Daily Build requesting Automatic Login during Installation  does
not set the value in SDDM. User must signin with password then manually
change the Auto Login setting in SDDM.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.43 [modified: usr/lib/ubiquity/plugins/ubi-prepare.py]
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CasperVersion: 1.366
Date: Mon Feb  8 10:28:11 2016
ExecutablePath: /usr/lib/ubiquity/user-setup/user-setup-ask
InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
InterpreterPath: /bin/bash
LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160208)
ProcEnviron:
 LC_COLLATE=C
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kubuntu ubiquity-2.21.43 xenial

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

Title:
  Auto Login not set in SDDM during Install

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

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

[Bug 1543373] [NEW] Login Automatically Not Set During Install GNOME 16.04 Daily Build

[Gene Soo]

Public bug reported:

Gnome 16.04 Daily Build. Selected Login Automatically however at first
boot after Install completes password is asked. Have to finish boot and
go to Users and manually set Automatic Login.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-control-center 1:3.18.2-1ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Feb  8 17:56:27 2016
ExecutablePath: /usr/bin/gnome-control-center.real
InstallationDate: Installed on 2016-02-08 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160207)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  Login Automatically Not Set During Install GNOME 16.04  Daily Build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1543373/+subscriptions

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

[Bug 1543373] Re: Login Automatically Not Set During Install GNOME 16.04 Daily Build

[Gene Soo]

Correction to original report. I stated that in order to correct the
problem of not setting Auto Login at installation time the circumvention
was to manually set in Settings > Users. After attempting this change
several times, the value set with that code is not being processed and I
am still being prompted for a password. The whole Auto Login process
needs to be examined at Install Settings, Post Install Settings, and
Login.

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

Title:
  Login Automatically Not Set During Install GNOME 16.04  Daily Build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1543373/+subscriptions

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

[Bug 1529450] Re: Installer crashed

[Gene Soo]

Failed to mention that the Daily Build encountering failiure is Kubuntu
Desktop.

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

Title:
  Installer crashed

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

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

[Bug 1529450] [NEW] Installer crashed

[Gene Soo]

Public bug reported:

Description:Ubuntu Xenial Xerus (development branch)
Release:16.04
Daily Build from tonight

This is a hard failure encountered several times.

Message output from Crash

Traceback (most recent call last):
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 1068, in 
on_next_clicked
self.dbfilter.ok_handler()
  File "/usr/lib/ubiquity/plugins/ubi-prepare.py", line 344, in ok_handler
secureboot_key = self.ui.get_secureboot_key()
AttributeError: 'PageKde' object has no attribute 'get_secureboot_key'

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.40
ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
Uname: Linux 4.3.0-2-generic x86_64
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
CasperVersion: 1.366
CurrentDesktop: KDE
Date: Sun Dec 27 08:17:18 2015
InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151227)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kubuntu ubiquity-2.21.40 xenial

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

Title:
  Installer crashed

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

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

[Bug 1513383] [NEW] Permissions Tab Missing Mark File As Executable

[Gene Soo]

Public bug reported:

Permissions Tab Missing Mark File As Executable

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: thunar 1.6.10-2
ProcVersionSignature: Ubuntu 4.2.0-16.19-lowlatency 4.2.3
Uname: Linux 4.2.0-16-lowlatency x86_64
ApportVersion: 2.19.2-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Nov  5 02:50:55 2015
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2015-11-05 (0 days ago)
InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151104)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: thunar
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Permissions Tab Missing Mark File As Executable

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

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

Re: [Bug 1513383] Re: Permissions Tab Missing Mark File As Executable

[Gene Soo]

Attaching two versions. Raw file from system where screenshots were
generated.
Second is a Zip file of that same raw file.

On Thu, Nov 5, 2015 at 6:12 AM, flocculant <1513...@bugs.launchpad.net>
wrote:

> Can you supply gvfs-info scripts-uzs please.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1513383
>
> Title:
>   Permissions Tab Missing Mark File As Executable
>
> Status in thunar package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Permissions Tab Missing Mark File As Executable
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: thunar 1.6.10-2
>   ProcVersionSignature: Ubuntu 4.2.0-16.19-lowlatency 4.2.3
>   Uname: Linux 4.2.0-16-lowlatency x86_64
>   ApportVersion: 2.19.2-0ubuntu2
>   Architecture: amd64
>   CurrentDesktop: XFCE
>   Date: Thu Nov  5 02:50:55 2015
>   ExecutablePath: /usr/bin/thunar
>   InstallationDate: Installed on 2015-11-05 (0 days ago)
>   InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64
> (20151104)
>   ProcEnviron:
>LANGUAGE=en_US
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: thunar
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1513383/+subscriptions
>


** Attachment added: "scripts-uzs"
   
https://bugs.launchpad.net/bugs/1513383/+attachment/4513360/+files/scripts-uzs

** Attachment added: "scripts-uzs.zip"
   
https://bugs.launchpad.net/bugs/1513383/+attachment/4513361/+files/scripts-uzs.zip

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

Title:
  Permissions Tab Missing Mark File As Executable

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

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

Re: [Bug 1513383] Re: Permissions Tab Missing Mark File As Executable

[Gene Soo]

I have a text script marked with leading meaningful name and no file
extension.
My customary action is to get into  the file Properties and Permission. On
the Permission Tab besides the User, Group,  and Other read/write controls,
there is supposed to be one other check box for whether the file is
executable. Since this is not present,  I must issue by command chmod +x
filename in order to turn on proper flag. Please advise if I need to send a
screens hot if this description is insufficient.

On Thu, Nov 5, 2015, 05:25 flocculant <1513...@bugs.launchpad.net>
wrote:

> Exactly where are you not seeing this?
>
> I can see it here for an appropriate file, though it's not called Mark
> file executable.
>
> ** Changed in: thunar (Ubuntu)
>Status: New => Incomplete
>
> ** Attachment added: "Screenshot_2015-11-05_11-18-44.png"
>
> https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1513383/+attachment/4513339/+files/Screenshot_2015-11-05_11-18-44.png
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1513383
>
> Title:
>   Permissions Tab Missing Mark File As Executable
>
> Status in thunar package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Permissions Tab Missing Mark File As Executable
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: thunar 1.6.10-2
>   ProcVersionSignature: Ubuntu 4.2.0-16.19-lowlatency 4.2.3
>   Uname: Linux 4.2.0-16-lowlatency x86_64
>   ApportVersion: 2.19.2-0ubuntu2
>   Architecture: amd64
>   CurrentDesktop: XFCE
>   Date: Thu Nov  5 02:50:55 2015
>   ExecutablePath: /usr/bin/thunar
>   InstallationDate: Installed on 2015-11-05 (0 days ago)
>   InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64
> (20151104)
>   ProcEnviron:
>LANGUAGE=en_US
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: thunar
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1513383/+subscriptions
>

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

Title:
  Permissions Tab Missing Mark File As Executable

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

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

Re: [Bug 1513383] Re: Permissions Tab Missing Mark File As Executable

[Gene Soo]

Attaching screenshot of issue. If you notice, there is no additional check
box for whether the file is Executable. I do not have this problem with the
KDE File Manager Dolphin.

On Thu, Nov 5, 2015 at 5:18 AM, flocculant <1513...@bugs.launchpad.net>
wrote:

> Exactly where are you not seeing this?
>
> I can see it here for an appropriate file, though it's not called Mark
> file executable.
>
> ** Changed in: thunar (Ubuntu)
>Status: New => Incomplete
>
> ** Attachment added: "Screenshot_2015-11-05_11-18-44.png"
>
> https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1513383/+attachment/4513339/+files/Screenshot_2015-11-05_11-18-44.png
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1513383
>
> Title:
>   Permissions Tab Missing Mark File As Executable
>
> Status in thunar package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Permissions Tab Missing Mark File As Executable
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: thunar 1.6.10-2
>   ProcVersionSignature: Ubuntu 4.2.0-16.19-lowlatency 4.2.3
>   Uname: Linux 4.2.0-16-lowlatency x86_64
>   ApportVersion: 2.19.2-0ubuntu2
>   Architecture: amd64
>   CurrentDesktop: XFCE
>   Date: Thu Nov  5 02:50:55 2015
>   ExecutablePath: /usr/bin/thunar
>   InstallationDate: Installed on 2015-11-05 (0 days ago)
>   InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64
> (20151104)
>   ProcEnviron:
>LANGUAGE=en_US
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: thunar
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1513383/+subscriptions
>


** Attachment added: "Thunar Properties snapshot2.png"
   
https://bugs.launchpad.net/bugs/1513383/+attachment/4513353/+files/Thunar%20Properties%20snapshot2.png

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

Title:
  Permissions Tab Missing Mark File As Executable

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

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

Re: [Bug 1513383] Re: Permissions Tab Missing Mark File As Executable

[Gene Soo]

Attaching Screenshot of Dolphin on same system and Properties of same
file.

On Thu, Nov 5, 2015 at 5:18 AM, flocculant <1513...@bugs.launchpad.net>
wrote:

> Exactly where are you not seeing this?
>
> I can see it here for an appropriate file, though it's not called Mark
> file executable.
>
> ** Changed in: thunar (Ubuntu)
>Status: New => Incomplete
>
> ** Attachment added: "Screenshot_2015-11-05_11-18-44.png"
>
> https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1513383/+attachment/4513339/+files/Screenshot_2015-11-05_11-18-44.png
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1513383
>
> Title:
>   Permissions Tab Missing Mark File As Executable
>
> Status in thunar package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Permissions Tab Missing Mark File As Executable
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: thunar 1.6.10-2
>   ProcVersionSignature: Ubuntu 4.2.0-16.19-lowlatency 4.2.3
>   Uname: Linux 4.2.0-16-lowlatency x86_64
>   ApportVersion: 2.19.2-0ubuntu2
>   Architecture: amd64
>   CurrentDesktop: XFCE
>   Date: Thu Nov  5 02:50:55 2015
>   ExecutablePath: /usr/bin/thunar
>   InstallationDate: Installed on 2015-11-05 (0 days ago)
>   InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64
> (20151104)
>   ProcEnviron:
>LANGUAGE=en_US
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: thunar
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1513383/+subscriptions
>


** Attachment added: "Dolphin Properties snapshot.png"
   
https://bugs.launchpad.net/bugs/1513383/+attachment/4513356/+files/Dolphin%20Properties%20snapshot.png

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

Title:
  Permissions Tab Missing Mark File As Executable

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

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

Re: [Bug 1513383] Re: Permissions Tab Missing Mark File As Executable

[Gene Soo]

I am not sure what to respond other than to observe.
I have a default utility of Thunar being called under the current Daily
Drop of Ubuntu Studio 16.04.
I expect it to be able to set an Executable Attribute for the File within
this utility rather than having to control that attribute with either a
another File Manager utility or via Unix Command Line.
If Thunar is expected to control this setting then it is not currently
doing so and I consider this a bug.
If Thunar does not support controlling or displaying this setting, the
authors of this Utility missed this functionality when setting the goals.
Regardless, this renders the default Utility not usable and I am forced to
seek alternatives such as using Dolphin or Command Line.
Obviously, I would prefer to use the Default Utility rather than to perform
work arounds.


On Thu, Nov 5, 2015 at 6:53 AM, flocculant <1513...@bugs.launchpad.net>
wrote:

> gvfs-info for that file shows
>
> standard::content-type: text/plain
> access::can-execute: FALSE
>
> not sure why you'd expect it to run, neither am I sure why dolphin does
> :)
>
>
> display name: scripts-uzs
> edit name: scripts-uzs
> name: scripts-uzs
> type: regular
> size:  40
> uri: file:///home/wolf/Desktop/scripts-uzs
> attributes:
>   standard::type: 1
>   standard::name: scripts-uzs
>   standard::display-name: scripts-uzs
>   standard::edit-name: scripts-uzs
>   standard::copy-name: scripts-uzs
>   standard::icon: text-plain, text-x-generic
>   standard::content-type: text/plain
>   standard::fast-content-type: application/octet-stream
>   standard::size: 40
>   standard::allocated-size: 4096
>   standard::symbolic-icon: text-plain-symbolic, text-x-generic-symbolic,
> text-plain, text-x-generic
>   etag::value: 1446727744:690135
>   id::file: l2055:1052662
>   id::filesystem: l2055
>   access::can-read: TRUE
>   access::can-write: TRUE
>   access::can-execute: FALSE
>   access::can-delete: TRUE
>   access::can-trash: TRUE
>   access::can-rename: TRUE
>   time::modified: 1446727744
>   time::modified-usec: 690135
>   time::access: 1446727752
>   time::access-usec: 302225
>   time::changed: 1446727935
>   time::changed-usec: 124402
>   unix::device: 2055
>   unix::inode: 1052662
>   unix::mode: 33204
>   unix::nlink: 1
>   unix::uid: 1000
>   unix::gid: 1000
>   unix::rdev: 0
>   unix::block-size: 4096
>   unix::blocks: 8
>   owner::user: wolf
>   owner::user-real: wolf
>   owner::group: wolf
>
> I'll confirm it - but I'm not sure it's actually a thunar bug.
>
> ** Changed in: thunar (Ubuntu)
>Status: Incomplete => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1513383
>
> Title:
>   Permissions Tab Missing Mark File As Executable
>
> Status in thunar package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Permissions Tab Missing Mark File As Executable
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: thunar 1.6.10-2
>   ProcVersionSignature: Ubuntu 4.2.0-16.19-lowlatency 4.2.3
>   Uname: Linux 4.2.0-16-lowlatency x86_64
>   ApportVersion: 2.19.2-0ubuntu2
>   Architecture: amd64
>   CurrentDesktop: XFCE
>   Date: Thu Nov  5 02:50:55 2015
>   ExecutablePath: /usr/bin/thunar
>   InstallationDate: Installed on 2015-11-05 (0 days ago)
>   InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64
> (20151104)
>   ProcEnviron:
>LANGUAGE=en_US
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: thunar
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1513383/+subscriptions
>

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

Title:
  Permissions Tab Missing Mark File As Executable

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

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

Re: [Bug 1513383] Re: Permissions Tab Missing Mark File As Executable

[Gene Soo]

Very disappointing.
Another app that almost got it right but now ends up on the avoid list.

Thanks and have a good day.

On Thu, Nov 5, 2015, 07:45 Pasi Lallinaho 
wrote:

> FWIW, adding a shebang (eg. #!/bin/bash) as the first line in the file
> allows the file to be marked executable in Thunar.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1513383
>
> Title:
>   Permissions Tab Missing Mark File As Executable
>
> Status in thunar package in Ubuntu:
>   Opinion
>
> Bug description:
>   Permissions Tab Missing Mark File As Executable
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: thunar 1.6.10-2
>   ProcVersionSignature: Ubuntu 4.2.0-16.19-lowlatency 4.2.3
>   Uname: Linux 4.2.0-16-lowlatency x86_64
>   ApportVersion: 2.19.2-0ubuntu2
>   Architecture: amd64
>   CurrentDesktop: XFCE
>   Date: Thu Nov  5 02:50:55 2015
>   ExecutablePath: /usr/bin/thunar
>   InstallationDate: Installed on 2015-11-05 (0 days ago)
>   InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64
> (20151104)
>   ProcEnviron:
>LANGUAGE=en_US
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: thunar
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1513383/+subscriptions
>

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

Title:
  Permissions Tab Missing Mark File As Executable

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

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

Re: [Bug 1488909] Re: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in package account-plugi

[Gene Soo]

I don't know that I would have made the assumption that the installation
would be broken if you rebooted. I would agree that if you rebooted while
not successfully completing the software installation that you were doing
might cause things not to work right.

There have been many times where I received Network errors that failed to
contact. For Example, when it goes through the list of modules to install,
an error accessing the repository will fail that component from updating on
that instance of  Update/install. I go back and repeat the same command
whether I was installing and App or Update, Upgrade, Dist-Upgrade or -F
Install to correct dependency problems(Net comment here is to repeat prior
command). Doing this, the apt-get process picks up with incomplete updates
and reattempts. I have even have a script which will perform the steps to
clear the package locking used to serialize updating. This is needed when
the update fails catastrophically and does not clean up the locking. Your
updates will be blocked if that locking is not cleared. If you are doing
this on a mission critical system then you may want to be careful about
having good backups before performing updates but most of my testing is on
Virtual Box throw away Guests. I regularly update my base platforms and
have not performed a distribution upgrade since Ubuntu 14.04. Since 16.04
just came out, I will be looking at doing that for my base level systems.

Final most systems that I perform maintenance on, I will keep driving to
completion successful installation of the target I was trying to install
before attempting to reboot.
Some things are not fixable.. Case in point the current Daily Builds for
16.04 Xenial have a Systemd bug that freezes the boot process. I could not
find any workarounds and until the development team promotes corrective
code to the nightly distribution, I cannot test those distributions.

Gene

On Mon, Nov 2, 2015 at 1:15 PM, Andrei Marinescu <
iandrei.marine...@gmail.com> wrote:

> I'm also looking for a fix for this. I did a apt-get install kubuntu-
> desktop this morning and it busted my package manager. I expect that  if
> I try to reboot the machine it's going to fail, since it failed midway
> in installing KDE.
>
> Any workarounds, or at least rollback instructions available?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1488909
>
> Title:
>   package kaccounts-providers (not installed) failed to install/upgrade:
>   trying to overwrite '/usr/share/accounts/providers/google.provider',
>   which is also in package account-plugin-google
>   0.12+15.10.20150723-0ubuntu1
>
> Status in kaccounts-providers package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Errors during kubuntu-desktop kubuntu-restricted-extras install after,
>   successful ubuntu-desktop ubuntu-restricted-extras install on a Ubuntu
>   Server 15.10 system.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 15.10
>   Package: kaccounts-providers (not installed)
>   ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
>   Uname: Linux 4.1.0-3-generic x86_64
>   ApportVersion: 2.18-0ubuntu7
>   Architecture: amd64
>   Date: Tue Aug 25 18:00:45 2015
>   DuplicateSignature: package:kaccounts-providers:(not installed):trying
> to overwrite '/usr/share/accounts/providers/google.provider', which is also
> in package account-plugin-google 0.12+15.10.20150723-0ubuntu1
>   ErrorMessage: trying to overwrite
> '/usr/share/accounts/providers/google.provider', which is also in package
> account-plugin-google 0.12+15.10.20150723-0ubuntu1
>   InstallationDate: Installed on 2015-08-25 (0 days ago)
>   InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Alpha amd64
> (20150825)
>   RelatedPackageVersions:
>dpkg 1.18.2ubuntu2
>apt  1.0.9.10ubuntu6
>   SourcePackage: kaccounts-providers
>   Title: package kaccounts-providers (not installed) failed to
> install/upgrade: trying to overwrite
> '/usr/share/accounts/providers/google.provider', which is also in package
> account-plugin-google 0.12+15.10.20150723-0ubuntu1
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/kaccounts-providers/+bug/1488909/+subscriptions
>

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

Title:
  package kaccounts-providers (not installed) failed to install/upgrade:
  trying to overwrite '/usr/share/accounts/providers/google.provider',
  which is also in package account-plugin-google
  0.12+15.10.20150723-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kaccounts-providers/+bug/1488909/+subscriptions

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

[Bug 477551] Re: rcksum-xxxxxx temporay files left on disk by zsync

[Gene Soo]

Not only is ZSYNC leaving the temporary file, it is also creating that
file in the current working directory. In my case, that happens to be
the sub folder for all of my Installation and Maintenance BAsH scripts.
This temp working file should be created in some sort of temp data
folder eligible for cleanup by system processes in case the ZSYNC
commands terminates early before work file cleanup can occur.

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

Title:
  rcksum-xx temporay files left on disk by zsync

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

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

[Bug 1506404] [NEW] package systemd 225-1ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Gene Soo]

Public bug reported:

unknown

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: systemd 225-1ubuntu7
ProcVersionSignature: Ubuntu 4.2.0-16.19-lowlatency 4.2.3
Uname: Linux 4.2.0-16-lowlatency x86_64
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
Date: Thu Oct 15 05:09:04 2015
DuplicateSignature: package:systemd:225-1ubuntu7:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2015-10-15 (0 days ago)
InstallationMedia: Ubuntu-Studio 15.10 "Wily Werewolf" - Alpha amd64 (20151014)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-lowlatency 
root=UUID=d38c5715-21eb-4fa3-9747-6ac78e823383 ro quiet splash
RelatedPackageVersions:
 dpkg 1.18.2ubuntu4
 apt  1.0.10.2ubuntu1
SourcePackage: systemd
SystemdFailedUnits:
 Error: command ['systemctl', 'status', '--full', 'Error:'] failed with exit 
code 3: ● Error:.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
Title: package systemd 225-1ubuntu7 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-package wily

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

Title:
  package systemd 225-1ubuntu7 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/systemd/+bug/1506404/+subscriptions

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

[Bug 1505790] [NEW] Auto Login Not Set for KDE 15.10 Daily Build

[Gene Soo]

Public bug reported:

Effected Distribution is KDE 15.10 Daily Build from last night.

Navigation:  System Settings > Personalisation > Account Details > User
Manager > Auto Login.

Setting this value for the Admin User requests Root password however the
underlying software does not make the proper changes to implement Auto
Login nor does it preserve the value.

I found the proper Navigation to make this change.

It is Login Screen(SDDM) > Advanced > Auto Login.

The duplication of these panels needs to be eliminated and the correct
code Invoking the SDDM version of Auto Login should be implemented off
the Systems Settings navigation.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: systemsettings 4:5.4.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Oct 13 14:05:03 2015
ExecutablePath: /usr/bin/systemsettings5
InstallationDate: Installed on 2015-10-13 (0 days ago)
InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Alpha amd64 (20151013)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: systemsettings
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug wily

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

Title:
  Auto Login Not Set for KDE 15.10 Daily Build

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

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

[Bug 1502097] [NEW] package udev 225-1ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Gene Soo]

Public bug reported:

APT-GET UPDATE hung and finally crashed.

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: udev 225-1ubuntu5
ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
Uname: Linux 4.2.0-11-generic x86_64
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
Date: Fri Oct  2 05:49:42 2015
DuplicateSignature: package:udev:225-1ubuntu5:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2015-10-02 (0 days ago)
InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic 
root=UUID=e5c0431b-fff3-4b45-8595-5afb62f714c8 ro quiet splash
RelatedPackageVersions:
 dpkg 1.18.2ubuntu4
 apt  1.0.9.10ubuntu7
SourcePackage: systemd
Title: package udev 225-1ubuntu5 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-package wily

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

Title:
  package udev 225-1ubuntu5 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/systemd/+bug/1502097/+subscriptions

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

Re: [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Gene Soo]

I'm sorry, I don't know how to proceed with this issue.

Early on, you asked for Verbose Logging from Virtualbox. I supplied the
Machine Log for the failing Guest and I knew Verbose was probably Defaulted
to Off.
Since then, I have found the commands to change the running machine
"VBoxManage debugvm" however the VirtualBox Documentation is weak on
descriptions and examples of how to turn on the Verbose logging for Audio
issues.  I can see in some of their supporting Code Snippets that Group 2
Logging maybe applicable. I cannot find any "VBoxManage debugvm" examples
controlling setting verbose by group.

I am also having difficulty in understanding what coding changes needs to
be done in order to address your last couple of updates.

So here is the difficulties I am facing.

I would feel more comfortable if we pursued tracing the problem rather than
making code changes.

If you are unable to direct me toward specifying the correct commands to
accomplish this then I can try getting help from the VirtualBox Forum site.
I will say they have not been very helpful so far regarding this issue.

Short of these two options, I am prepared to drop the issue entirely and
someone else with the same problem and is better up to speed with working
with this code and these tools can pickup the effort.


On Tue, Sep 1, 2015 at 12:07 PM, Raymond <1487...@bugs.launchpad.net>
wrote:

> http://git.alsa-project.org/?p=alsa-
> kmirror.git;a=commitdiff_plain;h=bb9a16dc52281d98dfb525552d29d8939845d8e2
>
>
> it was this patch change master mono from mono to stereo
>
>
>
> /* build master mono controls */
> if (snd_ac97_try_volume_mix(ac97, AC97_MASTER_MONO)) {
> -   if ((err = snd_ctl_add(card,
> snd_ac97_cnew(_ac97_controls_master_mono[0], ac97))) < 0)
> +   if ((err = snd_ac97_cmix_new(card, "Master Mono Playback",
> AC97_MASTER_MONO, ac97)) < 0)
> return err;
> -   if ((err = snd_ctl_add(card, kctl =
> snd_ac97_cnew(_ac97_controls_master_mono[1], ac97))) < 0)
> -   return err;
> -   snd_ac97_change_volume_params1(ac97, AC97_MASTER_MONO,
> );
> -   kctl->private_value &= ~(0xff << 16);
> -   kctl->private_value |= (int)max << 16;
> -   snd_ac97_write_cache(ac97, AC97_MASTER_MONO, 0x8000 | max);
> }
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1487168
>
> Title:
>   [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
>   problem
>
> Status in Virtualbox:
>   New
> Status in alsa-driver package in Ubuntu:
>   Incomplete
> Status in virtualbox package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Volume Slider is only controlling PCM channel and is not controlling
>   Master. In effect, Master is restricting the audio level to the
>   default of approximately 45 Percent. In order to raise the Master
>   Volume Level, alsamixer is capable of changing Master. Without
>   manually raising Master to Max Volume, Volume Slider can only control
>   volume from 0-45% which is the default level of Master.
>
>   Description:  Ubuntu Wily Werewolf (development branch)
>   Release:  15.10
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 15.10
>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>   ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
>   Uname: Linux 4.1.0-3-generic x86_64
>   ApportVersion: 2.18-0ubuntu7
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  gene   1330 F pulseaudio
> gene   1922 F alsamixer
>   CurrentDesktop: Unity
>   Date: Thu Aug 20 13:00:57 2015
>   InstallationDate: Installed on 2015-08-19 (1 days ago)
>   InstallationMedia: Edubuntu 15.10 "Wily Werewolf" - Alpha amd64
> (20150819)
>   PackageArchitecture: all
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Symptom_Card: Built-in Audio - Intel 82801AA-ICH
>   Symptom_Type: Volume slider, or mixer problems
>   Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/01/2006
>   dmi.bios.vendor: innotek GmbH
>   dmi.bios.version: VirtualBox
>   dmi.board.name: VirtualBox
>   dmi.board.vendor: Oracle Corporation
>   dmi.board.version: 1.2
>   dmi.chassis.type: 1
>   dmi.chassis.vendor: Oracle Corporation
>   dmi.modalias:
> dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
>   dmi.product.name: VirtualBox
>   dmi.product.version: 1.2
>   dmi.sys.vendor: innotek GmbH
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/virtualbox/+bug/1487168/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

Re: [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Gene Soo]

My interpretation of this update is that I believe you are trying to
suggest that I apply this patch to correct a scaling problem with HDA,
Is that what you are trying to communicate?

Also, I understand that this code is or maybe broken but why are we working
on Intel HDA when the default ICH AC97 seems to have the problem. I would
rather work on getting the defaulted Driver correct.

On Sat, Sep 5, 2015 at 10:07 AM, Raymond <1487...@bugs.launchpad.net>
wrote:

>
> https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/patch_sigmatel.c?id=7c7767ebe2fa847c91a0dd5551ca422aba359473
>
>
> ALSA: hda - Halve too large volume scales for STAC/IDT codecs
> STAC/IDT codecs have often too large volume scales such as -96dB,
> and exposing this as is results in too large scale in percentage
> representation.
>
> This patch adds the check of the volume scale and halves the
> volume range if it's too large automatically.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1487168
>
> Title:
>   [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
>   problem
>
> Status in Virtualbox:
>   New
> Status in alsa-driver package in Ubuntu:
>   Incomplete
> Status in virtualbox package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Volume Slider is only controlling PCM channel and is not controlling
>   Master. In effect, Master is restricting the audio level to the
>   default of approximately 45 Percent. In order to raise the Master
>   Volume Level, alsamixer is capable of changing Master. Without
>   manually raising Master to Max Volume, Volume Slider can only control
>   volume from 0-45% which is the default level of Master.
>
>   Description:  Ubuntu Wily Werewolf (development branch)
>   Release:  15.10
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 15.10
>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>   ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
>   Uname: Linux 4.1.0-3-generic x86_64
>   ApportVersion: 2.18-0ubuntu7
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  gene   1330 F pulseaudio
> gene   1922 F alsamixer
>   CurrentDesktop: Unity
>   Date: Thu Aug 20 13:00:57 2015
>   InstallationDate: Installed on 2015-08-19 (1 days ago)
>   InstallationMedia: Edubuntu 15.10 "Wily Werewolf" - Alpha amd64
> (20150819)
>   PackageArchitecture: all
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Symptom_Card: Built-in Audio - Intel 82801AA-ICH
>   Symptom_Type: Volume slider, or mixer problems
>   Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/01/2006
>   dmi.bios.vendor: innotek GmbH
>   dmi.bios.version: VirtualBox
>   dmi.board.name: VirtualBox
>   dmi.board.vendor: Oracle Corporation
>   dmi.board.version: 1.2
>   dmi.chassis.type: 1
>   dmi.chassis.vendor: Oracle Corporation
>   dmi.modalias:
> dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
>   dmi.product.name: VirtualBox
>   dmi.product.version: 1.2
>   dmi.sys.vendor: innotek GmbH
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/virtualbox/+bug/1487168/+subscriptions
>

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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

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

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

Re: [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Gene Soo]

LocutusOfBorg, I am in desperate need of help on this issue in several
areas.
I would have hoped this would have been much easier to report and let you
experts work the issue however even though I can describe what I am seeing,
it is very difficult to supply the respective folks with enough
documentation to take over. I am a mainframe programmer so I understand
parts of this but not familiar with coding and debugging on this platform.

I've tried to communicate to Raymond that I do not know the proper command
syntax to perform Verbose Logging. I did see a reference to "all" in some
of the documentation however near that reference, it was clearly stated
that you probably don't want to do that. If you can let me know, the
VBoxManage debugvm commands that would be appropriate to figure out Audio
Problems, I would really appreciate it.

As to your offer of supplying latest patched to your ppa, I would take you
up on that offer however I need help with the proper commands to get those
changes into my environment. Not knowing all of the terminology, I was able
to run the SVN commands to establish a development fork on my Test system
obtained from the FAQs from the VirtualBox Forum. I have not gone into
intensive study into making updates of any of the downloaded files and what
it takes to recreate the final installation package. Last night, I removed
the VirtualBox Directory and recreated it followed by rerunning all of the
SVN, and subsequent commands(make, KMK, etc) to get the latest code. I was
able to bring up a fresh copy of VirtualBox. *If you can confirm that If I
make a source code change and repeat all commands starting with the first
Make, that is the proper steps to get that change compiled and integrated
into the test package?*

A supplemental comment to Raymond about this, You are making references in
your responses that it is easy switch to Intel HDA from emulated AC97 as a
workaround.
I went into VBox Guest Settings and made this change for the two remaining
distributions having the problem(Lubuntu and Mate).
I am attaching a Zip file of Screen Snapshots. To summarize on Lubuntu,
Slider Level defaults to Below Max level(Only controlling Master channel)
with MAXed and MINed Slider settings confirming only Master channel Level
being controlled. On Mate, The Slider Defaults at Max Level which is
inconsistent with the Master Channel Level reported by alsamixer. Then when
I MINed the Slider, the only channel that seemed to be effected was S/PDIF.
Moving the Slider did not change the Master or any of the Headhone/Speakers
channels.
This setting seems to be worse than the ICH AC97 setting.


On Sat, Sep 5, 2015 at 3:18 AM, LocutusOfBorg  wrote:

> Hi Gene, if you need to have some virtualbox builds feel free to just ask
> me, I'll upload all the patches you want to test in my ppa.
> (I'll prefer to apply them on top of 5.0.2 if possible)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1487168
>
> Title:
>   [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
>   problem
>
> Status in Virtualbox:
>   New
> Status in alsa-driver package in Ubuntu:
>   Incomplete
> Status in virtualbox package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Volume Slider is only controlling PCM channel and is not controlling
>   Master. In effect, Master is restricting the audio level to the
>   default of approximately 45 Percent. In order to raise the Master
>   Volume Level, alsamixer is capable of changing Master. Without
>   manually raising Master to Max Volume, Volume Slider can only control
>   volume from 0-45% which is the default level of Master.
>
>   Description:  Ubuntu Wily Werewolf (development branch)
>   Release:  15.10
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 15.10
>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>   ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
>   Uname: Linux 4.1.0-3-generic x86_64
>   ApportVersion: 2.18-0ubuntu7
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  gene   1330 F pulseaudio
> gene   1922 F alsamixer
>   CurrentDesktop: Unity
>   Date: Thu Aug 20 13:00:57 2015
>   InstallationDate: Installed on 2015-08-19 (1 days ago)
>   InstallationMedia: Edubuntu 15.10 "Wily Werewolf" - Alpha amd64
> (20150819)
>   PackageArchitecture: all
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Symptom_Card: Built-in Audio - Intel 82801AA-ICH
>   Symptom_Type: Volume slider, or mixer problems
>   Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/01/2006
>   dmi.bios.vendor: innotek GmbH
>   dmi.bios.version: VirtualBox
>   dmi.board.name: VirtualBox
>   dmi.board.vendor: Oracle Corporation
>   dmi.board.version: 1.2
>   dmi.chassis.type: 1
>   

Re: [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Gene Soo]

I have no idea what "the output of alsa-info.sh" is. Is this some sort of
Shell script that needs to be run?
If so, when do you run it,
a) One time only,
b)Before changing the Slider Position,

Giving me these short segments of details without specific instructions is
causing me to give up on pursuing this issue as not being able to be fixed
because it is taking too long to get you sufficient documentation to work
the issue.

On Sat, Sep 5, 2015 at 9:44 AM, Raymond <1487...@bugs.launchpad.net>
wrote:

> you have to post the output of alsa-info.sh if enumerated hda does not
> work as expected
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1487168
>
> Title:
>   [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
>   problem
>
> Status in Virtualbox:
>   New
> Status in alsa-driver package in Ubuntu:
>   Incomplete
> Status in virtualbox package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Volume Slider is only controlling PCM channel and is not controlling
>   Master. In effect, Master is restricting the audio level to the
>   default of approximately 45 Percent. In order to raise the Master
>   Volume Level, alsamixer is capable of changing Master. Without
>   manually raising Master to Max Volume, Volume Slider can only control
>   volume from 0-45% which is the default level of Master.
>
>   Description:  Ubuntu Wily Werewolf (development branch)
>   Release:  15.10
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 15.10
>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>   ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
>   Uname: Linux 4.1.0-3-generic x86_64
>   ApportVersion: 2.18-0ubuntu7
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  gene   1330 F pulseaudio
> gene   1922 F alsamixer
>   CurrentDesktop: Unity
>   Date: Thu Aug 20 13:00:57 2015
>   InstallationDate: Installed on 2015-08-19 (1 days ago)
>   InstallationMedia: Edubuntu 15.10 "Wily Werewolf" - Alpha amd64
> (20150819)
>   PackageArchitecture: all
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Symptom_Card: Built-in Audio - Intel 82801AA-ICH
>   Symptom_Type: Volume slider, or mixer problems
>   Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/01/2006
>   dmi.bios.vendor: innotek GmbH
>   dmi.bios.version: VirtualBox
>   dmi.board.name: VirtualBox
>   dmi.board.vendor: Oracle Corporation
>   dmi.board.version: 1.2
>   dmi.chassis.type: 1
>   dmi.chassis.vendor: Oracle Corporation
>   dmi.modalias:
> dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
>   dmi.product.name: VirtualBox
>   dmi.product.version: 1.2
>   dmi.sys.vendor: innotek GmbH
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/virtualbox/+bug/1487168/+subscriptions
>

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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

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

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

Re: [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Gene Soo]

Attempting to attached two zip files. First logs and Screenshots from
Lubuntu 15.10 Distribution. Second is Logs and screenshots from Mate 15.10.


On Sat, Aug 29, 2015 at 3:11 AM, Raymond 1487...@bugs.launchpad.net
wrote:

 if (pbus-pcms[0].r[0].slots  (1  AC97_SLOT_PCM_SLEFT)) {
 chip-multi4 = 1;
 if (pbus-pcms[0].r[0].slots  (1  AC97_SLOT_LFE)) {
 chip-multi6 = 1;
 if (chip-ac97[0]-flags  AC97_HAS_8CH)
 chip-multi8 = 1;
 }
 }

 the alsa driver set chip-multi6 when slot have AC97_SLOT_LFE

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1487168

 Title:
   [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
   problem

 Status in alsa-driver package in Ubuntu:
   Invalid
 Status in virtualbox package in Ubuntu:
   Confirmed

 Bug description:
   Volume Slider is only controlling PCM channel and is not controlling
   Master. In effect, Master is restricting the audio level to the
   default of approximately 45 Percent. In order to raise the Master
   Volume Level, alsamixer is capable of changing Master. Without
   manually raising Master to Max Volume, Volume Slider can only control
   volume from 0-45% which is the default level of Master.

   Description:  Ubuntu Wily Werewolf (development branch)
   Release:  15.10

   ProblemType: Bug
   DistroRelease: Ubuntu 15.10
   Package: alsa-base 1.0.25+dfsg-0ubuntu5
   ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
   Uname: Linux 4.1.0-3-generic x86_64
   ApportVersion: 2.18-0ubuntu7
   Architecture: amd64
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:  gene   1330 F pulseaudio
 gene   1922 F alsamixer
   CurrentDesktop: Unity
   Date: Thu Aug 20 13:00:57 2015
   InstallationDate: Installed on 2015-08-19 (1 days ago)
   InstallationMedia: Edubuntu 15.10 Wily Werewolf - Alpha amd64
 (20150819)
   PackageArchitecture: all
   SourcePackage: alsa-driver
   Symptom: audio
   Symptom_Card: Built-in Audio - Intel 82801AA-ICH
   Symptom_Type: Volume slider, or mixer problems
   Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
   UpgradeStatus: No upgrade log present (probably fresh install)
   dmi.bios.date: 12/01/2006
   dmi.bios.vendor: innotek GmbH
   dmi.bios.version: VirtualBox
   dmi.board.name: VirtualBox
   dmi.board.vendor: Oracle Corporation
   dmi.board.version: 1.2
   dmi.chassis.type: 1
   dmi.chassis.vendor: Oracle Corporation
   dmi.modalias:
 dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
   dmi.product.name: VirtualBox
   dmi.product.version: 1.2
   dmi.sys.vendor: innotek GmbH

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions



** Attachment added: U1510LUDLY Alsamixer After First Boot Slider Maxed Fails 
to Alter PCM.png.zip
   
https://bugs.launchpad.net/bugs/1487168/+attachment/4454070/+files/U1510LUDLY%20Alsamixer%20After%20First%20Boot%20Slider%20Maxed%20Fails%20to%20Alter%20PCM.png.zip

** Attachment added: U1510MateDly Alsamixer After First Boot Slider Maxed 
Alsamixer Corrections to Master.png.zip
   
https://bugs.launchpad.net/bugs/1487168/+attachment/4454071/+files/U1510MateDly%20Alsamixer%20After%20First%20Boot%20Slider%20Maxed%20Alsamixer%20Corrections%20to%20Master.png.zip

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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions

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

Re: [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Gene Soo]

I'll attempt to describe the patterns and symptoms I am noticing and with a
subsequent email attach ScreenShot files to support those observations.

With this latest round of testing  the Ubuntu 15.10 daily drops, most of
the distributions are behaving correctly in that Volume Slider does control
volume levels correctly adjusting channels Master and PCM.
alsamixer reports Card: Intel 82801AA-ICH
Chip: Sigmatel STAC9700,83,84

The two distributions I am having problems with is.

Distribution: Lubuntu 15.10
*Volume Slider Controls Master Only and Not PCM.*

alsamixer reports same Card and Chip information as above however the
Volume Slider


Distribution: Mate 15.10(Had Not Previously tried this Distribution)
Volume Slider Only Controlling PCM and Not Master This Symptom was common
in the previous testing when more distributions were effected however I am
not sure that the Chip identified below was the same in those past tests.

alsamixer reports Card: Intel 82801AA-ICH
Chip: *Analog Devices AD1980*

On my next update, I will attach all of the Screenshots and Vbox Logfiles
for the failing machines.


On Sat, Aug 29, 2015 at 2:55 AM, Raymond 1487...@bugs.launchpad.net
wrote:

 the reason for no master playback volume/switch is

 master rename as master surround but no headphone playback volume/switch

 state.I82801AAICH {
 control.1 {
 iface MIXER
 name 'Master Surround Playback Switch'
 value.0 true
 value.1 true
 comment {
 access 'read write'
 type BOOLEAN
 count 2
 }
 }
 control.2 {
 iface MIXER
 name 'Master Surround Playback Volume'
 value.0 17
 value.1 17
 comment {
 access 'read write'
 type INTEGER
 count 2
 range '0 - 31'
 dbmin -4650
 dbmax 0
 dbvalue.0 -2100
 dbvalue.1 -2100
 }
 }


 static int patch_ad1888_specific(struct snd_ac97 *ac97)
 {
 if (!ac97-spec.ad18xx.lo_as_master) {
 /* rename 0x04 as Master and 0x02 as Master Surround */
 snd_ac97_rename_vol_ctl(ac97, Master Playback,
 Master Surround Playback);
 snd_ac97_rename_vol_ctl(ac97, Headphone Playback,
 Master Playback);
 }
 return patch_build_controls(ac97, snd_ac97_ad1888_controls,
 ARRAY_SIZE(snd_ac97_ad1888_controls));
 }

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1487168

 Title:
   [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
   problem

 Status in alsa-driver package in Ubuntu:
   Invalid
 Status in virtualbox package in Ubuntu:
   Confirmed

 Bug description:
   Volume Slider is only controlling PCM channel and is not controlling
   Master. In effect, Master is restricting the audio level to the
   default of approximately 45 Percent. In order to raise the Master
   Volume Level, alsamixer is capable of changing Master. Without
   manually raising Master to Max Volume, Volume Slider can only control
   volume from 0-45% which is the default level of Master.

   Description:  Ubuntu Wily Werewolf (development branch)
   Release:  15.10

   ProblemType: Bug
   DistroRelease: Ubuntu 15.10
   Package: alsa-base 1.0.25+dfsg-0ubuntu5
   ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
   Uname: Linux 4.1.0-3-generic x86_64
   ApportVersion: 2.18-0ubuntu7
   Architecture: amd64
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:  gene   1330 F pulseaudio
 gene   1922 F alsamixer
   CurrentDesktop: Unity
   Date: Thu Aug 20 13:00:57 2015
   InstallationDate: Installed on 2015-08-19 (1 days ago)
   InstallationMedia: Edubuntu 15.10 Wily Werewolf - Alpha amd64
 (20150819)
   PackageArchitecture: all
   SourcePackage: alsa-driver
   Symptom: audio
   Symptom_Card: Built-in Audio - Intel 82801AA-ICH
   Symptom_Type: Volume slider, or mixer problems
   Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
   UpgradeStatus: No upgrade log present (probably fresh install)
   dmi.bios.date: 12/01/2006
   dmi.bios.vendor: innotek GmbH
   dmi.bios.version: VirtualBox
   dmi.board.name: VirtualBox
   dmi.board.vendor: Oracle Corporation
   dmi.board.version: 1.2
   dmi.chassis.type: 1
   dmi.chassis.vendor: Oracle Corporation
   dmi.modalias:
 dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
   dmi.product.name: VirtualBox
   

Re: [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Gene Soo]

First, you dd not answer my question on whether or not I could attach the
files directly to this email and whether you would be able to get them or
do I need to upload them somewhere?


Second, I want to clarify the Verbose Log you want. Is that the Log from
Show Log CTRL+L? If so, I assume you want all of the available logs so you
can see from installation to last boot?

Third, I don't understand the last sentence starting with the linux driver
check nor do I know what to make of the URL you sent. If the sentence is
supposed to give me instructions to do something in relationship to the URL
contents I need clarification. Otherwise it would be best for me to get you
those screenshots so you can see what I am seeing.

On Fri, Aug 28, 2015 at 8:31 PM, Raymond 1487...@bugs.launchpad.net
wrote:

 you need virtualbox verbose log which provide debug messages printed by
 LogFlowFunc()

 the linux driver check those ad specific registers for multi codecs ,
 and ADI compatiable mode


 https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/sound/pci/ac97/ac97_patch.c

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1487168

 Title:
   [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
   problem

 Status in alsa-driver package in Ubuntu:
   Invalid
 Status in virtualbox package in Ubuntu:
   Confirmed

 Bug description:
   Volume Slider is only controlling PCM channel and is not controlling
   Master. In effect, Master is restricting the audio level to the
   default of approximately 45 Percent. In order to raise the Master
   Volume Level, alsamixer is capable of changing Master. Without
   manually raising Master to Max Volume, Volume Slider can only control
   volume from 0-45% which is the default level of Master.

   Description:  Ubuntu Wily Werewolf (development branch)
   Release:  15.10

   ProblemType: Bug
   DistroRelease: Ubuntu 15.10
   Package: alsa-base 1.0.25+dfsg-0ubuntu5
   ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
   Uname: Linux 4.1.0-3-generic x86_64
   ApportVersion: 2.18-0ubuntu7
   Architecture: amd64
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:  gene   1330 F pulseaudio
 gene   1922 F alsamixer
   CurrentDesktop: Unity
   Date: Thu Aug 20 13:00:57 2015
   InstallationDate: Installed on 2015-08-19 (1 days ago)
   InstallationMedia: Edubuntu 15.10 Wily Werewolf - Alpha amd64
 (20150819)
   PackageArchitecture: all
   SourcePackage: alsa-driver
   Symptom: audio
   Symptom_Card: Built-in Audio - Intel 82801AA-ICH
   Symptom_Type: Volume slider, or mixer problems
   Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
   UpgradeStatus: No upgrade log present (probably fresh install)
   dmi.bios.date: 12/01/2006
   dmi.bios.vendor: innotek GmbH
   dmi.bios.version: VirtualBox
   dmi.board.name: VirtualBox
   dmi.board.vendor: Oracle Corporation
   dmi.board.version: 1.2
   dmi.chassis.type: 1
   dmi.chassis.vendor: Oracle Corporation
   dmi.modalias:
 dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
   dmi.product.name: VirtualBox
   dmi.product.version: 1.2
   dmi.sys.vendor: innotek GmbH

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions


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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions

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

Re: [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Gene Soo]

I discovered that the Volume Slider problem exists even after the clean
install of Virtual Box 5.0.2.

I have screenshots that document the errant behavior.

I am not used to submitting documentation for problems other than typing in
descriptive text when prompted.

Can I attach the screenshot files as attachments to one of these emails and
will they be posted in your problem tracking application?
If not, can you direct me to instructions on how to submit documentation?


On Thu, Aug 27, 2015 at 11:25 AM, Alberto Salvia Novella 
es204904...@gmail.com wrote:

 ** Changed in: virtualbox (Ubuntu)
Importance: Undecided = Medium

 ** Changed in: alsa-driver (Ubuntu)
Importance: Undecided = Medium

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1487168

 Title:
   [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
   problem

 Status in alsa-driver package in Ubuntu:
   Invalid
 Status in virtualbox package in Ubuntu:
   Confirmed

 Bug description:
   Volume Slider is only controlling PCM channel and is not controlling
   Master. In effect, Master is restricting the audio level to the
   default of approximately 45 Percent. In order to raise the Master
   Volume Level, alsamixer is capable of changing Master. Without
   manually raising Master to Max Volume, Volume Slider can only control
   volume from 0-45% which is the default level of Master.

   Description:  Ubuntu Wily Werewolf (development branch)
   Release:  15.10

   ProblemType: Bug
   DistroRelease: Ubuntu 15.10
   Package: alsa-base 1.0.25+dfsg-0ubuntu5
   ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
   Uname: Linux 4.1.0-3-generic x86_64
   ApportVersion: 2.18-0ubuntu7
   Architecture: amd64
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:  gene   1330 F pulseaudio
 gene   1922 F alsamixer
   CurrentDesktop: Unity
   Date: Thu Aug 20 13:00:57 2015
   InstallationDate: Installed on 2015-08-19 (1 days ago)
   InstallationMedia: Edubuntu 15.10 Wily Werewolf - Alpha amd64
 (20150819)
   PackageArchitecture: all
   SourcePackage: alsa-driver
   Symptom: audio
   Symptom_Card: Built-in Audio - Intel 82801AA-ICH
   Symptom_Type: Volume slider, or mixer problems
   Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
   UpgradeStatus: No upgrade log present (probably fresh install)
   dmi.bios.date: 12/01/2006
   dmi.bios.vendor: innotek GmbH
   dmi.bios.version: VirtualBox
   dmi.board.name: VirtualBox
   dmi.board.vendor: Oracle Corporation
   dmi.board.version: 1.2
   dmi.chassis.type: 1
   dmi.chassis.vendor: Oracle Corporation
   dmi.modalias:
 dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
   dmi.product.name: VirtualBox
   dmi.product.version: 1.2
   dmi.sys.vendor: innotek GmbH

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions


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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions

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

Re: [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Gene Soo]

VirtualBox ticket 14508 created to report this issue. Any comments from the
Audio team can be submitted referencing that ticket number.

On Thu, Aug 27, 2015 at 3:34 AM, LocutusOfBorg 
costamagnagianfra...@yahoo.it wrote:

 Hi, can you please report then on the upstream Virtualbox ticket page?
 or also the mail list might be good
 https://www.virtualbox.org/newticket

 cheers,

 Gianfranco

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1487168

 Title:
   [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
   problem

 Status in alsa-driver package in Ubuntu:
   Invalid
 Status in virtualbox package in Ubuntu:
   Confirmed

 Bug description:
   Volume Slider is only controlling PCM channel and is not controlling
   Master. In effect, Master is restricting the audio level to the
   default of approximately 45 Percent. In order to raise the Master
   Volume Level, alsamixer is capable of changing Master. Without
   manually raising Master to Max Volume, Volume Slider can only control
   volume from 0-45% which is the default level of Master.

   Description:  Ubuntu Wily Werewolf (development branch)
   Release:  15.10

   ProblemType: Bug
   DistroRelease: Ubuntu 15.10
   Package: alsa-base 1.0.25+dfsg-0ubuntu5
   ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
   Uname: Linux 4.1.0-3-generic x86_64
   ApportVersion: 2.18-0ubuntu7
   Architecture: amd64
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:  gene   1330 F pulseaudio
 gene   1922 F alsamixer
   CurrentDesktop: Unity
   Date: Thu Aug 20 13:00:57 2015
   InstallationDate: Installed on 2015-08-19 (1 days ago)
   InstallationMedia: Edubuntu 15.10 Wily Werewolf - Alpha amd64
 (20150819)
   PackageArchitecture: all
   SourcePackage: alsa-driver
   Symptom: audio
   Symptom_Card: Built-in Audio - Intel 82801AA-ICH
   Symptom_Type: Volume slider, or mixer problems
   Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
   UpgradeStatus: No upgrade log present (probably fresh install)
   dmi.bios.date: 12/01/2006
   dmi.bios.vendor: innotek GmbH
   dmi.bios.version: VirtualBox
   dmi.board.name: VirtualBox
   dmi.board.vendor: Oracle Corporation
   dmi.board.version: 1.2
   dmi.chassis.type: 1
   dmi.chassis.vendor: Oracle Corporation
   dmi.modalias:
 dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
   dmi.product.name: VirtualBox
   dmi.product.version: 1.2
   dmi.sys.vendor: innotek GmbH

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions


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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions

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

Re: [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Gene Soo]

You made a lot of updates to this record and I cannot tell whether or not
you hit on issues that requires coding changes on the Ubuntu Audio side.

I did want to report that I seem to have found a resolution that I am
satisfied with.

To summarize, I mentioned that after backing off from Virtual Box 5.0.2 and
installing Virtual Box 4.3.30, my audio problems were resolved and I was
able to use the Volume Slider in order to control the Volume. After
contacting the Virtual Box team, they gave me a customization option change
to correct the video problems I was experiencing that did not relate to
this audio problem. Since that customization option solved the video
problem, I wanted to go back and reinstall VBox 5.0.2 to see if the Audio
problems persist.
Short answer is No, they did not exist under a fresh install of 5.0.2. I
speculated to the VBox team that I perceive the Maintenance upgrade from
VBox 5.0.0 to 5.0.2 did not work completely correct. The fact that I
performed a full uninstall of VBox going to the older 4.3 level and to the
current 5.0 levels both had the audio working correctly. I can only assume
the service upgrade process was the cause.

Please close this record as resolved at your earliest convenience.


On Sun, Aug 23, 2015 at 2:51 AM, Raymond 1487...@bugs.launchpad.net
wrote:

 0:74 = 1000

 1:74 = 4000

 2:74 = 2000

 the emulated ad1980 report different codec register mask
 it make the alsa driver believe that there are three codecs


 Serial Configuration Register (Index 74h)

 REGM3 Slave 3 Codec Register Mask
 REGM0 Master Codec Register Mask
 REGM1 Slave 1 Codec Register Mask
 REGM2 Slave 2 Codec Register Mask

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1487168

 Title:
   [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
   problem

 Status in alsa-driver package in Ubuntu:
   Incomplete
 Status in virtualbox package in Ubuntu:
   New

 Bug description:
   Volume Slider is only controlling PCM channel and is not controlling
   Master. In effect, Master is restricting the audio level to the
   default of approximately 45 Percent. In order to raise the Master
   Volume Level, alsamixer is capable of changing Master. Without
   manually raising Master to Max Volume, Volume Slider can only control
   volume from 0-45% which is the default level of Master.

   Description:  Ubuntu Wily Werewolf (development branch)
   Release:  15.10

   ProblemType: Bug
   DistroRelease: Ubuntu 15.10
   Package: alsa-base 1.0.25+dfsg-0ubuntu5
   ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
   Uname: Linux 4.1.0-3-generic x86_64
   ApportVersion: 2.18-0ubuntu7
   Architecture: amd64
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:  gene   1330 F pulseaudio
 gene   1922 F alsamixer
   CurrentDesktop: Unity
   Date: Thu Aug 20 13:00:57 2015
   InstallationDate: Installed on 2015-08-19 (1 days ago)
   InstallationMedia: Edubuntu 15.10 Wily Werewolf - Alpha amd64
 (20150819)
   PackageArchitecture: all
   SourcePackage: alsa-driver
   Symptom: audio
   Symptom_Card: Built-in Audio - Intel 82801AA-ICH
   Symptom_Type: Volume slider, or mixer problems
   Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
   UpgradeStatus: No upgrade log present (probably fresh install)
   dmi.bios.date: 12/01/2006
   dmi.bios.vendor: innotek GmbH
   dmi.bios.version: VirtualBox
   dmi.board.name: VirtualBox
   dmi.board.vendor: Oracle Corporation
   dmi.board.version: 1.2
   dmi.chassis.type: 1
   dmi.chassis.vendor: Oracle Corporation
   dmi.modalias:
 dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
   dmi.product.name: VirtualBox
   dmi.product.version: 1.2
   dmi.sys.vendor: innotek GmbH

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions


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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions

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

[Bug 1488909] [NEW] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in package account-plugin-

[Gene Soo]

Public bug reported:

Errors during kubuntu-desktop kubuntu-restricted-extras install after,
successful ubuntu-desktop ubuntu-restricted-extras install on a Ubuntu
Server 15.10 system.

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: kaccounts-providers (not installed)
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu7
Architecture: amd64
Date: Tue Aug 25 18:00:45 2015
DuplicateSignature: package:kaccounts-providers:(not installed):trying to 
overwrite '/usr/share/accounts/providers/google.provider', which is also in 
package account-plugin-google 0.12+15.10.20150723-0ubuntu1
ErrorMessage: trying to overwrite 
'/usr/share/accounts/providers/google.provider', which is also in package 
account-plugin-google 0.12+15.10.20150723-0ubuntu1
InstallationDate: Installed on 2015-08-25 (0 days ago)
InstallationMedia: Ubuntu-Server 15.10 Wily Werewolf - Alpha amd64 (20150825)
RelatedPackageVersions:
 dpkg 1.18.2ubuntu2
 apt  1.0.9.10ubuntu6
SourcePackage: kaccounts-providers
Title: package kaccounts-providers (not installed) failed to install/upgrade: 
trying to overwrite '/usr/share/accounts/providers/google.provider', which is 
also in package account-plugin-google 0.12+15.10.20150723-0ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: kaccounts-providers (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package package-conflict wily

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

Title:
  package kaccounts-providers (not installed) failed to install/upgrade:
  trying to overwrite '/usr/share/accounts/providers/google.provider',
  which is also in package account-plugin-google
  0.12+15.10.20150723-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kaccounts-providers/+bug/1488909/+subscriptions

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

Re: [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Gene Soo]

I believe I have discovered the cause of the problem.
Your prompting me to look at the Open Issues for VirtualBox pointed out
that I was on V5.0.0 and when I went to the Downloads Page, V5.0.2 was
currently available.
VirtualBox will send a push notification when the team indicates and
important release is available and is displayed when you start VirtualBox.
Although 5.0.2 is generally available, they did not mark it for Push
Notification.

I upgraded to 5.0.2 and also followed through with a process called Install
Guest Additions, that led to more serious errors.
The Guest Additions Scripting installs custom support for a variety of
system dependent things including advanced Video capabilities like Screen
resizing.
I had noticed this issue before but was not zoned in on it because it is a
critical failure for the new KDE Distro and not with the other Desktops.

I decided to backoff to VBox V4.33 which is the latest release for V4 of
VirtualBox.

Spot checking all of the 15.10 Distros having this audio problem, just
getting into alsamixer and adjusting the Volume Slider, they seem to work
correctly with VBox V4.33.

The VirtualBox Team had a V5.0.3 release that hasn't been finalized but is
available for users to manually install. I have not tried that release to
see if the Audio issues are resolved.

I need to turn my attention to reporting both this Audio Issue and the
Video issue to the respective Virtual Box teams.

I believe you can mark this issues as Closed.

Thanks for all of the help in getting this issue sorted out.

On Fri, Aug 21, 2015 at 7:00 AM, Raymond 1487...@bugs.launchpad.net
wrote:


 https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/intel8x0.c?id=4235a31784f59c9be5ff71534743c055091f9735

 the real ac97 controller 8086:2415 does not support 6 channels

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1487168

 Title:
   [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
   problem

 Status in alsa-driver package in Ubuntu:
   Incomplete

 Bug description:
   Volume Slider is only controlling PCM channel and is not controlling
   Master. In effect, Master is restricting the audio level to the
   default of approximately 45 Percent. In order to raise the Master
   Volume Level, alsamixer is capable of changing Master. Without
   manually raising Master to Max Volume, Volume Slider can only control
   volume from 0-45% which is the default level of Master.

   Description:  Ubuntu Wily Werewolf (development branch)
   Release:  15.10

   ProblemType: Bug
   DistroRelease: Ubuntu 15.10
   Package: alsa-base 1.0.25+dfsg-0ubuntu5
   ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
   Uname: Linux 4.1.0-3-generic x86_64
   ApportVersion: 2.18-0ubuntu7
   Architecture: amd64
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:  gene   1330 F pulseaudio
 gene   1922 F alsamixer
   CurrentDesktop: Unity
   Date: Thu Aug 20 13:00:57 2015
   InstallationDate: Installed on 2015-08-19 (1 days ago)
   InstallationMedia: Edubuntu 15.10 Wily Werewolf - Alpha amd64
 (20150819)
   PackageArchitecture: all
   SourcePackage: alsa-driver
   Symptom: audio
   Symptom_Card: Built-in Audio - Intel 82801AA-ICH
   Symptom_Type: Volume slider, or mixer problems
   Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
   UpgradeStatus: No upgrade log present (probably fresh install)
   dmi.bios.date: 12/01/2006
   dmi.bios.vendor: innotek GmbH
   dmi.bios.version: VirtualBox
   dmi.board.name: VirtualBox
   dmi.board.vendor: Oracle Corporation
   dmi.board.version: 1.2
   dmi.chassis.type: 1
   dmi.chassis.vendor: Oracle Corporation
   dmi.modalias:
 dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
   dmi.product.name: VirtualBox
   dmi.product.version: 1.2
   dmi.sys.vendor: innotek GmbH

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions


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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions

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

Re: [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Gene Soo]

Correction to last comments concerning problem resolution.

I inadvertently referred to backing off from Version 5.0.2  to VirtualBox
Release 4.33.
The correct backoff release number is 4.3.30-101610.

On Fri, Aug 21, 2015 at 8:36 AM, Gene Soo genesoo77...@gmail.com
wrote:

 I believe I have discovered the cause of the problem.
 Your prompting me to look at the Open Issues for VirtualBox pointed out
 that I was on V5.0.0 and when I went to the Downloads Page, V5.0.2 was
 currently available.
 VirtualBox will send a push notification when the team indicates and
 important release is available and is displayed when you start VirtualBox.
 Although 5.0.2 is generally available, they did not mark it for Push
 Notification.

 I upgraded to 5.0.2 and also followed through with a process called
 Install Guest Additions, that led to more serious errors.
 The Guest Additions Scripting installs custom support for a variety of
 system dependent things including advanced Video capabilities like Screen
 resizing.
 I had noticed this issue before but was not zoned in on it because it is a
 critical failure for the new KDE Distro and not with the other Desktops.

 I decided to backoff to VBox V4.33 which is the latest release for V4 of
 VirtualBox.

 Spot checking all of the 15.10 Distros having this audio problem, just
 getting into alsamixer and adjusting the Volume Slider, they seem to work
 correctly with VBox V4.33.

 The VirtualBox Team had a V5.0.3 release that hasn't been finalized but is
 available for users to manually install. I have not tried that release to
 see if the Audio issues are resolved.

 I need to turn my attention to reporting both this Audio Issue and the
 Video issue to the respective Virtual Box teams.

 I believe you can mark this issues as Closed.

 Thanks for all of the help in getting this issue sorted out.

 On Fri, Aug 21, 2015 at 7:00 AM, Raymond 1487...@bugs.launchpad.net
 wrote:


 https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/intel8x0.c?id=4235a31784f59c9be5ff71534743c055091f9735

 the real ac97 controller 8086:2415 does not support 6 channels

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1487168

 Title:
   [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
   problem

 Status in alsa-driver package in Ubuntu:
   Incomplete

 Bug description:
   Volume Slider is only controlling PCM channel and is not controlling
   Master. In effect, Master is restricting the audio level to the
   default of approximately 45 Percent. In order to raise the Master
   Volume Level, alsamixer is capable of changing Master. Without
   manually raising Master to Max Volume, Volume Slider can only control
   volume from 0-45% which is the default level of Master.

   Description:  Ubuntu Wily Werewolf (development branch)
   Release:  15.10

   ProblemType: Bug
   DistroRelease: Ubuntu 15.10
   Package: alsa-base 1.0.25+dfsg-0ubuntu5
   ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
   Uname: Linux 4.1.0-3-generic x86_64
   ApportVersion: 2.18-0ubuntu7
   Architecture: amd64
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:  gene   1330 F pulseaudio
 gene   1922 F alsamixer
   CurrentDesktop: Unity
   Date: Thu Aug 20 13:00:57 2015
   InstallationDate: Installed on 2015-08-19 (1 days ago)
   InstallationMedia: Edubuntu 15.10 Wily Werewolf - Alpha amd64
 (20150819)
   PackageArchitecture: all
   SourcePackage: alsa-driver
   Symptom: audio
   Symptom_Card: Built-in Audio - Intel 82801AA-ICH
   Symptom_Type: Volume slider, or mixer problems
   Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
   UpgradeStatus: No upgrade log present (probably fresh install)
   dmi.bios.date: 12/01/2006
   dmi.bios.vendor: innotek GmbH
   dmi.bios.version: VirtualBox
   dmi.board.name: VirtualBox
   dmi.board.vendor: Oracle Corporation
   dmi.board.version: 1.2
   dmi.chassis.type: 1
   dmi.chassis.vendor: Oracle Corporation
   dmi.modalias:
 dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
   dmi.product.name: VirtualBox
   dmi.product.version: 1.2
   dmi.sys.vendor: innotek GmbH

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions




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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions

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

Re: [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Gene Soo]

I don't know how to proceed with the following recommendation:
you can select the emulated hda and stac9221 hda codec

When I get into the Audio Settings for this guest, I have two Pull Downs I
can control.

First is Host Audio Driver: Pulse Audio(Default), Null Audio Driver, OSS
Audio Driver, ALSA Audio Driver.

Second is Audio Controller: ICH AC97(Default), Intel HD Audio, Soundblaster
16.

I did some experimenting and was able to get the Slider to work
correctly.

The change that I made was switching the Host Audio Driver from Pulse Audio
to ALSA Audio Driver.


I went back and reviewed the Audio settings for each of the Guest Distros
involved in this testing. All defaulted to Pulse Audio  ICH AC97. I don't
know if this is an issue with Virtual Box selecting the wrong driver to
default to or if design changes in Audio Support for Pulse Audio is now in
error. I can only compare between Unity Desktop, Ubuntu Gnome, and Ubuntu
Studio does support this default fine so I would guess that VirtualBox
support would argue this is an Host Audio issue.

On Fri, Aug 21, 2015 at 12:23 AM, Raymond 1487...@bugs.launchpad.net
wrote:


 https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Devices/Audio/DevIchAc97.cpp

 any reason to use the emulated ac97 and ad1980 codec ?

 you can select the emulated hda and stac9221 hda codec

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1487168

 Title:
   [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
   problem

 Status in alsa-driver package in Ubuntu:
   Incomplete

 Bug description:
   Volume Slider is only controlling PCM channel and is not controlling
   Master. In effect, Master is restricting the audio level to the
   default of approximately 45 Percent. In order to raise the Master
   Volume Level, alsamixer is capable of changing Master. Without
   manually raising Master to Max Volume, Volume Slider can only control
   volume from 0-45% which is the default level of Master.

   Description:  Ubuntu Wily Werewolf (development branch)
   Release:  15.10

   ProblemType: Bug
   DistroRelease: Ubuntu 15.10
   Package: alsa-base 1.0.25+dfsg-0ubuntu5
   ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
   Uname: Linux 4.1.0-3-generic x86_64
   ApportVersion: 2.18-0ubuntu7
   Architecture: amd64
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:  gene   1330 F pulseaudio
 gene   1922 F alsamixer
   CurrentDesktop: Unity
   Date: Thu Aug 20 13:00:57 2015
   InstallationDate: Installed on 2015-08-19 (1 days ago)
   InstallationMedia: Edubuntu 15.10 Wily Werewolf - Alpha amd64
 (20150819)
   PackageArchitecture: all
   SourcePackage: alsa-driver
   Symptom: audio
   Symptom_Card: Built-in Audio - Intel 82801AA-ICH
   Symptom_Type: Volume slider, or mixer problems
   Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
   UpgradeStatus: No upgrade log present (probably fresh install)
   dmi.bios.date: 12/01/2006
   dmi.bios.vendor: innotek GmbH
   dmi.bios.version: VirtualBox
   dmi.board.name: VirtualBox
   dmi.board.vendor: Oracle Corporation
   dmi.board.version: 1.2
   dmi.chassis.type: 1
   dmi.chassis.vendor: Oracle Corporation
   dmi.modalias:
 dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
   dmi.product.name: VirtualBox
   dmi.product.version: 1.2
   dmi.sys.vendor: innotek GmbH

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions


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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions

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

Re: [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Gene Soo]

Additional Comments regarding last change from Pulse Audio Driver to ALSA
Audio Driver.
Although this change did resolve the Volume Slider controlling both PCM and
Master output channels,
Extended playback using this driver causes instability in the playback
speed.
At first, the playback speed is normal but after a while, the playback
speed jumps up much faster. Somewhere on the order of 10 times normal.
Reboot of machine is not necessary to restore normal playback however I
would need to do additional longer testing to see whether Browser Reload of
webpage is enough to restore playback speed. I am inclined not to pursue
this testing unless I hear back that I must run on this ALSA Driver. I am
afraid that pursuing permanent run on this ALSA Driver would cause a
Multigroup Support issue involving your team as well as VirtualBox Support.

On Fri, Aug 21, 2015 at 12:58 AM, Gene Soo genesoo77...@gmail.com
wrote:

 I don't know how to proceed with the following recommendation:
 you can select the emulated hda and stac9221 hda codec

 When I get into the Audio Settings for this guest, I have two Pull Downs I
 can control.

 First is Host Audio Driver: Pulse Audio(Default), Null Audio Driver, OSS
 Audio Driver, ALSA Audio Driver.

 Second is Audio Controller: ICH AC97(Default), Intel HD Audio,
 Soundblaster 16.

 I did some experimenting and was able to get the Slider to work correctly.

 The change that I made was switching the Host Audio Driver from Pulse
 Audio to ALSA Audio Driver.


 I went back and reviewed the Audio settings for each of the Guest Distros
 involved in this testing. All defaulted to Pulse Audio  ICH AC97. I don't
 know if this is an issue with Virtual Box selecting the wrong driver to
 default to or if design changes in Audio Support for Pulse Audio is now in
 error. I can only compare between Unity Desktop, Ubuntu Gnome, and Ubuntu
 Studio does support this default fine so I would guess that VirtualBox
 support would argue this is an Host Audio issue.

 On Fri, Aug 21, 2015 at 12:23 AM, Raymond 1487...@bugs.launchpad.net
 wrote:


 https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Devices/Audio/DevIchAc97.cpp

 any reason to use the emulated ac97 and ad1980 codec ?

 you can select the emulated hda and stac9221 hda codec

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1487168

 Title:
   [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
   problem

 Status in alsa-driver package in Ubuntu:
   Incomplete

 Bug description:
   Volume Slider is only controlling PCM channel and is not controlling
   Master. In effect, Master is restricting the audio level to the
   default of approximately 45 Percent. In order to raise the Master
   Volume Level, alsamixer is capable of changing Master. Without
   manually raising Master to Max Volume, Volume Slider can only control
   volume from 0-45% which is the default level of Master.

   Description:  Ubuntu Wily Werewolf (development branch)
   Release:  15.10

   ProblemType: Bug
   DistroRelease: Ubuntu 15.10
   Package: alsa-base 1.0.25+dfsg-0ubuntu5
   ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
   Uname: Linux 4.1.0-3-generic x86_64
   ApportVersion: 2.18-0ubuntu7
   Architecture: amd64
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:  gene   1330 F pulseaudio
 gene   1922 F alsamixer
   CurrentDesktop: Unity
   Date: Thu Aug 20 13:00:57 2015
   InstallationDate: Installed on 2015-08-19 (1 days ago)
   InstallationMedia: Edubuntu 15.10 Wily Werewolf - Alpha amd64
 (20150819)
   PackageArchitecture: all
   SourcePackage: alsa-driver
   Symptom: audio
   Symptom_Card: Built-in Audio - Intel 82801AA-ICH
   Symptom_Type: Volume slider, or mixer problems
   Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
   UpgradeStatus: No upgrade log present (probably fresh install)
   dmi.bios.date: 12/01/2006
   dmi.bios.vendor: innotek GmbH
   dmi.bios.version: VirtualBox
   dmi.board.name: VirtualBox
   dmi.board.vendor: Oracle Corporation
   dmi.board.version: 1.2
   dmi.chassis.type: 1
   dmi.chassis.vendor: Oracle Corporation
   dmi.modalias:
 dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
   dmi.product.name: VirtualBox
   dmi.product.version: 1.2
   dmi.sys.vendor: innotek GmbH

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions




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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168

Re: [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Gene Soo]

Testing Results for Kubuntu-KDE 15.10 Distribution.
Original Problem report was issued from Edubuntu 15.10 Daily.
I tried switching the Virtualbox Audio Hardware Driver from Pulse Audio to
ALSA Audio consistent with results for the Edubuntu distribution.
Monitoring alsamixer for Channel levels, using the Volume Slider on KDE
does not Control the Master Audio out channels.

I performed similar changes to my Lubuntu and Xubuntu Guests and received
the same results as Kubuntu-KDE.
To Restate, the only Distribution that I have a workaround to restore
proper Volume Slider Control is Edubuntu.
Altering Virtual Box Hardware Audio Drive from Pulse Audio to ALSA Audio
has no effect on correcting Volume Slider's lack of controlling Master Out
Channel(s) for Kubuntu-KDE, Lubuntu,  Xubuntu..

On Fri, Aug 21, 2015 at 1:20 AM, Gene Soo genesoo77...@gmail.com
wrote:

 Additional Comments regarding last change from Pulse Audio Driver to ALSA
 Audio Driver.
 Although this change did resolve the Volume Slider controlling both PCM
 and Master output channels,
 Extended playback using this driver causes instability in the playback
 speed.
 At first, the playback speed is normal but after a while, the playback
 speed jumps up much faster. Somewhere on the order of 10 times normal.
 Reboot of machine is not necessary to restore normal playback however I
 would need to do additional longer testing to see whether Browser Reload of
 webpage is enough to restore playback speed. I am inclined not to pursue
 this testing unless I hear back that I must run on this ALSA Driver. I am
 afraid that pursuing permanent run on this ALSA Driver would cause a
 Multigroup Support issue involving your team as well as VirtualBox Support.

 On Fri, Aug 21, 2015 at 12:58 AM, Gene Soo genesoo77...@gmail.com wrote:

 I don't know how to proceed with the following recommendation:
 you can select the emulated hda and stac9221 hda codec

 When I get into the Audio Settings for this guest, I have two Pull Downs
 I can control.

 First is Host Audio Driver: Pulse Audio(Default), Null Audio Driver, OSS
 Audio Driver, ALSA Audio Driver.

 Second is Audio Controller: ICH AC97(Default), Intel HD Audio,
 Soundblaster 16.

 I did some experimenting and was able to get the Slider to work correctly.

 The change that I made was switching the Host Audio Driver from Pulse
 Audio to ALSA Audio Driver.


 I went back and reviewed the Audio settings for each of the Guest Distros
 involved in this testing. All defaulted to Pulse Audio  ICH AC97. I don't
 know if this is an issue with Virtual Box selecting the wrong driver to
 default to or if design changes in Audio Support for Pulse Audio is now in
 error. I can only compare between Unity Desktop, Ubuntu Gnome, and Ubuntu
 Studio does support this default fine so I would guess that VirtualBox
 support would argue this is an Host Audio issue.

 On Fri, Aug 21, 2015 at 12:23 AM, Raymond 1487...@bugs.launchpad.net
 wrote:


 https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Devices/Audio/DevIchAc97.cpp

 any reason to use the emulated ac97 and ad1980 codec ?

 you can select the emulated hda and stac9221 hda codec

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1487168

 Title:
   [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
   problem

 Status in alsa-driver package in Ubuntu:
   Incomplete

 Bug description:
   Volume Slider is only controlling PCM channel and is not controlling
   Master. In effect, Master is restricting the audio level to the
   default of approximately 45 Percent. In order to raise the Master
   Volume Level, alsamixer is capable of changing Master. Without
   manually raising Master to Max Volume, Volume Slider can only control
   volume from 0-45% which is the default level of Master.

   Description:  Ubuntu Wily Werewolf (development branch)
   Release:  15.10

   ProblemType: Bug
   DistroRelease: Ubuntu 15.10
   Package: alsa-base 1.0.25+dfsg-0ubuntu5
   ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
   Uname: Linux 4.1.0-3-generic x86_64
   ApportVersion: 2.18-0ubuntu7
   Architecture: amd64
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:  gene   1330 F pulseaudio
 gene   1922 F alsamixer
   CurrentDesktop: Unity
   Date: Thu Aug 20 13:00:57 2015
   InstallationDate: Installed on 2015-08-19 (1 days ago)
   InstallationMedia: Edubuntu 15.10 Wily Werewolf - Alpha amd64
 (20150819)
   PackageArchitecture: all
   SourcePackage: alsa-driver
   Symptom: audio
   Symptom_Card: Built-in Audio - Intel 82801AA-ICH
   Symptom_Type: Volume slider, or mixer problems
   Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
   UpgradeStatus: No upgrade log present (probably fresh install)
   dmi.bios.date: 12/01/2006
   dmi.bios.vendor: innotek GmbH
   dmi.bios.version: VirtualBox
   dmi.board.name: VirtualBox

Re: [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Gene Soo]

Last Update for tonight.

I understand it is monumentally difficult to support all of the varieties
of hardware that exist and because of that, I make myself available to test
or provide information for my specific operating environment.

For the most part, I expect that the OS packages that I install ask for
customary user input like names, passwords, and the like.
I do not expect to have to supply or know details about my specific
hardware other than gross features like memory allocations, number of
processors and similar things.

I have identified an Audio Problem that effects specific Ubuntu
Distributions currently under development and also identified related
distributions in the same Ubuntu Family that does not have this problem
with the same VirtualBox running on the same hardware platform.

Besides the Ubuntu distributions, I also run various other Linux
distributions, OpenSUSE, Linux Mint, Fedora, Oracle Linux, Windows 10
Technical Preview.
I have not experienced anything like this on any of the other Guest OSes
that I just listed

If you have additional information requests, I will be happy to try and
supply whatever you ask.
If you have possible workarounds or code solutions, I will happy to try
them .
If we need to get VirtualBox involved in debugging the problem, I will be
happy to work with their representatives.

Otherwise, I will track this issue and hope that some day it gets
resolved.



On Fri, Aug 21, 2015 at 3:46 AM, Raymond 1487...@bugs.launchpad.net wrote:

 sb16 is no longer supported by ubuntu since isa support was dropped

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1487168

 Title:
   [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
   problem

 Status in alsa-driver package in Ubuntu:
   Incomplete

 Bug description:
   Volume Slider is only controlling PCM channel and is not controlling
   Master. In effect, Master is restricting the audio level to the
   default of approximately 45 Percent. In order to raise the Master
   Volume Level, alsamixer is capable of changing Master. Without
   manually raising Master to Max Volume, Volume Slider can only control
   volume from 0-45% which is the default level of Master.

   Description:  Ubuntu Wily Werewolf (development branch)
   Release:  15.10

   ProblemType: Bug
   DistroRelease: Ubuntu 15.10
   Package: alsa-base 1.0.25+dfsg-0ubuntu5
   ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
   Uname: Linux 4.1.0-3-generic x86_64
   ApportVersion: 2.18-0ubuntu7
   Architecture: amd64
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:  gene   1330 F pulseaudio
 gene   1922 F alsamixer
   CurrentDesktop: Unity
   Date: Thu Aug 20 13:00:57 2015
   InstallationDate: Installed on 2015-08-19 (1 days ago)
   InstallationMedia: Edubuntu 15.10 Wily Werewolf - Alpha amd64
 (20150819)
   PackageArchitecture: all
   SourcePackage: alsa-driver
   Symptom: audio
   Symptom_Card: Built-in Audio - Intel 82801AA-ICH
   Symptom_Type: Volume slider, or mixer problems
   Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
   UpgradeStatus: No upgrade log present (probably fresh install)
   dmi.bios.date: 12/01/2006
   dmi.bios.vendor: innotek GmbH
   dmi.bios.version: VirtualBox
   dmi.board.name: VirtualBox
   dmi.board.vendor: Oracle Corporation
   dmi.board.version: 1.2
   dmi.chassis.type: 1
   dmi.chassis.vendor: Oracle Corporation
   dmi.modalias:
 dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
   dmi.product.name: VirtualBox
   dmi.product.version: 1.2
   dmi.sys.vendor: innotek GmbH

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions


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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions

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

Re: [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Gene Soo]

Let me start out by asking an important question.
In the Generated Problem Report between Title and Bug Description is the
following statement.

Status in alsa-driver package in Ubuntu:
  Incomplete

Is Audio support code still under development for this Volume Slider
function or should it be working properly? If it is supposed to be working
then please continue reading this response.

I don't understand the points you are making by referencing the User Manual
and also pointing out differences in emulated vs native support for the two
chipsets.
You had included cryptic text that looks like it is logic from an XML file
or perhaps comments from program code. Later I will reference User Manual
text that has a slight mention to AC97 and nothing about AC98.

I can't tell whether the point(s) your trying to make

1) is that it working as designed and there is no problem.
2) or, You can get it to work if you make a change(unfortunately I can't
make out what change you are suggesting).

The following is contents from the Virtualbox User Manual I have at my
disposal regarding the customizable Audio Selection options:
3.7. Audio settings

The Audio section in a virtual machine's Settings window determines
whether the VM will see a sound card connected, and whether the audio
output should be heard on the host system.

If audio is enabled for a guest, you can choose between the emulation of an
Intel AC'97 controller, an Intel HD Audio controller[16
https://www.virtualbox.org/manual/ch03.html#ftn.idp46785383838160] or a
SoundBlaster 16 card. In any case, you can select what audio driver
VirtualBox will use on the host.

On a Linux host, depending on your host configuration, you can also select
between the OSS, ALSA or the PulseAudio subsystem. On newer Linux
distributions, the PulseAudio subsystem should be preferred.


If you have specific recommendations for options to try then please be
specific.


On Fri, Aug 21, 2015 at 2:53 AM, Raymond 1487...@bugs.launchpad.net
wrote:

 1) the logic of the enumlated ac97  is defined in ichac97SetVolume()

 2) there are differences between real ad1980 and the emulated ad1980

 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1325308

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1487168

 Title:
   [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
   problem

 Status in alsa-driver package in Ubuntu:
   Incomplete

 Bug description:
   Volume Slider is only controlling PCM channel and is not controlling
   Master. In effect, Master is restricting the audio level to the
   default of approximately 45 Percent. In order to raise the Master
   Volume Level, alsamixer is capable of changing Master. Without
   manually raising Master to Max Volume, Volume Slider can only control
   volume from 0-45% which is the default level of Master.

   Description:  Ubuntu Wily Werewolf (development branch)
   Release:  15.10

   ProblemType: Bug
   DistroRelease: Ubuntu 15.10
   Package: alsa-base 1.0.25+dfsg-0ubuntu5
   ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
   Uname: Linux 4.1.0-3-generic x86_64
   ApportVersion: 2.18-0ubuntu7
   Architecture: amd64
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:  gene   1330 F pulseaudio
 gene   1922 F alsamixer
   CurrentDesktop: Unity
   Date: Thu Aug 20 13:00:57 2015
   InstallationDate: Installed on 2015-08-19 (1 days ago)
   InstallationMedia: Edubuntu 15.10 Wily Werewolf - Alpha amd64
 (20150819)
   PackageArchitecture: all
   SourcePackage: alsa-driver
   Symptom: audio
   Symptom_Card: Built-in Audio - Intel 82801AA-ICH
   Symptom_Type: Volume slider, or mixer problems
   Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
   UpgradeStatus: No upgrade log present (probably fresh install)
   dmi.bios.date: 12/01/2006
   dmi.bios.vendor: innotek GmbH
   dmi.bios.version: VirtualBox
   dmi.board.name: VirtualBox
   dmi.board.vendor: Oracle Corporation
   dmi.board.version: 1.2
   dmi.chassis.type: 1
   dmi.chassis.vendor: Oracle Corporation
   dmi.modalias:
 dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
   dmi.product.name: VirtualBox
   dmi.product.version: 1.2
   dmi.sys.vendor: innotek GmbH

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions


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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions

-- 
ubuntu-bugs mailing 

Re: [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Gene Soo]

I don't understand this response.
I am not an experienced programmer with respect to these platforms and have
no control what Virtual Box presents back to the OS.
I will say that this problem effects multiple distributions.
Particularly Kubuntu-KDE, Edubuntu, Lubuntu,  Xubuntu.
Luckily, the following distributions are not impacted, Ubuntu Gnome,
Ubuntu-Unity. Ubuntu-Studio.
If there is a interface problem between the Audio support software and
hardware/visualization, those issues need to be resolved between those two
owning groups.
I would recommend the development team research the differences of how
Audio is treated across the platforms that fail vs the ones that work.
I am sure there is differences and there is something going wrong in the
ones that are failing.
I would also guess that it is not likely that Virtual Box is the direct
cause because the list of work distros runs on the same Virtualbox platform
that serves the failing distros.


On Thu, Aug 20, 2015 at 9:08 PM, Raymond 1487...@bugs.launchpad.net wrote:

 it depend on how virtualbox 5.0 emulate ad1980 ac97

 ** Summary changed:

 - [ICH - Intel 82801AA-ICH, playback] volume slider problem
 + [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
 problem

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1487168

 Title:
   [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
   problem

 Status in alsa-driver package in Ubuntu:
   New

 Bug description:
   Volume Slider is only controlling PCM channel and is not controlling
   Master. In effect, Master is restricting the audio level to the
   default of approximately 45 Percent. In order to raise the Master
   Volume Level, alsamixer is capable of changing Master. Without
   manually raising Master to Max Volume, Volume Slider can only control
   volume from 0-45% which is the default level of Master.

   Description:  Ubuntu Wily Werewolf (development branch)
   Release:  15.10

   ProblemType: Bug
   DistroRelease: Ubuntu 15.10
   Package: alsa-base 1.0.25+dfsg-0ubuntu5
   ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
   Uname: Linux 4.1.0-3-generic x86_64
   ApportVersion: 2.18-0ubuntu7
   Architecture: amd64
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:  gene   1330 F pulseaudio
 gene   1922 F alsamixer
   CurrentDesktop: Unity
   Date: Thu Aug 20 13:00:57 2015
   InstallationDate: Installed on 2015-08-19 (1 days ago)
   InstallationMedia: Edubuntu 15.10 Wily Werewolf - Alpha amd64
 (20150819)
   PackageArchitecture: all
   SourcePackage: alsa-driver
   Symptom: audio
   Symptom_Card: Built-in Audio - Intel 82801AA-ICH
   Symptom_Type: Volume slider, or mixer problems
   Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
   UpgradeStatus: No upgrade log present (probably fresh install)
   dmi.bios.date: 12/01/2006
   dmi.bios.vendor: innotek GmbH
   dmi.bios.version: VirtualBox
   dmi.board.name: VirtualBox
   dmi.board.vendor: Oracle Corporation
   dmi.board.version: 1.2
   dmi.chassis.type: 1
   dmi.chassis.vendor: Oracle Corporation
   dmi.modalias:
 dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
   dmi.product.name: VirtualBox
   dmi.product.version: 1.2
   dmi.sys.vendor: innotek GmbH

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions


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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions

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

Re: [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Gene Soo]

Lots of questions, I'll attempt to answer as best as I can.

First. Host OS Level:
uname -a
Linux gwsux79 3.13.0-62-generic #102-Ubuntu SMP Tue Aug 11 14:29:36 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux

Second, Sound Card/Sound Support: I don't understand the question about
Real Sound Card Support 5.1.

Onboard Audio Intel Motherboard DX79SI The following URL is documentation
for the Motherboard.
https://downloadmirror.intel.com/20560/eng/DX79SI_TechProdSpec06.pdf

Third question asks Which Audio Backend is being used for VirtualBox 5.0?
I take the the defaults(Audio) for installing any Guest OSes. When I look
at the Settings for the guest I reported this issue, it lists
Host Driver: PulseAudio
Controller: ICH AC97

I hope this answers your questions.

On Thu, Aug 20, 2015 at 11:19 PM, Raymond 1487...@bugs.launchpad.net
wrote:

 those emulated sigmatel ac97 codec inside virtualbox 4.x support stereo
 only

 which host os are you using linux/windows ?

 do you have a real sound card support 5.1 ?

 which audio backend do your virtualbox5.0 using ?

 it seem that the emulated ad1980 ac97 support multi channel

 profiles:
 input:analog-stereo: Analog Stereo Input (priority 60,
 available: unknown)
 output:analog-stereo: Analog Stereo Output (priority 6000,
 available: unknown)
 output:analog-stereo+input:analog-stereo: Analog Stereo
 Duplex (priority 6060, available: unknown)
 output:analog-surround-21: Analog Surround 2.1 Output
 (priority 800, available: unknown)
 output:analog-surround-21+input:analog-stereo: Analog
 Surround 2.1 Output + Analog Stereo Input (priority 860, available: unknown)
 output:analog-surround-40: Analog Surround 4.0 Output
 (priority 700, available: unknown)
 output:analog-surround-40+input:analog-stereo: Analog
 Surround 4.0 Output + Analog Stereo Input (priority 760, available: unknown)
 output:analog-surround-41: Analog Surround 4.1 Output
 (priority 800, available: unknown)
 output:analog-surround-41+input:analog-stereo: Analog
 Surround 4.1 Output + Analog Stereo Input (priority 860, available: unknown)
 output:analog-surround-50: Analog Surround 5.0 Output
 (priority 700, available: unknown)
 output:analog-surround-50+input:analog-stereo: Analog
 Surround 5.0 Output + Analog Stereo Input (priority 760, available: unknown)
 output:analog-surround-51: Analog Surround 5.1 Output
 (priority 800, available: unknown)
 output:analog-surround-51+input:analog-stereo: Analog
 Surround 5.1 Output + Analog Stereo Input (priority 860, available: unknown)
 off: Off (priority 0, available: unknown)
 active profile: output:analog-stereo+input:analog-stereo

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1487168

 Title:
   [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
   problem

 Status in alsa-driver package in Ubuntu:
   New

 Bug description:
   Volume Slider is only controlling PCM channel and is not controlling
   Master. In effect, Master is restricting the audio level to the
   default of approximately 45 Percent. In order to raise the Master
   Volume Level, alsamixer is capable of changing Master. Without
   manually raising Master to Max Volume, Volume Slider can only control
   volume from 0-45% which is the default level of Master.

   Description:  Ubuntu Wily Werewolf (development branch)
   Release:  15.10

   ProblemType: Bug
   DistroRelease: Ubuntu 15.10
   Package: alsa-base 1.0.25+dfsg-0ubuntu5
   ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
   Uname: Linux 4.1.0-3-generic x86_64
   ApportVersion: 2.18-0ubuntu7
   Architecture: amd64
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:  gene   1330 F pulseaudio
 gene   1922 F alsamixer
   CurrentDesktop: Unity
   Date: Thu Aug 20 13:00:57 2015
   InstallationDate: Installed on 2015-08-19 (1 days ago)
   InstallationMedia: Edubuntu 15.10 Wily Werewolf - Alpha amd64
 (20150819)
   PackageArchitecture: all
   SourcePackage: alsa-driver
   Symptom: audio
   Symptom_Card: Built-in Audio - Intel 82801AA-ICH
   Symptom_Type: Volume slider, or mixer problems
   Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
   UpgradeStatus: No upgrade log present (probably fresh install)
   dmi.bios.date: 12/01/2006
   dmi.bios.vendor: innotek GmbH
   dmi.bios.version: VirtualBox
   dmi.board.name: VirtualBox
   dmi.board.vendor: Oracle Corporation
   dmi.board.version: 1.2
   dmi.chassis.type: 1
   dmi.chassis.vendor: Oracle Corporation
   dmi.modalias:
 dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
   dmi.product.name: 

[Bug 1487168] [NEW] [ICH - Intel 82801AA-ICH, playback] volume slider problem

[Gene Soo]

Public bug reported:

Volume Slider is only controlling PCM channel and is not controlling
Master. In effect, Master is restricting the audio level to the  default
of approximately 45 Percent. In order to raise the Master  Volume Level,
alsamixer is capable of changing Master. Without manually raising Master
to Max Volume, Volume Slider can only control volume from 0-45% which is
the default level of Master.

Description:Ubuntu Wily Werewolf (development branch)
Release:15.10

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gene   1330 F pulseaudio
  gene   1922 F alsamixer
CurrentDesktop: Unity
Date: Thu Aug 20 13:00:57 2015
InstallationDate: Installed on 2015-08-19 (1 days ago)
InstallationMedia: Edubuntu 15.10 Wily Werewolf - Alpha amd64 (20150819)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Built-in Audio - Intel 82801AA-ICH
Symptom_Type: Volume slider, or mixer problems
Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

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

Title:
  [ICH - Intel 82801AA-ICH, playback] volume slider problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions

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

[Bug 1481828] [NEW] package uuid-runtime 2.26.2-6ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Gene Soo]

Public bug reported:

None

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: uuid-runtime 2.26.2-6ubuntu3
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu5
Architecture: amd64
Date: Wed Aug  5 10:50:06 2015
DuplicateSignature: package:uuid-runtime:2.26.2-6ubuntu3:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2015-08-05 (0 days ago)
InstallationMedia: Xubuntu 15.10 Wily Werewolf - Alpha amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.18.1ubuntu1
 apt  1.0.9.10ubuntu1
SourcePackage: util-linux
Title: package uuid-runtime 2.26.2-6ubuntu3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package wily

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

Title:
  package uuid-runtime 2.26.2-6ubuntu3 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/util-linux/+bug/1481828/+subscriptions

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

[Bug 1419994] [NEW] Desktop Daily Build fails to install

[Gene Soo]

Public bug reported:

Failure during copying phase.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.8
ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
Uname: Linux 3.18.0-12-generic x86_64
ApportVersion: 2.16-0ubuntu1
Architecture: amd64
CasperVersion: 1.350
Date: Mon Feb  9 14:40:29 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150208)
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug ubiquity-2.21.8 ubuntu vivid

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

Title:
  Desktop Daily Build fails to install

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

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

Re: [Bug 1208129] Re: Compares NoneType() and str(), hence fails to make bootable usb

[Gene Soo]

I completely agree. I used to be a mainframe software developer and
understand the concepts.
The app needs to expose as much diagnostic information as required to
isolate and identify the problem without having an uneducated enduser
expected to recreate the problem running under a development environment.
The fact that the problem is hard to reproduce makes it more critical that
consideration be adhered too.
I can't remember now what ISO I was working with or whether I saved it or
not in order to attempt to recreate.

Gene


On Mon, Mar 31, 2014 at 7:58 AM, bootchk 1208...@bugs.launchpad.net wrote:

 I experienced this on 13.04.  I then downloaded the source package for
 usb-creator_0.2.47.2 (in raring updates repository) and ran usbcreator-
 gtk from inside Eclipse.  I could not reproduce the error in 3 attempts
 with various iso images and physical drives.

 So if you are a user reading this, it might not be fixed because it is
 hard to reproduce.

 I think in addition to printing the given error message, the app should
 also print the python trace. That wouldn't be any uglier to users, and
 might make it easier to track down the cause.

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1208129

 Title:
   Compares NoneType() and str(), hence fails to make bootable usb

 Status in usb-creator package in Ubuntu:
   Confirmed

 Bug description:
   Ubuntu version: 13.04 with all updates

   Steps to reproduce:
   1. Open usb-creator-gtk or usb-creator-kde
   2. Browse required iso and try to make a usb bootable
   3. Then just after it starts copying files, an error dialog box with
 following message appears.
   An uncaught exception was raised: unorderable types: NoneType() =
 str()
   In gtk version dialog box title is Installation failed, in kde it is
 Error - startup disk creator.

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1208129/+subscriptions


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

Title:
  Compares NoneType() and str(), hence fails to make bootable usb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1208129/+subscriptions

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