Re: [Bug 1956132] Re: Year doesn't change in notification panel at New Years
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956132 Title: Year doesn't change in notification panel at New Years To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1956132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956132] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1956132/+attachment/5550549/+files/monitors.xml.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956132 Title: Year doesn't change in notification panel at New Years To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1956132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956132] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1956132/+attachment/5550548/+files/ShellJournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956132 Title: Year doesn't change in notification panel at New Years To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1956132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956132] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1956132/+attachment/5550547/+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/1956132 Title: Year doesn't change in notification panel at New Years To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1956132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956132] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1956132/+attachment/5550546/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956132 Title: Year doesn't change in notification panel at New Years To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1956132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956132] Re: Year doesn't change in notification panel at New Years
apport information ** Tags added: apport-collected focal ** Description changed: The year doesn't change on the notification panel at New Years. Here is a screenshot: https://imgur.com/TXsMmyM OS Name: 20.04.3 LTS OS Type: 64-bit GNOME Version: 3.36.8 Windowing System: X11 Here is my uname -a readout: Linux jared-Precision-5510 5.11.0-43-generic #47~20.04.2-Ubuntu SMP Mon Dec 13 11:06:56 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.21 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-11-05 (422 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 + RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 + Tags: focal + Uname: Linux 5.11.0-43-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1956132/+attachment/5550545/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956132 Title: Year doesn't change in notification panel at New Years To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1956132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954342] Re: Client authentication error "Failed to convert SID ... to a PID"
I have this problem in all our environments. I see this in the above quote from the patch"As we require a running winbindd for domain member setups" Since when? We don't use winbindd and never havethis worked until this week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954342 Title: Client authentication error "Failed to convert SID ... to a PID" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1954342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947257] Re: Partial profile loss on upgrade from 21.04 to 21.10
Hi Olivier, I have given that a try but no luck. It still only finds 3 of the 4 windows that were open at the time of the upgrade with the one it can't find being the primary one with 50+ tabs. It does not show up in recently closed tabs/windows either so I guess it's just lost, extremely frustrating. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947257 Title: Partial profile loss on upgrade from 21.04 to 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947257] [NEW] Partial profile loss on upgrade from 21.04 to 21.10
Public bug reported: In the upgrade from 21.04 to 21.10 I noticed it had updated firefox. When restarting some of my profile was kept (themes, addons, etc) but I've noticed my primary window of 50+ tabs was lost. It opened 3 other windows correctly. I tried to find it via "recently closed tabs/windows" but it's not showing up. I have also confirmed there are no duplicate profiles. Silly me assumed it was done correctly and when the upgrade process offered to remove old packages I did so I can't seem to retrieve the old profile. Additional information: lsb_release -rd: Description:Ubuntu 21.10 Release:21.10 snap package information: snap-id: 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk tracking: latest/stable/ubuntu-21.10 refresh-date: today at 09:00 AEST channels: latest/stable:93.0-1 2021-10-08 (631) 157MB - latest/candidate: 93.0-1 2021-09-28 (631) 157MB - latest/beta: 94.0b5-1 2021-10-13 (650) 157MB - latest/edge: ↑ esr/stable: 78.15.0esr-1 2021-10-04 (637) 148MB - esr/candidate:91.2.0esr-1 2021-09-29 (634) 160MB - esr/beta: ↑ esr/edge: ↑ installed: 93.0-1 (631) 157MB - ** Affects: firefox (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/1947257 Title: Partial profile loss on upgrade from 21.04 to 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
@Rodolfo, We still aren't 100% certain that this particular change is the culprit but it's highly suspect because of the nature of the change compared to other commits. In this ticket you have at least 4 instances of this bug being reproducible by different people including Ubuntu maintainers and several Cloud Operators that had entire clouds go completely offline and had to roll back to previous version of Ussuri AND Train. We're now all in holding patterns and unable to upgrade to this version or beyond as long as this code exists. I do believe that there could be something specific to Ubuntu deployments and this code as I see that this change was triggered by a RHEL bug ticket, so maybe the change fixed a problem for RHEL deployments but broke things for Ubuntu deployments. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
@Christian, sorry if it wasn't clear but I don't believe this is database migration related. @Rodolfo, At the very least the code that was written with timeout=3 is likely problematic and should have been at least made user configurable. It's quite possible this change is the culprit and breaks Ubuntu deployments. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
Our order of operations went as such: - All packages get updated to latest available Ussuri (16.3.1) for Bionic via apt-get dist-upgrade - Stop services (systemctl stop neutron-dhcp-agent; systemctl stop neutron-metadata-agent; systemctl stop neutron-ovs-cleanup; systemctl stop neutron-l3-agent; systemctl stop neutron-openvswitch-agent; systemctl stop neutron-server) - Upgrade database (neutron-db-manage current; neutron-db-manage upgrade heads) - Start services back up (systemctl start neutron-dhcp-agent; systemctl start neutron-metadata-agent; systemctl start neutron-ovs-cleanup; systemctl start neutron-l3-agent; systemctl start neutron-openvswitch-agent; systemctl start neutron-server) - All L3 agents for all routers elect to be down - Rebooted control plane several times while troubleshooting, L3 agents stay down - Found that 16.3.2 was available on staging repository, installed it, all L3 agents go to standby - Install 16.0.0 for Focal (all I could find during my scramble to fix the outage), L3 agents start to elect a master for each router - Later that week, re-attempt 16.3.1, all L3 agents go to standby - Find 16.2.0 for Bionic and downgrade to it, all L3 agents begin to elect masters -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
Ante: Thank you for the link to the 16.3.0 packages. We managed to find 16.2.0 before your post and are currently using them and it seems to be working fine for us. Should the opportunity arise we will install 16.3.0 since we've downloaded the deb files just in case. Billy: I guess the hunt continues for which commit introduced the bug, but I do see that this change '590551d' is a result of the following bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1929829 where this operator was complaining that his L3 agents would not enter active state. Coincidentally it may have fixed the issue for them, but introduced a bad bug on the Ubuntu side of things. Corey: It's reassuring that you were able to reproduce this bug. Thank you for your efforts! ** Bug watch added: Red Hat Bugzilla #1929829 https://bugzilla.redhat.com/show_bug.cgi?id=1929829 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
Hey Ubuntu team, Is there any way for you to provide the Neutron 16.3.0 packages for Bionic? We are in emergency mode here and the current 16.0.0 we are running, although working better than 16.3.1 is causing major control plane instability. We are in desperate need of 16.3.0 packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
OK, I did find evidence that this issue did begin to happen as we upgraded our Train packages just before we upgraded to Ussuri (I believe its best practice to update all packages, THEN upgrade to a new version of OpenStack) Upgraded Neutron 15.3.0 to 15.3.3 at 16:40 EDT 2021-06-10 16:40:40 upgrade neutron-l3-agent:all 2:15.3.0-0ubuntu1~cloud2 2:15.3.3-0ubuntu1~cloud0 Evidence of gateway problems at 17:06 EDT (Might have seen this in the logs several minutes earlier but I had to purge a lot of logs from that day because of the sheer volume of them) 2021-06-10 17:06:23.440 33440 ERROR neutron.agent.l3.ha_router [-] Gateway interface for router 04a5a2c3-739f-4cf6-94bb-dd314c2a8e66 was not set up; router will not work properly Upgraded from latest Train to latest Ussuri happened at 17:12 2021-06-10 17:12:31 upgrade neutron-l3-agent:all 2:15.3.3-0ubuntu1~cloud0 2:16.3.1-0ubuntu1~cloud0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
keepalived: 1:1.3.9-1ubuntu0.18.04.2 from: http://archive.ubuntu.com/ubuntu bionic-updates/main neutron-l3-agent.log filled with the following log lines for every single router in our cluster: 2021-06-10 19:59:53.602 328191 ERROR neutron.agent.l3.ha_router [-] Gateway interface for router 9f276b0e-8581-4312-8780-ff4503c3df07 was not set up; router will not work properly We have 3 controllers and use l3 HA and usually have 1 l3 agent per controller, 2 standby, 1 active. We rolled back to 16.0.0 (only because we could not find 16.3.0 anywhere) and the issue stopped. OP was able to roll back to 16.3.0 and said the issue went away so I think we should focus on 16.3.1+ Before upgrading to Ussuri we did briefly upgrade to the latest Train packages, give me some time to see if I can see if those error messages started when we were briefly on latest Train packages. I need to do some cross-referencing for that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
590551d [L3][HA] Retry when setting HA router GW status. I'm not a developer but this change does reflect the log error messages myself and the OP are seeing. https://github.com/openstack/neutron/commit/8f5a801270f81bd9fe3559fee9c1714c97849b3e -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
I was not able to roll back to 16.3.0 because they are not on any repositories that I could find so I had to manually download neutron debian files for focal and thankfully they seem to kind of work on Bionic Ussuri. We are now running 16.0.0~b3~git2020041516.5f42488a9a- 0ubuntu2 which is not ideal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
I don't think so. We don't even use DVR. Our observations were basically identical to OP's which was a telltale log entry 'Gateway interface for router 02945b59-639b-41be-8237-3b7933b4e32d was not set up; router will not work properly' and also that any Layer-3 agents for a router all remained in a standby state. None of them would ever go active. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
This bug appears to be present in 16.3.2 in the proposed repository 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/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
This is a terrible bug. 16.3.1 needs to be pulled from the repositories immediately. This will cause all Ussuri OpenStack deployments on Bionic to be completely down. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863392] Re: marco crashed with SIGSEGV in INT_cairo_region_num_rectangles()
This appears to have not been fixed in 1.24.0-1ubuntu1 on the latest 20.04. It happens at occasional times when I close a window. There are some similar recent reports on the github page: https://github.com/mate-desktop/marco/issues/617 https://github.com/mate-desktop/marco/issues/661 Here's a backtrace from the core dump: Core was generated by `marco'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f05e10699d4 in cairo_region_num_rectangles () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 [Current thread is 1 (Thread 0x7f05dfb5aa80 (LWP 454768))] (gdb) bt #0 0x7f05e10699d4 in cairo_region_num_rectangles () at /usr/lib/x86_64-linux-gnu/libcairo.so.2 #1 0x7f05e1d3541e in () at /usr/lib/x86_64-linux-gnu/libmarco-private.so.2 #2 0x7f05e1d37944 in () at /usr/lib/x86_64-linux-gnu/libmarco-private.so.2 #3 0x7f05e1d38b1e in () at /usr/lib/x86_64-linux-gnu/libmarco-private.so.2 #4 0x7f05e1d3a0c9 in () at /usr/lib/x86_64-linux-gnu/libmarco-private.so.2 #5 0x7f05e1d42b06 in () at /usr/lib/x86_64-linux-gnu/libmarco-private.so.2 #6 0x7f05e1d8cbb9 in () at /usr/lib/x86_64-linux-gnu/libmarco-private.so.2 #7 0x7f05e122405f in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #8 0x7f05e122444a in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #9 0x7f05e11ec0f4 in gdk_display_get_event () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #10 0x7f05e12240f6 in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #11 0x7f05e1e0af9d in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f05e1e0b220 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7f05e1e0b513 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x561e8df74233 in main () ** Bug watch added: github.com/mate-desktop/marco/issues #617 https://github.com/mate-desktop/marco/issues/617 ** Bug watch added: github.com/mate-desktop/marco/issues #661 https://github.com/mate-desktop/marco/issues/661 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863392 Title: marco crashed with SIGSEGV in INT_cairo_region_num_rectangles() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1863392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915188] Re: Secondary monitor enters power save mode for no apparent reason
** Also affects: dell-sputnik 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/1915188 Title: Secondary monitor enters power save mode for no apparent reason To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1915188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906073] Re: Syslog generates an error per second - appears to be related to Discord notification icons
Happened again this evening, I've got the log files but they're literally 80GB total, if you need them or want them let me know and I'll find a way to get them to you. ** Attachment added: "Screenshot from 2020-11-28 23-48-16.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1906073/+attachment/5439164/+files/Screenshot%20from%202020-11-28%2023-48-16.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906073 Title: Syslog generates an error per second - appears to be related to Discord notification icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1906073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906073] [NEW] Syslog generates an error per second - appears to be related to Discord notification icons
Public bug reported: My computer recently stopped booting due to a 50GB+ syslog file, so I've had the syslog open in a terminal to follow any errors that repeat. Whilst on a call to some friends I noticed that the following error would generate once per second within the syslog file: Nov 27 23:02:36 jared-MS-7930 ubuntu-appindicat...@ubuntu.com[2305]: discord1, Impossible to lookup icon for 'discord1_53-panel' Nov 27 23:02:36 jared-MS-7930 gnome-shell[2305]: JS ERROR: Exception in callback for signal: icon: Error: Argument 'filename' (type filename) may not be null#012_createIconByName@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:406:26#012_cacheOrCreateIconByName@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:368:14#012_updateIconByType@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:574:18#012_updateIcon@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:601:14#012_emit@resource:///org/gnome/gjs/modules/core/_signals.js:133:47#012_onPropertiesChanged/<@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:220:22#012_onPropertiesChanged@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:214:15#012refreshPropertyOnProxy/<@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/util.js:51:19 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33-1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 27 23:04:20 2020 InstallationDate: Installed on 2014-12-07 (2182 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: Upgraded to focal on 2020-09-29 (59 days ago) ** Affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906073 Title: Syslog generates an error per second - appears to be related to Discord notification icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1906073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905196] [NEW] Install fail on installing apt from cd while installing enso (i used liveusb)
Public bug reported: help ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.445.1 Date: Sun Nov 22 12:25:57 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz boot=casper file=/cdrom/preseed/xubuntu.seed quiet splash --- LiveMediaBuild: Enso 0.4 "Singing Sunflower" (20200925) 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 xubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905196 Title: Install fail on installing apt from cd while installing enso (i used liveusb) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1905196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Actually I was able to make it work! I needed to remove "options snd-hda-intel dmic_detect=0" from /etc/modprobe.d/alsa-base.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
This does not work for me. My Hardware Devices were listed as follows List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 Added to line to /etc/modprobe.d/alsa-base.conf and my internal microphone did not work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
I have the hp spectre x360 13 convertible and the update to 20.04 did not work for me either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1860303] Re: Backlight brightness cannot be adjusted using keys
Thank you! On Sun, Mar 22, 2020 at 11:45 PM Kai-Heng Feng wrote: > https://lkml.org/lkml/2020/3/23/29 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1860303 > > Title: > Backlight brightness cannot be adjusted using keys > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > I cannot adjust the screen brightness using the keyboard keys or > changing /sys/call/backlight/intel_backlight/brightness values. I've > only been able to adjust the backlight using xrandr. > > Followed bug report on > https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques > and attached files. Additional information: > 1. echo 8 > /sys/class/backlight/intel_backlight/brightness does not > change the screen brightness > 2. video.use_bios_initial_backlight=0 does not enable brightness to be > changed > 3. Cannot login to when using kernel paramater acpi_osi=. Login does not > work and on one boot "y"s were being continuously typed without any keys > being depressed. It was odd. > 4. video.use_native_backlight=1 does not enabel brightness to be changed > 5. Created file /usr/share/X11/xorg.conf.d/80-backlight.conf and it had > no impact > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: linux-image-5.3.0-26-generic 5.3.0-26.28 > ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 > Uname: Linux 5.3.0-26-generic x86_64 > ApportVersion: 2.20.11-0ubuntu8.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: jaredy 1649 F pulseaudio >/dev/snd/pcmC0D0p: jaredy 1649 F...m pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Sun Jan 19 19:51:45 2020 > InstallationDate: Installed on 2020-01-03 (16 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > MachineType: HP HP Spectre x360 Convertible 13t-aw100 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic > root=UUID=5f505587-b59b-4abd-b8f2-28c04ab84c64 ro quiet splash > acpi_backlight=vendor vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-5.3.0-26-generic N/A >linux-backports-modules-5.3.0-26-generic N/A >linux-firmware1.183.3 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 11/15/2019 > dmi.bios.vendor: AMI > dmi.bios.version: F.10 > dmi.board.asset.tag: Base Board Asset Tag > dmi.board.name: 86FA > dmi.board.vendor: HP > dmi.board.version: 87.43 > dmi.chassis.type: 31 > dmi.chassis.vendor: HP > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnAMI:bvrF.10:bd11/15/2019:svnHP:pnHPSpectrex360Convertible13t-aw100:pvr:rvnHP:rn86FA:rvr87.43:cvnHP:ct31:cvrChassisVersion: > dmi.product.family: 103C_5335KV HP Spectre > dmi.product.name: HP Spectre x360 Convertible 13t-aw100 > dmi.product.sku: 6YG70AV > dmi.sys.vendor: HP > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860303/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860303 Title: Backlight brightness cannot be adjusted using keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1860303] Re: Backlight brightness cannot be adjusted using keys
It works! Keyboard keys adjust brightness and I found no obvious issues otherwise dmesg attached for reference On Fri, Mar 13, 2020 at 1:10 PM Kai-Heng Feng wrote: > Can you please test this kernel: > https://people.canonical.com/~khfeng/lp1860303/ > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1860303 > > Title: > Backlight brightness cannot be adjusted using keys > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > I cannot adjust the screen brightness using the keyboard keys or > changing /sys/call/backlight/intel_backlight/brightness values. I've > only been able to adjust the backlight using xrandr. > > Followed bug report on > https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques > and attached files. Additional information: > 1. echo 8 > /sys/class/backlight/intel_backlight/brightness does not > change the screen brightness > 2. video.use_bios_initial_backlight=0 does not enable brightness to be > changed > 3. Cannot login to when using kernel paramater acpi_osi=. Login does not > work and on one boot "y"s were being continuously typed without any keys > being depressed. It was odd. > 4. video.use_native_backlight=1 does not enabel brightness to be changed > 5. Created file /usr/share/X11/xorg.conf.d/80-backlight.conf and it had > no impact > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: linux-image-5.3.0-26-generic 5.3.0-26.28 > ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 > Uname: Linux 5.3.0-26-generic x86_64 > ApportVersion: 2.20.11-0ubuntu8.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: jaredy 1649 F pulseaudio >/dev/snd/pcmC0D0p: jaredy 1649 F...m pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Sun Jan 19 19:51:45 2020 > InstallationDate: Installed on 2020-01-03 (16 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > MachineType: HP HP Spectre x360 Convertible 13t-aw100 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic > root=UUID=5f505587-b59b-4abd-b8f2-28c04ab84c64 ro quiet splash > acpi_backlight=vendor vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-5.3.0-26-generic N/A >linux-backports-modules-5.3.0-26-generic N/A >linux-firmware1.183.3 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 11/15/2019 > dmi.bios.vendor: AMI > dmi.bios.version: F.10 > dmi.board.asset.tag: Base Board Asset Tag > dmi.board.name: 86FA > dmi.board.vendor: HP > dmi.board.version: 87.43 > dmi.chassis.type: 31 > dmi.chassis.vendor: HP > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnAMI:bvrF.10:bd11/15/2019:svnHP:pnHPSpectrex360Convertible13t-aw100:pvr:rvnHP:rn86FA:rvr87.43:cvnHP:ct31:cvrChassisVersion: > dmi.product.family: 103C_5335KV HP Spectre > dmi.product.name: HP Spectre x360 Convertible 13t-aw100 > dmi.product.sku: 6YG70AV > dmi.sys.vendor: HP > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860303/+subscriptions > ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/bugs/1860303/+attachment/5340241/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860303 Title: Backlight brightness cannot be adjusted using keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1860303] Re: Backlight brightness cannot be adjusted using keys
Is this what you need? On Mon, Mar 9, 2020 at 7:25 AM Kai-Heng Feng wrote: > Please test latest drm-tip kernel with kernel parameter "drm.debug=0xe" > and attach dmesg: > https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1860303 > > Title: > Backlight brightness cannot be adjusted using keys > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > I cannot adjust the screen brightness using the keyboard keys or > changing /sys/call/backlight/intel_backlight/brightness values. I've > only been able to adjust the backlight using xrandr. > > Followed bug report on > https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques > and attached files. Additional information: > 1. echo 8 > /sys/class/backlight/intel_backlight/brightness does not > change the screen brightness > 2. video.use_bios_initial_backlight=0 does not enable brightness to be > changed > 3. Cannot login to when using kernel paramater acpi_osi=. Login does not > work and on one boot "y"s were being continuously typed without any keys > being depressed. It was odd. > 4. video.use_native_backlight=1 does not enabel brightness to be changed > 5. Created file /usr/share/X11/xorg.conf.d/80-backlight.conf and it had > no impact > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: linux-image-5.3.0-26-generic 5.3.0-26.28 > ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 > Uname: Linux 5.3.0-26-generic x86_64 > ApportVersion: 2.20.11-0ubuntu8.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: jaredy 1649 F pulseaudio >/dev/snd/pcmC0D0p: jaredy 1649 F...m pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Sun Jan 19 19:51:45 2020 > InstallationDate: Installed on 2020-01-03 (16 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > MachineType: HP HP Spectre x360 Convertible 13t-aw100 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic > root=UUID=5f505587-b59b-4abd-b8f2-28c04ab84c64 ro quiet splash > acpi_backlight=vendor vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-5.3.0-26-generic N/A >linux-backports-modules-5.3.0-26-generic N/A >linux-firmware1.183.3 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 11/15/2019 > dmi.bios.vendor: AMI > dmi.bios.version: F.10 > dmi.board.asset.tag: Base Board Asset Tag > dmi.board.name: 86FA > dmi.board.vendor: HP > dmi.board.version: 87.43 > dmi.chassis.type: 31 > dmi.chassis.vendor: HP > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnAMI:bvrF.10:bd11/15/2019:svnHP:pnHPSpectrex360Convertible13t-aw100:pvr:rvnHP:rn86FA:rvr87.43:cvnHP:ct31:cvrChassisVersion: > dmi.product.family: 103C_5335KV HP Spectre > dmi.product.name: HP Spectre x360 Convertible 13t-aw100 > dmi.product.sku: 6YG70AV > dmi.sys.vendor: HP > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860303/+subscriptions > ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/bugs/1860303/+attachment/5336385/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860303 Title: Backlight brightness cannot be adjusted using keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1860303] Re: Backlight brightness cannot be adjusted using keys
I got it figured out and the kernel at https://people.canonical.com/~acelan/bugs/lp1861521/ did not fix the issue. On Fri, Mar 6, 2020 at 7:48 PM Jared Young wrote: > I installed from the .deb files and this did not make a difference for the > backlight, however the volume keys on the keyboard no longer work. > > I am not experienced in testing different kernels so it is possible that I > messed up the install. I did not apply the .patch files. > > > On Tue, Mar 3, 2020 at 11:50 PM Kai-Heng Feng > wrote: > >> Can you please test kernel here: >> https://people.canonical.com/~acelan/bugs/lp1861521/ >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1860303 >> >> Title: >> Backlight brightness cannot be adjusted using keys >> >> Status in linux package in Ubuntu: >> Incomplete >> >> Bug description: >> I cannot adjust the screen brightness using the keyboard keys or >> changing /sys/call/backlight/intel_backlight/brightness values. I've >> only been able to adjust the backlight using xrandr. >> >> Followed bug report on >> https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques >> and attached files. Additional information: >> 1. echo 8 > /sys/class/backlight/intel_backlight/brightness does not >> change the screen brightness >> 2. video.use_bios_initial_backlight=0 does not enable brightness to be >> changed >> 3. Cannot login to when using kernel paramater acpi_osi=. Login does >> not work and on one boot "y"s were being continuously typed without any >> keys being depressed. It was odd. >> 4. video.use_native_backlight=1 does not enabel brightness to be changed >> 5. Created file /usr/share/X11/xorg.conf.d/80-backlight.conf and it had >> no impact >> >> ProblemType: Bug >> DistroRelease: Ubuntu 19.10 >> Package: linux-image-5.3.0-26-generic 5.3.0-26.28 >> ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 >> Uname: Linux 5.3.0-26-generic x86_64 >> ApportVersion: 2.20.11-0ubuntu8.2 >> Architecture: amd64 >> AudioDevicesInUse: >>USERPID ACCESS COMMAND >>/dev/snd/controlC0: jaredy 1649 F pulseaudio >>/dev/snd/pcmC0D0p: jaredy 1649 F...m pulseaudio >> CurrentDesktop: ubuntu:GNOME >> Date: Sun Jan 19 19:51:45 2020 >> InstallationDate: Installed on 2020-01-03 (16 days ago) >> InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) >> MachineType: HP HP Spectre x360 Convertible 13t-aw100 >> ProcEnviron: >>TERM=xterm-256color >>PATH=(custom, no user) >>XDG_RUNTIME_DIR= >>LANG=en_US.UTF-8 >>SHELL=/bin/bash >> ProcFB: 0 i915drmfb >> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic >> root=UUID=5f505587-b59b-4abd-b8f2-28c04ab84c64 ro quiet splash >> acpi_backlight=vendor vt.handoff=7 >> RelatedPackageVersions: >>linux-restricted-modules-5.3.0-26-generic N/A >>linux-backports-modules-5.3.0-26-generic N/A >>linux-firmware1.183.3 >> SourcePackage: linux >> UpgradeStatus: No upgrade log present (probably fresh install) >> dmi.bios.date: 11/15/2019 >> dmi.bios.vendor: AMI >> dmi.bios.version: F.10 >> dmi.board.asset.tag: Base Board Asset Tag >> dmi.board.name: 86FA >> dmi.board.vendor: HP >> dmi.board.version: 87.43 >> dmi.chassis.type: 31 >> dmi.chassis.vendor: HP >> dmi.chassis.version: Chassis Version >> dmi.modalias: >> dmi:bvnAMI:bvrF.10:bd11/15/2019:svnHP:pnHPSpectrex360Convertible13t-aw100:pvr:rvnHP:rn86FA:rvr87.43:cvnHP:ct31:cvrChassisVersion: >> dmi.product.family: 103C_5335KV HP Spectre >> dmi.product.name: HP Spectre x360 Convertible 13t-aw100 >> dmi.product.sku: 6YG70AV >> dmi.sys.vendor: HP >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860303/+subscriptions >> > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860303 Title: Backlight brightness cannot be adjusted using keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1860303] Re: Backlight brightness cannot be adjusted using keys
I installed from the .deb files and this did not make a difference for the backlight, however the volume keys on the keyboard no longer work. I am not experienced in testing different kernels so it is possible that I messed up the install. I did not apply the .patch files. On Tue, Mar 3, 2020 at 11:50 PM Kai-Heng Feng wrote: > Can you please test kernel here: > https://people.canonical.com/~acelan/bugs/lp1861521/ > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1860303 > > Title: > Backlight brightness cannot be adjusted using keys > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > I cannot adjust the screen brightness using the keyboard keys or > changing /sys/call/backlight/intel_backlight/brightness values. I've > only been able to adjust the backlight using xrandr. > > Followed bug report on > https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques > and attached files. Additional information: > 1. echo 8 > /sys/class/backlight/intel_backlight/brightness does not > change the screen brightness > 2. video.use_bios_initial_backlight=0 does not enable brightness to be > changed > 3. Cannot login to when using kernel paramater acpi_osi=. Login does not > work and on one boot "y"s were being continuously typed without any keys > being depressed. It was odd. > 4. video.use_native_backlight=1 does not enabel brightness to be changed > 5. Created file /usr/share/X11/xorg.conf.d/80-backlight.conf and it had > no impact > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: linux-image-5.3.0-26-generic 5.3.0-26.28 > ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 > Uname: Linux 5.3.0-26-generic x86_64 > ApportVersion: 2.20.11-0ubuntu8.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: jaredy 1649 F pulseaudio >/dev/snd/pcmC0D0p: jaredy 1649 F...m pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Sun Jan 19 19:51:45 2020 > InstallationDate: Installed on 2020-01-03 (16 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > MachineType: HP HP Spectre x360 Convertible 13t-aw100 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic > root=UUID=5f505587-b59b-4abd-b8f2-28c04ab84c64 ro quiet splash > acpi_backlight=vendor vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-5.3.0-26-generic N/A >linux-backports-modules-5.3.0-26-generic N/A >linux-firmware1.183.3 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 11/15/2019 > dmi.bios.vendor: AMI > dmi.bios.version: F.10 > dmi.board.asset.tag: Base Board Asset Tag > dmi.board.name: 86FA > dmi.board.vendor: HP > dmi.board.version: 87.43 > dmi.chassis.type: 31 > dmi.chassis.vendor: HP > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnAMI:bvrF.10:bd11/15/2019:svnHP:pnHPSpectrex360Convertible13t-aw100:pvr:rvnHP:rn86FA:rvr87.43:cvnHP:ct31:cvrChassisVersion: > dmi.product.family: 103C_5335KV HP Spectre > dmi.product.name: HP Spectre x360 Convertible 13t-aw100 > dmi.product.sku: 6YG70AV > dmi.sys.vendor: HP > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860303/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860303 Title: Backlight brightness cannot be adjusted using keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1860303] Re: Backlight brightness cannot be adjusted using keys
There are no extensions or scripts that I have installed to handle the backlight. I did not include acpi_backlight=vendor as a kernel parameter at the same time as i915.enable_dpcd_backlight=1. The only kernel parameters currently are "i915.enable_dpcd_backlight=1 quiet splash". Should I try both backlight parameters at the same time? On Thu, Feb 13, 2020 at 10:05 PM Kai-Heng Feng wrote: > What if acpi_backlight=vendor is removed? Is there any extension or > script installed to handle the backlight? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1860303 > > Title: > Backlight brightness cannot be adjusted using keys > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > I cannot adjust the screen brightness using the keyboard keys or > changing /sys/call/backlight/intel_backlight/brightness values. I've > only been able to adjust the backlight using xrandr. > > Followed bug report on > https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques > and attached files. Additional information: > 1. echo 8 > /sys/class/backlight/intel_backlight/brightness does not > change the screen brightness > 2. video.use_bios_initial_backlight=0 does not enable brightness to be > changed > 3. Cannot login to when using kernel paramater acpi_osi=. Login does not > work and on one boot "y"s were being continuously typed without any keys > being depressed. It was odd. > 4. video.use_native_backlight=1 does not enabel brightness to be changed > 5. Created file /usr/share/X11/xorg.conf.d/80-backlight.conf and it had > no impact > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: linux-image-5.3.0-26-generic 5.3.0-26.28 > ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 > Uname: Linux 5.3.0-26-generic x86_64 > ApportVersion: 2.20.11-0ubuntu8.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: jaredy 1649 F pulseaudio >/dev/snd/pcmC0D0p: jaredy 1649 F...m pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Sun Jan 19 19:51:45 2020 > InstallationDate: Installed on 2020-01-03 (16 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > MachineType: HP HP Spectre x360 Convertible 13t-aw100 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic > root=UUID=5f505587-b59b-4abd-b8f2-28c04ab84c64 ro quiet splash > acpi_backlight=vendor vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-5.3.0-26-generic N/A >linux-backports-modules-5.3.0-26-generic N/A >linux-firmware1.183.3 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 11/15/2019 > dmi.bios.vendor: AMI > dmi.bios.version: F.10 > dmi.board.asset.tag: Base Board Asset Tag > dmi.board.name: 86FA > dmi.board.vendor: HP > dmi.board.version: 87.43 > dmi.chassis.type: 31 > dmi.chassis.vendor: HP > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnAMI:bvrF.10:bd11/15/2019:svnHP:pnHPSpectrex360Convertible13t-aw100:pvr:rvnHP:rn86FA:rvr87.43:cvnHP:ct31:cvrChassisVersion: > dmi.product.family: 103C_5335KV HP Spectre > dmi.product.name: HP Spectre x360 Convertible 13t-aw100 > dmi.product.sku: 6YG70AV > dmi.sys.vendor: HP > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860303/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860303 Title: Backlight brightness cannot be adjusted using keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1860303] Re: Backlight brightness cannot be adjusted using keys
This kernel parameter does make the backlight respond to keyboard input, as well as manually changing the brightness values in `/sys/class/backlight/intel_backlight/brightness`. However the behavior is odd. Adjusting the brightness using the keyboard results in erratic changes rather than a smooth change in brightness. The brightness settings appear to range between 655 and 65535 in `/sys/class/backlight/intel_backlight/brightness` when using the keyboard keys. However, the max screen brightness appears to be at 2047 when manually setting a brightness value in `/sys/class/backlight/intel_backlight/brightness`. On Thu, Feb 13, 2020 at 12:30 AM Kai-Heng Feng wrote: > Does kernel parameter "i915.enable_dpcd_backlight=1" help? > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1860303 > > Title: > Backlight brightness cannot be adjusted using keys > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > I cannot adjust the screen brightness using the keyboard keys or > changing /sys/call/backlight/intel_backlight/brightness values. I've > only been able to adjust the backlight using xrandr. > > Followed bug report on > https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques > and attached files. Additional information: > 1. echo 8 > /sys/class/backlight/intel_backlight/brightness does not > change the screen brightness > 2. video.use_bios_initial_backlight=0 does not enable brightness to be > changed > 3. Cannot login to when using kernel paramater acpi_osi=. Login does not > work and on one boot "y"s were being continuously typed without any keys > being depressed. It was odd. > 4. video.use_native_backlight=1 does not enabel brightness to be changed > 5. Created file /usr/share/X11/xorg.conf.d/80-backlight.conf and it had > no impact > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: linux-image-5.3.0-26-generic 5.3.0-26.28 > ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 > Uname: Linux 5.3.0-26-generic x86_64 > ApportVersion: 2.20.11-0ubuntu8.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: jaredy 1649 F pulseaudio >/dev/snd/pcmC0D0p: jaredy 1649 F...m pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Sun Jan 19 19:51:45 2020 > InstallationDate: Installed on 2020-01-03 (16 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > MachineType: HP HP Spectre x360 Convertible 13t-aw100 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic > root=UUID=5f505587-b59b-4abd-b8f2-28c04ab84c64 ro quiet splash > acpi_backlight=vendor vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-5.3.0-26-generic N/A >linux-backports-modules-5.3.0-26-generic N/A >linux-firmware1.183.3 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 11/15/2019 > dmi.bios.vendor: AMI > dmi.bios.version: F.10 > dmi.board.asset.tag: Base Board Asset Tag > dmi.board.name: 86FA > dmi.board.vendor: HP > dmi.board.version: 87.43 > dmi.chassis.type: 31 > dmi.chassis.vendor: HP > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnAMI:bvrF.10:bd11/15/2019:svnHP:pnHPSpectrex360Convertible13t-aw100:pvr:rvnHP:rn86FA:rvr87.43:cvnHP:ct31:cvrChassisVersion: > dmi.product.family: 103C_5335KV HP Spectre > dmi.product.name: HP Spectre x360 Convertible 13t-aw100 > dmi.product.sku: 6YG70AV > dmi.sys.vendor: HP > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860303/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860303 Title: Backlight brightness cannot be adjusted using keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1860303] Re: Backlight brightness cannot be adjusted using keys
Yes. AMOLED multitouch (3840 x 2160) panel On Tue, Feb 4, 2020, 1:06 AM Kai-Heng Feng wrote: > Is it an OLED panel? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1860303 > > Title: > Backlight brightness cannot be adjusted using keys > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > I cannot adjust the screen brightness using the keyboard keys or > changing /sys/call/backlight/intel_backlight/brightness values. I've > only been able to adjust the backlight using xrandr. > > Followed bug report on > https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques > and attached files. Additional information: > 1. echo 8 > /sys/class/backlight/intel_backlight/brightness does not > change the screen brightness > 2. video.use_bios_initial_backlight=0 does not enable brightness to be > changed > 3. Cannot login to when using kernel paramater acpi_osi=. Login does not > work and on one boot "y"s were being continuously typed without any keys > being depressed. It was odd. > 4. video.use_native_backlight=1 does not enabel brightness to be changed > 5. Created file /usr/share/X11/xorg.conf.d/80-backlight.conf and it had > no impact > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: linux-image-5.3.0-26-generic 5.3.0-26.28 > ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 > Uname: Linux 5.3.0-26-generic x86_64 > ApportVersion: 2.20.11-0ubuntu8.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: jaredy 1649 F pulseaudio >/dev/snd/pcmC0D0p: jaredy 1649 F...m pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Sun Jan 19 19:51:45 2020 > InstallationDate: Installed on 2020-01-03 (16 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > MachineType: HP HP Spectre x360 Convertible 13t-aw100 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic > root=UUID=5f505587-b59b-4abd-b8f2-28c04ab84c64 ro quiet splash > acpi_backlight=vendor vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-5.3.0-26-generic N/A >linux-backports-modules-5.3.0-26-generic N/A >linux-firmware1.183.3 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 11/15/2019 > dmi.bios.vendor: AMI > dmi.bios.version: F.10 > dmi.board.asset.tag: Base Board Asset Tag > dmi.board.name: 86FA > dmi.board.vendor: HP > dmi.board.version: 87.43 > dmi.chassis.type: 31 > dmi.chassis.vendor: HP > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnAMI:bvrF.10:bd11/15/2019:svnHP:pnHPSpectrex360Convertible13t-aw100:pvr:rvnHP:rn86FA:rvr87.43:cvnHP:ct31:cvrChassisVersion: > dmi.product.family: 103C_5335KV HP Spectre > dmi.product.name: HP Spectre x360 Convertible 13t-aw100 > dmi.product.sku: 6YG70AV > dmi.sys.vendor: HP > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860303/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860303 Title: Backlight brightness cannot be adjusted using keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860303] [NEW] Backlight brightness cannot be adjusted using keys
Public bug reported: I cannot adjust the screen brightness using the keyboard keys or changing /sys/call/backlight/intel_backlight/brightness values. I've only been able to adjust the backlight using xrandr. Followed bug report on https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques and attached files. Additional information: 1. echo 8 > /sys/class/backlight/intel_backlight/brightness does not change the screen brightness 2. video.use_bios_initial_backlight=0 does not enable brightness to be changed 3. Cannot login to when using kernel paramater acpi_osi=. Login does not work and on one boot "y"s were being continuously typed without any keys being depressed. It was odd. 4. video.use_native_backlight=1 does not enabel brightness to be changed 5. Created file /usr/share/X11/xorg.conf.d/80-backlight.conf and it had no impact ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaredy 1649 F pulseaudio /dev/snd/pcmC0D0p: jaredy 1649 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jan 19 19:51:45 2020 InstallationDate: Installed on 2020-01-03 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 13t-aw100 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=5f505587-b59b-4abd-b8f2-28c04ab84c64 ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2019 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FA dmi.board.vendor: HP dmi.board.version: 87.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.10:bd11/15/2019:svnHP:pnHPSpectrex360Convertible13t-aw100:pvr:rvnHP:rn86FA:rvr87.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13t-aw100 dmi.product.sku: 6YG70AV dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Bug report following guidance on https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques; https://bugs.launchpad.net/bugs/1860303/+attachment/5321620/+files/backlight%20bug%20report.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860303 Title: Backlight brightness cannot be adjusted using keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845246] Re: Failed to import plugin clustering
Installed python3-senlinclient from stein-proposed root@lab-controller:~# apt-cache policy python3-senlinclient python3-senlinclient: Installed: 1.9.0-0ubuntu1~cloud0 Candidate: 1.9.0-0ubuntu1~cloud0 Version table: *** 1.9.0-0ubuntu1~cloud0 500 500 http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-proposed/stein/main amd64 Packages 100 /var/lib/dpkg/status 1.7.0-0ubuntu2 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages Cluster warning is now gone! root@lab-controller:~# openstack image list +--+-++ | ID | Name| Status | +--+-++ | d3de179b-96b6-4cb5-835d-a36d3d1a6169 | cirros-good | active | +--+-++ root@lab-controller:~# openstack network list +--+---+--+ | ID | Name | Subnets | +--+---+--+ | 0f93a695-7a26-4835-903c-f7c55aceba17 | collaboratory_network | 2ba49081-89b4-4cc3-9189-ee4d46550b60 | | 1513a1a7-df84-448e-ae7e-8e6ec4fbe328 | cheeseburgers | 4badc741-5d50-4fc4-a600-b47b69ecee8e | | 5d2fa413-6ce5-43d4-aa2d-646025185eb8 | lab_network | 4ef39d3f-2e81-424b-89c7-611979c9aaa1 | +--+---+--+ Thank you Corey -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845246 Title: Failed to import plugin clustering To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1845246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845246] Re: Failed to import plugin clustering
Hi Corey, Looks like python3-senlinclient is already installed (but we dont use senlin). I would remove it but it wants to pull out all the openstack heat packages, which we use. root@lab-controller:~# dpkg -l | grep -i python3 | grep -i client ii python3-amqp 2.4.0-1~cloud0 all Low-level AMQP client (Python3 version) ii python3-aodhclient1.0.0-0ubuntu1 all OpenStack Alarming as a Service - Python 3.x client ii python3-barbicanclient4.6.0-0ubuntu1 all OpenStack Key Management API client - Python 3.x ii python3-blazarclient 2.1.0-0ubuntu1~cloud0 all OpenStack Reservation Service API client - Python 3 ii python3-ceilometerclient 2.9.0-0ubuntu1 all Client library for Openstack Ceilometer API server - Python 3.x ii python3-cinderclient 1:4.1.0-0ubuntu1~cloud0 all Python bindings to the OpenStack Volume API - Python 3.x ii python3-designateclient 2.9.0-0ubuntu1 all client library for the OpenStack Designate API - Python 3.x ii python3-glanceclient 1:2.16.0-0ubuntu1~cloud0 all Client library for Openstack glance server - Python 3.x ii python3-gnocchiclient 7.0.1-0ubuntu1 all bindings to the OpenStack Gnocchi API - Python 3.x ii python3-heatclient1.17.0-0ubuntu1~cloud0 all client library and CLI for OpenStack Heat - Python 3.x ii python3-httplib2 0.9.2+dfsg-1ubuntu0.1 all comprehensive HTTP client library written for Python3 ii python3-keystoneclient1:3.19.0-0ubuntu1~cloud0 all client library for the OpenStack Keystone API - Python 3.x ii python3-magnumclient 2.8.0-0ubuntu1 all client library for Magnum API - Python 3.x ii python3-manilaclient 1.27.0-0ubuntu1~cloud0 all OpenStack shared file system as a service - Python 3.x client ii python3-memcache 1.59-1~cloud0 all pure Python memcached client - Python 3.x ii python3-mistralclient 1:3.3.0-0ubuntu1 all OpenStack Workflow as a Service client - Python 3.x ii python3-monascaclient 1.14.0-0ubuntu1~cloud0 all client bindings for the Monasca API - Python 3.x ii python3-neutronclient 1:6.7.0-0ubuntu1 all client API library for Neutron - Python 3.x ii python3-novaclient2:13.0.0-0ubuntu1~cloud0 all client library for OpenStack Compute API - 3.x ii python3-octaviaclient 1.8.0-0ubuntu1~cloud0 all Octavia client for OpenStack Load Balancing - Python 3.x ii python3-openstackclient 3.18.0-0ubuntu1~cloud0 all OpenStack Command-line Client - Python 3.x ii python3-os-client-config 1.29.0-0ubuntu1 all OpenStack client configuration library - Python 3.x ii python3-osc-lib 1.12.1-0ubuntu1~cloud0 all OpenStackClient Library - Python 3.x ii python3-pymemcache1.3.2-3 all comprehensive, fast, pure Python memcached client - Python 3.x ii python3-saharaclient 2.2.0-0ubuntu1~cloud0 all Client library for Openstack Sahara API server - Python 3.x module ii python3-senlinclient 1.7.0-0ubuntu2 all OpenStack Clustering API Client Library - Python 3.x ii python3-statsd3.2.1-2 all Python client for the statsd daemon (Python 3) ii python3-suds 0.7~git20150727.94664dd-5 all Lightweight SOAP client for Python - Python 3.x ii python3-swiftclient 1:3.7.0-0ubuntu1~cloud0 all Client library for Openstack Swift API - Python 3.x ii python3-troveclient 1:2.14.0-0ubuntu1 all Client for OpenStack Database as a Service - Python 3.x ii python3-zaqarclient 1.9.0-0ubuntu1 all OpenStack Zaqar Queueing API, client and library - Python 3.x root@lab-controller:~#
[Bug 1845246] [NEW] Failed to import plugin clustering
Public bug reported: When running any openstack client command I am provided with the following error, including the correct output of the command. Example: openstack image list WARNING: Failed to import plugin clustering. +--+-++ | ID | Name| Status | +--+-++ | e7180a98-9630-4128-a457-48b272d819bb | cirros | active | | d3de179b-96b6-4cb5-835d-a36d3d1a6169 | cirros-good | active | +--+-++ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 openstack --version WARNING: Failed to import plugin clustering. openstack 3.18.0 dpkg -l | grep python3-openstackclient ii python3-openstackclient 3.18.0-0ubuntu1~cloud0 all OpenStack Command-line Client - Python 3.x ** Affects: python-openstackclient (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845246 Title: Failed to import plugin clustering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-openstackclient/+bug/1845246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659620] Re: Panels get broken with COMPRESS_OFFLINE = True
Running Ubuntu 18.04 with openstack-dashboard 14.0.3-0ubuntu1~cloud0 and having issues with certain modals not working (create object container, create keypair, upload keypair, create server group) all popping up as blank modals. This has been a chronic issue for us for Ubuntu 16.04 and also 18.04 spanning multiple OpenStack releases but when we first upgraded to Rocky these issues were gone. We did not seem to have any issues with openstack-dashboard 14.0.2-0ubuntu4~cloud0 and this was very surprising to see however we recently upgraded to 14.0.3-0ubuntu1~cloud0 and we are now having these issues with broken modals again. The problem seems to be related to what your memcached configuration is in /etc/openstack-dashboard/local_settings.py although I have not been able to pinpoint what exactly is the relationship between memcached and the collectstatic/compress operations building good or bad javascript. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659620 Title: Panels get broken with COMPRESS_OFFLINE = True To manage notifications about this bug go to: https://bugs.launchpad.net/designate-dashboard/+bug/1659620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830493] [NEW] package sendmail-bin 8.15.2-12 failed to install/upgrade: installed sendmail-bin package post-installation script subprocess returned error exit status 2
*** This bug is a duplicate of bug 1822866 *** https://bugs.launchpad.net/bugs/1822866 Public bug reported: Failed upgrade to Disco due to sendmail ProblemType: Package DistroRelease: Ubuntu 19.04 Package: sendmail-bin 8.15.2-12 ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Sat May 25 13:39:39 2019 ErrorMessage: installed sendmail-bin package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2015-07-26 (1399 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.1 SourcePackage: sendmail Title: package sendmail-bin 8.15.2-12 failed to install/upgrade: installed sendmail-bin package post-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to disco on 2019-05-25 (0 days ago) ** Affects: sendmail (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830493 Title: package sendmail-bin 8.15.2-12 failed to install/upgrade: installed sendmail-bin package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sendmail/+bug/1830493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749102] Re: Missing tmux dependency
Fixed in version 1.14-1.1 which will be shipped in Ubuntu Disco. ** Changed in: hollywood (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749102 Title: Missing tmux dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hollywood/+bug/1749102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635589] Re: man page contains unfinished sentence
Not present in Ubuntu Cosmic. Marking fixed. ** Changed in: hollywood (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635589 Title: man page contains unfinished sentence To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hollywood/+bug/1635589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666853] Re: grub-probe fail when fs is larger than 2tb
Possibly related bugs: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1812411 https://bugs.launchpad.net/cloud-utils/+bug/1762748 We run an OpenStack cloud and provide very large instances to our users and noticed that there was possibly a breaking change made in 1762748 which resulted in my new bug submission 1812411. I'd be happy to help test this issue as it is easily reproducible in my environment. Thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666853 Title: grub-probe fail when fs is larger than 2tb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1666853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812411] Re: cloud-init corrupting grub
Hi Scott, Yes probably related bugs for sure. Again, I'd be happy to help test a fix if one is developed as I'm able to easily reproduce this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812411 Title: cloud-init corrupting grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1812411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812411] [NEW] cloud-init corrupting grub
Public bug reported: I believe I have discovered problems in the *recent builds* of Ubuntu 14.04 and 16.04 (NO ISSUE with 18.04 or OLDER 14.04/16.04 builds) cloud images (https://cloud-images.ubuntu.com/) for instances with very large local disks. We are using OpenStack Queens on Ubuntu 16.04 and have noticed that when our users deploy our largest instance type with ~5TB local disk that the VM deploys but when that VM is rebooted for the first time it wont boot and becomes stuck at the 'grub rescue' prompt with 'error: unknown filesystem.'. I believe the issue is happening in the growpart function of cloud-init of the first boot of the VM to grow the root partition to fit the large local disk. I have attached as much logging and output information from 14.04, 16.04 and 18.04 but I do not have a developer background so I can't pinpoint the issue entirely. I am able to easily reproduce this issue and would happy to help with the resolution of this bug in any capacity. Thank you! ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Attachment added: "ubuntu-logs-screenshot.zip" https://bugs.launchpad.net/bugs/1812411/+attachment/5230331/+files/ubuntu-logs-screenshot.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812411 Title: cloud-init corrupting grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1812411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790432] Re: skilion base repo appears abandonded; recommend rebase to abraunegg fork
apt does not reflect this information. ~$ date +"%Y-%m-%d %T %Z" 2018-12-07 14:37:20 EST ~$ apt show onedrive Package: onedrive Version: 1.1.20180922~really1.1.3-1 Priority: optional Section: universe/net Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Norbert Preining Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 1,089 kB Depends: libc6 (>= 2.14), libgcc1 (>= 1:3.0), libphobos2-ldc-shared81 (>= 1:1.11.0), libsqlite3-0 (>= 3.7.15) Homepage: http://skilion.github.io/onedrive/ Download-Size: 255 kB APT-Sources: http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages Description: folder synchronization with OneDrive OneDrive is the cloud storage system of Microsoft. This package provides the command line client specialising in synchronizing with OneDrive cloud storage. ~$ onedrive --version onedrive v1.1.3 Currently apt shows version 1.1.20180922~really1.1.3-1 which is on par with the skilion release https://github.com/skilion/onedrive/releases. However https://github.com/abraunegg/onedrive/releases shows the current release is 2.2.1 from 4 days ago. The 2.x series was released 2018-07-10. All signs point to the package pointing to skilion and not abraunegg, including the software from the repo itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790432 Title: skilion base repo appears abandonded; recommend rebase to abraunegg fork To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onedrive/+bug/1790432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1411875] Re: I am unable to get desktop for ubuntu 14.04. sa-compile fails with exit 2.
** Changed in: spamassassin (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1411875 Title: I am unable to get desktop for ubuntu 14.04. sa-compile fails with exit 2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1411875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802017] Re: Error in v342.pre Config File Causes sa-compile Crash
** Description changed: In the spamassassin config file: /etc/mail/spamassassin/v342.pre, the line: parse_dkim_uris 1 - Under the comment "allow URI rules to look at DKIM headers if they + under the comment "allow URI rules to look at DKIM headers if they exist" causes a syntax error and for sa-compile to quit. System Information: --- Description:Ubuntu 18.04.1 LTS Release:18.04 sa-compile: - Installed: 3.4.2-0ubuntu0.18.04.1 - Candidate: 3.4.2-0ubuntu0.18.04.1 - Version table: - *** 3.4.2-0ubuntu0.18.04.1 500 - 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages - 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages - 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages - 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages - 100 /var/lib/dpkg/status - 3.4.1-8build1 500 - 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages - 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages + Installed: 3.4.2-0ubuntu0.18.04.1 + Candidate: 3.4.2-0ubuntu0.18.04.1 + Version table: + *** 3.4.2-0ubuntu0.18.04.1 500 + 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages + 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages + 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages + 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages + 100 /var/lib/dpkg/status + 3.4.1-8build1 500 + 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages ProblemType: Package DistroRelease: Ubuntu 18.04 Package: sa-compile 3.4.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Tue Nov 6 13:58:21 2018 ErrorMessage: installed sa-compile package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2013-03-02 (2075 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: - dpkg 1.19.0.5ubuntu2.1 - apt 1.6.6 + dpkg 1.19.0.5ubuntu2.1 + apt 1.6.6 SourcePackage: spamassassin Title: package sa-compile 3.4.2-0ubuntu0.18.04.1 failed to install/upgrade: installed sa-compile package post-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-04-28 (192 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802017 Title: Error in v342.pre Config File Causes sa-compile Crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1802017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802017] [NEW] Error in v342.pre Config File Causes sa-compile Crash
Public bug reported: In the spamassassin config file: /etc/mail/spamassassin/v342.pre, the line: parse_dkim_uris 1 under the comment "allow URI rules to look at DKIM headers if they exist" causes a syntax error and for sa-compile to quit. System Information: --- Description:Ubuntu 18.04.1 LTS Release:18.04 sa-compile: Installed: 3.4.2-0ubuntu0.18.04.1 Candidate: 3.4.2-0ubuntu0.18.04.1 Version table: *** 3.4.2-0ubuntu0.18.04.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 100 /var/lib/dpkg/status 3.4.1-8build1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages ProblemType: Package DistroRelease: Ubuntu 18.04 Package: sa-compile 3.4.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Tue Nov 6 13:58:21 2018 ErrorMessage: installed sa-compile package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2013-03-02 (2075 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: spamassassin Title: package sa-compile 3.4.2-0ubuntu0.18.04.1 failed to install/upgrade: installed sa-compile package post-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-04-28 (192 days ago) ** Affects: spamassassin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic ** Attachment removed: "Df.txt" https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1802017/+attachment/5209772/+files/Df.txt ** Attachment removed: "Dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1802017/+attachment/5209773/+files/Dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802017 Title: Error in v342.pre Config File Causes sa-compile Crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1802017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775170] Re: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata
I did a bit more investigating and it seems to me like the contents of the defined memcached server can influence the generation of the javascript in '/var/lib/openstack-dashboard/static/dashboard/js' Is that assumption correct? If so, maybe the collect/compress should flush the memcached contents? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775170 Title: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1775170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775170] Re: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata
Hey Corey,
I believe I have found the source of my problem with bad javascript
being generated at the compress and collect static stage and it has to
do with whats in my /etc/openstack-dashboard/local_settings.py,
specifically my memcached section. We run 3 controllers and 3 instances
of memcached. If we configure our local_settings.py with the 3 memcached
servers, bad javascript is generated at the compress and collectstatic
stage. If we just use a single memcached server, the javascript
generation is just fine. Any idea why this might be? Is our syntax for
the cache stanza incorrect? There's no examples provided on the
OpenStack site on how multiple memcached servers would look in terms of
syntax. Either way, even the 'bad' stanza as written below seems to work
in our lab (in terms of javascript generation)
GOOD:
SESSION_ENGINE = 'django.contrib.sessions.backends.cache'
CACHES = {
'default': {
'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',
'LOCATION': '172.25.4.17:11211',
},
}
BAD:
SESSION_ENGINE = 'django.contrib.sessions.backends.cache'
CACHES = {
'default': {
'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',
'LOCATION':
['172.25.4.17:11211','172.25.4.18:11211','172.25.4.19:11211'],
},
}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775170
Title:
[SRU] Fixing empty create swift container dialog after upgrading
horizon from newton to ocata
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1775170/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775170] Re: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata
I don't think it's necessary to go through the process of a pike -> queens upgrade to reproduce the issue. Reason I say that is because we can take our current install and purge & install the openstack-dashboard & related packages and without our customizations we still experience the problem. That being said we are unable to reproduce this issue from a fresh install in our lab environment by taking a fresh ubuntu 16.04 install and layering on the openstack packages. This has been good and bad. Bad because we are unable to reproduce the issue in our lab. Good because we can take this working environment and copy the dynamically generated javascript files from '/var/lib/openstack- dashboard/static/dashboard/js' to our production environment so that the create container modal works properly. Is there any way to get a more verbose output from the generation (collectstatic and compress) of those javascript files to see where it might be breaking? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775170 Title: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1775170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775170] Re: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata
Just to be clear, I've tried removing the following directories rm -rf /usr/share/openstack-dashboard/ rm -rf /var/lib/openstack-dashboard/static/ followed by an apt-get install --reinstall openstack-dashboard python- django-horizon Leaving the dashboard uncustomized, I am still getting a blank create container window. Chrome developer console when loading '/project/containers/' shows: Uncaught SyntaxError: Invalid or unexpected token for 95f4db675ac3.js:1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775170 Title: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1775170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775170] Re: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata
We implement the following customizations of the openstack-horizon dashboard: - /usr/share/openstack-dashboard/openstack_dashboard/templates/_login_footer.html - /usr/share/openstack-dashboard/openstack_dashboard/templates/_footer.html - /usr/share/openstack-dashboard/openstack_dashboard/static/dashboard/img/logo.svg - /usr/share/openstack-dashboard/openstack_dashboard/static/dashboard/img/logo-splash.svg We serve the openstack dashboard out of '/' instead of Ubuntu's default of '/horizon' and we do so by modifying the following: - /etc/openstack-dashboard/local_settings.py WEBROOT = '/' LOGIN_URL = WEBROOT + 'auth/login/' LOGOUT_URL = WEBROOT + 'auth/logout/' - /etc/apache2/conf-available/openstack-dashboard.conf WSGIScriptAlias / /usr/share/openstack-dashboard/openstack_dashboard/wsgi/django.wsgi process-group=horizon Alias /static /var/lib/openstack-dashboard/static/ Alias /horizon/static /var/lib/openstack-dashboard/static/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775170 Title: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1775170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775170] Re: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata
This particular bug of the container creation modal being blank has plagued us for several OpenStack releases now. We are running Queens on Ubuntu 16.04 currently (http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/queens/main amd64 Packages) python-django-horizon 3:13.0.1-0ubuntu2~cloud0 We are essentially seeing the same (or at least similar) problem. When we run python manage.py collectstatic -c && python manage.py compress some of the dynamicly generated javascript files are incomplete/truncated and causes this container creation modal to be blank. We have no idea whats causing the javascript to be generated in an incomplete way and has been very difficult for us to reproduce in a lab environment. This issue is mostly unique to our production environment however in the past we have been able to create this issue in the lab (this was probably on ocata). Does anyone have any guidance on this? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775170 Title: [SRU] Fixing empty create swift container dialog after upgrading horizon from newton to ocata To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1775170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794377] [NEW] package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3
Public bug reported: keeps crashing ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgles1 (not installed) ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Tue Sep 25 16:20:21 2018 DuplicateSignature: package:libgles1:(not installed) Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-MFEi2z/076-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.106-0ubuntu3 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 InstallationDate: Installed on 2017-10-27 (333 days ago) InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libglvnd Title: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 UpgradeStatus: Upgraded to bionic on 2018-06-14 (103 days ago) ** Affects: libglvnd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-conflict -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794377 Title: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1794377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791219] [NEW] Symbolic link to src.zip in openjdk-11-source points to an invalid location
Public bug reported: After installing all relevant open jdk 11 packages, (sudo apt install openjdk-11-*) navigate to /usr/lib/jvm/java-11-openjdk-amd64, the symbolic link to src.zip in ../openjdk-11/src.zip will be invalid. This should point to ../openjdk-11/lib/src.zip, or src.zip should be moved up one directory and ./lib should be deleted. ** Affects: openjdk-lts (Ubuntu) Importance: Undecided Status: New ** Tags: dpkg java jdk openjdk openjdk-11 openjdk-11-jdk openjdk-11-source package -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791219 Title: Symbolic link to src.zip in openjdk-11-source points to an invalid location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1791219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785419] [NEW] I chose "do something else" and set up an ext4 partition, and a 8gb swap partition, but it throws an error installing grub :-(
Public bug reported: while installing ubuntu, for my partitions, I selected "Something else", and I set up a 8gb swap partition, and the remainder as a ext4 partition. I'm doing all this on my sdb hard drive, as well as setting up grub on sdb. however, I get this error when the installer is installing grub. :-( The 'grub-efi-amd64-signed' package failed to install into / target/. Without the GRUB boot loader, the installed system will not boot. Thank you for your help! :) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 Date: Sat Aug 4 12:51:28 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785419 Title: I chose "do something else" and set up an ext4 partition, and a 8gb swap partition, but it throws an error installing grub :-( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1785419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775862] Re: Missing Magnum-UI package for Ubuntu 16.04
Are there any plans to release magnum-ui as part of the Ubuntu cloud archive repository? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775862 Title: Missing Magnum-UI package for Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/magnum/+bug/1775862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779129] [NEW] package libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux-gnu/libfdisk.so.1.1.0] failed to install/upgrade: package libfdisk1:amd64 is not ready for configuration canno
Public bug reported: i was installing latex-maker and as it ended i got that error. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux-gnu/libfdisk.so.1.1.0] ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu Jun 28 07:03:23 2018 DpkgTerminalLog: dpkg: error processing package libfdisk1:amd64 (--configure): package libfdisk1:amd64 is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package libfdisk1:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-06-18 (10 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: util-linux Title: package libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux-gnu/libfdisk.so.1.1.0] failed to install/upgrade: package libfdisk1:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779129 Title: package libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux- gnu/libfdisk.so.1.1.0] failed to install/upgrade: package libfdisk1:amd64 is not ready for configuration cannot configure (current status 'half-installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1779129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765616] Re: tomcat more or less broken -- java compat issues
I just installed 8.5.30-1ubuntu1.1 and it resolved the issue. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765616 Title: tomcat more or less broken -- java compat issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat8/+bug/1765616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769545] [NEW] DerInput.getLength(): lengthTag=9, too big.
Public bug reported: When using pkispawn with an external root CA the following error occurs. 2018-05-05 15:00:33 [https-jsse-nio-8443-exec-9] FINE: CertInfoProfile: Unable to populate certificate: Unable to get ca certificate: Unable to initialize, java.io.IOException: DerInput.getLength(): lengthTag=9, too big. 2018-05-05 15:00:33 [https-jsse-nio-8443-exec-9] SEVERE: Configuration failed: Unable to get ca certificate: Unable to initialize, java.io.IOException: DerInput.getLength(): lengthTag=9, too big. Unable to get ca certificate: Unable to initialize, java.io.IOException: DerInput.getLength(): lengthTag=9, too big. at com.netscape.cms.profile.def.ValidityDefault.populate(ValidityDefault.java:323) at com.netscape.certsrv.profile.CertInfoProfile.populate(CertInfoProfile.java:100) at com.netscape.cms.servlet.csadmin.CertUtil.createLocalCert(CertUtil.java:542) at com.netscape.cms.servlet.csadmin.ConfigurationUtils.configLocalCert(ConfigurationUtils.java:2754) at com.netscape.cms.servlet.csadmin.ConfigurationUtils.configCert(ConfigurationUtils.java:2578) at org.dogtagpki.server.rest.SystemConfigService.processCert(SystemConfigService.java:483) at org.dogtagpki.server.rest.SystemConfigService.processCerts(SystemConfigService.java:303) at org.dogtagpki.server.rest.SystemConfigService.configure(SystemConfigService.java:170) at org.dogtagpki.server.rest.SystemConfigService.configure(SystemConfigService.java:105) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:139) at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:295) at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:249) at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:236) at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:402) at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:209) at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221) at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:199) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:496) at com.netscape.cms.tomcat.ExternalAuthenticationValve.invoke(ExternalAuthenticationValve.java:82) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:650) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:803) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:790) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1460) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at
[Bug 1765616] Re: freeipa server install fails - RuntimeError: CA configuration failed.
dogtag-pki server now runs on bionic using 8.5.30-1ubuntu1.2 from the ppa. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765616 Title: freeipa server install fails - RuntimeError: CA configuration failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1765616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1658233] Re: missing apparmor rules
Seeing these log entries in Bionic: audit: type=1400 audit(1525128782.144:24): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/usr/sbin/mysqld" pid=24878 comm="apparmor_parser" audit: type=1400 audit(1525128782.420:25): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/sys/devices/system/node/" pid=24896 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 audit: type=1400 audit(1525128782.428:26): apparmor="DENIED" operation="capable" profile="/usr/sbin/mysqld" pid=24896 comm="mysqld" capability=2 capname="dac_read_search" audit: type=1400 audit(1525128782.448:27): apparmor="DENIED" operation="capable" profile="/usr/sbin/mysqld" pid=24896 comm="mysqld" capability=2 capname="dac_read_search" audit: type=1400 audit(1525128783.004:28): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/sys/devices/system/node/" pid=24930 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 audit: type=1400 audit(1525128787.392:29): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/sys/devices/system/node/" pid=25112 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 audit: type=1400 audit(1525128792.144:30): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/usr/sbin/mysqld" pid=25238 comm="apparmor_parser" audit: type=1400 audit(1525128797.052:31): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/sys/devices/system/node/" pid=25462 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 audit: type=1400 audit(1525128797.272:32): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/sys/devices/system/node/" pid=25475 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=106 ouid=0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1658233 Title: missing apparmor rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1658233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1658233] Re: missing apparmor rules
** Tags added: bionic xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1658233 Title: missing apparmor rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1658233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762748] Re: Larger than 2 TB disks not possible
I have tested cloud-guest-utils version 0.27-0ubuntu25.1 and it appears to allow instances with disks larger than 2TB to be deployed properly. My testing was to deploy an instance with a small root disk, then install the patched cloud-guest-utils on to the instance. I would then take a snapshot of the instance and re-deploy it as a larger VM with a >2TB root disk. I hope to see this patched version of cloud-guest-utils pushed to the Xenial ubuntu cloud images soon :) Thank you very much for your work -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762748 Title: Larger than 2 TB disks not possible To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-utils/+bug/1762748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
Thanks for reporting. I've reached out to have this LP bug looked at. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1766825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760937] Re: [Feature Freeze Exception]Update Ledmon in Ubuntu 18.04 05 new upstream 0.90
That plan makes sense. Again, sorry for not following up earlier. I've reached out to Intel about taking up maintainership (complete with JIRA task :) ). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760937 Title: [Feature Freeze Exception]Update Ledmon in Ubuntu 18.04 05 new upstream 0.90 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ledmon/+bug/1760937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760937] Re: [Feature Freeze Exception]Update Ledmon in Ubuntu 18.04 05 new upstream 0.90
Hey, I am (was?) the maintainer in Debian, which I'd been maintaining for my old team. I must've missed the pings about the package but saw this LP bug. Anyway, it's fallen really low on my to-do list because of other work, even though I'd hoped to have gotten to it a while ago. I'd really appreciate any help maintaining in Debian/Ubuntu. Honestly it's something I had been maintaining in Debian because Intel wasn't; I think ideally they should be the package maintainer as they're upstream. I'm happy to help with pushing for business case with them on that if desired. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760937 Title: [Feature Freeze Exception]Update Ledmon in Ubuntu 18.04 05 new upstream 0.90 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ledmon/+bug/1760937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608040] Re: fail2ban 0.9 branch does not support IPv6; existing logic can misinterpret IPv6 addresses in logs
** Also affects: fail2ban via https://github.com/fail2ban/fail2ban/issues/1493 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608040 Title: fail2ban 0.9 branch does not support IPv6; existing logic can misinterpret IPv6 addresses in logs To manage notifications about this bug go to: https://bugs.launchpad.net/fail2ban/+bug/1608040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744411] Re: Upgrade to fail2ban 0.10.0 or later?
Version 0.10.2-1 will be released with Ubuntu Bionic (18.04) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744411 Title: Upgrade to fail2ban 0.10.0 or later? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/1744411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744411] Re: Upgrade to fail2ban 0.10.0 or later?
** Changed in: fail2ban (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744411 Title: Upgrade to fail2ban 0.10.0 or later? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/1744411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217959] Re: 'metadata' file not found when creating backup ("Could not restore ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"
I just hit this bug. I recently put in a symlink for my ~/.cache
directory. My deja dup version is as follows:
~/.cache$ apt list --installed | grep deja
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
deja-dup/xenial-updates,now 34.2-0ubuntu1.1 amd64 [installed]
deja-dup-backend-gvfs/xenial-updates,xenial-updates,now 34.2-0ubuntu1.1 all
[installed,automatic]
deja-dup-backend-s3/xenial-updates,xenial-updates,now 34.2-0ubuntu1.1 all
[installed]
fonts-dejavu/xenial,xenial,now 2.35-1 all [installed,automatic]
fonts-dejavu-core/xenial,xenial,now 2.35-1 all [installed]
fonts-dejavu-extra/xenial,xenial,now 2.35-1 all [installed,automatic]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217959
Title:
'metadata' file not found when creating backup ("Could not restore
‘/home/user /.cache/deja-dup/metadata’: File not found in backup"
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1217959/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
(NB: superm1 and I work for Dell) Can anyone provide confirmation on this affecting them with the Dell XPS 13 (9350) with Intel i7? That's actually exactly what I'm running with Artful without issue, and we have not seen any escalations from Dell support on this issue on any Dell systems. Additionally, the 9350 does not have a BIOS core from Insyde. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1734198] [NEW] crash during installation of lubuntu
Public bug reported: crashed after asking what type of install i would like to do window saying ubi-partman crashed trying to install latest lubuntu 32 bit desktop on acer aspire one ZA3. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubiquity 17.10.10 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic i686 ApportVersion: 2.20.7-0ubuntu3 Architecture: i386 CasperVersion: 1.387 Date: Thu Nov 23 20:20:21 2017 LiveMediaBuild: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug artful i386 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734198 Title: crash during installation of lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1734198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682864] Re: fail2ban should remove references to imap3 in 17.04
** Bug watch added: Debian Bug tracker #867374 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867374 ** Also affects: fail2ban (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867374 Importance: Unknown Status: Unknown ** Tags added: artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682864 Title: fail2ban should remove references to imap3 in 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/1682864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726879] Re: Unescaped left brace in regex is deprecated
** Bug watch added: Debian Bug tracker #869408 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869408 ** Also affects: spamassassin (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869408 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726879 Title: Unescaped left brace in regex is deprecated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1726879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724678] [NEW] external monitor not detected with new kernel using integrated graphics
Public bug reported: 4.10.0-37-generic breaks the ability to use an external monitor. The output of lshw -numeric -C display is: *-display description: VGA compatible controller product: Intel Corporation [8086:5916] vendor: Intel Corporation [8086] physical id: 2 bus info: pci@:00:02.0 version: 02 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:277 memory:d000-d0ff memory:c000-cfff ioport:f000(size=64) memory:c-d lsb_release -rd: Description:Ubuntu 17.04 Release:17.04 ** Affects: linux-hwe (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/1724678 Title: external monitor not detected with new kernel using integrated graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1724678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
@Gael from what I can tell the fix has not been released based on this bug status is still 'in progress'. I'm running Ubuntu 16.04 with vlan 1.9-3.2ubuntu1 and it still contains the 'ip link set up dev $IF_VLAN_RAW_DEVICE' on line 63 of /etc/network /if-pre-up.d/vlan . You can modify the file yourself using Dan's instructions on step 9. Works like a charm 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/1573272 Title: default gateway route not installed for bond interfaces through reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649763] Re: Dell XPS 15 2016 with Ubuntu 16 Sound HDMI issues
** Project changed: dell-sputnik => unity-control-center -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649763 Title: Dell XPS 15 2016 with Ubuntu 16 Sound HDMI issues To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1649763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666157] Re: Unable to install GRUB in /dev/nvme (Dell XPS 13 9360)
** Changed in: dell-sputnik Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666157 Title: Unable to install GRUB in /dev/nvme (Dell XPS 13 9360) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1666157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss
@frail-knight, the right people are already subscribed to this bug. Please *stop* changing bugs to affect dell-sputnik ** Changed in: dell-sputnik Status: New => Incomplete ** Changed in: dell-sputnik Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654448 Title: XPS 13 9360, Realtek ALC3246, Headphone audio hiss To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661987] Re: Wrong colours on some monitors via USB-C to HDMI
** Project changed: dell-sputnik => linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661987 Title: Wrong colours on some monitors via USB-C to HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1661987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656659] Re: [Dell XPS 9350 Laptop] laptop fails to wake from suspend, requires restart
@frail-knight, please stop marking bugs as affecting dell-sputnik unless you are absolutely sure they're relevant ** Changed in: dell-sputnik Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656659 Title: [Dell XPS 9350 Laptop] laptop fails to wake from suspend, requires restart To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1656659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind
DKMS is a Dell project but not Project Sputnik. Marking as invalid for dell-sputnik. ** Changed in: dell-sputnik Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1515513 Title: /boot/initrd.img-*.old-dkms files left behind To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1515513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625498] Re: Heavy corruption in launcher icons on XPS 13 (Dell XPS 13 9350) running Xenial 16.04.1
This isn't a Dell-specific issue. It should be a Unity or Intel graphics issue. ** Changed in: dell-sputnik Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625498 Title: Heavy corruption in launcher icons on XPS 13 (Dell XPS 13 9350) running Xenial 16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1625498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1688317] Re: PCI/internal sound card not detected
You're running a non-OEM version of Ubuntu 16.04.1, which is too old to fully support this platform. Canonical maintains driver backports for this platform only for factory-installed Ubuntu 16.04, and that includes backport DKMS packages. Either wait until this is backported to a later Ubuntu 16.04 point release, use a later version of Ubuntu or purchase with Ubuntu pre-installed instead of Windows. ** Changed in: dell-sputnik Status: New => Invalid ** Changed in: alsa-driver (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1688317 Title: PCI/internal sound card not detected To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1688317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1650259] Re: [XPS 13 9350, Realtek ALC3246, Speaker, Internal] No sound at all from the headphone jack
Have you checked in the system settings GUI whether the headphone jack shows as an output option? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650259 Title: [XPS 13 9350, Realtek ALC3246, Speaker, Internal] No sound at all from the headphone jack To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1650259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649763] Re: Dell XPS 15 2016 with Ubuntu 16 Sound HDMI issues
It sounds to me like issue 1 should be opened as a separate bug report as a feature request. I think it makes sense to at least prompt the user whether they want to switch to external audio. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649763 Title: Dell XPS 15 2016 with Ubuntu 16 Sound HDMI issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1649763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1651433] Re: bluetooth mouse random disconnects
It looks like on OEM systems, we tweak /etc/bluetooth/main.conf by adding "AutoEnable=true". Can you check what that's set to on your system? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651433 Title: bluetooth mouse random disconnects To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1651433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649763] Re: Dell XPS 15 2016 with Ubuntu 16 Sound HDMI issues
** Package changed: ubuntu => unity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649763 Title: Dell XPS 15 2016 with Ubuntu 16 Sound HDMI issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1649763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643717] [NEW] package tar 1.27.1-1ubuntu0.1 failed to install/upgrade
Public bug reported: I'm new to bug reporting so please forgive me if I'm doing it wrong. I was trying to run apt-get updgrade and it crashed. There appears to be something wrong with tar, but I don't know what or how. My system is pretty hosed at the moment. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: tar 1.27.1-1ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39 Uname: Linux 3.13.0-101-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Tue Nov 22 12:14:59 2016 DuplicateSignature: package:tar:1.27.1-1ubuntu0.1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2014-10-22 (761 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.15 SourcePackage: tar Title: package tar 1.27.1-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2016-08-07 (106 days ago) ** Affects: tar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643717 Title: package tar 1.27.1-1ubuntu0.1 failed to install/upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1643717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1379427] Re: /etc/network/if-up.d/upstart emits static-network-up too early
** Summary changed: - /etc/network/if-up.d/upstart emits static-network-up to early + /etc/network/if-up.d/upstart emits static-network-up too early -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1379427 Title: /etc/network/if-up.d/upstart emits static-network-up too early To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1379427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603406] Re: /etc/init.d/networking restart
*** This bug is a duplicate of bug 1301015 *** https://bugs.launchpad.net/bugs/1301015 ** This bug has been marked a duplicate of bug 1301015 Networking does not restart -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603406 Title: /etc/init.d/networking restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1603406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632527] Re: [Dell][XPS]Touchscreen fails to function after resume from s3 by Lid close/open
The patch from Intel is now in the mainline kernel and tagged for stable: https://marc.info/?l=linux-gpio=147679440002043=2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632527 Title: [Dell][XPS]Touchscreen fails to function after resume from s3 by Lid close/open To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1632527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632527] Re: [Dell][XPS]Touchscreen fails to function after resume from s3 by Lid close/open
Please also make sure that this fix gets into all of these non-OEM Ubuntu releases: 14.04 (with 4.4 kernel), 16.04 and 16.10. Impact scope includes Dell XPS 13 9350 (SKL) and 9360 (KBL). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632527 Title: [Dell][XPS]Touchscreen fails to function after resume from s3 by Lid close/open To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1632527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579609] Re: [Xenial] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
** Tags added: yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579609 Title: [Xenial] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1579609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
