[Bug 2014784] Re: Missing zfs-list.cache folder causes zfs list cacher to fail
I reported upstream https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075941 Yours lopiuh ** Bug watch added: Debian Bug tracker #1075941 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075941 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2014784 Title: Missing zfs-list.cache folder causes zfs list cacher to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2014784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2014784] Re: Missing zfs-list.cache folder causes zfs list cacher to fail
To be more clear: https://manpages.debian.org/testing/zfsutils-linux/zfs-mount-generator.8.en.html states: "To begin, enable tracking for the pool: # touch /etc/zfs/zfs-list.cache/poolname " So I am right. The missing directory in a default state is a feature, no bug. Yours lopiuh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2014784 Title: Missing zfs-list.cache folder causes zfs list cacher to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2014784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2014784] Re: Missing zfs-list.cache folder causes zfs list cacher to fail
Hi, isn't that by design (intended) Because zfs-zed package is installed (e .g. default installation) but zfs-mount-generator should not be active in every case. So if I want to finally use zfs-mount-generator I have to manually create the /etc/zfs/zfs-list.cache folder? If it gets "corrected" man has to set package dependencies in a way that zfs-zed is not installed automatically. Or am I wrong? lopiuh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2014784 Title: Missing zfs-list.cache folder causes zfs list cacher to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2014784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738774]
FYI update: SVG icons on macOS have been fixed as per https://bugs.documentfoundation.org/show_bug.cgi?id=130678 which is a major milestone to move this enhancement request here forward. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738774 Title: Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1738774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057713] Re: [SRU] ceph 16.2.15
** Tags removed: verification-wallaby-needed ** Tags added: verification-wallaby-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057713 Title: [SRU] ceph 16.2.15 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2057713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057713] Re: [SRU] ceph 16.2.15
Ran the tests on focal, and they all went fine. Logs attached.
2024-04-15 22:23:17 [INFO] Events:
Configure zaza.openstack.charm_tests.glance.setup.add_lts_image:
Start: 1713219473.3381732
Finish: 1713219552.4053304
Elapsed Time: 79.06715726852417
PCT Of Run Time: 4
Deploy Bundle:
Start: 1713217566.8045628
Finish: 1713217655.9175
Elapsed Time: 89.11293721199036
PCT Of Run Time: 4
Prepare Environment:
Start: 1713217561.9191198
Finish: 1713217566.8043957
Elapsed Time: 4.885275840759277
PCT Of Run Time: 1
Test zaza.openstack.charm_tests.ceph.osd.tests.SecurityTest:
Start: 1713219789.2892342
Finish: 1713219792.6016865
Elapsed Time: 3.3124523162841797
PCT Of Run Time: 1
Test zaza.openstack.charm_tests.ceph.tests.CephLowLevelTest:
Start: 1713219562.9886076
Finish: 1713219629.921777
Elapsed Time: 66.9331693649292
PCT Of Run Time: 3
Test zaza.openstack.charm_tests.ceph.tests.CephPrometheusTest:
Start: 1713219792.6017141
Finish: 1713219797.773857
Elapsed Time: 5.17214298248291
PCT Of Run Time: 1
Test zaza.openstack.charm_tests.ceph.tests.CephRelationTest:
Start: 1713219629.9219327
Finish: 1713219683.6023407
Elapsed Time: 53.680408000946045
PCT Of Run Time: 3
Test zaza.openstack.charm_tests.ceph.tests.CephTest:
Start: 1713219683.6024494
Finish: 1713219789.2891512
Elapsed Time: 105.68670177459717
PCT Of Run Time: 5
Test zaza.openstack.charm_tests.ceph.tests.CheckPoolTypes:
Start: 1713219552.405795
Finish: 1713219562.9885502
Elapsed Time: 10.582755088806152
PCT Of Run Time: 1
Wait for Deployment:
Start: 1713217655.9179013
Finish: 1713219471.630942
Elapsed Time: 1815.7130408287048
PCT Of Run Time: 82
Metadata: {}
Ceph version:
ubuntu@juju-c2c204-zaza-aaf142bef3ef-6:~$ sudo ceph -v
ceph version 16.2.15 (618f440892089921c3e944a991122ddc44e60516) pacific (stable)
** Attachment added: "pacific-16.2.15-results.txt"
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/2057713/+attachment/5765899/+files/pacific-16.2.15-results.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057713
Title:
[SRU] ceph 16.2.15
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2057713/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043336] Re: [SRU] ceph 17.2.7 point release
Tested on jammy and the tests ran fine (attaching full logs).
2024-03-15 16:08:53 [INFO] Events:
Deploy Bundle:
Start: 1710515992.8099723
Finish: 1710516086.5489063
Elapsed Time: 93.73893404006958
PCT Of Run Time: 4
Prepare Environment:
Start: 1710515988.2187657
Finish: 1710515992.8092358
Elapsed Time: 4.5904700756073
PCT Of Run Time: 1
Test zaza.charm_tests.lifecycle.tests.UpgradeCharmsToPath;ceph-mon:
Start: 1710518663.496419
Finish: 1710518668.3889372
Elapsed Time: 4.8925182819366455
PCT Of Run Time: 1
Test zaza.openstack.charm_tests.ceph.mon.tests.CephPermissionUpgradeTest:
Start: 1710518882.371464
Finish: 1710518933.5469208
Elapsed Time: 51.17545676231384
PCT Of Run Time: 2
Test zaza.openstack.charm_tests.ceph.osd.tests.SecurityTest:
Start: 1710518839.4351707
Finish: 1710518841.249194
Elapsed Time: 1.8140232563018799
PCT Of Run Time: 1
Test zaza.openstack.charm_tests.ceph.tests.CephAuthTest:
Start: 1710518842.9432013
Finish: 1710518855.94271
Elapsed Time: 12.999508619308472
PCT Of Run Time: 1
Test zaza.openstack.charm_tests.ceph.tests.CephLowLevelTest:
Start: 1710518764.7217534
Finish: 1710518773.7229624
Elapsed Time: 9.001209020614624
PCT Of Run Time: 1
Test zaza.openstack.charm_tests.ceph.tests.CephMonActionsTest:
Start: 1710518855.9428604
Finish: 1710518882.3712504
Elapsed Time: 26.42839002609253
PCT Of Run Time: 1
Test zaza.openstack.charm_tests.ceph.tests.CephMonJujuPersistent:
Start: 1710518668.3891659
Finish: 1710518762.7588964
Elapsed Time: 94.3697304725647
PCT Of Run Time: 4
Test zaza.openstack.charm_tests.ceph.tests.CephPrometheusTest:
Start: 1710518841.2492943
Finish: 1710518842.943128
Elapsed Time: 1.693833827972412
PCT Of Run Time: 1
Test zaza.openstack.charm_tests.ceph.tests.CephTest:
Start: 1710518773.7234535
Finish: 1710518839.4349415
Elapsed Time: 65.71148800849915
PCT Of Run Time: 3
Test zaza.openstack.charm_tests.ceph.tests.CheckPoolTypes:
Start: 1710518762.7592592
Finish: 1710518764.7217026
Elapsed Time: 1.9624433517456055
PCT Of Run Time: 1
Wait for Deployment:
Start: 1710516086.548988
Finish: 1710518541.854
Elapsed Time: 2455.308789253235
PCT Of Run Time: 84
Metadata: {}
Ceph version:
(venv) ubuntu@lmlogiudice-bastion:~/src/$ juju ssh ceph-mon/0 -- 'ceph -v'
ceph version 17.2.7 (b12291d110049b2f35e32e0de30d70e9a4c060d2) quincy (stable)
** Attachment added: "jammy-result.txt"
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/2043336/+attachment/5756288/+files/jammy-result.txt
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2043336
Title:
[SRU] ceph 17.2.7 point release
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2043336/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057713] Re: [SRU] ceph 16.2.15
** Also affects: cloud-archive 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/2057713 Title: [SRU] ceph 16.2.15 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2057713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057713] [NEW] [SRU] ceph 16.2.15
Public bug reported: [Impact] This release fixes several bugs. We would like to make sure all of our users have access to these improvements. The update contains the following package updates: * ceph 16.2.15 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStackUpdates In order to avoid regression of existing users, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests will be attached to this bug. ** Affects: ceph (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/2057713 Title: [SRU] ceph 16.2.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/2057713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969775] Re: rbd-target-api crashes with `blacklist removal failed`
The fix proposed in https://bugs.launchpad.net/ubuntu/+source/ceph- iscsi/+bug/1883112 provides a partial solution (changing the test to use bytes instead of strings). However, that in itself is insufficient since that only helps to avoid TypeError exceptions - An additional fix is needed so that the messages being checked for inclusion are changed from `blacklist` to `blocklist` (they could be added instead of removed, to be safe). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969775 Title: rbd-target-api crashes with `blacklist removal failed` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph-iscsi/+bug/1969775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962639] [NEW] exigiu 50GB na partição para instalar o Ubuntu
Public bug reported: Formatei meu hd onde havia o Windows e ao instalar o Ubuntu recebi a mensagem que deveria ter uma partição com 50GB para instalar o Ubuntu, não segui está orientação e a intalação não se completou. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 20:37:52 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash nomodeset --- LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=pt_BR.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.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 focal ubiquity-20.04.15.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962639 Title: exigiu 50GB na partição para instalar o Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1962639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1958289] Re: computer does not shut down completely after the 5.13 kernel automatic updating
Thank you! After yesterday's updates my computer can shutdown correctly, Antonio On Tue, Jan 18, 2022 at 3:30 PM Ubuntu Foundations Team Bug Bot < 1958...@bugs.launchpad.net> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. It seems that your bug report is not filed about a > specific source package though, rather it is just filed against Ubuntu > in general. It is important that bug reports be filed about source > packages so that people interested in the package can find the bugs > about it. You can find some hints about determining what package your > bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. > You might also ask for help in the #ubuntu-bugs irc channel on Freenode. > > To change the source package that this bug is filed about visit > https://bugs.launchpad.net/ubuntu/+bug/1958289/+editstatus and add the > package name in the text box next to the word Package. > > [This is an automated message. I apologize if it reached you > inappropriately; please just reply to this message indicating so.] > > ** Tags added: bot-comment > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1958289 > > Title: > computer does not shut down completely after the 5.13 kernel > automatic updating > > Status in linux package in Ubuntu: > New > > Bug description: > dell inspiron 7415 2in1 > os 20.04.3lts > gnome 3.36.8 > x11 > > message on black screen > > [ 38.407808] systemd-shutdown [1]: Waiting for process: systemd-udevd, > systemd-udevd > [ 63.708267] systemd-udevd [381]: :03:00.7: Worker [412] processing > SEQNUM=3413 is taking a long time > [ 141.099020] atkbd serio0: Unknown key pressed (translated set 2, code > 0x67 on isa0060/seri00). > [ 141.099110] atkbd serio0: Use 'setkeycodes 67 to make it > known. > [ 141.103874) atkbd serio0: Unknown key released (translated set 2, code > 0x67 on isa0060/seri00). > [ 141.103964] atkbd serio0: Use 'setkeycodes 67 ' to make it > known. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: [amdgpu] Hang on shutdown: systemd-udevd ... Worker ... processing SEQNUM=... is taking a long time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] Re: [amdgpu] Hang on shutdown: systemd-udevd ... Worker ... processing SEQNUM=... is taking a long time
Hi, after the today's (02/01/22) updates my computer can shutdown again. Thank you for your time! The installed packages are listed below: 2022-02-01 07:44:37 startup archives unpack 2022-02-01 07:44:37 upgrade libsmbclient:amd64 2:4.13.14+dfsg-0ubuntu0.20.04.4 2 :4.13.17~dfsg-0ubuntu0.21.04.1 2022-02-01 07:44:37 status triggers-pending libc-bin:amd64 2.31-0ubuntu9.2 2022-02-01 07:44:37 status half-configured libsmbclient:amd64 2:4.13.14+dfsg-0ub untu0.20.04.4 2022-02-01 07:44:37 status unpacked libsmbclient:amd64 2:4.13.14+dfsg-0ubuntu0.2 0.04.4 2022-02-01 07:44:37 status half-installed libsmbclient:amd64 2:4.13.14+dfsg-0ubu ntu0.20.04.4 2022-02-01 07:44:37 status triggers-pending man-db:amd64 2.9.1-1 2022-02-01 07:44:37 status unpacked libsmbclient:amd64 2:4.13.17~dfsg-0ubuntu0.2 1.04.1 2022-02-01 07:44:37 upgrade libwbclient0:amd64 2:4.13.14+dfsg-0ubuntu0.20.04.4 2 :4.13.17~dfsg-0ubuntu0.21.04.1 2022-02-01 07:44:37 status half-configured libwbclient0:amd64 2:4.13.14+dfsg-0ub untu0.20.04.4 2022-02-01 07:44:37 status unpacked libwbclient0:amd64 2:4.13.14+dfsg-0ubuntu0.2 0.04.4 2022-02-01 07:44:37 status half-installed libwbclient0:amd64 2:4.13.14+dfsg-0ubu ntu0.20.04.4 2022-02-01 07:44:37 status unpacked libwbclient0:amd64 2:4.13.17~dfsg-0ubuntu0.2 1.04.1 2022-02-01 07:44:37 upgrade samba-libs:amd64 2:4.13.14+dfsg-0ubuntu0.20.04.4 2:4 .13.17~dfsg-0ubuntu0.21.04.1 2022-02-01 07:44:37 status half-configured samba-libs:amd64 2:4.13.14+dfsg-0ubun tu0.20.04.4 2022-02-01 07:44:37 status unpacked samba-libs:amd64 2:4.13.14+dfsg-0ubuntu0.20. 04.4 2022-02-01 07:44:37 status half-installed samba-libs:amd64 2:4.13.14+dfsg-0ubunt u0.20.04.4 2022-02-01 07:44:37 status unpacked samba-libs:amd64 2:4.13.17~dfsg-0ubuntu0.21. 04.1 2022-02-01 07:44:37 install linux-modules-5.13.0-28-generic:amd64 5.13.0- 28.31~20.04.1 2022-02-01 07:44:37 status half-installed linux-modules-5.13.0-28-generic:amd64 5.13.0-28.31~20.04.1 2022-02-01 07:44:39 status unpacked linux-modules-5.13.0-28-generic:amd64 5.13.0 -28.31~20.04.1 2022-02-01 07:44:39 install linux-image-5.13.0-28-generic:amd64 5.13.0-28 .31~20.04.1 2022-02-01 07:44:39 status half-installed linux-image-5.13.0-28-generic:amd64 5. 13.0-28.31~20.04.1 2022-02-01 07:44:39 status unpacked linux-image-5.13.0-28-generic:amd64 5.13.0-2 8.31~20.04.1 2022-02-01 07:44:39 install linux-modules-extra-5.13.0-28-generic:amd64 5 .13.0-28.31~20.04.1 2022-02-01 07:44:39 status half-installed linux-modules-extra-5.13.0-28-generic: amd64 5.13.0-28.31~20.04.1 2022-02-01 07:44:43 status unpacked linux-modules-extra-5.13.0-28-generic:amd64 5.13.0-28.31~20.04.1 2022-02-01 07:44:43 upgrade linux-generic-hwe-20.04:amd64 5.13.0.27.29~20.04.13 5.13.0.28.31~20.04.15 2022-02-01 07:44:43 status half-configured linux-generic-hwe-20.04:amd64 5.13.0. 27.29~20.04.13 2022-02-01 07:44:43 status unpacked linux-generic-hwe-20.04:amd64 5.13.0.27.29~2 0.04.13 2022-02-01 07:44:43 status half-installed linux-generic-hwe-20.04:amd64 5.13.0.2 7.29~20.04.13 2022-02-01 07:44:43 status unpacked linux-generic-hwe-20.04:amd64 5.13.0.28.31~2 0.04.15 2022-02-01 07:44:43 upgrade linux-image-generic-hwe-20.04:amd64 5.13.0.27.29~20. 04.13 5.13.0.28.31~20.04.15 2022-02-01 07:44:43 status half-configured linux-image-generic-hwe-20.04:amd64 5 .13.0.27.29~20.04.13 2022-02-01 07:44:43 status unpacked linux-image-generic-hwe-20.04:amd64 5.13.0.2 7.29~20.04.13 2022-02-01 07:44:43 status half-installed linux-image-generic-hwe-20.04:amd64 5. 13.0.27.29~20.04.13 2022-02-01 07:44:43 status unpacked linux-image-generic-hwe-20.04:amd64 5.13.0.2 8.31~20.04.15 2022-02-01 07:44:43 install linux-hwe-5.13-headers-5.13.0-28:all 5.13.0-2 8.31~20.04.1 2022-02-01 07:44:43 status half-installed linux-hwe-5.13-headers-5.13.0-28:all 5 .13.0-28.31~20.04.1 2022-02-01 07:44:46 status unpacked linux-hwe-5.13-headers-5.13.0-28:all 5.13.0- 28.31~20.04.1 2022-02-01 07:44:46 install linux-headers-5.13.0-28-generic:amd64 5.13.0- 28.31~20.04.1 2022-02-01 07:44:46 status half-installed linux-headers-5.13.0-28-generic:amd64 5.13.0-28.31~20.04.1 2022-02-01 07:44:47 status unpacked linux-headers-5.13.0-28-generic:amd64 5.13.0 -28.31~20.04.1 2022-02-01 07:44:47 upgrade linux-headers-generic-hwe-20.04:amd64 5.13.0.27.29~2 0.04.13 5.13.0.28.31~20.04.15 2022-02-01 07:44:47 status half-configured linux-headers-generic-hwe-20.04:amd64 5.13.0.27.29~20.04.13 2022-02-01 07:44:47 status unpacked linux-headers-generic-hwe-20.04:amd64 5.13.0 .27.29~20.04.13 2022-02-01 07:44:47 status half-installed linux-headers-generic-hwe-20.04:amd64 5.13.0.27.29~20.04.13 2022-02-01 07:44:47 status unpacked linux-headers-generic-hwe-20.04:amd64 5.13.0 .28.31~20.04.15 2022-02-01 07:44:47 startup packages configure 2022-02-01 07:44:47 configure libwbclient0:amd64 2:4.13.17~dfsg-0ubuntu0.21.04.1 2022-02-01 07:44:47 status unpacked libwbclient0:amd64 2:4.13.17~dfsg-0ubuntu0.2 1.04.1 2022-02-01 07:44:47 status half-configured libwbclient0:amd64 2:4.13.17~dfsg-0ub untu0.21.04.1
[Bug 1958289] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/476/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/478/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/474/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/477/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/475/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/471/+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/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/472/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/473/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/469/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/468/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/467/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/470/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/466/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/465/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/463/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/464/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/462/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] Re: computer does not shut down completely after the 5.13 kernel automatic updating
apport information ** Description changed: dell inspiron 7415 2in1 os 20.04.3lts gnome 3.36.8 x11 message on black screen [ 38.407808] systemd-shutdown [1]: Waiting for process: systemd-udevd, systemd-udevd [ 63.708267] systemd-udevd [381]: :03:00.7: Worker [412] processing SEQNUM=3413 is taking a long time [ 141.099020] atkbd serio0: Unknown key pressed (translated set 2, code 0x67 on isa0060/seri00). [ 141.099110] atkbd serio0: Use 'setkeycodes 67 to make it known. [ 141.103874) atkbd serio0: Unknown key released (translated set 2, code 0x67 on isa0060/seri00). [ 141.103964] atkbd serio0: Use 'setkeycodes 67 ' to make it known. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: antonio1800 F pulseaudio /dev/snd/controlC0: antonio1800 F pulseaudio /dev/snd/controlC2: antonio1800 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-06 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Inspiron 7415 2-in-1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=95fe2347-727f-4d0c-8559-24cb9ae1d39f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.187.25 Tags: focal Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2021 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 09X2G7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd11/04/2021:br1.6:svnDellInc.:pnInspiron74152-in-1:pvr1.6.0:rvnDellInc.:rn09X2G7:rvrA01:cvnDellInc.:ct31:cvr1.6.0:sku0A8C: dmi.product.family: Inspiron dmi.product.name: Inspiron 7415 2-in-1 dmi.product.sku: 0A8C dmi.product.version: 1.6.0 dmi.sys.vendor: Dell Inc. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.21 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: antonio1792 F pulseaudio + /dev/snd/controlC0: antonio1792 F pulseaudio + /dev/snd/controlC2: antonio1792 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2022-01-06 (12 days ago) + InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) + MachineType: Dell Inc. Inspiron 7415 2-in-1 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=95fe2347-727f-4d0c-8559-24cb9ae1d39f ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 + RelatedPackageVersions: + linux-restricted-modules-5.13.0-25-generic N/A + linux-backports-modules-5.13.0-25-generic N/A + linux-firmware 1.187.25 + Tags: focal + Uname: Linux 5.13.0-25-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/04/2021 + dmi.bios.release: 1.6 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.6.0 + dmi.board.name: 09X2G7 + dmi.board.vendor: Dell Inc. + dmi.board.version: A01 + dmi.chassis.type: 31 + dmi.chassis.vendor: Dell Inc. + dmi.chassis.version: 1.6.0 + dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd11/04/2021:br1.6:svnDellInc.:pnInspiron74152-in-1:pvr1.6.0:rvnDellInc.:rn09X2G7:rvrA01:cvnDellInc.:ct31:cvr1.6.0:sku0A8C: + dmi.product.family: Inspiron + dmi.product.name: Inspiron 7415 2-in-1 + dmi.product.sku: 0A8C + dmi.product.version: 1.6.0 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/461/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go
[Bug 1958289] Re: computer does not shut down completely after the 5.13 kernel automatic updating
** 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/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/307/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/306/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/305/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/304/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/303/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/302/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/301/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/300/+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/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/299/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/298/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/297/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/296/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/295/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/294/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/293/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/291/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/292/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] Re: computer does not shut down completely after the 5.13 kernel automatic updating
apport information ** Tags added: apport-collected ** Description changed: dell inspiron 7415 2in1 os 20.04.3lts gnome 3.36.8 x11 message on black screen [ 38.407808] systemd-shutdown [1]: Waiting for process: systemd-udevd, systemd-udevd [ 63.708267] systemd-udevd [381]: :03:00.7: Worker [412] processing SEQNUM=3413 is taking a long time [ 141.099020] atkbd serio0: Unknown key pressed (translated set 2, code 0x67 on isa0060/seri00). [ 141.099110] atkbd serio0: Use 'setkeycodes 67 to make it known. [ 141.103874) atkbd serio0: Unknown key released (translated set 2, code 0x67 on isa0060/seri00). [ 141.103964] atkbd serio0: Use 'setkeycodes 67 ' to make it known. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.21 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: antonio1800 F pulseaudio + /dev/snd/controlC0: antonio1800 F pulseaudio + /dev/snd/controlC2: antonio1800 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2022-01-06 (12 days ago) + InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) + MachineType: Dell Inc. Inspiron 7415 2-in-1 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=95fe2347-727f-4d0c-8559-24cb9ae1d39f ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 + RelatedPackageVersions: + linux-restricted-modules-5.13.0-25-generic N/A + linux-backports-modules-5.13.0-25-generic N/A + linux-firmware 1.187.25 + Tags: focal + Uname: Linux 5.13.0-25-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/04/2021 + dmi.bios.release: 1.6 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.6.0 + dmi.board.name: 09X2G7 + dmi.board.vendor: Dell Inc. + dmi.board.version: A01 + dmi.chassis.type: 31 + dmi.chassis.vendor: Dell Inc. + dmi.chassis.version: 1.6.0 + dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd11/04/2021:br1.6:svnDellInc.:pnInspiron74152-in-1:pvr1.6.0:rvnDellInc.:rn09X2G7:rvrA01:cvnDellInc.:ct31:cvr1.6.0:sku0A8C: + dmi.product.family: Inspiron + dmi.product.name: Inspiron 7415 2-in-1 + dmi.product.sku: 0A8C + dmi.product.version: 1.6.0 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1958289/+attachment/290/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958289] [NEW] computer does not shut down completely after the 5.13 kernel automatic updating
Public bug reported: dell inspiron 7415 2in1 os 20.04.3lts gnome 3.36.8 x11 message on black screen [ 38.407808] systemd-shutdown [1]: Waiting for process: systemd-udevd, systemd-udevd [ 63.708267] systemd-udevd [381]: :03:00.7: Worker [412] processing SEQNUM=3413 is taking a long time [ 141.099020] atkbd serio0: Unknown key pressed (translated set 2, code 0x67 on isa0060/seri00). [ 141.099110] atkbd serio0: Use 'setkeycodes 67 to make it known. [ 141.103874) atkbd serio0: Unknown key released (translated set 2, code 0x67 on isa0060/seri00). [ 141.103964] atkbd serio0: Use 'setkeycodes 67 ' to make it known. ** Affects: ubuntu Importance: Undecided Status: New ** Summary changed: - computer does not shut down completely after the 5.13 kernel updating + computer does not shut down completely after the 5.13 kernel automatic updating -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: computer does not shut down completely after the 5.13 kernel automatic updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1958289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943266] Re: Duplicated ARP responses from ovnmetadata namespaces
I deployed the openstack-base bundle (adjusted the bridge as in the reproducer). To check for ARP conflicts, I used the Linux tool arp-scan on the local interfaces and found no conflicts. I'm marking this as 'verification-done'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943266 Title: Duplicated ARP responses from ovnmetadata namespaces To manage notifications about this bug go to: https://bugs.launchpad.net/networking-ovn/+bug/1943266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937075] Re: ovn-ctl: ovsdb-server startup might sometimes get stuck and not upgrade clustered database
Tested with the new packages and the db server did not get stuck on startup for a clustered database. Marking it as 'verification-done'. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937075 Title: ovn-ctl: ovsdb-server startup might sometimes get stuck and not upgrade clustered database To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1937075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923691] [NEW] EIO-201 User-mode driver integration
Private bug reported: Base on Bug #1918683 EIO-201 driver integration ADVANTECH wants to integrate another user-mode driver (SUSI library) into Ubuntu image for EPC certification. Please help to check the attached file. EPC-U3233_SUSI4.2.16121_Release_2020_11_16_ubuntu20.04_x64.tar.gz -SUSI4.2.16121 --Driver ---[All *.so files & ini] Thanks. ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "EPC-U3233_SUSI4.2.16121_Release_2020_11_16_ubuntu20.04_x64.tar.gz" https://bugs.launchpad.net/bugs/1923691/+attachment/5487510/+files/EPC-U3233_SUSI4.2.16121_Release_2020_11_16_ubuntu20.04_x64.tar.gz ** Information type changed from Public to Private -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923691 Title: EIO-201 User-mode driver integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1923691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773246] Re: spectacle w/ rectangular region and dual monitor moves display views
Just made an observation: Because I had to take a bunch of screenshots and wanted to use my big screens, I reset the scaling to 1.0 and rebooted. As expected, spectacle worked. Then I set the scaling back to 1.25 and re-logged. And spectacle still works! It even survived a reboot! I would encourage everyone to try that workaround and hope it aids in resolving this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773246 Title: spectacle w/ rectangular region and dual monitor moves display views To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-spectacle/+bug/1773246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773246] Re: spectacle w/ rectangular region and dual monitor moves display views
I am facing the same issue. Arch Linux, Sepctacle 20.12.3. @sk1d can you tell us the output for: > spectacle --version please? :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773246 Title: spectacle w/ rectangular region and dual monitor moves display views To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-spectacle/+bug/1773246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912614] Re: kASLR incorrectly described as disabled by default in Security/Features
> TBH the information about how to point out errors in or discuss various sets of documentation leaves room for improvement. Hopefully we'll find the resources to do something about that going forward. I actually enjoy writing stuff like that. If you point me to someone with more context whom I can pester with my questions, I will try to carve out the time to write it down. Being an "outsider" might actually give me an advantage here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912614 Title: kASLR incorrectly described as disabled by default in Security/Features To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1912614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912614] Re: kASLR incorrectly described as disabled by default in Security/Features
Thanks a lot, Sorry for reaching out in the wrong place. I guess the right place for this would have been the mailing list? I started from: https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation Section "How can I help?" gave me the impression that Proof-reading and continuing with "Send in a bug report" (https://help.ubuntu.com/community/ReportingBugs) was the way of communicating errors in the wiki. Regarding checking the status of kASLR: I guess someone techy enough to care about kASLR will be able to work with the Solutions provided by @crass here: https://askubuntu.com/questions/704640/how-to-detect-in-runtime-is-kaslr-enabled-or-disabled :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912614 Title: kASLR incorrectly described as disabled by default in Security/Features To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1912614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912614] [NEW] kASLR incorrectly described as disabled by default in Security/Features
Public bug reported: According to: https://wiki.ubuntu.com/Security/Features kASLR is disabled by default. Additionally, it is reported that enabling kASLR will disable the ability to hibernate. I think that this is no longer true, but I don't want to edit the wiki without clarifying some details. I discovered the active kASRL when I spun up a qemu vm with Ubuntu 20.04, all defaults and ran volatility3 on a memory dump. On the vm itself the kernel params do not mention kASLR / Kernel hardening: cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=eb6426f9-969b-4ce8-a690-ef87e410d5bf ro quiet splash vt.handoff=7 I also found this somewhere as a supposedly reliable way to tell if kASLR is on: cat /proc/sys/kernel/randomize_va_space 2 I asked a colleague who runs his ubuntu 20.04 directly on his laptop for his cmdline and randomize_va_space, same results. He said he did not knowingly touch any settings regarding kASLR. Now, it seems like at some point kASLR became on by default. But I am not really sure whether it still affects hibernation? I can't find anything reliable on the wiki. My colleague is not sure whether he disabled hibernation for different reasons or whether it was disabled in the first place and I don't want to use my vm as reference, since its not necessarily a "typical environment". Note, the answers here should be updated as well, since checking the kernel params will no longer be reliable. https://askubuntu.com/questions/704640/how-to-detect-in-runtime-is- kaslr-enabled-or-disabled ** Affects: ubuntu-docs (Ubuntu) Importance: Undecided Status: New ** Description changed: According to: https://wiki.ubuntu.com/Security/Features kASLR is disabled by default. Additionally, it is reported that enabling kASLR will disable the ability to hibernate. - I think that this is no longer true, but I don't want to edit the wiki without clarifying some details. - I discovered the active kASRL this when I spun up a qemu vm with Ubuntu 20.04, all defaults and ran volatility3 on a memory dump. On the vm itself the kernel params do not mention kASLR / Kernel hardening: + I think that this is no longer true, but I don't want to edit the wiki without clarifying some details. + I discovered the active kASRL when I spun up a qemu vm with Ubuntu 20.04, all defaults and ran volatility3 on a memory dump. On the vm itself the kernel params do not mention kASLR / Kernel hardening: cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=eb6426f9-969b-4ce8-a690-ef87e410d5bf ro quiet splash vt.handoff=7 - I also found this somewhere as a supposedly reliable way to tell if kASLR is on: + I also found this somewhere as a supposedly reliable way to tell if kASLR is on: cat /proc/sys/kernel/randomize_va_space 2 I asked a colleague who runs his ubuntu 20.04 directly on his laptop for his cmdline and randomize_va_space, same results. He said he did not knowingly touch any settings regarding kASLR. Now, it seems like at some point kASLR became on by default. But I am not really sure whether it still affects hibernation? I can't find anything reliable on the wiki. My colleague is not sure whether he disabled hibernation for different reasons or whether it was disabled in the first place and I don't want to use my vm as reference, since its not necessarily a "typical environment". Note, the answers here should be updated as well, since checking the kernel params will no longer be reliable. https://askubuntu.com/questions/704640/how-to-detect-in-runtime-is- kaslr-enabled-or-disabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912614 Title: kASLR incorrectly described as disabled by default in Security/Features To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1912614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897682] [NEW] unable to upgrade to 20.04 from 18.04
Public bug reported: Unable to upgrade to 20.04 LTS from 18.04 LTS Description:Ubuntu 18.04.5 LTS Release:18.04 philip@philip-ThinkPad-T520:/var/log/dist-upgrade$ sudo do-release-upgrade [sudo] password for philip: Checking for a new Ubuntu release Get:1 Upgrade tool signature [1,554 B] Get:2 Upgrade tool [1,342 kB] Fetched 1,344 kB in 0s (0 B/s) authenticate 'focal.tar.gz' against 'focal.tar.gz.gpg' extracting 'focal.tar.gz' Reading cache Checking package manager Reading package lists... Done Building dependency tree Reading state information... Done Hit http://ca.archive.ubuntu.com/ubuntu bionic InRelease Get:1 http://ca.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:2 http://ca.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB] Get:3 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB] Hit http://archive.canonical.com/ubuntu bionic InRelease Get:4 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [1,089 kB] Get:5 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages [748 kB] Fetched 2,089 kB in 0s (0 B/s) Reading package lists... Done Building dependency tree Reading state information... Done Updating repository information Hit http://ca.archive.ubuntu.com/ubuntu focal InRelease Hit http://archive.canonical.com/ubuntu focal InRelease Get:1 http://ca.archive.ubuntu.com/ubuntu focal-updates InRelease [111 kB] Get:2 http://security.ubuntu.com/ubuntu focal-security InRelease [107 kB] Get:3 http://ca.archive.ubuntu.com/ubuntu focal-backports InRelease [98.3 kB] Fetched 317 kB in 0s (0 B/s) Checking package manager Reading package lists... Done Building dependency tree Reading state information... Done Calculating the changes Calculating the changes 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'. Restoring original system state Aborting Reading package lists... Done Building dependency tree Reading state information... Done ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Sep 29 00:51:09 2020 InstallationDate: Installed on 2018-10-13 (717 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-09-29 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade ** Attachment added: "main.log" https://bugs.launchpad.net/bugs/1897682/+attachment/5415151/+files/main.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897682 Title: unable to upgrade to 20.04 from 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1897682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886877] [NEW] ippusbxd assert failure: ippusbxd: entrygroup.c:255:avahi_entry_group_commit: Assertion `group' failed
Public bug reported: I get this error everytime i start the computer, my printer stop working properly, sometimes it hangs on pause and nothing gets printed, i have to unplug and plug back in the usb port for the printer to print again. pausing or unpausing printer has no effect. I had attempted to type sudo chmod 644 /etc/cups/ppd/ET_2650_Series_583250423038393298_.ppd on my terminal and temporarily works until it hangs again after alittle while. then does the same thing. Description:Ubuntu 20.04 LTS Release:20.04 OS Type: 64bit GNOME Version: 3.36.2 Windowing System: X11 Package: ippusbxd 1.34-2ubuntu1 Title: ippusbxd assert failure: ippusbxd: entrygroup.c:255:avahi_entry_group_commit: Assertion `group' failed ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AssertionMessage: ippusbxd assert failure: ippusbxd: entrygroup.c:255:avahi_entry_group_commit: Assertion `group' failed ProcCmdline: /usb/sbin/ippusbxd --bus-device 003:010 --from-port 6 --logging Never had this issue on Ubuntu 18, I did a clean install of ubuntu 20.04 ** Affects: ippusbxd (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/1886877 Title: ippusbxd assert failure: ippusbxd: entrygroup.c:255:avahi_entry_group_commit: Assertion `group' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ippusbxd/+bug/1886877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732678] [NEW] package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: attempted upgrade and had crash during install. Resumed install, this is result. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.12 Architecture: amd64 Date: Wed Nov 15 19:25:52 2017 ErrorMessage: triggers looping, abandoned RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2017-11-16 (0 days ago) ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 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/1732678 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1732678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725824] [NEW] package linux-gke-tools-4.4.0-1018 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.4.4.0-1018', which is also in package linux-aws-tools-4.4
Public bug reported: The error happens after some changes in Other Software in Software & Update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-gke-tools-4.4.0-1018 (not installed) ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sat Oct 21 13:42:19 2017 DuplicateSignature: package:linux-gke-tools-4.4.0-1018:(not installed) Unpacking linux-gke-tools-4.4.0-1018 (4.4.0-1018.18) ... dpkg: error processing archive /var/cache/apt/archives/linux-gke-tools-4.4.0-1018_4.4.0-1018.18_amd64.deb (--unpack): trying to overwrite '/usr/lib/libcpupower.so.4.4.0-1018', which is also in package linux-aws-tools-4.4.0-1018 4.4.0-1018.27 ErrorMessage: trying to overwrite '/usr/lib/libcpupower.so.4.4.0-1018', which is also in package linux-aws-tools-4.4.0-1018 4.4.0-1018.27 InstallationDate: Installed on 2017-05-24 (150 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: linux-gke Title: package linux-gke-tools-4.4.0-1018 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.4.4.0-1018', which is also in package linux-aws-tools-4.4.0-1018 4.4.0-1018.27 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-gke (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725824 Title: package linux-gke-tools-4.4.0-1018 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.4.4.0-1018', which is also in package linux- aws-tools-4.4.0-1018 4.4.0-1018.27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1725824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296270] Re: Have to login twice after suspending
An update- It only worked once, and then I started having to log in twice again :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296270 Title: Have to login twice after suspending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1296270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296270] Re: Have to login twice after suspending
Hey guys, I have figured out what was causing the problem for me. In the power manager, there is an option that says "automatically lock the screen" and it was set to "when the screensaver was activated". Along with that, there was another checkbox that was checked that said "lock screen when system is going for sleep." Because both of these things happened when my system went for sleep, the system ended up locking itself twice. Setting the "automatically lock the screen" option to "never" fixed 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/1296270 Title: Have to login twice after suspending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1296270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296270] Re: Have to login twice after suspending
By the way, I'm on Xubuntu Xenial (16.04) as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296270 Title: Have to login twice after suspending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1296270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697630] [NEW] add python3 packages
Public bug reported: please add a python3 version of the package, and also update the python2 package. a release which works for both (py2 and py3) can be found here: https://github.com/lo/pivy/releases/tag/0.6.2 This is a fork of pivy. nice regards ** Affects: pivy (Ubuntu) Importance: Undecided Status: New ** Tags: python3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697630 Title: add python3 packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pivy/+bug/1697630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692985] Re: Juju openstack lvd returns always "Container is already running a start operation"
Hello, No news for this topic ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692985 Title: Juju openstack lvd returns always "Container is already running a start operation" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1692985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692985] Re: Juju openstack lvd returns always "Container is already running a start operation"
Hello, Sorry for the missing logs. ** Attachment added: "log during juju openstack initialization" https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1692985/+attachment/4882432/+files/log_lxd.tar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692985 Title: Juju openstack lvd returns always "Container is already running a start operation" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1692985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692985] [NEW] Juju openstack lvd returns always "Container is already running a start operation"
Public bug reported: When I tried to set up Openstack development environment, the same and always error is returned : container=juju-db2944-18 err="Container is already running a start operation" lvl=eror msg="stop hook failed" t=2017-05-23T18:11:05+0200 action=start created=2017-05-23T16:11:02+ ephemeral=false lvl=eror msg="Failed starting container" name=juju-db2944-18 stateful=false t=2017-05-23T18:11:10+0200 used=1970-01-01T00:00:00+ created=2017-05-23T16:11:02+ ephemeral=false lvl=info msg="Deleting container" name=juju-db2944-18 t=2017-05-23T18:11:11+0200 used=2017-05-23T16:11:05+ created=2017-05-23T16:11:02+ ephemeral=false lvl=info msg="Deleted container" name=juju-db2944-18 t=2017-05-23T18:11:11+0200 used=2017-05-23T16:11:05+ ephemeral=false lvl=info msg="Creating container" name=juju-db2944-18 t=2017-05-23T18:11:21+0200 ephemeral=false lvl=info msg="Created container" name=juju-db2944-18 t=2017-05-23T18:11:21+0200 action=start created=2017-05-23T16:11:21+ ephemeral=false lvl=info msg="Starting container" name=juju-db2944-18 stateful=false t=2017-05-23T18:11:24+0200 used=1970-01-01T00:00:00+ container=juju-db2944-18 err="Container is already running a start operation" lvl=eror msg="stop hook failed" t=2017-05-23T18:11:24+0200 action=start created=2017-05-23T16:11:21+ ephemeral=false lvl=eror msg="Failed starting container" name=juju-db2944-18 stateful=false t=2017-05-23T18:11:29+0200 used=1970-01-01T00:00:00+ created=2017-05-23T16:11:21+ ephemeral=false lvl=info msg="Deleting container" name=juju-db2944-18 t=2017-05-23T18:11:30+0200 used=2017-05-23T16:11:24+ created=2017-05-23T16:11:21+ ephemeral=false lvl=info msg="Deleted container" name=juju-db2944-18 t=2017-05-23T18:11:30+0200 used=2017-05-23T16:11:24+ ephemeral=false lvl=info msg="Creating container" name=juju-db2944-18 t=2017-05-23T18:11:40+0200 ephemeral=false lvl=info msg="Created container" name=juju-db2944-18 t=2017-05-23T18:11:40+0200 action=start created=2017-05-23T16:11:40+ ephemeral=false lvl=info msg="Starting container" name=juju-db2944-18 stateful=false t=2017-05-23T18:11:43+0200 used=1970-01-01T00:00:00+ container=juju-db2944-18 err="Container is already running a start operation" lvl=eror msg="stop hook failed" t=2017-05-23T18:11:43+0200 action=start created=2017-05-23T16:11:40+ ephemeral=false lvl=eror msg="Failed starting container" name=juju-db2944-18 stateful=false t=2017-05-23T18:11:48+0200 used=1970-01-01T00:00:00+ created=2017-05-23T16:11:40+ ephemeral=false lvl=info msg="Deleting container" name=juju-db2944-18 t=2017-05-23T18:11:48+0200 used=2017-05-23T16:11:43+ created=2017-05-23T16:11:40+ ephemeral=false lvl=info msg="Deleted container" name=juju-db2944-18 t=2017-05-23T18:11:49+0200 used=2017-05-23T16:11:43+ ephemeral=false lvl=info msg="Creating container" name=juju-db2944-18 t=2017-05-23T18:11:59+0200 ephemeral=false lvl=info msg="Created container" name=juju-db2944-18 t=2017-05-23T18:11:59+0200 action=start created=2017-05-23T16:11:59+ ephemeral=false lvl=info msg="Starting container" name=juju-db2944-18 stateful=false t=2017-05-23T18:12:02+0200 used=1970-01-01T00:00:00+ container=juju-db2944-18 err="Container is already running a start operation" lvl=eror msg="stop hook failed" t=2017-05-23T18:12:02+0200 action=start created=2017-05-23T16:11:59+ ephemeral=false lvl=eror msg="Failed starting container" name=juju-db2944-18 stateful=false t=2017-05-23T18:12:07+0200 used=1970-01-01T00:00:00+ created=2017-05-23T16:11:59+ ephemeral=false lvl=info msg="Deleting container" name=juju-db2944-18 t=2017-05-23T18:12:07+0200 used=2017-05-23T16:12:02+ created=2017-05-23T16:11:59+ ephemeral=false lvl=info msg="Deleted container" name=juju-db2944-18 t=2017-05-23T18:12:08+0200 used=2017-05-23T16:12:02+ vagrant@openstack:~$ juju version 2.1.2-xenial-amd64 ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Description changed: When I tried to set up Openstack development environment, the same and always error is returned : container=juju-db2944-18 err="Container is already running a start operation" lvl=eror msg="stop hook failed" t=2017-05-23T18:11:05+0200 action=start created=2017-05-23T16:11:02+ ephemeral=false lvl=eror msg="Failed starting container" name=juju-db2944-18 stateful=false t=2017-05-23T18:11:10+0200 used=1970-01-01T00:00:00+ created=2017-05-23T16:11:02+ ephemeral=false lvl=info msg="Deleting container" name=juju-db2944-18 t=2017-05-23T18:11:11+0200 used=2017-05-23T16:11:05+ created=2017-05-23T16:11:02+ ephemeral=false lvl=info msg="Deleted container" name=juju-db2944-18 t=2017-05-23T18:11:11+0200 used=2017-05-23T16:11:05+ ephemeral=false lvl=info msg="Creating container" name=juju-db2944-18 t=2017-05-23T18:11:21+0200 ephemeral=false lvl=info msg="Created container"
[Bug 1648388] Re: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting
Hi Joseph The kernel 4.11-rc1 with 16.04 still has the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648388 Title: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648388] Re: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting
I try install Ubuntu14.04 in RAID1 and update mainline kernel v4.10-rc3. It reboots successfully without any error. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648388 Title: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648388] Re: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting
Christopher, I try mainline kernel from 3.12 to 3.19 in Ubuntu16.04. Still found the issue. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648388 Title: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648388] Re: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting
Christopher, I try the latest mainline kernel v4.10-rc3 still found the issue. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648388 Title: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648388] Re: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting
To : Christopher M. Penalver 1 ) I test kernel version is 4.9-rc8 2 ) Done. The default kernel version is 4.4.0-21-generic Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648388 Title: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648388] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1648388/+attachment/4796435/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648388 Title: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648388] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1648388/+attachment/4796438/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648388 Title: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648388] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1648388/+attachment/4796436/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648388 Title: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648388] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1648388/+attachment/4796437/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648388 Title: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648388] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1648388/+attachment/4796432/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648388 Title: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648388] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1648388/+attachment/4796434/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648388 Title: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648388] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1648388/+attachment/4796440/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648388 Title: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648388] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1648388/+attachment/4796441/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648388 Title: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648388] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1648388/+attachment/4796433/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648388 Title: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648388] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1648388/+attachment/4796439/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648388 Title: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648388] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1648388/+attachment/4796431/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648388 Title: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648388] Re: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting
apport information ** Description changed: Install Ubuntu16.04 in RAID1 created by Intel RSTe no matter legacy mode or UEFI mode. System hangs while rebooting Not found the issue in RAID0 No issue on Ubuntu14.04 Driver-OS inbox support Below as error messages === INFO: task systemd-shutdow:1 blocked for more than 120 seconds. Not tainted 4.4.0-21-generic #37-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. INFO: task jbd2/md126p2-8:1732 blocked for more than 120 seconds. Not tainted 4.4.0-21-generic #37-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. INFO: task ext4lazyinit:1873 blocked for more than 120 seconds. Not tainted 4.4.0-21-generic #37-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. INFO: task kworker/u66:4:3139 blocked for more than 120 seconds. Not tainted 4.4.0-21-generic #37-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. === Then I edit /etc/sysctl.conf with follow commands and the system don't hang while rebooting vm.dirty_background_ratio=5 vm.dirty_ratio=10 kernel.panic=3 kernel.hung_task_panic=1 kernel.hung_task_timeout_secs=30 But I don't know if it's an appropriate fix or not. Thanks --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-12-15 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) Package: linux (not installed) ProcEnviron: LANGUAGE=en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: xenial Uname: Linux 4.9.0-040900rc8-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True + --- + ApportVersion: 2.20.1-0ubuntu2 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=f578df47-a1b8-4e66-bd37-904f943eb01b + InstallationDate: Installed on 2016-12-15 (10 days ago) + InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) + MachineType: Dell DCS6430G + Package: linux (not installed) + ProcEnviron: + LANGUAGE=en + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=bc552762-1955-44b8-a83e-2a414f0e0bd1 ro + ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-4.4.0-21-generic N/A + linux-backports-modules-4.4.0-21-generic N/A + linux-firmware1.157 + RfKill: + + Tags: xenial + Uname: Linux 4.4.0-21-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 03/22/2016 + dmi.bios.vendor: Dell + dmi.bios.version: 2.0.3 + dmi.board.name: 038VV0 + dmi.board.vendor: Dell + dmi.board.version: X01 + dmi.chassis.type: 23 + dmi.chassis.vendor: Dell + dmi.modalias: dmi:bvnDell:bvr2.0.3:bd03/22/2016:svnDell:pnDCS6430G:pvr:rvnDell:rn038VV0:rvrX01:cvnDell:ct23:cvr: + dmi.product.name: DCS6430G + dmi.sys.vendor: Dell ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1648388/+attachment/4796430/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648388 Title: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648388] Re: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting
apport information ** Tags added: apport-collected xenial ** Description changed: Install Ubuntu16.04 in RAID1 created by Intel RSTe no matter legacy mode or UEFI mode. System hangs while rebooting Not found the issue in RAID0 No issue on Ubuntu14.04 Driver-OS inbox support Below as error messages === INFO: task systemd-shutdow:1 blocked for more than 120 seconds. Not tainted 4.4.0-21-generic #37-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. INFO: task jbd2/md126p2-8:1732 blocked for more than 120 seconds. Not tainted 4.4.0-21-generic #37-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. INFO: task ext4lazyinit:1873 blocked for more than 120 seconds. Not tainted 4.4.0-21-generic #37-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. INFO: task kworker/u66:4:3139 blocked for more than 120 seconds. Not tainted 4.4.0-21-generic #37-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. === Then I edit /etc/sysctl.conf with follow commands and the system don't hang while rebooting vm.dirty_background_ratio=5 vm.dirty_ratio=10 kernel.panic=3 kernel.hung_task_panic=1 kernel.hung_task_timeout_secs=30 But I don't know if it's an appropriate fix or not. Thanks + --- + ApportVersion: 2.20.1-0ubuntu2 + Architecture: amd64 + DistroRelease: Ubuntu 16.04 + InstallationDate: Installed on 2016-12-15 (0 days ago) + InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) + Package: linux (not installed) + ProcEnviron: + LANGUAGE=en + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + Tags: xenial + Uname: Linux 4.9.0-040900rc8-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1648388/+attachment/4792290/+files/JournalErrors.txt ** 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/1648388 Title: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648388] Re: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting
After update the latest v4.9 kernel ,the issue still exist. Below as error messages === INFO: task systemd-shutdow:1 blocked for more than 120 seconds. Not tainted 4.9.0-040900rc8-generic #201612051443 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. INFO: task jbd2/md126p2-8:2710 blocked for more than 120 seconds. Not tainted 4.9.0-040900rc8-generic #201612051443 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. === Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648388 Title: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648388] Re: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting
** 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/1648388 Title: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1620060] [NEW] Consume all the memory till freeze the computer
Public bug reported: Hi, When I browse webp folders and open some webp pictures, gthumb start to consume a lot of ram each time I open a picture, till freeze the OS for complete. I been using as webp browser since is the only ubuntu app that works with webP, but after viewing lets say... 20pics.. have to close it, and open it again. Seems like each time it open a picture and close, it didn't free the memory, and keep increasing memory usage till freeze the whole PC. This bug has been since webP support arrived. I was lazy to report it. Ubuntu 16.04 updated. 4GB-RAM (2 years ago I converted all my pictures to webP) ** Affects: gthumb (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/1620060 Title: Consume all the memory till freeze the computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gthumb/+bug/1620060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1100190] Re: [Upstream] I/O Error while opening file from WebDAV over GVFS from Nautilus
I confirm the GVFS issue with SMB shares. https://bugs.documentfoundation.org/show_bug.cgi?id=72504 https://ask.libreoffice.org/en/question/69586/error-opening-odb-from-url-share-linux/ http://askubuntu.com/questions/768533/odb-base-error-opening-from-smb-share GVFS shares are much more flexible and today I can't open an ODB from an SMB share. (Ubuntu 16.04, LO Build ID: 1:5.1.2-0ubuntu1 ** Bug watch added: Document Foundation Bugzilla #72504 https://bugs.documentfoundation.org/show_bug.cgi?id=72504 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1100190 Title: [Upstream] I/O Error while opening file from WebDAV over GVFS from Nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1100190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1510383] [NEW] updated from 15.04 to 15.10 and upon reboot X no longer works
Public bug reported: Hi, I just updated from 15.04 to 15.10 and upon reboot X no longer works. Gdm tried to start it up several times but the screen just blinks. I had a look at the gdm and Xorg logs but there is no error. I tried starting X manually with startx but it does the same thing. I tried uninstalling the nvidia proprietary driver, switching to the nouveau driver and rebooting but no luck. I tried different nvidia driver versions, I tried generating the xorg.conf file usimg the nvidia tool, I rebooted in between each try, etcstill nothing. What I don't getbis why the xorg logs have no errors (EE). Can someone help? Thanks, Gabriel ** Affects: 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/1510383 Title: updated from 15.04 to 15.10 and upon reboot X no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1510383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1510383] Re: updated from 15.04 to 15.10 and upon reboot X no longer works
I do create this bug, because I have the same bug, but I have a Intel video card, I do the system works by reseting the system with the kernel 3.19.0-31-generic, without problems, so i think it could be related to the kernel 4.2 that may not work with some specific video cards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1510383 Title: updated from 15.04 to 15.10 and upon reboot X no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1510383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1406222] Re: Can't switch to Radeon rendering
Hi Christopher, Exactly, if I force with vgaswitcheroo to DIScrete (radeon), display goes off. I think, since it is a muxless system, Radeon GPU have no populated display port. Only works as gpu coprocessor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1406222 Title: Can't switch to Radeon rendering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1406222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1406222] Re: Can't switch to Radeon rendering
Hi Christopher, Notebook HP G62 model: G62-b85SS product: XF219EA#ABE -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1406222 Title: Can't switch to Radeon rendering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1406222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1406222] Re: Can't switch to Radeon rendering
Hi Chris, No option. Running latest Bios. I think this muxless config is like a rendering coprocesor with no pin to external display. Radeon coprocess data and use DMA to Intel FB to connect to display. Something new 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/1406222 Title: Can't switch to Radeon rendering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1406222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1406222] Re: Can't switch to Radeon rendering
Hi Christopher, I'm running kernel 3.19 + oibaf ppa (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers) Beside that, I added DRI_PRIME=1 variable to /etc/enviroment to make it default. Even with that variable, latest kernel+mesa+, Bricscad fail to inicialize in 3D with this ugly message: intel_do_flush_locked failed: No such file or directory Recently added LIBGL_ALWAYS_SOFTWARE=1 variable and seems to launch Bricscad in 3D. I will 3D test more with this laptop. If something new appear, I will write here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1406222 Title: Can't switch to Radeon rendering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1406222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 752542] Re: ACPI DSDT info
I have black screen after echo DIS to vgaswitcheroo. Even changing backlight by script a.sh echo DIS /sys/kernel/debug/vgaswitcheroo/switch echo 10 /sys/class/backlight/acpi_video0/brightness echo 10 /sys/class/backlight/acpi_video1/brightness echo 10 /sys/class/backlight/radeon_bl0/brightness service lightdm start xorg.conf Section Device Identifier iHD Driver intel BusID PCI:0:2:0 EndSection Section Device Identifier rHD Driver radeon BusID PCI:1:0:0 EndSection Section Screen Identifier Default Screen Monitor Configured Monitor Device rHD EndSection Any help is really appreciated! ** Attachment added: Hewlett-Packard-HP_G62_Notebook_PC.tar.gz https://bugs.launchpad.net/lpbugreporter/+bug/752542/+attachment/4321008/+files/Hewlett-Packard-HP_G62_Notebook_PC.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/752542 Title: ACPI DSDT info To manage notifications about this bug go to: https://bugs.launchpad.net/bumblebee/+bug/752542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 977804] Re: Unity crashes when many windows are opened (intel_do_flush_locked failed: No space left on device)
Happens to me, every time I launch bricscad in 3D mode intel_do_flush_locked failed: No such file or directory [ Ubuntu 14.10, PPA Olaf ] [ HP G62: VGA Intel i915 with hybrid muxless Radeon HD54xx ] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/977804 Title: Unity crashes when many windows are opened (intel_do_flush_locked failed: No space left on device) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/977804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
