[Bug 2078630] [NEW] package fprintd (not installed) failed to install/upgrade: tr it doenst detecting my fprint sensor ım using huawei matebook d16 2024ying to overwrite '/usr/bin/fprin
Public bug reported: it doesnt detecting my fprint sensor ım using huawei matebook d16 2024 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: fprintd (not installed) ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 AptOrdering: python3-validity:amd64: Remove open-fprintd:amd64: Remove fprintd:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Sep 1 19:02:15 2024 DpkgTerminalLog: Preparing to unpack .../fprintd_1.94.3-1_amd64.deb ... Unpacking fprintd (1.94.3-1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/fprintd_1.94.3-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/fprintd-delete', which is also in package fprintd-clients 1.90.1-0build1~noble ErrorMessage: trying to overwrite '/usr/bin/fprintd-delete', which is also in package fprintd-clients 1.90.1-0build1~noble InstallationDate: Installed on 2024-08-30 (2 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6.1 apt 2.7.14build2 SourcePackage: fprintd Title: package fprintd (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/fprintd-delete', which is also in package fprintd-clients 1.90.1-0build1~noble UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fprintd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078630 Title: package fprintd (not installed) failed to install/upgrade: tr it doenst detecting my fprint sensor ım using huawei matebook d16 2024ying to overwrite '/usr/bin/fprintd-delete', which is also in package fprintd-clients 1.90.1-0build1~noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/2078630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075143] [NEW] got error during upgrade
Public bug reported: i was upgrading my linux but got error when its reached the setting channels sections and thrw this Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'.\ ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.14 ProcVersionSignature: Ubuntu 6.5.0-44.44-generic 6.5.13 Uname: Linux 6.5.0-44-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Jul 30 14:38:16 2024 InstallationDate: Installed on 2024-06-14 (46 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2024-07-30 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade mantic wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075143 Title: got error during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2075143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073846] Re: [SRU] Fix the session workqueue thread priority setting issue for newer Linux kernels (>=6.x)
** Tags added: seg sts-sponsor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073846 Title: [SRU] Fix the session workqueue thread priority setting issue for newer Linux kernels (>=6.x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/2073846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073846] Re: [SRU] Fix the session workqueue thread priority setting issue for newer Linux kernels (>=6.x)
** Description changed:
[ Impact ]
The Linux SCSI driver uses `alloc_workqueue()` to create a kernel
workqueue for session transmit work. This call would cause the kernel <
6.x to create a dedicated worker thread for the workqueue. The userspace
library open-iscsi version < 2.1.10 then adjusts the workqueue thread's
nice value for performance reasons when a new iSCSI session is
initiated. The algorithm for that is roughly as follows
(https://github.com/open-iscsi/open-
iscsi/blob/2.1.9/usr/initiator.c#L1390) :
- Check if the driver in use has a write work queue. If not, abort.
- Open the /proc dir, and iterate over all dir entries:
- Run "stat" over /proc//stat
- Read the contents of "stat" file, which looks like the following:
898582 (kworker/u512:1-iscsi_q_0) I 2 0 0 0 -1 69238880 0 0 0 0 0 8 0 0 20 0
1 0 52431895 0 0 18446744073709551615 0 0 0 0 0 0 0 2147483647 0 1 0 0 17 28 0
0 0 0 0 0 0 0 0 0 0 0 0
- Try to locate "(" with strchr, starting from the beginning. Skip the
process if not found.
- Try to locate ")" with strchr, starting from the position of "(". Skip the
process if not found.
- Check whether the string between "(" and ")" contains the following pattern
"iscsi_q_%d"
- Check the number %d matches with the host ID of the session.
- If %d matches the session id, grab the PID of the current proc entry and
call `setpriority()`
So the algorithm assumes the following about the kernel workqueue
thread:
- It would be present in the /proc list
- Its name would match the iscsi_q_%d pattern
Due to the changes in how Linux workqueue threads work in v6.x, the
priority setting approach won't work for the following reasons:
- The `alloc_workqueue()` no longer creates a dedicated thread for the
workqueue. The workqueue thread is shared between different workqueues.
- The workqueue thread is dynamically renamed to the name of the workqueue
that's actively running
- The workqueue thread disappears from the /proc list when it's inactive
The algorithm as-is does the following right now:
- If the kernel workqueue thread *by luck* happens to be running the
iscsi task, the name matches, and the priority is set. But that's not
what the code wants to do since it also increases the priority for all
the other tasks that are scheduled to the workqueue thread as well.
- If not, the open-iscsi prints the following log message, and proceeds
to operate as normal:
```
iscsistart: Could not set session1 priority. READ/WRITE throughout and
latency could be affected.
```
The upstream has fixed this issue with the patch
(https://github.com/open-iscsi/open-iscsi/pull/445). The patch sets the
default nice value for `node.session.xmit_thread_priority` to `0`, and
then skips the priority adjustment algorithm altogether when the
priority is set to zero.
This SRU proposes to backport this patch to the Ubuntu releases that use
Linux kernel 6.8 and above by default, and have an open-iscsi version of
less than (2.1.10).
-
[ Test Plan ]
# Launch a test VM:
$> lxc launch ubuntu:noble --vm iscsi-test-noble
# Obtain a shell from the VM:
$> lxc shell iscsi-test-noble
# Install 'tgt' and 'open-iscsi':
- $> sudo apt -y update && sudo apt -y install tgt open-iscsi
+ $> sudo apt -y update && sudo apt -y install tgt open-iscsi
# Configure 'tgt':
## Step 1: Configure a LUN
Add the following to '/etc/tgt/conf.d/iscsi.conf':
- backing-store /dev/sda
- initiator-address 127.0.0.1
- incominguser iscsi-user password
- outgoinguser iscsi-target secretpass
+ backing-store /dev/sda
+ initiator-address 127.0.0.1
+ incominguser iscsi-user password
+ outgoinguser iscsi-target secretpass
(change /dev/sda to an existing device's name if it's not present)
## Step 2: Restart 'tgt' to make changes effective:
$> systemctl restart tgt
## Step 3: Check if 'tgt' has started serving the LUN:
$> tgtadm --mode target --op show
(output should be similar to below)
Target 1: iqn.2020-07.example.com:lun1
- System information:
- Driver: iscsi
- State: ready
- I_T nexus information:
- LUN information:
- LUN: 0
- Type: controller
- SCSI ID: IET 0001
- SCSI SN: beaf10
- Size: 0 MB, Block size: 1
- Online: Yes
- Removable media: No
- Prevent removal: No
- Readonly: No
- SWP: No
- Thin-provisioning: No
- Backing store type: null
- Backing store path: None
- Backing store flags:
- Account information:
- iscsi-user
- iscsi-target (outgoing)
- ACL information:
- 127.0.0.1
-
+ System information:
+ Driver: iscsi
+ State: ready
+ I_T nexus information:
+ LUN information:
+
[Bug 2073846] Re: [SRU] Fix the session workqueue thread priority setting issue for newer Linux kernels (>=6.x)
Removed 'oracular' from targets as it seems to be updated to 2.1.10 already. ** No longer affects: open-iscsi (Ubuntu Oracular) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073846 Title: [SRU] Fix the session workqueue thread priority setting issue for newer Linux kernels (>=6.x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/2073846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073846] [NEW] [SRU] Fix the session workqueue thread priority setting issue for newer Linux kernels (>=6.x)
;: InitiatorName=iqn.2020-07.example.com:lun1 ## Step 3: Modify the following file '/etc/iscsi/nodes/iqn.2020-07.example.com:lun1/127.0.0.1,3260,1/default': # (the file must already exist, it should've been automatically created after the discovery) Append the following lines to the end of the file, and save: ``` node.session.auth.authmethod = CHAP node.session.auth.username = iscsi-user node.session.auth.password = password node.session.auth.username_in = iscsi-target node.session.auth.password_in = secretpass node.startup = automatic ``` ## Step 4: Restart open-iscsi to make changes effective: $> systemctl restart open-iscsi.service iscsid ## Step 5: Check the outcome # (the service status should indicate that login to 'iqn.2020-07.example.com:lun1' has been successful) systemctl status open-iscsi.service ● open-iscsi.service - Login to default iSCSI targets Loaded: loaded (/usr/lib/systemd/system/open-iscsi.service; enabled; preset: enabled) Active: active (exited) since Mon 2024-07-22 13:36:15 UTC; 4s ago Docs: man:iscsiadm(8) man:iscsid(8) Process: 3049 ExecStart=/usr/sbin/iscsiadm -m node --loginall=automatic (code=exited, status=0/SUCCESS) Process: 3065 ExecStart=/usr/lib/open-iscsi/activate-storage.sh (code=exited, status=0/SUCCESS) Main PID: 3065 (code=exited, status=0/SUCCESS) CPU: 4ms Jul 22 13:36:15 welcomed-bluebird systemd[1]: Starting open-iscsi.service - Login to default iSCSI targets... Jul 22 13:36:15 welcomed-bluebird iscsiadm[3049]: Logging in to [iface: default, target: iqn.2020-07.example.com:lun1, portal: 127.0.0.1,3260] Jul 22 13:36:15 welcomed-bluebird iscsiadm[3049]: Login to [iface: default, target: iqn.2020-07.example.com:lun1, portal: 127.0.0.1,3260] successful. Jul 22 13:36:15 welcomed-bluebird systemd[1]: Finished open-iscsi.service - Login to default iSCSI targets # (the command should list an active connection to the 'iqn.2020-07.example.com:lun1') $> iscsiadm -m session -o show tcp: [1] 127.0.0.1:3260,1 iqn.2020-07.example.com:lun1 (non-flash) # Observe iscsid complaining about priority: cat /var/log/syslog | grep "Could not set" 2024-07-22T13:36:16.874243+00:00 welcomed-bluebird iscsid: Could not set session1 priority. READ/WRITE throughout and latency could be affected. 2024-07-22T13:38:31.002732+00:00 welcomed-bluebird iscsid: Could not set session1 priority. READ/WRITE throughout and latency could be affected. # TODO: Add fix ppa steps here [ Where problems could occur ] The change prevents a priority change that shouldn't happen in the first place. That might affect some workloads unknowingly depending on it. On the other hand, the nice setting happens intermittently (i.e. by luck) so the behavior right now can't be depended on anyway. The patch only touches the priority setting code so I wouldn't expect any serious breakage. * Think about what the upload changes in the software. Imagine the change is wrong or breaks something else: how would this show up? * It is assumed that any SRU candidate patch is well-tested before upload and has a low overall risk of regression, but it's important to make the effort to think about what ''could'' happen in the event of a regression. * This must '''never''' be "None" or "Low", or entirely an argument as to why your upload is low risk. * This both shows the SRU team that the risks have been considered, and provides guidance to testers in regression-testing the SRU. [ Other Info ] The other releases that is running a 6.x kernel installed with other means (e.g. hw-enablement, availability) may set the `node.session.xmit_thread_priority` from `-20` to `0` in `/etc/iscsid.conf` as a workaround: node.session.xmit_thread_priority = 0 which is the default priorty for the workqueue threads. ** Affects: open-iscsi (Ubuntu) Importance: Undecided Assignee: Mustafa Kemal Gilor (mustafakemalgilor) Status: In Progress ** Affects: open-iscsi (Ubuntu Noble) Importance: Undecided Assignee: Mustafa Kemal Gilor (mustafakemalgilor) Status: In Progress ** Affects: open-iscsi (Ubuntu Oracular) Importance: Undecided Assignee: Mustafa Kemal Gilor (mustafakemalgilor) Status: In Progress ** Also affects: open-iscsi (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: open-iscsi (Ubuntu Oracular) Importance: Undecided Assignee: Mustafa Kemal Gilor (mustafakemalgilor) Status: New ** Changed in: open-iscsi (Ubuntu Noble) Assignee: (unassigned) => Mustafa Kemal Gilor (mustafakemalgilor) ** Changed in: open-iscsi (Ubuntu Noble) Status: New => In Progress ** Changed in: open-iscsi (Ubuntu Oracular) Status: New => In Progress -- You received this bug notification b
[Bug 2071745] [NEW] Upgrade to 24.04 lts to 23.10 not working
Public bug reported: It fails to fix broken PPAs of existing application like chrome and edge, slack etc ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.14 ProcVersionSignature: Ubuntu 6.5.0-42.42-generic 6.5.13 Uname: Linux 6.5.0-42-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Jul 3 03:23:00 2024 InstallationDate: Installed on 2024-03-01 (124 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2024-07-02 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade mantic wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071745 Title: Upgrade to 24.04 lts to 23.10 not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2071745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057687] Re: systemctl hibernate error: "Call to Hibernate failed: Invalid argument"
@Joris I guess you need to calculate the offset in a different way since you 're using logical volume Reply to #14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057687 Title: systemctl hibernate error: "Call to Hibernate failed: Invalid argument" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2057687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1998789] Re: [SRU] PooledLDAPHandler.result3 does not release pool connection back when an exception is raised
Verification is done for Ussuri. Tested the -proposed package with the test plan and confirmed that the problem has disappeared. ** Tags removed: verification-ussuri-needed ** Tags added: verification-ussuri-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1998789 Title: [SRU] PooledLDAPHandler.result3 does not release pool connection back when an exception is raised To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1998789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955847] [NEW] (nvidia-settings:3392): GLib-GObject-CRITICAL **: 22:15:47.935: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ** Message: 22:15:48.068: PRIME: No offloading required. Abo
Public bug reported: (nvidia-settings:3392): GLib-GObject-CRITICAL **: 22:15:47.935: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ** Message: 22:15:48.068: PRIME: No offloading required. Abort ** Message: 22:15:48.068: PRIME: is it supported? no Package xorg-server was not found in the pkg-config search path. Perhaps you should add the directory containing `xorg-server.pc' to the PKG_CONFIG_PATH environment variable No package 'xorg-server' found Error executing /usr/share/screen-resolution-extra/nvidia-polkit: Permission denied ERROR: Unable to open X config file '/etc/X11/xorg.conf' for writing. that is the output when i run nvidai-settings from the terminal the first one is on lunch the 2nd is when i open the save config window and the 3rd when i press save ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-settings 470.57.01-0ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 27 22:16:59 2021 ExecutablePath: /usr/bin/nvidia-settings SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Attachment added: "image of the output on the terminal" https://bugs.launchpad.net/bugs/1955847/+attachment/5549844/+files/Screenshot%20from%202021-12-27%2022-16-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/1955847 Title: (nvidia-settings:3392): GLib-GObject-CRITICAL **: 22:15:47.935: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ** Message: 22:15:48.068: PRIME: No offloading required. Abort ** Message: 22:15:48.068: PRIME: is it supported? no WARNING: Unable to parse X.Org version string. WARNING: Unable to parse X.Org version string. Package xorg-server was not found in the pkg-config search path. Perhaps you should add the directory containing `xorg-server.pc' to the PKG_CONFIG_PATH environment variable No package 'xorg-server' found Error executing /usr/share/screen-resolution-extra/nvidia- polkit: Permission denied ERROR: Unable to open X config file '/etc/X11/xorg.conf' for writing. that is the output when i run nvidai-settings from the terminal the first one is on lunch the 2nd is when i open the save config window and the 3rd when i press save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1955847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946658] [NEW] package vim-runtime 2:8.1.2269-1ubuntu5.3 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/vim-runtime.list-new': Operation not permitted
Public bug reported: packages are not installing on one time need to use same command two times for the installation of packages on ubuntu. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: vim-runtime 2:8.1.2269-1ubuntu5.3 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: vim-tiny:amd64: Install vim-common:amd64: Install vim-runtime:amd64: Install vim:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 11 19:35:26 2021 ErrorMessage: unable to create new file '/var/lib/dpkg/info/vim-runtime.list-new': Operation not permitted InstallationDate: Installed on 2021-10-11 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: vim Title: package vim-runtime 2:8.1.2269-1ubuntu5.3 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/vim-runtime.list-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vim (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946658 Title: package vim-runtime 2:8.1.2269-1ubuntu5.3 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/vim-runtime.list-new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1946658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942001] [NEW] failure to compile on Kernel 5.13.9 Ubuntu 21.04
Public bug reported: trying to compile NDISWrapper from source and I keep getting this: omar_mustafa@omar-mustafa-HP-Laptop-15-da1xxx:~/Downloads/ndiswrapper-1.63$ sudo make make -C utils make[1]: Entering directory '/home/omar_mustafa/Downloads/ndiswrapper-1.63/utils' gcc -g -Wall -I../driver -o loadndisdriver loadndisdriver.c make[1]: Leaving directory '/home/omar_mustafa/Downloads/ndiswrapper-1.63/utils' make -C driver make[1]: Entering directory '/home/omar_mustafa/Downloads/ndiswrapper-1.63/driver' make -C /usr/src/linux-headers-5.13.9-051309-generic M=/home/omar_mustafa/Downloads/ndiswrapper-1.63/driver make[2]: Entering directory '/usr/src/linux-headers-5.13.9-051309-generic' MKEXPORT /home/omar_mustafa/Downloads/ndiswrapper-1.63/driver/crt_exports.h CC [M] /home/omar_mustafa/Downloads/ndiswrapper-1.63/driver/crt.o MKEXPORT /home/omar_mustafa/Downloads/ndiswrapper-1.63/driver/hal_exports.h CC [M] /home/omar_mustafa/Downloads/ndiswrapper-1.63/driver/hal.o CC [M] /home/omar_mustafa/Downloads/ndiswrapper-1.63/driver/iw_ndis.o CC [M] /home/omar_mustafa/Downloads/ndiswrapper-1.63/driver/loader.o /home/omar_mustafa/Downloads/ndiswrapper-1.63/driver/loader.c: In function ‘load_sys_files’: /home/omar_mustafa/Downloads/ndiswrapper-1.63/driver/loader.c:157:4: error: too many arguments to function ‘__vmalloc’ 157 |__vmalloc(load_driver->sys_files[i].size, |^ In file included from ./include/asm-generic/io.h:911, from ./arch/x86/include/asm/io.h:375, from ./include/linux/scatterlist.h:9, from ./include/linux/dma-mapping.h:10, from ./include/linux/skbuff.h:31, from ./include/net/net_namespace.h:38, from ./include/linux/netdevice.h:37, from /home/omar_mustafa/Downloads/ndiswrapper-1.63/driver/ntoskernel.h:25, from /home/omar_mustafa/Downloads/ndiswrapper-1.63/driver/ndis.h:19, from /home/omar_mustafa/Downloads/ndiswrapper-1.63/driver/loader.c:16: ./include/linux/vmalloc.h:131:14: note: declared here 131 | extern void *__vmalloc(unsigned long size, gfp_t gfp_mask); | ^ make[3]: *** [scripts/Makefile.build:273: /home/omar_mustafa/Downloads/ndiswrapper-1.63/driver/loader.o] Error 1 make[2]: *** [Makefile:1859: /home/omar_mustafa/Downloads/ndiswrapper-1.63/driver] Error 2 make[2]: Leaving directory '/usr/src/linux-headers-5.13.9-051309-generic' make[1]: *** [Makefile:183: modules] Error 2 make[1]: Leaving directory '/home/omar_mustafa/Downloads/ndiswrapper-1.63/driver' make: *** [Makefile:23: driver] Error 2 ** Affects: ndiswrapper (Ubuntu) Importance: Undecided Status: New ** Tags: 5.13.9 ndiswrapper -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942001 Title: failure to compile on Kernel 5.13.9 Ubuntu 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/1942001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254628] Re: update-notifier crashed with SIGSEGV in rate_limiter_free()
I got this in 21.04 (hirsute) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254628 Title: update-notifier crashed with SIGSEGV in rate_limiter_free() To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1254628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778359] Re: Software Updater hangs on "Waiting for packagekitd to exit"
Still happens on 21.04. sudo systemctl stop fixes it temporarily on my system. Restarting the computer did not help by the way. Packagekitd was always starting at boot, not sure why. It works sometimes though, not much critical and can be fixed by stopping packagekitd but it always frustrates me. Maybe packagekitd should get some sort of timeout or such? Don't know much about what it does. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778359 Title: Software Updater hangs on "Waiting for packagekitd to exit" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1778359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926451] [NEW] Simply tried to install Ubuntu mate after my Manjaro wouldnt boot with a Kernel panic and pepppermint stuck at boot with a dash blinking on top left. have yet to restart my install
Public bug reported: I need help as my Ubuntu and any Linux distro ends up with some sort of error. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.19 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Wed Apr 28 17:04:09 2021 InstallCmdLine: initrd=/casper/initrd file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash --- BOOT_IMAGE=/casper/vmlinuz LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) RebootRequiredPkgs: linux-image-5.11.0-16-generic linux-base 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.19 ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926451 Title: Simply tried to install Ubuntu mate after my Manjaro wouldnt boot with a Kernel panic and pepppermint stuck at boot with a dash blinking on top left. have yet to restart my installed ubuntu with a grub install error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1926451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920676] [NEW] Ubuntu installation failed
Public bug reported: Installation just fails no matter how I partition the disk ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 21 16:59:29 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: linux-image-5.8.0-45-generic linux-base linux-image-5.8.0-25-generic linux-base SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.13 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920676 Title: Ubuntu installation failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1920676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906315] Re: apt update hangs on Turkish lang
Okey but its not include any error or detailed report I think. Its not that hard to reproduce my issue just change mirror by software- properties-gtk on Turkish lang. Or just freshly installed ubuntu 20.10 apt update. ** Attachment added: "term.log" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1906315/+attachment/5439958/+files/term.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906315 Title: apt update hangs on Turkish lang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1906315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906315] [NEW] apt update hangs on Turkish lang
Public bug reported: When I do "sudo apt update" hangs on Tr lang. I made fix it by LANG=C env but that is not really fix(!) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apt 2.1.10 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 Uname: Linux 5.8.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 1 00:49:56 2020 InstallationDate: Installed on 2020-11-30 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906315 Title: apt update hangs on Turkish lang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1906315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893454] [NEW] lvm misdetected: as root=dm-2; should be dm-0 or rhel7-root
Public bug reported: This is a problem that requires editing the grub.cfg after every update as follows: diff -r1.2 /boot/grub/grub.cfg 320c320 < linux /vmlinuz-0-rescue-094290ad3c25419d9b671b141b6ea616 root=/dev/dm-0 --- > linux /vmlinuz-0-rescue-094290ad3c25419d9b671b141b6ea616 root=/dev/dm-2 333c333 < linux /vmlinuz-0-rescue-094290ad3c25419d9b671b141b6ea616 root=/dev/dm-0 --- > linux /vmlinuz-0-rescue-094290ad3c25419d9b671b141b6ea616 > root=/dev/dm-2 345c345 < linux /vmlinuz-3.10.0-862.3.2.el7.x86_64 root=/dev/dm-0 --- > linux /vmlinuz-3.10.0-862.3.2.el7.x86_64 root=/dev/dm-2 The target kernel expects to find the root filesystem on dm-0, also known as rhel_smt2-root, not on dm-2. However, Ubuntu kernel numbers the dm-* devices differently, as follows: mu@mu-HP-Z620-Workstation:~/Desktop Fri Aug 28 11:39:11 1 1 $ sudo dmsetup ls 200828_113958 rhel_smt2-swap (253:4) rhel_smt2-root (253:2) vgubuntu-root (253:0) vgubuntu-swap_1 (253:1) rhel_smt2-home (253:3) mu@mu-HP-Z620-Workstation:~/Desktop Fri Aug 28 11:39:58 1 0 $ ls -l /dev/dm-* 200828_114013 brw-rw 1 root disk 253, 0 Aug 28 10:30 /dev/dm-0 brw-rw 1 root disk 253, 1 Aug 28 10:30 /dev/dm-1 brw-rw 1 root disk 253, 2 Aug 28 10:30 /dev/dm-2 brw-rw 1 root disk 253, 3 Aug 28 10:30 /dev/dm-3 brw-rw 1 root disk 253, 4 Aug 28 10:30 /dev/dm-4 That is, the dm- minor device numbering differs. Symptom: The boot menuentry breaks whenever os-update is called, practically after every new kernel update, and rhel7 becomes unbootable. Suggested workaround: Use the OS-defined name, rhel_smt2-root, instead of dm-2 in the root= parameter. Reverse lookup of minor device number in the first table gives the OS name. ** Affects: os-prober (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/1893454 Title: lvm misdetected: as root=dm-2; should be dm-0 or rhel7-root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1893454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881844] [NEW] ubiquity crash installing release in free space on internal nvme disk alongside windows
Public bug reported: Crash occurred after selecting to install release on /dev/nvme0n1 in space left over after shrinking windows after fresh windows install. Size of free space is 127 GiB, i.e, half of the nvme. After crash, name of free space changed to /dev/nvme0n1p5 in dick utility. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 3 00:06:46 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed quiet splash --- InstallationDate: Installed on 2020-01-20 (134 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: Upgraded to focal on 2020-01-20 (134 days ago) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-19.10.21 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881844 Title: ubiquity crash installing release in free space on internal nvme disk alongside windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1881844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871670] Re: cnf-update-db crashed with sqlite3.OperationalError in create(): database is locked
Same problems still go on.. please be aware i like to work with ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871670 Title: cnf-update-db crashed with sqlite3.OperationalError in create(): database is locked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1871670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871670] Re: cnf-update-db crashed with sqlite3.OperationalError in create(): database is locked
Dear Guys, Same problem for my other computer which i try to load it. But i should say that i am a new user of UBUNTU since 20 days. After 18.04 this is marvellous it will be better i believe. But same problem. İ think something like loading files. Anyway Good luck -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871670 Title: cnf-update-db crashed with sqlite3.OperationalError in create(): database is locked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1871670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871670] Re: cnf-update-db crashed with sqlite3.OperationalError in create(): database is locked
My first machine i did it with remove and reinstall but now i can not solve yet i think. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871670 Title: cnf-update-db crashed with sqlite3.OperationalError in create(): database is locked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1871670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839353] Re: Login screen and desktop corruption (18.04.2)
installed Unity Desktop and no desktop/login/lock screen corruption happening on the laptop with no external monitor. but On Screen indicator symbols dont work (example screenshot for on screen indicators: https://launchpadlibrarian.net/424611485/Screenshot%20from%202019-05-20%2023-32-46.png) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839353 Title: Login screen and desktop corruption (18.04.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1839353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839353] Re: Login screen and desktop corruption (18.04.2)
9 years ago similar problems have been reported as well >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/541501 it seems it is ATI driver problem more than being old machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839353 Title: Login screen and desktop corruption (18.04.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1839353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839353] Re: Login screen and desktop corruption (18.04.2)
another issue that on dock, icons getting cut as you see in attached screenshot in "Text Editor" and "Show Applications" icons, half is cut. it is happening randomly to other icons too. ** Attachment added: "corrupted dock icons" https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1839353/+attachment/5281822/+files/dock%20icons.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839353 Title: Login screen and desktop corruption (18.04.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1839353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839353] Re: Login screen and desktop corruption (18.04.2)
Ubuntu 18.04.2-64bit i noticed that wallpaper corruption is happening mostly in ubuntu official wallpapers such as purple disco dingo wallpaper. when i change to standard wallpapers like a photograph corruption not happening. Lock screen is also corrupting same as default wallpaper (related screenshot is in attachment) Additionally ubuntu-gnome default on screen indicator symbols such as volume control dont appear. ** Attachment added: "lock screen corruption-18.04.2" https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1839353/+attachment/5281775/+files/IMG_8093.JPG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839353 Title: Login screen and desktop corruption (18.04.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1839353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839353] Re: Login screen and desktop corruption (18.04.2)
** Attachment added: "disco-dingo official wallpaper corruption on 18.04.2" https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1839353/+attachment/5281776/+files/Screenshot%20from%202019-08-09%2016-58-33.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839353 Title: Login screen and desktop corruption (18.04.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1839353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839353] Re: Login screen and desktop corruption (18.04.2)
OK. recent update is this, i re-installed 18.04 and when i first booted after installation desktop wallpaper was corrupted again. then i changed desktop wallpaper and there was no corruption. i installed mesa drivers, some codecs and rebooted again. then same thing happened that desktop wallpaper corrupted. then i changed wallpaper again. something is corrupting desktop and login screen i guess. i have transparent effects at top bar and dock. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839353 Title: Login screen and desktop corruption (18.04.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1839353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839353] Re: Login screen and desktop corruption (18.04.2)
screen flickering and login screen corruption problem with docking station and external monitor still exists. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839353 Title: Login screen and desktop corruption (18.04.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1839353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839353] Re: Login screen and desktop corruption (18.04.2)
** Attachment added: "screen flickering screenshot" https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1839353/+attachment/5281611/+files/IMG_8080.JPG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839353 Title: Login screen and desktop corruption (18.04.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1839353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839353] Re: Login screen and desktop corruption (18.04.2)
installed Unity desktop to 19.04 and LightDM for login screen and no more screen corruption on login screen after installed lightdm and unity desktop but still there is no transparent effects. top bar at desktop and terminal interface is white. screen flickering continuing on docking station attached to external monitor.(attached via DVI Port) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839353 Title: Login screen and desktop corruption (18.04.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1839353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839353] Re: Login screen and desktop corruption (18.04.2)
Login screen corruption and screen flickering as in the screenshot: https://launchpadlibrarian.net/436378920/file-3.jpeg is happening while on docking station attached to external monitor (Lenovo ThinkVision LT2252p) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839353 Title: Login screen and desktop corruption (18.04.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1839353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839353] Re: Login screen and desktop corruption (18.04.2)
another issue, sound is too low even i enabled Over-Amplification. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839353 Title: Login screen and desktop corruption (18.04.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1839353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839353] Re: Login screen and desktop corruption (18.04.2)
Fresh installed Ubuntu 19.04. setup gone fine. no login or boot screen corruption. just at first time logged in there was corruption on desktop same as i faced 18.04. after i ran "sudo apt update && sudo apt full- upgrade" and rebooted, desktop is fine. but there is no transparent effects on top bar and dock, just black background. also noticed that i cant watch Netflix. Firefox version is 68.0.1 which most recent version in Ubuntu and suppose to play movies in Netflix. i am getting Error Code: F7111-1331. cant play videos on other html5 based website. just youtube working fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839353 Title: Login screen and desktop corruption (18.04.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1839353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839353] Re: Login screen and desktop corruption (18.04.2)
recent update. i am on now Ubuntu 19.04 Live USB. Kernel: Linux ubuntu 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux no screen corruption at desktop or login screen. everything seems fine. Ubuntu 19.04 Device name: ubuntu Memory: 2.9 GiB Processor: Intel Core2 CPU T7200 @ 2.00GHzx2 Graphics: ATI RV515 GNOME: 3.32.1 OS type: 64-bit Disk: 240.1 GB -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839353 Title: Login screen and desktop corruption (18.04.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1839353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839353] Re: Login screen and desktop corruption (18.04.2)
just to mention kernel version on 16.04 live usb is : Linux ubuntu 4.15.0-45-generic #48~16.04.1-Ubuntu SMP Tue Jan 29 18:03:48 UTC 2019 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/1839353 Title: Login screen and desktop corruption (18.04.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1839353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839353] Re: Login screen and desktop corruption (18.04.2)
i am now typing on Ubuntu 16.04.6 Live USB and there is no screen corruption or flickering. it seems to be working fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839353 Title: Login screen and desktop corruption (18.04.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1839353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839353] Re: Login screen and desktop corruption (18.04.2)
** Attachment added: "corrupted ubuntu boot-login screenshot" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1839353/+attachment/5281457/+files/file-3.jpeg ** Description changed: Device: Lenovo/IBM ThinkPad T60 CPU: Intel Core2 Duo T7200 (upgraded from T2400) Graphics: ATI Mobility Radeon X1300 RAM: 2x2GB Samsung PC2-6400S Harddisk: Intel 730 Series SSD 240GB Ubuntu version: 18.04.2 Kernel: 5.0.0.23 i recently upgraded CPU from T2400 to T7200 to have 64-bit support to be able to install Ubuntu 18.04 64-bit. after fresh install i got very laggy login and no ubuntu boot loading screen, very corrupted login screen that user name and other informations were not visible and i typed password without seeing password box, then corrupted desktop. i ran "sudo apt update && sudo apt full-upgrade" to check if it s driver or update issue but problem is continuing. i also tested kernel 4.18.0-15 and 5.3.0-.50300rc3 but still same problem. - i know laptop is too old but i wanted to try. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-23-generic 5.0.0-23.24~18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 19:10:54 2019 InstallationDate: Installed on 2019-08-07 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839353 Title: Login screen and desktop corruption (18.04.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1839353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839353] Re: Login screen and desktop corruption (18.04.2)
:~$ dmesg [0.00] microcode: microcode updated early to revision 0xd1, date = 2010-10-01 [0.00] Linux version 5.0.0-23-generic (buildd@lgw01-amd64-030) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 (Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=ec11e16f-fc16-42ca-b66c-b5e912c05b98 ro quiet splash vt.handoff=1 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] x86/fpu: x87 FPU will use FXSAVE [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009efff] usable [0.00] BIOS-e820: [mem 0x0009f000-0x0009] reserved [0.00] BIOS-e820: [mem 0x000d2000-0x000d3fff] reserved [0.00] BIOS-e820: [mem 0x000dc000-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xbfec] usable [0.00] BIOS-e820: [mem 0xbfed-0xbfedefff] ACPI data [0.00] BIOS-e820: [mem 0xbfedf000-0xbfef] ACPI NVS [0.00] BIOS-e820: [mem 0xbff0-0xbfff] reserved [0.00] BIOS-e820: [mem 0xf000-0xf3ff] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec0] reserved [0.00] BIOS-e820: [mem 0xfed0-0xfed003ff] reserved [0.00] BIOS-e820: [mem 0xfed14000-0xfed19fff] reserved [0.00] BIOS-e820: [mem 0xfed1c000-0xfed8] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xff80-0x] reserved [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.4 present. [0.00] DMI: LENOVO 2007ZX9/2007ZX9, BIOS 79ETE7WW (2.27 ) 03/21/2011 [0.00] tsc: Fast TSC calibration using PIT [0.00] tsc: Detected 1994.866 MHz processor [0.033119] e820: update [mem 0x-0x0fff] usable ==> reserved [0.033124] e820: remove [mem 0x000a-0x000f] usable [0.033140] last_pfn = 0xbfed0 max_arch_pfn = 0x4 [0.033153] MTRR default type: uncachable [0.033156] MTRR fixed ranges enabled: [0.033159] 0-9 write-back [0.033162] A-B uncachable [0.033165] C-C write-protect [0.033167] D-DBFFF uncachable [0.033169] DC000-D write-back [0.033172] E-F write-protect [0.033174] MTRR variable ranges enabled: [0.033178] 0 base 0 mask F8000 write-back [0.033181] 1 base 08000 mask FC000 write-back [0.033185] 2 base 0BFF0 mask 0 uncachable [0.033186] 3 disabled [0.033188] 4 disabled [0.033190] 5 disabled [0.033191] 6 disabled [0.033193] 7 disabled [0.035199] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [0.035400] total RAM covered: 3071M [0.036286] Found optimal setting for mtrr clean up [0.036289] gran_size: 64K chunk_size: 2M num_reg: 3 lose cover RAM: 0G [0.056348] found SMP MP-table at [mem 0x000f6810-0x000f681f] [0.062868] check: Scanning 1 areas for low memory corruption [0.062882] BRK [0x71c01000, 0x71c01fff] PGTABLE [0.062887] BRK [0x71c02000, 0x71c02fff] PGTABLE [0.062891] BRK [0x71c03000, 0x71c03fff] PGTABLE [0.062997] BRK [0x71c04000, 0x71c04fff] PGTABLE [0.063003] BRK [0x71c05000, 0x71c05fff] PGTABLE [0.063488] BRK [0x71c06000, 0x71c06fff] PGTABLE [0.063612] RAMDISK: [mem 0x9000-0x35993fff] [0.063633] ACPI: Early table checksum verification disabled [0.063804] ACPI: RSDP 0x000F67E0 24 (v02 LENOVO) [0.063813] ACPI: XSDT 0xBFED1322 94 (v01 LENOVO TP-79 2270 LTP ) [0.063828] ACPI: FACP 0xBFED1400 F4 (v03 LENOVO TP-79 2270 LNVO 0001) [0.063839] ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block: 64/32 (20181213/tbfadt-569) [0.063846] ACPI BIOS Warning (bug): Optional FADT field Gpe1Block has valid Address but zero Length: 0x102C/0x0 (20181213/tbfadt-624) [0.063858] ACPI: DSDT 0xBFED175E 00D467 (v01 LENOVO TP-79 2270 MSFT 010E) [0.063868] ACPI: FACS 0xBFEF4000 40 [0.063876] ACPI: FACS 0xBFEF4000 40 [0.063884] ACPI: SSDT 0xBFED15B4 0001AA (v01 LENOVO TP-79 2270 MSFT 010E) [0.063893] ACPI: ECDT 0xBFEDEBC5 52 (v01 LENOVO TP-79 2270 LNVO 0001) [0.063903] ACPI: TCPA 0xBFEDEC17 32 (v02 LENOVO TP-79 2270 LNVO 0001) [0.063912] ACPI: APIC 0xBFEDEC49 68 (v01 LENOVO TP-79
[Bug 1839353] [NEW] Login screen and desktop corruption (18.04.2)
Public bug reported: Device: Lenovo/IBM ThinkPad T60 CPU: Intel Core2 Duo T7200 (upgraded from T2400) Graphics: ATI Mobility Radeon X1300 RAM: 2x2GB Samsung PC2-6400S Harddisk: Intel 730 Series SSD 240GB Ubuntu version: 18.04.2 Kernel: 5.0.0.23 i recently upgraded CPU from T2400 to T7200 to have 64-bit support to be able to install Ubuntu 18.04 64-bit. after fresh install i got very laggy login and no ubuntu boot loading screen, very corrupted login screen that user name and other informations were not visible and i typed password without seeing password box, then corrupted desktop. i ran "sudo apt update && sudo apt full-upgrade" to check if it s driver or update issue but problem is continuing. i also tested kernel 4.18.0-15 and 5.3.0-.50300rc3 but still same problem. i know laptop is too old but i wanted to try. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-23-generic 5.0.0-23.24~18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 19:10:54 2019 InstallationDate: Installed on 2019-08-07 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "corrupted desktop" https://bugs.launchpad.net/bugs/1839353/+attachment/5281445/+files/Screenshot%20from%202019-08-07%2018-16-08.png ** Description changed: Device: Lenovo/IBM ThinkPad T60 CPU: Intel Core2 Duo T7200 (upgraded from T2400) Graphics: ATI Mobility Radeon X1300 RAM: 2x2GB Samsung PC2-6400S Harddisk: Intel 730 Series SSD 240GB Ubuntu version: 18.04.2 Kernel: 5.0.0.23 i recently upgraded CPU from T2400 to T7200 to have 64-bit support to be able to install Ubuntu 18.04 64-bit. after fresh install i got very laggy login and no ubuntu boot loading screen, very corrupted login - screen that user name and other informations were not visible, then - corrupted desktop. i ran "sudo apt update && sudo apt full-upgrade" to - check if it s driver or update issue but problem is continuing. i also - tested kernel 4.18.0-15 and 5.3.0-.50300rc3 but still same problem. + screen that user name and other informations were not visible and i + typed password without seeing password box, then corrupted desktop. i + ran "sudo apt update && sudo apt full-upgrade" to check if it s driver + or update issue but problem is continuing. i also tested kernel + 4.18.0-15 and 5.3.0-.50300rc3 but still same problem. i know laptop is too old but i wanted to try. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-23-generic 5.0.0-23.24~18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 19:10:54 2019 InstallationDate: Installed on 2019-08-07 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839353 Title: Login screen and desktop corruption (18.04.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1839353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787974] Re: Fingerprint authentication not available in 18.04
just to clarify i tested on ThinkPad T400, and fingerprint reader device ID: Bus 004 Device 002: ID 08ff:2810 AuthenTec, Inc. AES2810 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787974 Title: Fingerprint authentication not available in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1787974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787974] Re: Fingerprint authentication not available in 18.04
i tried on Ubuntu 18.04.2 > "sudo apt install -y fprintd libpam-fprintd" and "sudo pam-auth-update" on my ThinkPad T400 (a bit old laptop) device info: Bus 004 Device 002: ID 08ff:2810 AuthenTec, Inc. AES2810 but it doesnt work. in Users>Settings when i try to enable and choose finger to enroll it gets freeze and causes fingerprint reader get extremely hot. i had to quit the setting when it happened and remove "fprintd" and "libpam-fprintd" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787974 Title: Fingerprint authentication not available in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1787974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829651] Re: Caps Lock status notifications
hi Sebastien, i posted issue in there as you suggested me: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1306 but it is annoying that there is no default "Caps Lock" notification/indicator on screen. dont you think so? some laptops or keyboards dont have led indicator physically like mine. and 3rd party apps for caps lock really dont suit with default notifications. thanks. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1306 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1306 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829651 Title: Caps Lock status notifications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829651] Re: Caps Lock indicator on screen
@Sebastien Bacher, another screenshot of "Volume mute" attached. Caps Lock indicator also should be "on screen" looks like other indicators. not on top bar or anywhere else. for example when Caps Lock is on bright white A logo in the box, and when Caps Lock is off gray crossed A looks like the volume mute indicator in the box. you can add settings like to do it permanent on screen when Caps Lock is ON and temporary when it is OFF or both can be visible permanent on screen. those can be optional in my suggestion. as a suggestion maybe you can put Num Lock and Scroll Lock indicators as well. thank you all in advance for your hard works and contributions to make Ubuntu the best. ** Attachment added: "Volume mute indicator" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+attachment/5265129/+files/Screenshot%20from%202019-05-20%2023-32-51.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829651 Title: Caps Lock indicator on screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829651] Re: Caps Lock indicator on screen
Hi. i am expecting a Caps Lock indicator by default (without need of usage any 3rd party app which are not working proper tested few) like the screenshot of Volume indicator as an example i attached. thanks. ** Attachment added: "example - Volume indicator on screen" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+attachment/5265128/+files/Screenshot%20from%202019-05-20%2023-32-46.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829651 Title: Caps Lock indicator on screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734887] Re: No caps lock indicator on login screen
i am currently using Lenovo ThinkPad x230 which doesnt have physical caps lock indicator on keyboard like some other ThinkPad laptops. i noticed that on Ubuntu 18.04.2 there is no Caps Lock indicator on screen. it would be perfect if you put it default as other on screen indicators such as volume controls, microphone indicator, screen brightness indicator. thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734887 Title: No caps lock indicator on login screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1734887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829651] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1829651/+attachment/5264768/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829651 Title: Caps Lock indicator on screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829651] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1829651/+attachment/5264766/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829651 Title: Caps Lock indicator on screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829651] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1829651/+attachment/5264767/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829651 Title: Caps Lock indicator on screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829651] Re: Caps Lock indicator on screen
apport information ** Package changed: powernap (Ubuntu) => gnome-shell (Ubuntu) ** Tags added: apport-collected bionic ** Description changed: - this is suggestion more than a bug report. ubuntu has default cool on - screen indicators for volume control, display brightness ..ie. but there - is no Caps Lock on screen indicator by default. i am currently using - Lenovo ThinkPad X230 and unfortunately there is no led indicator light - on the keyboard for caps lock. could you please consider putting caps - lock on screen indicator by default to ubuntu? it would be cool if you - could. thanks. + this is suggestion more than a bug report. ubuntu has default cool on screen indicators for volume control, display brightness ..ie. but there is no Caps Lock on screen indicator by default. i am currently using Lenovo ThinkPad X230 and unfortunately there is no led indicator light on the keyboard for caps lock. could you please consider putting caps lock on screen indicator by default to ubuntu? it would be cool if you could. thanks. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.6 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-05-14 (4 days ago) + InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) + Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 + Tags: bionic + Uname: Linux 4.18.0-20-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1829651/+attachment/5264765/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829651 Title: Caps Lock indicator on screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829651] [NEW] Caps Lock indicator on screen
Public bug reported: this is suggestion more than a bug report. ubuntu has default cool on screen indicators for volume control, display brightness ..ie. but there is no Caps Lock on screen indicator by default. i am currently using Lenovo ThinkPad X230 and unfortunately there is no led indicator light on the keyboard for caps lock. could you please consider putting caps lock on screen indicator by default to ubuntu? it would be cool if you could. thanks. ** Affects: powernap (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/1829651 Title: Caps Lock indicator on screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powernap/+bug/1829651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809110] [NEW] Intel drivers
Public bug reported: i wanna see if it helps with setting up vagrant ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None Date: Wed Dec 19 14:33:31 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f] Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f] InstallationDate: Installed on 2018-01-28 (324 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. OptiPlex 760 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=7dde6342-329e-4620-8e17-2e953c29f852 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0M858N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd02/18/2009:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0M858N:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 760 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809110 Title: Intel drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1809110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
In the Live Version on MacBook Pro 2015 (13 inches, Retina) I changed the 'Screen Scale' from 200% to 100%, settings > Device > Display, and solved! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751252 Title: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: '' To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1751252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767874] Re: ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
*** This bug is a duplicate of bug 1751252 *** https://bugs.launchpad.net/bugs/1751252 In the Live Version on MacBook Pro 2015 (13 inches, Retina) I changed the 'Screen Scale' from 200% to 100%, settings > Device > Display, and solved -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767874 Title: ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: '' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767874] Re: ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
*** This bug is a duplicate of bug 1751252 *** https://bugs.launchpad.net/bugs/1751252 For Installing ubuntu 18.04 on MacBook Pro 2015, I have this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767874 Title: ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: '' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 977228] Re: gnome-screenshot forgets "last-save-directory"
Still present in Ubuntu 16.04. It only remembers last-save-directory when gnome-screenshot is running interactively. But when I press shift + prnt scr shortcut it forgets the last-save-directory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/977228 Title: gnome-screenshot forgets "last-save-directory" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screenshot/+bug/977228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579548] Re: OTR plugin does not load in Xenial
Still have the same bug. Is this going to be patched? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579548 Title: OTR plugin does not load in Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irssi-plugin-otr/+bug/1579548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800279] Re: microphone bar is changing the connected phone's song volume.
this is the first time im reporting anybug i like ubuntu and you all feel free to contact me about this bug, Contact number : +923444966706 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800279 Title: microphone bar is changing the connected phone's song volume. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1800279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800279] [NEW] microphone bar is changing the connected phone's song volume.
Public bug reported: ive connected my computer with my iPhone 5s running lated ios12 and problem im facing is that ive connected the bluetooth of iPhone with ubuntu (just a direct connect not any thirdparty software ) and after connection when im playing a song on iphone it broadcasting it to ubuntu, the problem is that when i open drop down menu of Wifi/Bluetooth/Power menu from top right corner and change the microphone it changes the sound quantity and quality , but changing the volume bar changing volume of song in a manificient way rather than changing microphpone who is ruining the quality, and it is not supposed to change it :| ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 27 15:37:21 2018 InstallationDate: Installed on 2018-10-10 (16 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 3542 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=688940ab-691d-4fec-9fec-0f5d4c316bde ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0DXYP6 dmi.board.vendor: Dell Inc. dmi.board.version: A14 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0DXYP6:rvrA14:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3542 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 9C:AD:97:15:3E:52 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:22188568 acl:36355 sco:0 events:1564 errors:0 TX bytes:51481 acl:454 sco:0 commands:341 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Kazam_screenshot_0.png" https://bugs.launchpad.net/bugs/1800279/+attachment/5206179/+files/Kazam_screenshot_0.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800279 Title: microphone bar is changing the connected phone's song volume. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1800279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
My ubuntu 16.04 has affected but #77 fixed it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606365 Title: unable to import config with inlined ca, cert, key or tls-auth To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/606365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787485] [NEW] Cannot complete installation of 18.04.1
Public bug reported: 'grub-efi-amd64-signed' package failed to install into /target/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 16:33:27 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash oem-config/enable=true --- LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787485 Title: Cannot complete installation of 18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1787485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1777204] package linux-image-4.15.0-23-lowlatency (not installed) failed to install/upgrade: installed linux-image-4.15.0-23-lowlatency package pre-removal script subprocess returned error ex
Thanks for responding. I think this report was triggered by a new linux image installation failing because of lack of space in the /boot partition. A re-install, using aptitude, after removing old kernels, had already resolved the issue before submitting the report. The report was auto generated after a reboot. I filled and it as appropriate, then realized it was a duplicate. It is a non-bug as such and may be closed :). Best regards, Mustafa > On Jun 19, 2018, at 9:09 AM, Joseph Salisbury > wrote: > > You may need to run the following from a terminal: > > sudo apt-get install -f > sudo apt-get clean > sudo apt-get update > > Then re-install the package or updates. > > If that does not resolve your issue, please mark the bug as "Confirmed" > > ** Changed in: linux (Ubuntu) > Importance: Undecided => Low > > ** Changed in: linux (Ubuntu) > Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1777204 > > Title: > package linux-image-4.15.0-23-lowlatency (not installed) failed to > install/upgrade: installed linux-image-4.15.0-23-lowlatency package > pre-removal script subprocess returned error exit status 1 > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Known bug, worked around by removing old kernels. > > ProblemType: Package > DistroRelease: Ubuntu 18.10 > Package: linux-image-4.15.0-23-lowlatency (not installed) > ProcVersionSignature: Ubuntu 4.15.0-24.26-lowlatency 4.15.18 > Uname: Linux 4.15.0-24-lowlatency x86_64 > ApportVersion: 2.20.10-0ubuntu3 > Architecture: amd64 > AudioDevicesInUse: > USERPID ACCESS COMMAND > /dev/snd/controlC0: gdm2193 F pulseaudio >mlthost2767 F pulseaudio > Date: Fri Jun 15 19:32:44 2018 > ErrorMessage: installed linux-image-4.15.0-23-lowlatency package pre-removal > script subprocess returned error exit status 1 > HibernationDevice: RESUME=UUID=8fe6b1c9-1cbd-491d-b1fb-28cb0310bbe4 > InstallationDate: Installed on 2017-07-18 (332 days ago) > InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 > (20170215.2) > Lsusb: > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 004: ID 8087:0a2b Intel Corp. > Bus 001 Device 003: ID 413c:2113 Dell Computer Corp. > Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: Dell Inc. OptiPlex 5050 > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-lowlatency > root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > Python3Details: /usr/bin/python3.6, Python 3.6.6rc1, python3-minimal, 3.6.5-3 > PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3 > RelatedPackageVersions: grub-pc 2.02-2ubuntu10 > SourcePackage: linux > Title: package linux-image-4.15.0-23-lowlatency (not installed) failed to > install/upgrade: installed linux-image-4.15.0-23-lowlatency package > pre-removal script subprocess returned error exit status 1 > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 05/06/2017 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.3.11 > dmi.board.name: 0782GW > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 3 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr1.3.11:bd05/06/2017:svnDellInc.:pnOptiPlex5050:pvr:rvnDellInc.:rn0782GW:rvrA00:cvnDellInc.:ct3:cvr: > dmi.product.family: OptiPlex > dmi.product.name: OptiPlex 5050 > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777204/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777204 Title: package linux-image-4.15.0-23-lowlatency (not installed) failed to install/upgrade: installed linux-image-4.15.0-23-lowlatency package pre-removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777204] [NEW] package linux-image-4.15.0-23-lowlatency (not installed) failed to install/upgrade: installed linux-image-4.15.0-23-lowlatency package pre-removal script subprocess returned error
Public bug reported: Known bug, worked around by removing old kernels. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: linux-image-4.15.0-23-lowlatency (not installed) ProcVersionSignature: Ubuntu 4.15.0-24.26-lowlatency 4.15.18 Uname: Linux 4.15.0-24-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2193 F pulseaudio mlthost2767 F pulseaudio Date: Fri Jun 15 19:32:44 2018 ErrorMessage: installed linux-image-4.15.0-23-lowlatency package pre-removal script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=8fe6b1c9-1cbd-491d-b1fb-28cb0310bbe4 InstallationDate: Installed on 2017-07-18 (332 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 413c:2113 Dell Computer Corp. Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 5050 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-lowlatency root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.6rc1, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3 RelatedPackageVersions: grub-pc 2.02-2ubuntu10 SourcePackage: linux Title: package linux-image-4.15.0-23-lowlatency (not installed) failed to install/upgrade: installed linux-image-4.15.0-23-lowlatency package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.11 dmi.board.name: 0782GW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.11:bd05/06/2017:svnDellInc.:pnOptiPlex5050:pvr:rvnDellInc.:rn0782GW:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 5050 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777204 Title: package linux-image-4.15.0-23-lowlatency (not installed) failed to install/upgrade: installed linux-image-4.15.0-23-lowlatency package pre-removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1773575] Re: dual vga
yes it solved my problem thanks alot i could not find such a solution online. you saved my day On Sun, May 27, 2018 at 8:34 AM, Christopher M. Penalver < christopher.m.penal...@gmail.com> wrote: > mustafa: > > 1) Regarding crash files, you would not want to attach them, as they may > contain sensitive information you don't want to reveal publicly. > > Instead, one may report them in a privacy respectful way via a terminal: > ubuntu-bug /var/crash/FILENAME.crash > > where FILENAME is the name of the crash file. > > 2) It is advised to immediately back up your data (config files, list of > what apps you have installed, etc.), so that in the event of a disaster > (hardware failure, OS stops working entirely, etc.) you may perform a > clean install and bring the OS back to the desired state. Stating "i do > not want to lose my server configuration and reinstall Ubuntu and all > the configuration and apps that i used" doesn't mean you won't have to > do it. This is a matter of how prepared are you if you must. > > 3) Post the results of the following terminal command: > history > > 4) To confirm a WORKAROUND, if you install the package gnome-session- > flashback and login to GNOME (Metacity), does this allow you to use the > GUI again? > > ** Attachment removed: "_usr_lib_x86_64-linux-gnu_ > unity_compiz-config-profile-setter.1000_copy.crash" >https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/ > 1773575/+attachment/5145036/+files/_usr_lib_x86_64-linux- > gnu_unity_compiz-config-profile-setter.1000_copy.crash > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1773575 > > Title: > dual vga > > Status in xorg package in Ubuntu: > Incomplete > > Bug description: > i have a laptop dell which has two vga one from intel and the other > one is amd. i tried to update the drivers in one way or another every > thing stoped and i can not use the gui anymore > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: xorg 1:7.7+13ubuntu3 > ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 > Uname: Linux 4.13.0-43-generic x86_64 > .tmp.unity_support_test.1: > > ApportVersion: 2.20.1-0ubuntu2.17 > Architecture: amd64 > CompizPlugins: No value set for `/apps/compiz-1/general/ > screen0/options/active_plugins' > CompositorRunning: None > Date: Sat May 26 22:00:13 2018 > DistUpgraded: Fresh install > DistroCodename: xenial > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, including running git bisection searches > GraphicsCard: >Intel Corporation 3rd Gen Core processor Graphics Controller > [8086:0166] (rev 09) (prog-if 00 [VGA controller]) > Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:05b8] >Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] > [1002:6601] (rev ff) (prog-if ff) > InstallationDate: Installed on 2018-01-10 (136 days ago) > InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 > (20170801) > MachineType: Dell Inc. Inspiron 5521 > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic > root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > Xrandr: Screen 0: minimum 0 x 0, current 3600 x 1080, maximum 4096 x 4096 > dmi.bios.date: 07/31/2015 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A14 > dmi.board.name: 0C46Y8 > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 8 > dmi.chassis.vendor: Dell Inc. > dmi.chassis.version: A14 > dmi.modalias: dmi:bvnDellInc.:bvrA14:bd07/31/2015:svnDellInc.: > pnInspiron5521:pvrA14:rvnDellInc.:rn0C46Y8:rvrA00:cvnDellInc.:ct8:cvrA14: > dmi.product.family: 103C_5335KV > dmi.product.name: Inspiron 5521 > dmi.product.version: A14 > dmi.sys.vendor: Dell Inc. > version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 > version.ia32-libs: ia32-libs N/A > version.libdrm2: libdrm2 2.4.83-1~16.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 > version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A > version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.10.1-1ubuntu2 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20160325-1ubuntu1.2 > version.xserver-xorg-vide
Re: [Bug 1773575] Re: dual vga
i tried all the possibilities that i found online even to install invidia because they told me that there might help installing some important files. now it doesn't allow me to use the GUI i can use only command line. i tried many ways to restore the original drivers but i could not restore them. in windows there is something called soft system reset which reinstall the system basic files and drivers which i could not find it on ubuntu, because i do not want to lose my server configuration and reinstall Ubuntu and all the configuration and apps that i used. so if there is any future from the command line to restore the drivers or the basic files of the system without damaging my web server it would be helpful please. it might not be a bug but i can see it as bug because i tried to remove the new installed drivers and though i can not use the gui and it gives me error when i try to login with my user and pass. Could you please advise what you did precisely, in a keyboard click-for-click fashion? concerning this question i can not give you an answer because i tried many things and now i can not remember them . i tired to install amd drivers and intel and something from invidia and then tried to remove them all but the gui still give me error when i try to login . in my crash i can find the following / in the attachment/ i could not understand all the things inside the crash file thanks for the great job that you and the team doing and i hope that you can help me to solve this problem. greetings On Sun, May 27, 2018 at 7:20 AM, Christopher M. Penalver < christopher.m.penal...@gmail.com> wrote: > mustafa, thank you for reporting this and helping make Ubuntu better. > > 1) Regarding your Bug Description: > >"i tried to update the drivers in one way or another..." > > This is not enough information. Could you please advise what you did > precisely, in a keyboard click-for-click fashion? > > 2) Are there any crash files in the /var/crash folder? > > 3) As per your logs, you install unsupported software (PPA) and have > installed the nvidia proprietary drivers when you don't have a nvidia > card installed. Hence, after removing all PPAs and the nvidia drivers, > and rebooting does this allow you to use the GUI? > > ** Tags added: latest-bios-a14 > > ** Changed in: xorg (Ubuntu) >Importance: Undecided => Low > > ** Changed in: xorg (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1773575 > > Title: > dual vga > > Status in xorg package in Ubuntu: > Incomplete > > Bug description: > i have a laptop dell which has two vga one from intel and the other > one is amd. i tried to update the drivers in one way or another every > thing stoped and i can not use the gui anymore > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: xorg 1:7.7+13ubuntu3 > ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 > Uname: Linux 4.13.0-43-generic x86_64 > .tmp.unity_support_test.1: > > ApportVersion: 2.20.1-0ubuntu2.17 > Architecture: amd64 > CompizPlugins: No value set for `/apps/compiz-1/general/ > screen0/options/active_plugins' > CompositorRunning: None > Date: Sat May 26 22:00:13 2018 > DistUpgraded: Fresh install > DistroCodename: xenial > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, including running git bisection searches > GraphicsCard: >Intel Corporation 3rd Gen Core processor Graphics Controller > [8086:0166] (rev 09) (prog-if 00 [VGA controller]) > Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:05b8] >Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] > [1002:6601] (rev ff) (prog-if ff) > InstallationDate: Installed on 2018-01-10 (136 days ago) > InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 > (20170801) > MachineType: Dell Inc. Inspiron 5521 > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic > root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > Xrandr: Screen 0: minimum 0 x 0, current 3600 x 1080, maximum 4096 x 4096 > dmi.bios.date: 07/31/2015 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A14 > dmi.board.name: 0C46Y8 > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 8 > dmi.chassis.vendor: Dell Inc. > dmi.chassis.version: A14 > dmi.modalias: dmi:bvnDellInc.:bvrA14:bd07/31/2015:svnDellInc.: > pnInspiron5521:pvrA14:rvnDellInc.:rn0C46Y8:rvrA00:cvnDellInc.:ct8:cvrA14: > dmi.product.family: 103C
[Bug 1773575] [NEW] dual vga
Public bug reported: i have a laptop dell which has two vga one from intel and the other one is amd. i tried to update the drivers in one way or another every thing stoped and i can not use the gui anymore ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat May 26 22:00:13 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:05b8] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] (rev ff) (prog-if ff) InstallationDate: Installed on 2018-01-10 (136 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Inspiron 5521 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) Xrandr: Screen 0: minimum 0 x 0, current 3600 x 1080, maximum 4096 x 4096 dmi.bios.date: 07/31/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0C46Y8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A14 dmi.modalias: dmi:bvnDellInc.:bvrA14:bd07/31/2015:svnDellInc.:pnInspiron5521:pvrA14:rvnDellInc.:rn0C46Y8:rvrA00:cvnDellInc.:ct8:cvrA14: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 5521 dmi.product.version: A14 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue May 22 09:07:33 2018 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 927 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug possible-manual-nvidia-install third-party-packages 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/1773575 Title: dual vga To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641290] Re: [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised
Hi @Igor, I restarted and the reader does recover, but I run into the same issue as before when I try to re-enroll: Here's the log: = ╰─$ sudo examples/enroll This program will enroll your right index finger, unconditionally overwriting any right-index print that was enrolled previously. If you want to continue, press enter, otherwise hit Ctrl+C fp:debug [fp_init] fp:debug [register_driver] registered driver upekts fp:debug [register_driver] registered driver aes3500 fp:debug [register_driver] registered driver aes4000 fp:debug [register_driver] registered driver aes2501 fp:debug [register_driver] registered driver aes2550 fp:debug [register_driver] registered driver uru4000 fp:debug [register_driver] registered driver vcom5s fp:debug [register_driver] registered driver upeksonly fp:debug [register_driver] registered driver aes1610 fp:debug [register_driver] registered driver aes1660 fp:debug [register_driver] registered driver aes2660 fp:debug [register_driver] registered driver vfs101 fp:debug [register_driver] registered driver vfs301 fp:debug [register_driver] registered driver vfs5011 fp:debug [register_driver] registered driver upektc fp:debug [register_driver] registered driver upektc_img fp:debug [register_driver] registered driver etes603 fp:debug [register_driver] registered driver vfs0050 fp:debug [register_driver] registered driver elan fp:debug [find_supporting_driver] driver elan supports USB device 04f3:0903 fp:debug [find_supporting_driver] selected driver elan supports USB device 04f3:0903 Found device claimed by ElanTech Fingerprint Sensor driver sync:debug [fp_dev_open] async:debug [fp_async_dev_open] elan:debug [dev_init] async:debug [fpi_drvcb_open_complete] status 0 sync:debug [sync_open_cb] status 0 Opened device. It's now time to enroll your finger. You will need to successfully scan your finger 5 times to complete the process. Scan your finger now. sync:debug [fp_enroll_finger_img] async:debug [fp_async_enroll_start] starting enrollment fp:debug [generic_acquire_start] action 1 elan:debug [dev_activate] elan:debug [elan_activate] elan:debug [elan_dev_reset] drv:debug [__ssm_call_handler] 0x72ab00 entering state 0 elan:debug [elan_run_cmd] 4019 sync:debug [fp_enroll_finger_img] elan will handle enroll stage 0/4 elan:debug [elan_cmd_cb] elan:debug [elan_cmd_read] elan:debug [elan_cmd_cb] elan:debug [elan_cmd_done] drv:debug [__ssm_call_handler] 0x72ab00 entering state 1 elan:debug [activate_run_state] FW ver 0x0135 drv:debug [__ssm_call_handler] 0x72ab00 entering state 2 elan:debug [elan_run_cmd] 000c elan:debug [elan_cmd_cb] elan:debug [elan_cmd_read] elan:debug [elan_cmd_cb] elan:debug [elan_cmd_done] drv:debug [__ssm_call_handler] 0x72ab00 entering state 3 elan:debug [activate_run_state] sensor dimensions, WxH: 96x96 drv:debug [__ssm_call_handler] 0x72ab00 entering state 4 elan:debug [elan_run_cmd] 402a elan:debug [elan_run_cmd] skipping for this device elan:debug [elan_cmd_done] drv:debug [fpi_ssm_mark_completed] 0x72ab00 completed with status 0 elan:debug [activate_complete] elan:debug [elan_calibrate] elan:debug [elan_dev_reset] drv:debug [__ssm_call_handler] 0x6fc490 entering state 0 elan:debug [elan_run_cmd] 0009 elan:debug [elan_cmd_cb] elan:debug [elan_cmd_read] elan:debug [elan_cmd_cb] elan:debug [elan_cmd_done] drv:debug [__ssm_call_handler] 0x6fc490 entering state 1 elan:debug [elan_save_background] elan:debug [elan_save_frame] elan:debug [calibrate_run_state] FW does not support calibration drv:debug [fpi_ssm_mark_completed] 0x6fc490 completed with status 0 elan:debug [calibrate_complete] fp:debug [fpi_imgdev_activate_complete] status 0 async:debug [fpi_drvcb_enroll_started] status 0 elan:debug [elan_capture] elan:debug [elan_dev_reset] drv:debug [__ssm_call_handler] 0x704440 entering state 0 elan:debug [elan_run_cmd] 4031 elan:debug [elan_cmd_cb] elan:debug [elan_cmd_read] elan:debug [elan_cmd_read] skipping read, not expecting anything elan:debug [elan_cmd_done] drv:debug [__ssm_call_handler] 0x704440 entering state 1 elan:debug [elan_run_cmd] 403f elan:debug [elan_cmd_cb] elan:debug [elan_cmd_read] elan:debug [elan_cmd_cb] elan:debug [elan_cmd_done] drv:debug [__ssm_call_handler] 0x704440 entering state 2 fp:debug [fpi_imgdev_report_finger_status] finger on sensor elan:debug [elan_run_cmd] 0009 elan:debug [elan_cmd_cb] elan:debug [elan_cmd_read] elan:debug [elan_cmd_cb] elan:debug [elan_cmd_done] drv:debug [__ssm_call_handler] 0x704440 entering state 3 elan:debug [elan_save_img_frame] elan:debug [elan_save_frame] drv:debug [__ssm_call_handler] 0x704440 entering state 1 elan:debug [elan_run_cmd] 403f elan:debug [elan_cmd_cb] elan:debug [elan_cmd_read] elan:debug [elan_cmd_cb] elan:debug [elan_cmd_done] drv:debug [__ssm_call_handler] 0x704440 entering state 2 fp:debug [fpi_imgdev_report_finger_status] finger on sensor fp:debug [fpi_imgdev_report_finger_status] ignoring statu
[Bug 1641290] Re: [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised
@Igor I compiled and ran the tests for your latest driver and found that it would not correctly enroll my fingerprint on the Asus UX490UA which uses the ELAN 04f3:0903 device. This is the output: This program will enroll your right index finger, unconditionally overwriting any right-index print that was enrolled previously. If you want to continue, press enter, otherwise hit Ctrl+C fp:debug [fp_init] fp:debug [register_driver] registered driver upekts fp:debug [register_driver] registered driver aes3500 fp:debug [register_driver] registered driver aes4000 fp:debug [register_driver] registered driver aes2501 fp:debug [register_driver] registered driver aes2550 fp:debug [register_driver] registered driver uru4000 fp:debug [register_driver] registered driver vcom5s fp:debug [register_driver] registered driver upeksonly fp:debug [register_driver] registered driver aes1610 fp:debug [register_driver] registered driver aes1660 fp:debug [register_driver] registered driver aes2660 fp:debug [register_driver] registered driver vfs101 fp:debug [register_driver] registered driver vfs301 fp:debug [register_driver] registered driver vfs5011 fp:debug [register_driver] registered driver upektc fp:debug [register_driver] registered driver upektc_img fp:debug [register_driver] registered driver etes603 fp:debug [register_driver] registered driver vfs0050 fp:debug [register_driver] registered driver elan fp:debug [find_supporting_driver] driver elan supports USB device 04f3:0903 fp:debug [find_supporting_driver] selected driver elan supports USB device 04f3:0903 Found device claimed by ElanTech Fingerprint Sensor driver sync:debug [fp_dev_open] async:debug [fp_async_dev_open] elan:debug [dev_init] async:debug [fpi_drvcb_open_complete] status 0 sync:debug [sync_open_cb] status 0 Opened device. It's now time to enroll your finger. You will need to successfully scan your finger 5 times to complete the process. Scan your finger now. sync:debug [fp_enroll_finger_img] async:debug [fp_async_enroll_start] starting enrollment fp:debug [generic_acquire_start] action 1 elan:debug [dev_activate] elan:debug [elan_activate] elan:debug [elan_dev_reset] drv:debug [__ssm_call_handler] 0x10bac00 entering state 0 elan:debug [elan_run_cmd] 4019 sync:debug [fp_enroll_finger_img] elan will handle enroll stage 0/4 elan:debug [elan_cmd_cb] elan:debug [elan_cmd_cb] transfer timed out drv:debug [fpi_ssm_mark_aborted] error -110 from state 0 drv:debug [fpi_ssm_mark_completed] 0x10bac00 completed with status -110 elan:debug [activate_complete] fp:debug [fpi_imgdev_activate_complete] status -110 async:debug [fpi_drvcb_enroll_started] status -110 sync:debug [sync_enroll_cb] result -110 sync:error [fp_enroll_finger_img] unrecognised return code -110 sync:debug [fp_enroll_finger_img] ending enrollment async:debug [fp_async_enroll_stop] elan:debug [dev_deactivate] elan:debug [elan_deactivate] elan:debug [elan_dev_reset] drv:debug [__ssm_call_handler] 0x10bac00 entering state 0 elan:debug [deactivate_run_state] elan:debug [elan_run_cmd] 000b elan:debug [elan_cmd_cb] elan:debug [elan_cmd_cb] transfer timed out drv:debug [fpi_ssm_mark_aborted] error -110 from state 0 drv:debug [fpi_ssm_mark_completed] 0x10bac00 completed with status -110 elan:debug [deactivate_complete] fp:debug [fpi_imgdev_deactivate_complete] async:debug [fpi_drvcb_enroll_stopped] sync:debug [enroll_stop_cb] Enroll failed with error -22 sync:debug [fp_dev_close] elan:debug [dev_deinit] elan:debug [elan_dev_reset] async:debug [fpi_drvcb_close_complete] sync:debug [sync_close_cb] fp:debug [fp_exit] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641290 Title: [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1641290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742668] [NEW] budgie-daemon crashed with SIGSEGV in g_object_unref()
Public bug reported: Using Budgie on 18.04 pre-release, originally installed Kubuntu then installed ubuntu-budgie-desktop meta package, still using sddm if that matters. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: budgie-core 10.4+git20171031.10.g9f71bb8-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Thu Jan 11 12:59:59 2018 ExecutablePath: /usr/bin/budgie-daemon InstallationDate: Installed on 2017-12-12 (30 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: budgie-daemon ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f76a67d3efe: movq $0x0,(%rax,%rdx,8) PC (0x7f76a67d3efe) ok source "$0x0" ok destination "(%rax,%rdx,8)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: budgie-desktop StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libwnck-3.so.0 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () ?? () __libc_start_main (main=0x560d5311b050, argc=1, argv=0x7ffd0dd95328, init=, fini=, rtld_fini=, stack_end=0x7ffd0dd95318) at ../csu/libc-start.c:308 Title: budgie-daemon crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirt lpadmin sambashare sudo ** Affects: budgie-desktop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic need-amd64-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742668 Title: budgie-daemon crashed with SIGSEGV in g_object_unref() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1742668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741675] [NEW] desktop screen
Public bug reported: when i go to launcher the screen keeps resetting ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Jan 6 18:33:24 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (primary) [1028:022f] Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1028:022f] LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Inspiron 1525 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0CP549 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd10/16/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0CP549:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 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/1741675 Title: desktop screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1741675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740835] [NEW] package mysql-server-5.7 5.7.20-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: can not install mysql it can be access from terminal and also i install it in xampp server and it work with php my admin but i can't access it in terminal so laravel can't work withit thanks ProblemType: Package DistroRelease: Ubuntu 16.04 Package: mysql-server-5.7 5.7.20-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 Date: Fri Dec 29 13:50:48 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-11-15 (47 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf: [mysqld_safe] syslog MySQLVarLibDirListing: ['ib_logfile0', 'debian-5.7.flag', 'ibdata1', 'sys', 'ib_buffer_pool', 'incapi', 'auto.cnf', 'ib_logfile1', 'mysql', 'performance_schema', 'ibtmp1'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic root=UUID=1f6b15cf-25cd-4c0c-9e9a-4624db1f60f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: mysql-5.7 Title: package mysql-server-5.7 5.7.20-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-5.7 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740835 Title: package mysql-server-5.7 5.7.20-0ubuntu0.16.04.1 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/mysql-5.7/+bug/1740835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738724] [NEW] [iMac15, 1, Cirrus Logic CS4206, Speaker, Internal] No sound at all
Public bug reported: I have iMac 15.1 2014. Sometimes my internal speaker works, sometimes doesn't. When I ran the ubuntu-bug tool, internal speakers worked, however when I use spotify or youtube from different browsers, there are no sound at all. I did remove&install alsa-lib again and again but no luck. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: said 2018 F pulseaudio /dev/snd/pcmC0D0p: said 2018 F...m pulseaudio /dev/snd/controlC0: said 2018 F pulseaudio CurrentDesktop: GNOME Date: Mon Dec 18 09:42:42 2017 InstallationDate: Installed on 2017-08-01 (138 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [iMac15,1, Cirrus Logic CS4206, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM151.88Z.0207.B06.1602221600 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-FA842E06C61E91C5 dmi.board.vendor: Apple Inc. dmi.board.version: iMac15,1 dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-FA842E06C61E91C5 dmi.modalias: dmi:bvnAppleInc.:bvrIM151.88Z.0207.B06.1602221600:bd02/22/2016:svnAppleInc.:pniMac15,1:pvr1.0:rvnAppleInc.:rnMac-FA842E06C61E91C5:rvriMac15,1:cvnAppleInc.:ct13:cvrMac-FA842E06C61E91C5: dmi.product.name: iMac15,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-10-24T17:32:41.504894 ** Affects: alsa-driver (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/1738724 Title: [iMac15,1, Cirrus Logic CS4206, Speaker, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1738724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608542] Re: package gitlab 8.5.8+dfsg-5 [modified: var/lib/gitlab/gitlab-debian.conf] failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 7
I have the same problem, anybody found a fix ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608542 Title: package gitlab 8.5.8+dfsg-5 [modified: var/lib/gitlab/gitlab- debian.conf] failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gitlab/+bug/1608542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1735231] [NEW] booter loadingproblem
Public bug reported: booting programe can not be installed ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubiquity 17.10.10 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CasperVersion: 1.387 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 29 20:27:39 2017 LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) 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 artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1735231 Title: booter loadingproblem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1735231/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712181] Re: Error installing OBS studio on AMD Ubuntu 17.4
I have that exact issue on my Laptop, Ubuntu Unity 17.04 Kernel: 4.14.0-041400-generic Please let me know if you need more information from my side. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712181 Title: Error installing OBS studio on AMD Ubuntu 17.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/1712181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 732677] Re: bcmwl 5.100.82.38+bdcom-0ubuntu2 not work on BCM4311
** Also affects: broadcom-sta 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/732677 Title: bcmwl 5.100.82.38+bdcom-0ubuntu2 not work on BCM4311 To manage notifications about this bug go to: https://bugs.launchpad.net/broadcom-sta/+bug/732677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645018] [NEW] package linux-image-3.19.0-69-generic 3.19.0-69.77 failed to install/upgrade: package linux-image-3.19.0-69-generic is already installed and configured
Public bug reported: just opened up computer and its saying theres a error not sure whats the issue ProblemType: Package DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-69-generic 3.19.0-69.77 ProcVersionSignature: Ubuntu 3.19.0-74.82-generic 3.19.8-ckt22 Uname: Linux 3.19.0-74-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.8 AptTermLog: AptdaemonVersion: 1.1.1+bzr982-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teresa123 1383 F pulseaudio Date: Fri Nov 25 01:13:51 2016 DpkgLog: DuplicateSignature: package:linux-image-3.19.0-69-generic:3.19.0-69.77:package linux-image-3.19.0-69-generic is already installed and configured ErrorMessage: package linux-image-3.19.0-69-generic is already installed and configured HibernationDevice: RESUME=UUID=2ac3b6fe-7946-4a2e-82b5-390b8069da8b InstallationDate: Installed on 2016-09-05 (82 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Precision M4300 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-74-generic root=UUID=fd6908eb-3702-4822-b1d6-e60f4b408a8f ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-22ubuntu1.5 SourcePackage: dpkg Title: package linux-image-3.19.0-69-generic 3.19.0-69.77 failed to install/upgrade: package linux-image-3.19.0-69-generic is already installed and configured UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0UY141 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/19/2013:svnDellInc.:pnPrecisionM4300:pvr:rvnDellInc.:rn0UY141:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M4300 dmi.sys.vendor: Dell Inc. ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package need-duplicate-check vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645018 Title: package linux-image-3.19.0-69-generic 3.19.0-69.77 failed to install/upgrade: package linux-image-3.19.0-69-generic is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1645018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556482] [NEW] gnome-software crashed with SIGSEGV in g_variant_get_va()
*** This bug is a duplicate of bug 1552420 *** https://bugs.launchpad.net/bugs/1552420 Public bug reported: this is the first time ive ben able to report some problems with 16.04. ( problem in gnome-software cannot be reported.) you have obsolete package versions installed. please upgrade the following and check if the problem still occurs) so i 1)sudo apt-get update 2)sudo apt-get autoclean 3)sudo apt-get upgrade 4)sudo apt-get autoremove. now it crashes again but lets me report it please advise what can or could be done ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-software 3.19.92~git20160310.0c17ea0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20-0ubuntu3 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity Date: Sat Mar 12 14:20:27 2016 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2016-03-12 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160304) ProcCmdline: /usr/bin/gnome-software --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0xb6885c82: movl $0x0,(%edi) PC (0xb6885c82) ok source "$0x0" ok destination "(%edi)" (0x0010) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-software StacktraceTop: ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_variant_get_va () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_variant_get () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/gs-plugins-9/libgs_plugin_apt.so Title: gnome-software crashed with SIGSEGV in g_variant_get_va() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash i386 xenial ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556482 Title: gnome-software crashed with SIGSEGV in g_variant_get_va() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1556482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506378] Re: libvirt-bin configuration after installatioin fails
Now I am on new installation and this issue doesn't happen anymore. You can mark it as closed as I can't reproduce it anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506378 Title: libvirt-bin configuration after installatioin fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1506378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507365] [NEW] Error creating new machine in virt-manager
Public bug reported: Creating new machine in virt-manager I get: Error launching manager: 'NoneType' object has no attribute 'get_default_storage_format' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 889, in _do_show_create self._get_create_dialog().show(src.topwin, uri) File "/usr/share/virt-manager/virtManager/create.py", line 170, in show self.reset_state(uri) File "/usr/share/virt-manager/virtManager/create.py", line 393, in reset_state self.addstorage.reset_state() File "/usr/share/virt-manager/virtManager/addstorage.py", line 196, in reset_state fmt = self.conn.get_default_storage_format() AttributeError: 'NoneType' object has no attribute 'get_default_storage_format' ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: virt-manager 1:1.0.1-5ubuntu2 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: Sun Oct 18 21:12:59 2015 InstallationDate: Installed on 2015-10-18 (0 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US.utf8 TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/bash SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: virt-manager (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/1507365 Title: Error creating new machine in virt-manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1507365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506378] Re: libvirt-bin configuration after installatioin fails
mustafa@mustafa-All-Series:~$ sudo systemctl status libvirt-bin.service [sudo] password for mustafa: ● libvirt-bin.service - Virtualization daemon Loaded: loaded (/lib/systemd/system/libvirt-bin.service; enabled; vendor preset: enabled) Active: failed (Result: start-limit) since Thu 2015-10-15 20:20:49 AST; 4min 54s ago Docs: man:libvirtd(8) http://libvirt.org Process: 924 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=exited, status=1/FAILURE) Main PID: 924 (code=exited, status=1/FAILURE) CGroup: /system.slice/libvirt-bin.service Oct 15 20:20:48 mustafa-All-Series systemd[1]: Failed to start Virtualization daemon. Oct 15 20:20:48 mustafa-All-Series systemd[1]: libvirt-bin.service: Unit entered failed state. Oct 15 20:20:48 mustafa-All-Series systemd[1]: libvirt-bin.service: Failed with result 'exit-code'. Oct 15 20:20:49 mustafa-All-Series systemd[1]: libvirt-bin.service: Service hold-off time ove...rt. Oct 15 20:20:49 mustafa-All-Series systemd[1]: Stopped Virtualization daemon. Oct 15 20:20:49 mustafa-All-Series systemd[1]: libvirt-bin.service: Start request repeated to...ly. Oct 15 20:20:49 mustafa-All-Series systemd[1]: Failed to start Virtualization daemon. Oct 15 20:20:49 mustafa-All-Series systemd[1]: libvirt-bin.service: Unit entered failed state. Oct 15 20:20:49 mustafa-All-Series systemd[1]: libvirt-bin.service: Failed with result 'start...t'. Hint: Some lines were ellipsized, use -l to show in full. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506378 Title: libvirt-bin configuration after installatioin fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1506378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506378] Re: libvirt-bin configuration after installatioin fails
mustafa@mustafa-All-Series:~$ sudo journalctl -u libvirt-bin -- Logs begin at Thu 2015-10-15 20:20:47 AST, end at Thu 2015-10-15 20:26:42 AST. -- Oct 15 20:20:48 mustafa-All-Series systemd[1]: Starting Virtualization daemon... Oct 15 20:20:48 mustafa-All-Series libvirtd[786]: /usr/sbin/libvirtd: initialization failed Oct 15 20:20:48 mustafa-All-Series systemd[1]: libvirt-bin.service: Main process exited, code=exited, status=1/FAILURE Oct 15 20:20:48 mustafa-All-Series systemd[1]: Failed to start Virtualization daemon. Oct 15 20:20:48 mustafa-All-Series systemd[1]: libvirt-bin.service: Unit entered failed state. Oct 15 20:20:48 mustafa-All-Series systemd[1]: libvirt-bin.service: Failed with result 'exit-code'. Oct 15 20:20:48 mustafa-All-Series systemd[1]: libvirt-bin.service: Service hold-off time over, scheduling restart. Oct 15 20:20:48 mustafa-All-Series systemd[1]: Stopped Virtualization daemon. Oct 15 20:20:48 mustafa-All-Series systemd[1]: Starting Virtualization daemon... Oct 15 20:20:48 mustafa-All-Series libvirtd[817]: /usr/sbin/libvirtd: initialization failed Oct 15 20:20:48 mustafa-All-Series systemd[1]: libvirt-bin.service: Main process exited, code=exited, status=1/FAILURE Oct 15 20:20:48 mustafa-All-Series systemd[1]: Failed to start Virtualization daemon. Oct 15 20:20:48 mustafa-All-Series systemd[1]: libvirt-bin.service: Unit entered failed state. Oct 15 20:20:48 mustafa-All-Series systemd[1]: libvirt-bin.service: Failed with result 'exit-code'. Oct 15 20:20:48 mustafa-All-Series systemd[1]: libvirt-bin.service: Service hold-off time over, scheduling restart. Oct 15 20:20:48 mustafa-All-Series systemd[1]: Stopped Virtualization daemon. Oct 15 20:20:48 mustafa-All-Series systemd[1]: Starting Virtualization daemon... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506378 Title: libvirt-bin configuration after installatioin fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1506378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506378] Re: libvirt-bin configuration after installatioin fails
** Attachment added: "sources.list" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1506378/+attachment/4495848/+files/sources.list -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506378 Title: libvirt-bin configuration after installatioin fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1506378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506378] Re: libvirt-bin configuration after installatioin fails
** Attachment added: "term.log" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1506378/+attachment/4495849/+files/term.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506378 Title: libvirt-bin configuration after installatioin fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1506378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506378] Re: libvirt-bin configuration after installatioin fails
mustafa@mustafa-All-Series:~$ ls -l /etc/libvirt total 76 drwxr-xr-x 2 root root 4096 Sep 29 04:02 hooks -rw-r--r-- 1 root root 518 Sep 29 04:02 libvirt.conf -rw-r--r-- 1 root root 14376 Sep 29 04:02 libvirtd.conf -rw-r--r-- 1 root root 834 Sep 29 04:02 libxl.conf -rw-r--r-- 1 root root 2169 Sep 29 04:02 libxl-lockd.conf -rw-r--r-- 1 root root 1235 Sep 29 04:02 lxc.conf drwxr-xr-x 2 root root 4096 Oct 15 11:30 nwfilter drwxr-xr-x 3 root root 4096 Oct 15 09:50 qemu -rw--- 1 root root 18987 Sep 29 04:02 qemu.conf -rw-r--r-- 1 root root 2169 Sep 29 04:02 qemu-lockd.conf -rw-r--r-- 1 root root 2134 Sep 29 04:02 virtlockd.conf -rw-r--r-- 1 root root 1217 Sep 29 04:02 virt-login-shell.conf mustafa@mustafa-All-Series:~$ cat /proc/self/mountinfo 19 25 0:18 / /sys rw,nosuid,nodev,noexec,relatime shared:7 - sysfs sysfs rw 20 25 0:4 / /proc rw,nosuid,nodev,noexec,relatime shared:13 - proc proc rw 21 25 0:6 / /dev rw,nosuid,relatime shared:2 - devtmpfs udev rw,size=8037228k,nr_inodes=2009307,mode=755 22 21 0:14 / /dev/pts rw,nosuid,noexec,relatime shared:3 - devpts devpts rw,gid=5,mode=620,ptmxmode=000 23 25 0:19 / /run rw,nosuid,noexec,relatime shared:5 - tmpfs tmpfs rw,size=1610920k,mode=755 25 0 8:3 / / rw,relatime shared:1 - ext4 /dev/sda3 rw,errors=remount-ro,data=ordered 26 19 0:12 / /sys/kernel/security rw,nosuid,nodev,noexec,relatime shared:8 - securityfs securityfs rw 27 21 0:21 / /dev/shm rw,nosuid,nodev shared:4 - tmpfs tmpfs rw 28 23 0:22 / /run/lock rw,nosuid,nodev,noexec,relatime shared:6 - tmpfs tmpfs rw,size=5120k 29 19 0:23 / /sys/fs/cgroup rw shared:9 - tmpfs tmpfs rw,mode=755 30 29 0:24 / /sys/fs/cgroup/systemd rw,nosuid,nodev,noexec,relatime shared:10 - cgroup cgroup rw,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd 31 19 0:25 / /sys/fs/pstore rw,nosuid,nodev,noexec,relatime shared:11 - pstore pstore rw 32 19 0:26 / /sys/firmware/efi/efivars rw,nosuid,nodev,noexec,relatime shared:12 - efivarfs efivarfs rw 33 29 0:27 / /sys/fs/cgroup/perf_event rw,nosuid,nodev,noexec,relatime shared:14 - cgroup cgroup rw,perf_event,release_agent=/run/cgmanager/agents/cgm-release-agent.perf_event 34 29 0:28 / /sys/fs/cgroup/memory rw,nosuid,nodev,noexec,relatime shared:15 - cgroup cgroup rw,memory 35 29 0:29 / /sys/fs/cgroup/cpu,cpuacct rw,nosuid,nodev,noexec,relatime shared:16 - cgroup cgroup rw,cpu,cpuacct 36 29 0:30 / /sys/fs/cgroup/devices rw,nosuid,nodev,noexec,relatime shared:17 - cgroup cgroup rw,devices 37 29 0:31 / /sys/fs/cgroup/freezer rw,nosuid,nodev,noexec,relatime shared:18 - cgroup cgroup rw,freezer 38 29 0:32 / /sys/fs/cgroup/net_cls,net_prio rw,nosuid,nodev,noexec,relatime shared:19 - cgroup cgroup rw,net_cls,net_prio 39 29 0:33 / /sys/fs/cgroup/hugetlb rw,nosuid,nodev,noexec,relatime shared:20 - cgroup cgroup rw,hugetlb,release_agent=/run/cgmanager/agents/cgm-release-agent.hugetlb 40 29 0:34 / /sys/fs/cgroup/cpuset rw,nosuid,nodev,noexec,relatime shared:21 - cgroup cgroup rw,cpuset,clone_children 41 29 0:35 / /sys/fs/cgroup/blkio rw,nosuid,nodev,noexec,relatime shared:22 - cgroup cgroup rw,blkio 42 20 0:36 / /proc/sys/fs/binfmt_misc rw,relatime shared:23 - autofs systemd-1 rw,fd=22,pgrp=1,timeout=0,minproto=5,maxproto=5,direct 45 21 0:17 / /dev/mqueue rw,relatime shared:24 - mqueue mqueue rw 43 19 0:7 / /sys/kernel/debug rw,relatime shared:25 - debugfs debugfs rw 44 21 0:37 / /dev/hugepages rw,relatime shared:26 - hugetlbfs hugetlbfs rw 46 19 0:38 / /sys/fs/fuse/connections rw,relatime shared:27 - fusectl fusectl rw 47 25 8:5 / /mnt rw,relatime shared:28 - ext4 /dev/sda5 rw,data=ordered 48 25 8:1 / /boot/efi rw,relatime shared:29 - vfat /dev/sda1 rw,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 97 23 0:40 / /run/cgmanager/fs rw,relatime shared:77 - tmpfs cgmfs rw,size=100k,mode=755 150 23 0:42 / /run/user/117 rw,nosuid,nodev,relatime shared:79 - tmpfs tmpfs rw,size=1610920k,mode=700,uid=117,gid=126 153 23 0:43 / /run/user/1000 rw,nosuid,nodev,relatime shared:81 - tmpfs tmpfs rw,size=1610920k,mode=700,uid=1000,gid=1000 I have no external repos (/etc/apt/sources.list.d/*) ** Attachment added: "history.log" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1506378/+attachment/4495838/+files/history.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506378 Title: libvirt-bin configuration after installatioin fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1506378/+sub
[Bug 1506499] [NEW] Transparency doesn't last more than few seconds
Public bug reported: Compositor is on (or at least it is ticked), but no transparency, when I change the rendering backend to XRender, the panel becomes transparent for about 4 seconds, then get back to non-transparent. both OpenGL version don't activate transparency at all. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: kwin 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: Thu Oct 15 17:35:45 2015 InstallationDate: Installed on 2015-10-13 (1 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) PackageArchitecture: all SourcePackage: kwin UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kwin (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/1506499 Title: Transparency doesn't last more than few seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1506499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506378] [NEW] libvirt-bin configuration after installatioin fails
Public bug reported: Trying to install libvirt-bin fail mustafa@mustafa-All-Series:~$ sudo apt install libvirt-bin Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: qemu-kvm qemu radvd The following NEW packages will be installed: libvirt-bin 0 to upgrade, 1 to newly install, 0 to remove and 0 not to upgrade. Need to get 0 B/2,290 kB of archives. After this operation, 12.3 MB of additional disk space will be used. Selecting previously unselected package libvirt-bin. (Reading database ... 193743 files and directories currently installed.) Preparing to unpack .../libvirt-bin_1.2.16-2ubuntu11_amd64.deb ... Unpacking libvirt-bin (1.2.16-2ubuntu11) ... Processing triggers for man-db (2.7.4-1) ... Processing triggers for systemd (225-1ubuntu7) ... Processing triggers for ureadahead (0.100.0-19) ... Setting up libvirt-bin (1.2.16-2ubuntu11) ... invoke-rc.d: Unit libvirt-bin.service is masked Job for libvirt-bin.service failed because the control process exited with error code. See "systemctl status libvirt-bin.service" and "journalctl -xe" for details. invoke-rc.d: initscript libvirt-bin, action "start" failed. dpkg: error processing package libvirt-bin (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: libvirt-bin E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: libvirt-bin 1.2.16-2ubuntu11 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: Thu Oct 15 11:35:41 2015 InstallationDate: Installed on 2015-10-13 (1 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu.conf'] ** Affects: libvirt (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/1506378 Title: libvirt-bin configuration after installatioin fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1506378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506375] [NEW] Long delay when logging into Plasma
Public bug reported: I am using Wily beta 2, I notice a delay when I log into the Plasma session. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: plasma-desktop 4:5.4.2-0ubuntu2 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: Thu Oct 15 11:35:09 2015 InstallationDate: Installed on 2015-10-13 (1 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) SourcePackage: plasma-desktop UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: plasma-desktop (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/1506375 Title: Long delay when logging into Plasma To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1506375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506337] [NEW] No Internet inside Docker containers
Public bug reported: I've installed Docker, when I run: sudo docker run -it debian I get into the container, but I can't reach anything, ping 8.8.8.8 returns "Destination Host Unreachable" Using 'ip ad' I get: mustafa@mustafa-All-Series:~$ ip ad 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether ac:22:0b:c6:6f:d7 brd ff:ff:ff:ff:ff:ff inet6 fe80::ae22:bff:fec6:6fd7/64 scope link valid_lft forever preferred_lft forever 3: docker0: mtu 1500 qdisc noqueue state DOWN group default link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff inet6 fe80::d0fb:3aff:fe0c:36b7/64 scope link valid_lft forever preferred_lft forever 5: ppp0: mtu 1480 qdisc pfifo_fast state UNKNOWN group default qlen 3 link/ppp inet 172.31.1.32 peer 172.31.0.1/32 scope global ppp0 valid_lft forever preferred_lft forever The NO-CARRIER thing is strange for docker bridge. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: docker (not installed) 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: Thu Oct 15 09:48:30 2015 InstallationDate: Installed on 2015-10-13 (1 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) SourcePackage: docker UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: docker (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/1506337 Title: No Internet inside Docker containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker/+bug/1506337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446689] Re: network-manager configured to use /usr/sbin/pppoe but does not recommend pppoe
Could you increase the priority of this bug, maybe even mark it as blocker, its effect is bad and it is easy to fix, just a build flag or added dependency. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446689 Title: network-manager configured to use /usr/sbin/pppoe but does not recommend pppoe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1446689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446689] Re: network-manager configured to use /usr/sbin/pppoe but does not recommend pppoe
This still exist in Wily Werewolf beta 1, this is important and the release is approaching. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446689 Title: network-manager configured to use /usr/sbin/pppoe but does not recommend pppoe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1446689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1365695] Re: No longer able to use GUI after update
exakt_cl...@hotmail.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1365695 Title: No longer able to use GUI after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1365695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 282117] Re: Please purge from archive: lippigment* python-pgm
** Also affects: pigment 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/282117 Title: Please purge from archive: lippigment* python-pgm To manage notifications about this bug go to: https://bugs.launchpad.net/moovida/+bug/282117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446689] Re: network-manager configured to use /usr/sbin/pppoe but does not recommend pppoe
Installing pppoe solves the problem for me -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446689 Title: network-manager configured to use /usr/sbin/pppoe but does not recommend pppoe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1446689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446689] [NEW] networkmanager requires pppoe but it is not in "requires"
Public bug reported: networkmanager switched from using ppp to using pppoe binary for dsl/pppoe connections, I am using pppoe and I can't connect to the Internet unless I install "pppoe" package. From: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-0-9-10&id=7955806a02db64b20079267743056d7d9d45af3b "for now, work around this by using the userland pppoe client rather than the kernel code" One way to fix it is to include pppoe Another way is to configure --with-pppoe=/usr/sbin/pppd. I think this is urgent as pppoe/dsl on all vivid machines will be broken out-of-the-box. ** Affects: network-manager (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/1446689 Title: networkmanager requires pppoe but it is not in "requires" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1446689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 882779] Re: 10ec:8176 WLAN card cannot be activated, it is hard-rfkill-ed and fn-f2 does not work
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/882779 Title: 10ec:8176 WLAN card cannot be activated, it is hard-rfkill-ed and fn-f2 does not work To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/882779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1436350] [NEW] package python3-apport 2.14.1-0ubuntu3.8 failed to install/upgrade: package python3-apport is already installed and configured
Public bug reported: . ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python3-apport 2.14.1-0ubuntu3.8 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: amd64 Date: Wed Mar 25 16:03:20 2015 DuplicateSignature: package:python3-apport:2.14.1-0ubuntu3.8:package python3-apport is already installed and configured ErrorMessage: package python3-apport is already installed and configured InstallationDate: Installed on 2014-09-18 (188 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: dpkg Title: package python3-apport 2.14.1-0ubuntu3.8 failed to install/upgrade: package python3-apport is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package need-duplicate-check trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1436350 Title: package python3-apport 2.14.1-0ubuntu3.8 failed to install/upgrade: package python3-apport is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1436350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397544] [NEW] package fontconfig 2.11.0-0ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: problem ProblemType: Package DistroRelease: Ubuntu 14.04 Package: fontconfig 2.11.0-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Fri Nov 28 23:51:10 2014 DuplicateSignature: package:fontconfig:2.11.0-0ubuntu4.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-04-18 (224 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: fontconfig Title: package fontconfig 2.11.0-0ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397544 Title: package fontconfig 2.11.0-0ubuntu4.1 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/fontconfig/+bug/1397544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397544] Re: package fontconfig 2.11.0-0ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
problem -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1397544 Title: package fontconfig 2.11.0-0ubuntu4.1 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/fontconfig/+bug/1397544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
