[Touch-packages] [Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object
vanvugt: nope, also when booting the live ISO for the first time (so I can confirm it's not just at logouts; trying to get a stack trace, but network's really unstable today, so unable to download debug symbols) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: Confirmed Status in indicator-messages package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/2015962/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object
I can confirm I'm facing the same issue in the latest Ubuntu Unity daily build (with the latest version of accountsservice). indicator-messages crashes on every login, not just on log out (including booting the ISO). You should be able to reproduce this bug with the latest Ubuntu Unity ISO at https://cdimage.ubuntu.com/ubuntu- unity/daily-live/current. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: Confirmed Status in indicator-messages package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/2015962/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735998] Re: [Needs-Packaging]Decouple unity related settings as unity-settings
@jbicha I'm not sure why this package wasn't approved, since the other flavours do have settings packages (such as ubuntustudio-default- settings and lubuntu-default-settings, as well as kubuntu-settings- desktop). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1735998 Title: [Needs-Packaging]Decouple unity related settings as unity-settings Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: This is an attempt to resolve "* Shared GSettings keys" issue listed under https://wiki.ubuntu.com/Unity/NotDefaultIssues. Ubuntu so far is providing session related overrides for both ubuntu & unity sessions in a single package, i.e. ubuntu-settings. But now that Unity is not the default desktop it doesn't make any sense to carry unity related overrides in ubuntu-settings. For this purpose I have created a new project: unity-settings (https://code.launchpad.net/~khurshid-alam/unity-settings/trunk) and the binary would be unity-settings in universe. To make this happen in under 18.04 cycle, the work-flow should be: 1) Have unity-settings in the universe 2) Have ubuntu-unity-desktop in the universe 3) Let ubuntu-unity-desktop depends on unity-settings 4) Drop unity related settings in ubuntu-settings (merge request in-progress) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1735998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902907] Re: Developer Options shows 'groovy-proposed' instead of 'hirsute-proposed' (software-properties-gtk on 21.04 Hirsute Hippo)
I'll take a look with the latest ISO. I had tested with the first daily build on 21.04 that was released. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1902907 Title: Developer Options shows 'groovy-proposed' instead of 'hirsute- proposed' (software-properties-gtk on 21.04 Hirsute Hippo) Status in software-properties package in Ubuntu: Incomplete Bug description: When testing Hirsute Hippo (21.04), I found that software-properties- gtk shows 'groovy-proposed' instead of 'hirsute-proposed'. This is from a live session in VirtualBox. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: software-properties-gtk 0.99.3 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Nov 4 16:16:14 2020 LiveMediaBuild: Ubuntu Unity 21.04 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1902907/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902907] [NEW] Developer Options shows 'groovy-proposed' instead of 'hirsute-proposed' (software-properties-gtk on 21.04 Hirsute Hippo)
Public bug reported: When testing Hirsute Hippo (21.04), I found that software-properties-gtk shows 'groovy-proposed' instead of 'hirsute-proposed'. This is from a live session in VirtualBox. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: software-properties-gtk 0.99.3 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Nov 4 16:16:14 2020 LiveMediaBuild: Ubuntu Unity 21.04 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1902907 Title: Developer Options shows 'groovy-proposed' instead of 'hirsute- proposed' (software-properties-gtk on 21.04 Hirsute Hippo) Status in software-properties package in Ubuntu: New Bug description: When testing Hirsute Hippo (21.04), I found that software-properties- gtk shows 'groovy-proposed' instead of 'hirsute-proposed'. This is from a live session in VirtualBox. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: software-properties-gtk 0.99.3 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Nov 4 16:16:14 2020 LiveMediaBuild: Ubuntu Unity 21.04 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1902907/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1281580] Re: glib-compile-schemas doesn't compile relocatable schemas
I can confirm that this issue is still present in Ubuntu 20.04.1 Focal
Fossa.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1281580
Title:
glib-compile-schemas doesn't compile relocatable schemas
Status in GLib:
Expired
Status in glib2.0 package in Ubuntu:
Confirmed
Bug description:
Dear Developers,
I am using the Ubuntu 14.04 development release with the GNOME Shell 3.10
and, because my wife is using this system as well, I defined some settings in a
gschema.override file.
Everything is working right, except applying settings related to custom
key-bindings.
I added following lines my gschema.override file:
[org.gnome.settings-daemon.plugins.media-keys]
www='w'
email='e'
custom-keybindings =
['/org/gnome/settings-daemon/plugins/media-keys/custom-keybinding/custom0']
[org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/]
name = 'Launch Gedit'
command = 'gedit'
binding = 'g'
I put my gschema.override file in the '/usr/share/glib-2.0/schemas'
directory. After I added these lines, I ran 'glib-compile-schemas
/usr/share/glib2.0/schemas' and no error was reported.
For testing purposes I created a new user, logged out, and logged in with the
new user. In the best case, the custom key-binding were applied automatically,
but this has not happened. Other defined key-bindings were applied correctly.
In the gnome-control-center's key-bindings tab, the table containing custom
shortcuts is empty, containing one row with empty columns.
Running 'gsettings list-recursively org.gnome.settings-daemon.plugins
.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins
/media-keys/custom-keybindings/custom0/' shows, the name, command, and
binding key pairs contain empty ('') values.
If I manually run following commands, the custom key-binding is created
correctly:
gsettings set
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
name "Launch Gedit"
gsettings set
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
command "gedit"
gsettings set
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
binding "g"
Am I doing anything wrong when I want to add a custom key-bindings in
my schema file, or is 'glib-compile-schemas' really not applying this
part from the schema file?
Attila
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libglib2.0-bin 2.39.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
Uname: Linux 3.13.0-8-generic i686
ApportVersion: 2.13.2-0ubuntu4
Architecture: i386
CurrentDesktop: GNOME
Date: Tue Feb 18 13:58:37 2014
InstallationDate: Installed on 2013-12-13 (67 days ago)
InstallationMedia: BeLin 3.02 i386
SourcePackage: glib2.0
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1281580/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1866959] Re: Password - No Place
** Description changed: - In all Ubuntu versions, sometimes, I'd type, but the input would not be - visible. This is urgent since people might type wrong passwords and then - think that they have forgotten the password. + In all Ubuntu versions using LightDM, sometimes, I'd type, but the input + would not be visible. This is urgent since people might type wrong + passwords and then think that they have forgotten the password. Description:Ubuntu 18.04.4 LTS Release:18.04 lightdm: - Installed: 1.26.0-0ubuntu1 - Candidate: 1.26.0-0ubuntu1 - Version table: - *** 1.26.0-0ubuntu1 500 - 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.26.0-0ubuntu1 + Candidate: 1.26.0-0ubuntu1 + Version table: + *** 1.26.0-0ubuntu1 500 + 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages + 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1866959 Title: Password - No Place Status in lightdm package in Ubuntu: New Bug description: In all Ubuntu versions using LightDM, sometimes, I'd type, but the input would not be visible. This is urgent since people might type wrong passwords and then think that they have forgotten the password. Description:Ubuntu 18.04.4 LTS Release:18.04 lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1866959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled.
** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1706770 Title: Lock screen can be bypassed when auto-login is enabled. Status in Ubuntu MATE: Confirmed Status in lightdm package in Ubuntu: Fix Committed Status in mate-session-manager package in Ubuntu: Confirmed Bug description: 16.04 LTS = Hi, My machine is set up with full-disk encryption, so it requires a password when I boot it up. Because of this I thought I would enable auto-login to avoid having to enter two passwords at boot. When I leave my computer for short periods of time, I lock it. I thought this was working fine for a long time, but I've discovered the lock screen is actually easily bypassable when auto-login is enabled. All one has to do is click "Switch User" on the lock screen, then press "Unlock" and the computer unlocks without prompting for a password. Perhaps this is just me being an idiot, but I thought this was secure until now. It seems like either unlocking should always require a password (otherwise what's the point of locking in the first place) or it should be made totally obvious that unlocking doesn't actually require a password (i.e. removing the password box from the lock screen when auto-login is enabled). Thanks, Chris To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1706770/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled.
** Changed in: ubuntu-mate Status: New => Confirmed ** Information type changed from Public Security to Private Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1706770 Title: Lock screen can be bypassed when auto-login is enabled. Status in Ubuntu MATE: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in mate-session-manager package in Ubuntu: Confirmed Bug description: 16.04 LTS = Hi, My machine is set up with full-disk encryption, so it requires a password when I boot it up. Because of this I thought I would enable auto-login to avoid having to enter two passwords at boot. When I leave my computer for short periods of time, I lock it. I thought this was working fine for a long time, but I've discovered the lock screen is actually easily bypassable when auto-login is enabled. All one has to do is click "Switch User" on the lock screen, then press "Unlock" and the computer unlocks without prompting for a password. Perhaps this is just me being an idiot, but I thought this was secure until now. It seems like either unlocking should always require a password (otherwise what's the point of locking in the first place) or it should be made totally obvious that unlocking doesn't actually require a password (i.e. removing the password box from the lock screen when auto-login is enabled). Thanks, Chris To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1706770/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1222527] Re: Rename 'Software & Updates' label
** Changed in: ayatana-design Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1222527 Title: Rename 'Software & Updates' label Status in Ayatana Design: Confirmed Status in software-properties package in Ubuntu: Confirmed Bug description: Ubuntu 13.10 Language: English US UX Problem: When searching in the Dash for the system software updater - a pretty common task - always two entries are presented to the user with nearly the same name. There is the update-manager labeled ' Software Updater' and there is software-properties labeled 'Software & Updates', result: 'Software Updater' and 'Software & Updates'. Both names start with a capital S and a capital U → they should be easier to distinguish. Suggested solution: Relabel the less common GenericName of the .desktop file to something else. As the software-properties are less important IMHO for the daily use of an average user, I purpose to relabel it to 'Software Settings'. Not my favorite name, but visual much better to distinguish then the current name and it would share the naming pattern of having 'Settings' at the end of a program that allows the user to configure something. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: software-properties-gtk 0.92.25 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sun Sep 8 20:50:21 2013 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2013-08-27 (11 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130827) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1222527/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1866959] [NEW] Password - No Place
Public bug reported: In all Ubuntu versions, sometimes, I'd type, but the input would not be visible. This is urgent since people might type wrong passwords and then think that they have forgotten the password. Description:Ubuntu 18.04.4 LTS Release:18.04 lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1866959 Title: Password - No Place Status in lightdm package in Ubuntu: New Bug description: In all Ubuntu versions, sometimes, I'd type, but the input would not be visible. This is urgent since people might type wrong passwords and then think that they have forgotten the password. Description:Ubuntu 18.04.4 LTS Release:18.04 lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1866959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862341] Re: Errors thrown at boot: Security
** Changed in: xorg (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1862341 Title: Errors thrown at boot: Security Status in xorg package in Ubuntu: Confirmed Bug description: DETAILS: Version: Ubuntu Focal Fossa (development branch) Release: 20.04 xorg: Installed: 1:7.7+19ubuntu13 Candidate: 1:7.7+19ubuntu13 Version table: *** 1:7.7+19ubuntu13 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Xorg, at boot, through a couple of errors: [ error ] display server started at tty -1 For 20 seconds, the xorg server went on complaining the same issue. I tried to ssh into the virtual machine in VirtualBox, and it simply logged in without a password. Note: Automatic Login was disabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.438 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 7 11:41:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity SourcePackage: xorg Symptom: display 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.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1862341/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
