[Bug 2012388] Re: X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks
Even though I'm not using anydesk, I experience the same problem. And I think its caused by "dropbox" > gnome-extensions disable ubuntu-appindicat...@ubuntu.com This workaround seems to work -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2012388 Title: X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2012388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver
> GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash initcall_blacklist=simpledrm_platform_driver_init” This workaround worket for me too. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060268 Title: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968929] Re: Missing Wayland login option on NVIDIA systems
I just did a fresh install of the official release of 22.04 LTS image today, and hit this problem. I see no gear icon, and it defaults to X11, with no option to select Wayland, whether I have just the NVIDIA GPU enabled, or both the Intel integrated GPU and the NVIDIA discrete GPU enabled in hybrid mode. I had previously installed a nightly build of 22.04 LTS (beta) last week, and had the gear as an option, and was able to select and use Wayland. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968929 Title: Missing Wayland login option on NVIDIA systems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969254] Re: wayland session not longer an option after recent update on Ubuntu 22.04
*** This bug is a duplicate of bug 1969243 *** https://bugs.launchpad.net/bugs/1969243 I just did a fresh install of the official release 22.04 LTS image today, and hit this problem. No gear, and it defaults to X11, whether I have just the NVIDIA GPU enabled, or both the Intel integrated GPU and the NVIDIA discrete GPU enabled in hybrid mode. I had previously installed a nightly build of 22.04 LTS (beta) last week, and had the gear as an option, and was able to use Wayland. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969254 Title: wayland session not longer an option after recent update on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 935713] Re: Can no longer drop tabs onto tabs area in Chromium
In ubuntu 21.04, using chromium Version 98.0.4727.0 (Developer Build) (64-bit) with kwin x window manager, i am unable to move tabs around (before or after others). Instead new window is opening. Short keys is working nut not mouse movement drag and drop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/935713 Title: Can no longer drop tabs onto tabs area in Chromium To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/935713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872311] Re: Brightness hotkeys not working on Lenovo S740
Thanks for the suggestion. However, this does not make any difference. I ran also "watch -n1 cat /proc/interrupts", "acpi_listen" and "sudo showkey -s" and no reaction to brightness hotkeys whereas volume hotkeys work and that also shows up when running these commands. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872311 Title: Brightness hotkeys not working on Lenovo S740 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872311] Re: Brightness hotkeys not working on Lenovo S740
Hi, unfortunately not. Maybe it will get fixed sometime. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872311 Title: Brightness hotkeys not working on Lenovo S740 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1689539] Re: Pulseaudio "Access Denied" on Fedora 25 with Awesome WM as desktop environment
** Changed in: snapd (Ubuntu) Status: Incomplete => In Progress ** Changed in: snapd (Ubuntu) Status: In Progress => Fix Committed ** Changed in: snapd (Ubuntu) Status: Fix Committed => New ** Changed in: snapd (Ubuntu) Status: New => Incomplete ** Changed in: snapd (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1689539 Title: Pulseaudio "Access Denied" on Fedora 25 with Awesome WM as desktop environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1689539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917474] [NEW] Vaio touchpad dont work properly
Public bug reported: I'm a Vaio user and my touchpad do not work at all OS boots. Sometimes the touchpad initialize with system but stop to work after a variate time lapse (5 minutes or 5 hours). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-44-generic 5.8.0-44.50~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 2 11:46:27 2021 InstallationDate: Installed on 2020-12-09 (83 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.8 (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/1917474 Title: Vaio touchpad dont work properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1917474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820584] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.
After some more digging and having reproduced the issue a few more times, here is what seems to happen. Seahorse is running, using the avahi library. Seahorse has called avahi_glib_poll_new() and some AvahiTimeout timeouts have been created. Then things are stopped because the computer is about to be rebooted. Seahorse is closing down and therefore does some cleanup, among other things it calls avahi_glib_poll_free() which calls cleanup_timeouts() which destroys all the timeouts. However, after the timeouts were destroyed, there still exists a pointer to one of those timeouts in the dispatch_timeout member in a ConnectionData struct. For some reason the dispatch_timeout_callback() function is called at this point, and it does "ConnectionData *d = userdata" and that ConnectionData struct has inside it a dispatch_timeout pointer which is now invalid because the timeout was destroyed, its memory was freed, as a result of the avahi_glib_poll_free() call earlier. dispatch_timeout_callback() passes the ConnectionData *d to request_dispatch() which calls timeout_update() passing the invalid d->dispatch_timeout pointer, which is then used and happens to point to some garbage which gives the assertion failure. Not sure exactly how to fix the problem, but it seems bad that pointers to destroyed data structures are still lying around, maybe things should be destroyed in a different order. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820584 Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1820584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820584] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.
I added some extra debug output in avahi and waited for the error to
happen again, in this way found out that the assertion failure happens
when the time_event_queue_root(q) call gives NULL so that the "else"
part is used in update_timeout() in avahi-core/timeeventq.c:
static void update_timeout(AvahiTimeEventQueue *q) {
AvahiTimeEvent *e;
assert(q);
if ((e = time_event_queue_root(q)))
q->poll_api->timeout_update(q->timeout, >expiry);
else
q->poll_api->timeout_update(q->timeout, NULL); <-- assertion failure
inside this call
}
So time_event_queue_root(q) gives NULL which means that q->prioq->root
is NULL. Why would that happen?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820584
Title:
seahorse assert failure: seahorse: glib-watch.c:195: timeout_update:
Assertion `!t->dead' failed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1820584/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907869] Re: Weird audio problems UR22C
Update II: This used to occur again and again, plus the playback freeze was permanent. ^ also applies to v5.4.0-56 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907869 Title: Weird audio problems UR22C To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1907869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907869] Re: Weird audio problems UR22C
Update: This time the playback freeze happened after an uptime of ~40min. Did play audio almost right after logging in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907869 Title: Weird audio problems UR22C To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1907869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
I have followed this guide https://davidwpearson.wordpress.com/2020/01/10/lenovo-laptop-subwoofers-and-linux/#fix i don't think it did a thing for the subwoofer, but it manages to sound a bit nicer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907869] [NEW] Weird audio problems UR22C
Public bug reported: Occurs only with my audio interface Steinberg UR22C, which is connected via USB-C. This is a regression. Latest kernel known to work properly was: linux-image-5.4.0-48-generic. (If I boot my current system with this one, everything's working fine.) As far as I can tell this broke with vthe v5.4.0-51 update. ## Problem 1: On reboot: after a few seconds playback stops (and freezes the application that was currently playing audio). ### For v5.4.0-56 This happens only once after each boot. Works fine after closing the hanging player. ### With v5.4.0-51 This used to occur again and again, plus the playback freeze was permanent. Workaround: pulseaudio --kill +then: pulseaudio --start until the next freeze would happen) ### Characteristics Audio would suddenly go completely silent. ## Problem 2: Applies to v5.4.0-56 After starting some playback the first few seconds will also "contain" some unpleasant weird crackles. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-56-generic 5.4.0-56.62~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-56.62~18.04.1-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat Dec 12 00:59:47 2020 InstallationDate: Installed on 2018-10-20 (783 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug audio bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907869 Title: Weird audio problems UR22C To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1907869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872333] Re: MSFT0001:01 touchpad randomly does not work after boot (Lenovo Yoga S740)
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872333 Title: MSFT0001:01 touchpad randomly does not work after boot (Lenovo Yoga S740) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872333] Re: MSFT0001:01 touchpad randomly does not work after boot (Lenovo Yoga S740)
Sorry, I mixed secure boot to UEFI etc. After disabling secure boot, I have been using mainline kernel 5.9.6-050906-generic for a while now in Ubuntu 20.04 and the touchpad has always worked. Seems fixed there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872333 Title: MSFT0001:01 touchpad randomly does not work after boot (Lenovo Yoga S740) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622499] Re: [master] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in packa
Ubuntu 20.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622499 Title: [master] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit- options.d/accounts.google.com.conf', which is also in package account- plugin-google 0.13+16.04.20160719-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1622499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872333] Re: MSFT0001:01 touchpad randomly does not work after boot (Lenovo Yoga S740)
https://forums.lenovo.com/t5/Other-Linux-Discussions/Lenovo-Yoga-S740 -Linux-Trackpad-very-temperamental-and-FN-Keys-barely-work/m-p/5037384 Just found out that this issue might be fixed in kernel 5.9. How could I install 5.9 kernel and test this? I have secure boot enabled so the mainline kernels are not working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872333 Title: MSFT0001:01 touchpad randomly does not work after boot (Lenovo Yoga S740) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872333] Re: MSFT0001:01 touchpad randomly does not work after boot (Lenovo Yoga S740)
Hi, just wanted to update that the problem persists in 20.10 and 4.8 kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872333 Title: MSFT0001:01 touchpad randomly does not work after boot (Lenovo Yoga S740) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900390] [NEW] do-release-update hangs from use of user $PATH (specifically 'npm which')
Public bug reported: When I updated from 18.04 to 20.04 with do-release-upgrade, I noticed that the cups package prerm script would hang forever. After I hit ctrl-C, it was fairly messy to fix the system back together. When I traced this, I found that `which` in the prerm script (and not just cups but potentially all of them?) resolved to /usr/local/bin/which from my $PATH, which was from the npm `which` package. I don't really understand how even `npm which` could hang, but it did somehow. Everything worked again after I deleted npm `which`. The lesson here seems to be that do-release-upgrade should restrict $PATH so that these kinds of problems can't happen. This is a possible problem for apt in general, but it's more problematic for do-release-update since it could not be rolled back in this case. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.28 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon Oct 19 10:12:55 2020 InstallationDate: Installed on 2018-11-13 (706 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-10-17 (1 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900390 Title: do-release-update hangs from use of user $PATH (specifically 'npm which') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1900390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888585] Re: seahorse crash: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed
*** This bug is a duplicate of bug 1820584 *** https://bugs.launchpad.net/bugs/1820584 Looking at the code it seems the assertion that was triggered is in the source code of the avahi package, so it probably makes sense to mark this as a duplicate of bug #1820584 for avahi. ** This bug has been marked a duplicate of bug 1820584 seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888585 Title: seahorse crash: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1888585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820584] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.
Related: bug #1888585 ( https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1888585 ) The error "seahorse (seahorse) glib-watch.c → 195 → timeout_update → Assertion `!t->dead'' failed." is listed with hundreds of occurrences each day at https://errors.ubuntu.com/ but there is no bug report assigned to it there, the "Bug report" column is empty. Should it be associated with this bug report, or perhaps with bug #1888585 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820584 Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1820584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888585] Re: seahorse crash: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed
> * Is this reproducible? I don't have an exact way to reproduce it but it happens hundreds of times each day, presumably for many different users, as seen at https://errors.ubuntu.com/ However, although the "seahorse (seahorse) glib-watch.c → 195 → timeout_update → Assertion `!t->dead'' failed." error is listed there at https://errors.ubuntu.com/ as one of the most frequent crashes, it has no bug report assigned to it there. How can we associate the error at https://errors.ubuntu.com/ to this bug report? I see that the importance was set to "low" -- is that really a good idea given that this is one of the most frequent crashes at https://errors.ubuntu.com/ ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888585 Title: seahorse crash: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1888585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888585] [NEW] seahorse crash: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed
Public bug reported: This bug is seen in the list at https://errors.ubuntu.com/ where it says: seahorse -- Ubuntu 20.04 -- seahorse (seahorse) glib-watch.c → 195 → timeout_update → Assertion `!t->dead'' failed. According to the list at https://errors.ubuntu.com/ it occurred 3201 times the past week, so it clearly happens to many people and not only me, but there is still no bug report associated with it. Therefore I am making this bug report now, hoping this can be associated with the bug listed at https://errors.ubuntu.com/ and help developers become aware of the problem. This is for Ubuntu 20.04. Package: seahorse 3.36-1 PackageArchitecture: amd64 ** Affects: seahorse (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/1888585 Title: seahorse crash: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1888585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873587] Re: [Ice Lake] Display flickers a lot during plymouth boot animations
Hi, with some updates during spring and summer this flickering has stopped, so problem solved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873587 Title: [Ice Lake] Display flickers a lot during plymouth boot animations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885459] Re: Nautilus does not ask for ssh login credentials
This is a false alarm, at least partly. If username is defined like sftp://u...@some.server.org, everything works OK. It is likely that in the live USB test case the server I use checks username from LDAP. As I did not specify user name and the default "ubuntu" was used, connection got denied. On another test server I did get the user/password window even when I did not specify username as above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885459 Title: Nautilus does not ask for ssh login credentials To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1885459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885459] [NEW] Nautilus does not ask for ssh login credentials
Public bug reported: When trying to connect a server using ssh:// or sftp:// no user/password information is asked and I get error saying "Access Denied". Expected behaviour: user/password would be asked. I tested also with 20.04 live USB - same behaviour. Same erroneus action also when trying to use Déja-Dup over SSH: no login information is asked -> Access Denied -message. SSH connection to the same server using CLI works OK on both installed system and Live session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 29 00:51:01 2020 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2020-06-26 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=fi_FI.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (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/1885459 Title: Nautilus does not ask for ssh login credentials To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1885459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786822] Re: Pinta constantly crashes in Ubuntu 18.04 fresh install
for the record, the default mono version that comes with MX 19 is: $ mono -V Mono JIT compiler version 5.18.0.240 (Debian 5.18.0.240+dfsg-3 Wed Apr 17 16:37:36 UTC 2019) after adding the official latest stable mono release and upgrading $ sudo apt upgrade I landed with $ mono -V Mono JIT compiler version 6.8.0.123 (tarball Tue May 12 15:15:28 UTC 2020) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786822 Title: Pinta constantly crashes in Ubuntu 18.04 fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/pinta/+bug/1786822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786822] Re: Pinta constantly crashes in Ubuntu 18.04 fresh install
#4 rocks! Thanks Jason. I can confirm, adding the official latest stable mono release to my package repos resolved the frequent crashes I used to have with pinta. For the record, I am using MX Linux (so I used the debian packages for mono) $ uname -a Linux mx 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786822 Title: Pinta constantly crashes in Ubuntu 18.04 fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/pinta/+bug/1786822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880824] Re: Crashes when dragging items out of Budgie's task icon list
Indeed, crashing it twice within a few seconds will make the whole session “crash” – just like doing `killall budgie-panel` twice. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880824 Title: Crashes when dragging items out of Budgie's task icon list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1880824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880824] Re: Crashes when dragging items out of Budgie's task icon list
Another finding: There's a 3rd case what can happen: Panel crashes but doesn't reopen again. Could make it crash twice. After the first time it restarted. So I waited a short while and made it crash again. Didn't reopen anymore. I would guess, if I hadn't waited, the whole session would have crashed (gonna try this out now). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880824 Title: Crashes when dragging items out of Budgie's task icon list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1880824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880824] Re: Crashes when dragging items out of Budgie's task icon list
apport information ** Tags added: apport-collected bionic third-party-packages ** Description changed: Budgie Panel (or sometimes even the whole session) crashes when dragging items out of Budgie's task icon list. Notes: Budgie Panel is placed on bottom on the very bottom screen (of 3). Dragging them downside out of screen causes the crash. Crash details: Either budgie-panel freezes (and restarts after ~10 secs), or the whole session crashes and one ends up at the display manager's login screen. This issue also applied to Ubuntu Budgie 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: budgie-desktop 10.5-0ubuntu7 ProcVersionSignature: Ubuntu 5.3.0-53.47-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed May 27 09:13:01 2020 InstallationDate: Installed on 2019-08-26 (274 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: budgie-desktop UpgradeStatus: Upgraded to eoan on 2020-01-24 (123 days ago) + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.15 + Architecture: amd64 + CurrentDesktop: Budgie:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-10-20 (589 days ago) + InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + Package: budgie-desktop 10.4+git20180830.02.f2dbc215fdb-0+10.5ubuntu6 [origin: LP-PPA-ubuntubudgie-backports] + PackageArchitecture: all + ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 + Tags: bionic third-party-packages + Uname: Linux 5.3.0-53-generic x86_64 + UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1880824/+attachment/5379270/+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/1880824 Title: Crashes when dragging items out of Budgie's task icon list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1880824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880824] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1880824/+attachment/5379272/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880824 Title: Crashes when dragging items out of Budgie's task icon list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1880824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880824] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1880824/+attachment/5379271/+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/1880824 Title: Crashes when dragging items out of Budgie's task icon list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1880824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880824] Re: Crashes when dragging items out of Budgie's task icon list
Managed to reproduce this under 18.04.4, unfortunately. Differences: - It only happens sometimes. Seems like there's some (unknown) precondition. - There's no freezing. Either budgie-panel or the whole session will crash right away. ** Changed in: budgie-desktop (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880824 Title: Crashes when dragging items out of Budgie's task icon list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1880824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880824] Re: Crashes when dragging items out of Budgie's task icon list
Appears to be not reproducible in an Ubuntu Budgie 20.04 amd64 Live system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880824 Title: Crashes when dragging items out of Budgie's task icon list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1880824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880824] [NEW] Crashes when dragging items out of Budgie's task icon list
Public bug reported: Budgie Panel (or sometimes even the whole session) crashes when dragging items out of Budgie's task icon list. Notes: Budgie Panel is placed on bottom on the very bottom screen (of 3). Dragging them downside out of screen causes the crash. Crash details: Either budgie-panel freezes (and restarts after ~10 secs), or the whole session crashes and one ends up at the display manager's login screen. This issue also applied to Ubuntu Budgie 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: budgie-desktop 10.5-0ubuntu7 ProcVersionSignature: Ubuntu 5.3.0-53.47-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed May 27 09:13:01 2020 InstallationDate: Installed on 2019-08-26 (274 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: budgie-desktop UpgradeStatus: Upgraded to eoan on 2020-01-24 (123 days ago) ** Affects: budgie-desktop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880824 Title: Crashes when dragging items out of Budgie's task icon list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1880824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872311] Re: Brightness hotkeys not working on Lenovo S740
Hi, I posted about this here: https://forums.lenovo.com/t5/Ubuntu /Lenovo-Yoga-S740-14IIL-Brightness-hotkeys-not-working-on- Ubuntu-20-04/m-p/5011698 Let's hope someone picks up on this - so far no one has. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872311 Title: Brightness hotkeys not working on Lenovo S740 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849119] Re: package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to install/upgrade: error: snap "chromium" has "install-snap" change in progress
An user called chirag patel solves the problem and posted it on Medium: https://medium.com/@chiragpatel_52497/unable-to-install-package-name- snap-package-name-has-install-snap-change-in-progress-b6768f2ce81d This solves the problem: Snap is probably still working on something in the background (or at least it thinks so). Open a terminal and run snap changes so see a list of ongoing changes. $ snap changes ... 123 Doing 2018-04-28T10:40:11Z - Install "foo" snap ... You can abort ongoing change(s): $ sudo snap abort 123 Then you should be able to successfully install chromium-brownser through the software center. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849119 Title: package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to install/upgrade: error: snap "chromium" has "install-snap" change in progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872311] Re: Brightness hotkeys not working on Lenovo S740
Thanks, "sudo showkey -s" does not show anything for the brightness key combination. Neither do the interrupts increase when the brightness key combination is pressed. So I assume this cannot be fixed from the software side. The brightness keys are working on Windows. However, the laptop is quite new so maybe the support just isn't there yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872311 Title: Brightness hotkeys not working on Lenovo S740 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874041] [NEW] [UE BOOM 2, playback] Playback problem
Public bug reported: some sounds are playing over the device (like sound the box makes when i turn the volume to max) but chrome sound output does not appear on bluetooth box this appeard after i upgraded yesterday from 19.10 -> 20.04 via do- release-upgrade all pkg's are up to date tried to reboot device // bluetooth box, reconnected, changed audio outputs, disconnected everything expect the bluetooth box, nothing helped ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erami 12984 F pulseaudio /dev/snd/pcmC0D0p: erami 12984 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 11:51:25 2020 InstallationDate: Installed on 2019-03-22 (395 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: UE BOOM 2 Symptom_Type: Only some of outputs are working Title: [UE BOOM 2, playback] Playback problem UpgradeStatus: Upgraded to focal on 2020-04-20 (0 days ago) dmi.bios.date: 02/20/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET48W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S2JW00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET48W(1.23):bd02/20/2019:svnLENOVO:pn20L5S2JW00:pvrThinkPadT480:rvnLENOVO:rn20L5S2JW00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S2JW00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (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/1874041 Title: [UE BOOM 2, playback] Playback problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873587] [NEW] Display flickers a lot starting from grub and ending to desktop (Lenovo S740, Intel Core i7-1065G7)
Public bug reported: After going forward from grub, the display flickers a lot, continuing it throughout the boot and even in GDM. The display flickers a few times in the desktop, and after that, the flickering goes away. So this is mainly a cosmetic thing as the flickering stops after logging in and waiting for a bit. I have attached a video to this bug report showing the whole process from the boot. I use Lenovo Yoga S740 with Intel Core i7-1065G7 and Intel Iris graphics (10th generation). I have not done any customizations to the installation after updating to 20.04 from 19.10 a couple of weeks ago. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: plymouth 0.9.4git20200323-0ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 18 21:43:41 2020 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2019-11-19 (150 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81RS ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=101c7da4-860d-4496-ae06-d98699795f9a ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=101c7da4-860d-4496-ae06-d98699795f9a ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: Upgraded to focal on 2020-04-04 (14 days ago) dmi.bios.date: 03/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BYCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S740-14IIL dmi.modalias: dmi:bvnLENOVO:bvrBYCN33WW:bd03/10/2020:svnLENOVO:pn81RS:pvrLenovoYogaS740-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS740-14IIL: dmi.product.family: Yoga S740-14IIL dmi.product.name: 81RS dmi.product.sku: LENOVO_MT_81RS_BU_idea_FM_Yoga S740-14IIL dmi.product.version: Lenovo Yoga S740-14IIL dmi.sys.vendor: LENOVO ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Video of the problem" https://bugs.launchpad.net/bugs/1873587/+attachment/5356518/+files/20200418_192631.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873587 Title: Display flickers a lot starting from grub and ending to desktop (Lenovo S740, Intel Core i7-1065G7) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1873587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872311] Re: Brightness hotkeys not working on Lenovo S740
Thanks for the comments. Please find attached the requested file (sudo acpidump > acpi.log). However, "watch -n1 cat /proc/interrupts" did not increase when I used the Fn + F10/F11 (brightness) button. Contrast to that, the (working) volume hotkeys increased the interrupts. I also ran "acpi_listen" and same thing - nothing when brightness hotkeys were pressed, and the correct input with volume hotkeys. ** Attachment added: "acpi.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872311/+attachment/5356489/+files/acpi.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872311 Title: Brightness hotkeys not working on Lenovo S740 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872333] [NEW] MSFT0001:01 touchpad randomly does not work after boot (Lenovo Yoga S740)
Public bug reported: About 50% of the Ubuntu 20.04 Ubuntu boots end up so that the touchpad of my Lenovo Yoga S740 does not work (cursor does not move). External mouse works even then. After one or two reboots the touchpad starts working, and it works until the next boot, when it may not work again. This seems very similar to this Lenovo Yoga S940 touchpad problem: https://bbs.archlinux.org/viewtopic.php?id=252711 Attached (i2c_error.txt) is the output of "dmesg |grep i2c" on a boot when the touchpad did not work. The main error message seems to be "i2c_designware i2c_designware.1: controller timed out". The name of the touchpad is "MSFT0001:01 06CB:CDB0 Touchpad" (from cat /proc/bus/input/devices) This bug report has been created on a boot where the touchpad does work. FYI, on Windows, the touchpad has always worked without problems. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: elias 1447 F pulseaudio /dev/snd/controlC0: elias 1447 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 19:56:05 2020 InstallationDate: Installed on 2019-11-19 (144 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81RS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=101c7da4-860d-4496-ae06-d98699795f9a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-04 (8 days ago) dmi.bios.date: 03/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BYCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S740-14IIL dmi.modalias: dmi:bvnLENOVO:bvrBYCN33WW:bd03/10/2020:svnLENOVO:pn81RS:pvrLenovoYogaS740-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS740-14IIL: dmi.product.family: Yoga S740-14IIL dmi.product.name: 81RS dmi.product.sku: LENOVO_MT_81RS_BU_idea_FM_Yoga S740-14IIL dmi.product.version: Lenovo Yoga S740-14IIL dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "i2c_error.txt" https://bugs.launchpad.net/bugs/1872333/+attachment/5352678/+files/i2c_error.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872333 Title: MSFT0001:01 touchpad randomly does not work after boot (Lenovo Yoga S740) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872311] Re: Brightness hotkeys not working on Lenovo S740
** Attachment added: "xkbcomp.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872311/+attachment/5352616/+files/xkbcomp.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872311 Title: Brightness hotkeys not working on Lenovo S740 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872311] [NEW] Brightness hotkeys not working on Lenovo S740
Public bug reported: Brightness hotkeys (Fn + F11 for decrease and Fn + F12 for increase) do not work on Ubuntu 20.04 and Lenovo S740 laptop. The brightness hotkeys did not work on 19.10 either. I followed the guide here: https://wiki.ubuntu.com/Hotkeys/Troubleshooting In "Step-by-step Troubleshooting", none of the steps (1-7) did produce any reaction to brightness change key combinations. However, I am able to change the laptop screen brightness through the brightness applet. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: elias 1447 F pulseaudio /dev/snd/controlC0: elias 1447 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 16:12:01 2020 InstallationDate: Installed on 2019-11-19 (144 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81RS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=101c7da4-860d-4496-ae06-d98699795f9a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-04 (7 days ago) dmi.bios.date: 03/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BYCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S740-14IIL dmi.modalias: dmi:bvnLENOVO:bvrBYCN33WW:bd03/10/2020:svnLENOVO:pn81RS:pvrLenovoYogaS740-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS740-14IIL: dmi.product.family: Yoga S740-14IIL dmi.product.name: 81RS dmi.product.sku: LENOVO_MT_81RS_BU_idea_FM_Yoga S740-14IIL dmi.product.version: Lenovo Yoga S740-14IIL dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal ** Attachment added: "udev-db.txt" https://bugs.launchpad.net/bugs/1872311/+attachment/5352595/+files/udev-db.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872311 Title: Brightness hotkeys not working on Lenovo S740 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872311] Re: Brightness hotkeys not working on Lenovo S740
** Attachment added: "xkbmap.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872311/+attachment/5352615/+files/xkbmap.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872311 Title: Brightness hotkeys not working on Lenovo S740 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535045] Re: [SRU] Biosdevname does not provide interface naming information for ConnecX4 Devices
I also want add that I've tested a manually compiled biosdevname v0.7.2 on our oldest hardware, HP Proliant G6 and our newest Dell PE Gen 14. Intel, Mellanox and Broadcom cards. All works. It would be awesome if next Ubuntu release got biosdevname v0.7.2 instead of a patched v0.4.1. Anyways, let me know what do do in order for this bug to be solved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535045 Title: [SRU] Biosdevname does not provide interface naming information for ConnecX4 Devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/biosdevname/+bug/1535045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535045] Re: [SRU] Biosdevname does not provide interface naming information for ConnecX4 Devices
I have the hardware. What do I need to do in order for this to be accepted and pushed to the repositories? And a side note is that this is fixed upstream, just upgrading to v0.7.2 will fix the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535045 Title: [SRU] Biosdevname does not provide interface naming information for ConnecX4 Devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/biosdevname/+bug/1535045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1595366] Re: Text invisible in GTK windows when resuming session
I've now stumbled on this issue twice. It's pretty rare. For me, I don't think it's directly tied to resuming a session (from suspend or just from the lock screen). I'm using nvidia-driver-430 with Geforce 1080 Ti on Ubuntu 18.04. ** Attachment added: "Ubuntu_invisible_letters.png" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1595366/+attachment/5297383/+files/Ubuntu_invisible_letters.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1595366 Title: Text invisible in GTK windows when resuming session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1595366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584475] Re: No input events for FutureMax Dance Mat
I also have FutureMax Dance Mat. I think the main problem is with Stepmania, however. I've been using the following patch for Stepmania. It works most of the time. https://github.com/stepmania/stepmania/pull/1745 Sometimes (after resuming from suspend and such) there are some intermittent failures to recognize the dance mat though. I haven't quite managed to track the cause of those down. But the patch definitely works. The reason that "vanilla" Stepmania doesn't work on Linux is because it expects analog inputs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584475 Title: No input events for FutureMax Dance Mat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840597] [NEW] Web Extension API, `browser.search.get` throws error `An unexpected error occurred`
Public bug reported: Web Extension API, `browser.search.get` throws error `An unexpected error occurred` on ubuntu's version of firefox 68 Steps to reproduce 1. Extract attached ff-extensions.zip 2. In the extracted folder, run `web-ext run` 3. In address bar type about:debugging. Temporary extensions 'Test Extension' will be loaded. 4. Click 'Debug' It gives an error in console tab, Error: "An unexpected error occurred" This issue is reproducible only with the Firefox installations from 'Ubuntu Software', not with the Firefox downloads from Mozilla's page. This is the possible root cause for "Tridactyl is broken on ubuntu's version of firefox 68", see https://github.com/tridactyl/tridactyl/issues/1670 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 68.0.1+build1-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-55.60~16.04.2-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anoop 2183 F pulseaudio BuildID: 20190718135155 Channel: Unavailable CurrentDesktop: Unity Date: Mon Aug 19 01:09:47 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1141 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-01-08 (587 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.100 metric 600 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1141 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=69.0/20190807220259 (Out of date) Profile0 (Default) - LastVersion=68.0.1/20190718135155 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to xenial on 2018-09-10 (342 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 0G0G6Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd08/07/2017:svnDellInc.:pnPrecision3520:pvr:rvnDellInc.:rn0G0G6Y:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 3520 dmi.sys.vendor: Dell Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "ff-extensions.zip" https://bugs.launchpad.net/bugs/1840597/+attachment/5283206/+files/ff-extensions.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840597 Title: Web Extension API, `browser.search.get` throws error `An unexpected error occurred` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1840597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824705] [NEW] gnome-sound-recorder crashes when trying to play sound clip
Public bug reported: When I open the "Sound Recorder" program (gnome-sound-recorder) it shows a list of sound clips that I have recorded earlier. If I click the play button next to any of the sound clips, the program crashes. The gnome-sound-recorder version used is 3.28.1-4 Expected behavior: sound clip is played. Observed behavior: program crashed, no sound played. This problem is reproducible, it crashes like this every time I try it. Here is some of the info from the .crash file that was created in the /var/crash/ directory: ProblemType: Crash Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 15:18:00 2019 DistroRelease: Ubuntu 18.10 ExecutablePath: /usr/bin/gjs-console ExecutableTimestamp: 1542889273 ProcCmdline: /usr/bin/gjs /usr/bin/gnome-sound-recorder More detailed info is available in the attached file. ** Affects: gnome-sound-recorder (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Part of crash file that was generated in /var/crash directory" https://bugs.launchpad.net/bugs/1824705/+attachment/5255688/+files/truncated_usr_bin_gjs-console.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824705 Title: gnome-sound-recorder crashes when trying to play sound clip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-sound-recorder/+bug/1824705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823404] [NEW] Memory errors reported by valgrind for gdebi-gtk
Public bug reported: This is for gdebi version 0.9.5.7+nmu2. When running gdebi-gtk through valgrind, for example like this: valgrind gdebi-gtk -h that shows lots of memory errors, for example: - Conditional jump or move depends on uninitialised value(s) - Use of uninitialised value of size 8 - Invalid read of size 4 - Address 0x4e68020 is 304 bytes inside a block of size 2,208 free'd and so on. So there are bugs in the code that can cause the program to crash. One example of a used that got a crash is here: https://askubuntu.com/questions/1131516/gdebi-gtk-segmentation-fault-core-dumped ** Affects: gdebi (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/1823404 Title: Memory errors reported by valgrind for gdebi-gtk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1823404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574287] Re: tasksel: forcefully removes packages when tasks overlap
I just ran into this bug. Started uninstalling everything when I was removing lamp-server. Thankfully I caught it at about 15% and killed the session when I started noticing things disappearing. This is a critical disastrous bug. How has it not been touched in so long? If it's not going to get fixed, at least remove tasksel out of production or at least remove the remove function from it. This is ridiculous. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/574287 Title: tasksel: forcefully removes packages when tasks overlap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/574287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817638] [NEW] I don't understend this problens, I will try again now
Public bug reported: Sorry, I Don't more information about this. Thank you ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.9 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: overlay dm_mirror dm_region_hash dm_log hid_generic usbhid hid uas usb_storage rtsx_pci_sdmmc amdkfd amd_iommu_v2 radeon i915 r8169 psmouse mii ahci ttm i2c_algo_bit libahci drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops rtsx_pci drm video fjes ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CasperVersion: 1.376.2 Date: Mon Feb 25 20:26:09 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/custom.seed boot=casper initrd=/casper/initrd.gz quiet splash -- LiveMediaBuild: Astronomy Linux 16.04 "First" (20190107) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages ubiquity-2.21.63.9 xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817638 Title: I don't understend this problens, I will try again now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1817638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815249] [NEW] error when installing ubuntu 18.04 from USB Drive
Public bug reported: After I choose the partition to install Ubuntu, i got the error. I was trying to install it in my new HD. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 8 19:34:11 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=pt_BR.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815249 Title: error when installing ubuntu 18.04 from USB Drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1815249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535045] Re: Biosdevname does not provide interface naming information for ConnecX4 Devices
I'm also affected by this (Mellanox ConnectX-4). Ubuntu 16.04.5 LTS kernel 4.15.0-42-generic biosdevname 0.4.1-0ubuntu9 Is there a packaged version of biosdevname with the patch? Why does Xenial from 2016 have a biosdevname from 2012? There are lot newer versions of biosdevname at http://linux.dell.com/files/biosdevname/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535045 Title: Biosdevname does not provide interface naming information for ConnecX4 Devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/biosdevname/+bug/1535045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803871] Re: [HP Spectre x360 Convertible 15-ch0xx, Realtek ALC295, Speaker, Internal] No proper automute when playback is active on headphones plug in
Audio recording of this problem. @0sec Front... _noise_ _silence_(background-noise-only)_ @3sec Fron _noise_ _silence_(background-noise-only)_ ** Attachment added: "playback -> plug in -> noise -> plug out -> silence; 2x" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1803871/+attachment/5213923/+files/bug1803871_noise-recording.ogg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803871 Title: [HP Spectre x360 Convertible 15-ch0xx, Realtek ALC295, Speaker, Internal] No proper automute when playback is active on headphones plug in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1803871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803871] Re: [HP Spectre x360 Convertible 15-ch0xx, Realtek ALC295, Speaker, Internal] No proper automute when playback is active on headphones plug in
This weird behavior isn't new and has been persisting since May (when I installed Ubuntu on this device for the first time). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803871 Title: [HP Spectre x360 Convertible 15-ch0xx, Realtek ALC295, Speaker, Internal] No proper automute when playback is active on headphones plug in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1803871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803871] [NEW] [HP Spectre x360 Convertible 15-ch0xx, Realtek ALC295, Speaker, Internal] No proper automute when playback is active on headphones plug in
Public bug reported: When some audio playback is active (e.g. playing music with Audacious) and one plugs in headphones, audio will get played on the headphones, but the internal speakers don't really mute. Instead they get "stuck" at some constant sound. To work-around this bug, one has to pause all audio playback before plugging in headphones. (Or plug out headphones to stop the "stuck" sound) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: elias 1688 F...m pulseaudio /dev/snd/controlC0: elias 1688 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Sun Nov 18 14:37:51 2018 InstallationDate: Installed on 2018-10-20 (28 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: No auto-mute between outputs Title: [HP Spectre x360 Convertible 15-ch0xx, Realtek ALC295, Speaker, Internal] No automute UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2018 dmi.bios.vendor: AMI dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83BB dmi.board.vendor: HP dmi.board.version: 60.31 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.21:bd06/14/2018:svnHP:pnHPSpectrex360Convertible15-ch0xx:pvr:rvnHP:rn83BB:rvr60.31:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-ch0xx dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803871 Title: [HP Spectre x360 Convertible 15-ch0xx, Realtek ALC295, Speaker, Internal] No proper automute when playback is active on headphones plug in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1803871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803704] [NEW] package libflite1:amd64 2.0.0-release-1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.
Public bug reported: erro ao processar o pacote libflite1:amd64 (--configure): O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Erros foram encontrados durante o processamento de: libflite1:amd64 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libflite1:amd64 2.0.0-release-1 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Nov 15 17:08:50 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libasound2 1.1.0-0ubuntu1 libasound2-data 1.1.0-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. InstallationDate: Installed on 2018-11-05 (10 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: flite Title: package libflite1:amd64 2.0.0-release-1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: flite (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803704 Title: package libflite1:amd64 2.0.0-release-1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flite/+bug/1803704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803363] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1803363/+attachment/5213178/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803363 Title: The default shortcut for taking a screenshot kills X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803363] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1803363/+attachment/5213177/+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/1803363 Title: The default shortcut for taking a screenshot kills X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803363] Re: The default shortcut for taking a screenshot kills X
apport information ** Tags added: apport-collected bionic ** Description changed: I was looking for the default key for taking a screenshot from Unity/GNOME settings and found a list of keyboard shortcuts (as in the attached screenshot). It turns out that Ctrl+Alt+Print also happens to kill X by default. This is not optimal:-) + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 18.04 + GsettingsChanges: + b'org.gnome.shell' b'command-history' redacted by apport + b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" + InstallationDate: Installed on 2018-11-13 (2 days ago) + InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-39-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1803363/+attachment/5213176/+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/1803363 Title: The default shortcut for taking a screenshot kills X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800523] [NEW] el medio de instalacion no es adecuado
Public bug reported: La imagen de ubuntu 18 se grabo en una memoria usb de 16 gb con rufus. Cuando se estan copiando los datos al disco duros(ssd 240 gb) sale que la instalacion no puede continuar porque los datos no estan correctos en el medio. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 29 13:48:55 2018 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=es_CO.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CO.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1800523 Title: el medio de instalacion no es adecuado To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1800523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799059] Re: GNOME Screenshot crashes on "Grab the current window"
yeah, it's a Budgie session (Ubuntu Budgie). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799059 Title: GNOME Screenshot crashes on "Grab the current window" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1799059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799059] Re: GNOME Screenshot crashes on "Grab the current window"
Here you are. ** Attachment added: "gdb --args gnome-screenshot -i >log.txt 2>&1" https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1799059/+attachment/5204981/+files/log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799059 Title: GNOME Screenshot crashes on "Grab the current window" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1799059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799740] Re: Moving desktop icons places them with some offset
attached a should-is comparison to the original message -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799740 Title: Moving desktop icons places them with some offset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1799740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799740] [NEW] Moving desktop icons places them with some offset
Public bug reported: Desktop Environment: Budgie Note: I have HighDPI scaling enabled (200%). Moving icons on desktop doesn't place them at the position where you drag them to, but about 100px top-left from the target position. This "error offset" is constant, though. It does NOT get bigger on different (more bottom right) positions. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed Oct 24 17:33:51 2018 InstallationDate: Installed on 2018-10-20 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Low Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "should-is.png" https://bugs.launchpad.net/bugs/1799740/+attachment/5204955/+files/should-is.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799740 Title: Moving desktop icons places them with some offset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1799740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788727] Re: upgrade crashing due to unsigned kernels
Maybe signing the mainline kernels (kernel.ubuntu.com/~kernel- ppa/mainline/) could prevent this happening for some users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788727 Title: upgrade crashing due to unsigned kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1788727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799059] [NEW] GNOME Screenshot crashes on "Grab the current window"
Public bug reported: GNOME Screenshot crashes on "Take screenshot" when "Grab the current window" is selected. "Grab the whole screen" and "Select area to grab" are working fine. Might be related to Budgie. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-screenshot 3.25.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Oct 21 17:26:37 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799059 Title: GNOME Screenshot crashes on "Grab the current window" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1799059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796533] [NEW] installation falled
Public bug reported: " the installer encountered an unrecoverable error. A dsktop sessionwill be run so that you may investigate the problem or try installingagain. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity 2.18.8.1 [modified: usr/share/ubiquity/apt-setup] ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CasperVersion: 1.340 Date: Sat Oct 6 22:42:41 2018 LiveMediaBuild: Santoku 14.04 - Release amd64 SourcePackage: ubiquity UbiquitySyslog: UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug custom trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796533 Title: installation falled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1796533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771239] [NEW] [Inspiron 5537, Realtek ALC3223, Speaker, Internal] No sound at all
Public bug reported: My sound was working just fine, then tonight I came to use my notebook, and noticed that there was no sound from any applications. Using the ubuntu settings sound test, I was getting audio from both speaker and headphones, but moving the volume bar doesn't do any feedback, chrome and spotivyhave no audio. Reinstalled the pulseaudio, now moving the volume bar plays the feedback "beep", but still no audio from applications, and no more audio on speaker test! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: esoares6391 F pulseaudio /dev/snd/controlC0: esoares6391 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 14 22:11:08 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-18 (603 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2642 F pulseaudio esoares6391 F pulseaudio /dev/snd/controlC0: gdm2642 F pulseaudio esoares6391 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Inspiron 5537, Realtek ALC3223, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to bionic on 2017-10-24 (202 days ago) dmi.bios.date: 08/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0YK7DY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron5537:pvrA09:rvnDellInc.:rn0YK7DY:rvrA00:cvnDellInc.:ct8:cvrA09: dmi.product.family: 00 dmi.product.name: Inspiron 5537 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771239 Title: [Inspiron 5537, Realtek ALC3223, Speaker, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1771239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770156] [NEW] missing freecad example files
Public bug reported: 1) Description:Ubuntu 17.10 Release:17.10 2) freecad: Installed: 0.16+dfsg2-3 Candidate: 0.16+dfsg2-3 Version table: *** 0.16+dfsg2-3 500 500 http://se.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 100 /var/lib/dpkg/status 3) I expected the application to load the default example files when clicked upon. 4) Error message popped up with file-not-found error ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: freecad 0.16+dfsg2-3 ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 9 14:23:05 2018 InstallationDate: Installed on 2018-03-11 (59 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: freecad UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: freecad (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770156 Title: missing freecad example files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freecad/+bug/1770156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767499] [NEW] grub package could not be installed
Public bug reported: I had Ubuntu installed beside Arch. I finished setting Arch up so I deleted Ubuntu. This rendered my system unbootable. I'm trying to install another distro beside Arch to try to correct the problem but no distro so far has been able to install grub. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 Date: Fri Apr 27 16:04:05 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic lubuntu ubiquity-18.04.14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767499 Title: grub package could not be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1767499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1755642] Re: Keeps crashing at the same point in the install. Error 5
Hello Jean; That may be true as you say but there is just one problem with that. I attempted to reinstall 16.04 and it also crashed during installation of Files. in both instances I was able to go online download stuff but only while the disk was in the drive. The machine was working fine until the problem with password occurred. Now it only appears to get worse. Right now I am attempting to re-install 16.04 again. I hope that this one is successful. It just said that installation is complete and that I should restart. I will see how this works. Winston Elias On Wed, Mar 14, 2018 at 4:47 AM, Jean-Baptiste Lallement < jean-baptiste.lallem...@ubuntu.com> wrote: > Thanks for your report. > > >From syslog > Mar 14 01:34:52 ubuntu kernel: [ 7171.752143] sr 0:0:0:0: [sr0] tag#0 > FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE > Mar 14 01:34:52 ubuntu kernel: [ 7171.752148] sr 0:0:0:0: [sr0] tag#0 > Sense Key : Medium Error [current] > Mar 14 01:34:52 ubuntu kernel: [ 7171.752151] sr 0:0:0:0: [sr0] tag#0 Add. > Sense: L-EC uncorrectable error > Mar 14 01:34:52 ubuntu kernel: [ 7171.752156] sr 0:0:0:0: [sr0] tag#0 CDB: > Read(10) 28 00 00 0c d0 e5 00 00 02 00 > Mar 14 01:34:52 ubuntu kernel: [ 7171.752159] print_req_error: I/O error, > dev sr0, sector 3359636 > Mar 14 01:34:52 ubuntu kernel: [ 7171.752251] print_req_error: I/O error, > dev loop0, sector 3358672 > Mar 14 01:34:52 ubuntu kernel: [ 7171.752324] SQUASHFS error: > squashfs_read_data failed to read block 0x667e4775 > > It seems your installation medium is corrupted. Please recreate it or > try with another one. > > Don't hesitate to file any bug you may find. > > ** Changed in: ubiquity (Ubuntu) >Status: New => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1755642 > > Title: > Keeps crashing at the same point in the install. Error 5 > > Status in ubiquity package in Ubuntu: > Invalid > > Bug description: > It crashes during file install for Linux 18.04 > It said Error 5 > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: ubiquity 18.04.3 > ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 > Uname: Linux 4.15.0-10-generic x86_64 > ApportVersion: 2.20.8-0ubuntu10 > Architecture: amd64 > CasperVersion: 1.389 > CurrentDesktop: ubuntu:GNOME > Date: Tue Mar 13 21:35:04 2018 > InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper > initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity > LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311) > 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) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/ > 1755642/+subscriptions > -- Quick Term Quote <https://aqterm.aq2e.com/ms/winston> http://JustLoansAlone.com To do unto all men as you would have them do unto you, was and still is the best way to live. Live well have a great day. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755642 Title: Keeps crashing at the same point in the install. Error 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1755642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755642] [NEW] Keeps crashing at the same point in the install. Error 5
Public bug reported: It crashes during file install for Linux 18.04 It said Error 5 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CasperVersion: 1.389 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 13 21:35:04 2018 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.3 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755642 Title: Keeps crashing at the same point in the install. Error 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1755642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1754993] Re: will not accept password, Will not reboot
Hello Tech Support; My problems are just getting worse. My 16.04 desktop stopped accepting my password. After many attempts and after checking online for help and finding that nothing worked I attempted to install 18.08. That is what caused me to send in that crash report. On the second attempt I got much further before that crash occurred with the option to continue. It installed but the pointer kept going around and around as though something was still being installed. That stayed on for almost 2 hours until I stopped it. I was then instructed to eject the DVD and press Enter. I was able to go online check several different things while all the while the pointer kept going round and around. I restarted the computer once more and the 18.08 installation disappeared completely. Now when I attempt to start it it goes right back to my original problem insisting that I put in my password. The DVD gets ejected every time I insert it into the drive. I cannot boot from the DVD neither can I find the installed version of 18.04. I need HELP ASAP. W Elias On Sun, Mar 11, 2018 at 4:17 PM, Ubuntu Foundations Team Bug Bot < 1754...@bugs.launchpad.net> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. We noticed that you were installing the LTS version of > Ubuntu using an older version of the installation media. The latest > point release of 16.04 is 16.04.3. Please try installing from that > version of the installation media and see if that resolves your issue. > Thanks in advance! > > [This is an automated message. I apologize if it reached you > inappropriately; please just reply to this message indicating so.] > > ** Changed in: ubiquity (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1754993 > > Title: > will not accept password, Will not reboot > > Status in ubiquity package in Ubuntu: > Incomplete > > Bug description: > Not sure what the problem is, but the computer refuses to accept > pastword. After many attempts I tried a reinstall that has crashed and > it suggested that I file this report. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: ubiquity 2.21.63.2 > ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 > Uname: Linux 4.4.0-31-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.1 > Architecture: amd64 > CasperVersion: 1.376 > Date: Sun Mar 11 17:13:12 2018 > InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper > initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity > LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 > SourcePackage: ubiquity > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/ > 1754993/+subscriptions > -- Quick Term Quote <https://aqterm.aq2e.com/ms/winston> http://JustLoansAlone.com To do unto all men as you would have them do unto you, was and still is the best way to live. Live well have a great day. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754993 Title: will not accept password, Will not reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1754993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754993] [NEW] will not accept password, Will not reboot
Public bug reported: Not sure what the problem is, but the computer refuses to accept pastword. After many attempts I tried a reinstall that has crashed and it suggested that I file this report. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CasperVersion: 1.376 Date: Sun Mar 11 17:13:12 2018 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63.2 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754993 Title: will not accept password, Will not reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1754993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736138] Re: stress-ng does end after set time with -t or --timeout
Yes, I am seeing this behaviour. My mistake - I did not understand that the -t or --timeout define the length of test using one type of stressor, not the length of the whole test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736138 Title: stress-ng does end after set time with -t or --timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1736138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736138] [NEW] stress-ng does end after set time with -t or --timeout
Public bug reported: Expected behaviour when running stress-ng --class cpu --sequential 4 --timeout 30s -v --tz or stress-ng --class cpu --sequential 4 -t 30 -v --tz is the test should stop after 30 seconds. The test goes on until user does CTRL-C in terminal window. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: stress-ng 0.05.23-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: Unity Date: Mon Dec 4 13:57:27 2017 InstallationDate: Installed on 2017-11-27 (6 days ago) InstallationMedia: Ubuntu 16.04.3 LTS (Finnish Remix) "Xenial Xerus" - Release amd64 (20170801) SourcePackage: stress-ng UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: stress-ng (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736138 Title: stress-ng does end after set time with -t or --timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1736138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448254] Re: openvswitch systemd unit file ordering wrong
I might as well just add some facts and my logs. First of all, I have one Xenial node where open vswitch worked, guessing that that time open vswitch daemon started before trying to setup network. And then on other machines it doesn't work cause the daemon isn't started before trying to setup networking. Here are the logs from a broken system. ``` Sep 12 16:11:07 vm10 systemd[1]: Reached target Network. Sep 12 16:11:07 vm10 systemd[1]: networking.service: Failed with result 'exit-code'. Sep 12 16:11:07 vm10 systemd[1]: networking.service: Unit entered failed state. Sep 12 16:11:07 vm10 systemd[1]: Failed to start Raise network interfaces. Sep 12 16:11:07 vm10 systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE Sep 12 16:11:07 vm10 ntpdate[3027]: no servers can be used, exiting Sep 12 16:11:07 vm10 ifup[2858]: Failed to bring up br0. Sep 12 16:11:07 vm10 ifup[2858]: Cannot find device "br0" Sep 12 16:11:07 vm10 ifup[2858]: Failed to bring up mgm. Sep 12 16:11:07 vm10 ifup[2858]: Cannot find device "mgm" Sep 12 16:11:07 vm10 ifup[2858]: mgm: ERROR while getting interface flags: No such device Sep 12 16:11:07 vm10 ifup[2858]: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) Sep 12 16:11:07 vm10 ovs-vsctl[2991]: ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) Sep 12 16:11:07 vm10 ovs-vsctl[2991]: ovs|1|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --may-exist add-port br0 mgm vlan_mode=access -- set Interface mgm type=internal -- set interface mgm external-ids:iface-id=vm10-mgm-vif Sep 12 16:11:07 vm10 ifup[2858]: Failed to bring up bond0. Sep 12 16:11:07 vm10 ifup[2858]: Cannot find device "bond0" Sep 12 16:11:07 vm10 kernel: bnx2x :01:00.1 em2: NIC Link is Up, 1 Mbps full duplex, Flow control: none Sep 12 16:11:06 vm10 kernel: bnx2x :01:00.1 em2: using MSI-X IRQs: sp 50 fp[0] 52 ... fp[7] 59 Sep 12 16:11:06 vm10 kernel: bnx2x :01:00.0 em1: NIC Link is Up, 1 Mbps full duplex, Flow control: none Sep 12 16:11:06 vm10 kernel: bnx2x :01:00.0 em1: using MSI-X IRQs: sp 39 fp[0] 41 ... fp[7] 48 Sep 12 16:11:05 vm10 ifup[2858]: bond0: ERROR while getting interface flags: No such device Sep 12 16:11:05 vm10 ifup[2858]: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) Sep 12 16:11:05 vm10 ovs-vsctl[2922]: ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) Sep 12 16:11:05 vm10 ovs-vsctl[2922]: ovs|1|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --fake-iface add-bond br0 bond0 em1 em2 vlan_mode=native-untagged bond_mode=balance-tcp lacp=active other_config:lacp-time=fast -- Sep 12 16:11:05 vm10 ifup[2858]: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) Sep 12 16:11:05 vm10 ovs-vsctl[2908]: ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) Sep 12 16:11:05 vm10 ovs-vsctl[2908]: ovs|1|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --may-exist add-br br0 -- Sep 12 16:11:05 vm10 systemd[1]: Starting Raise network interfaces... ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448254 Title: openvswitch systemd unit file ordering wrong To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448254] Re: openvswitch systemd unit file ordering wrong
Can also confirm that Marks patch worked. This was two years ago, why haven't this been fixed yet? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448254 Title: openvswitch systemd unit file ordering wrong To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1663926] Re: Dell XPS 15 9560 (Nvidia 1050) black screen, Feb 11, 2017
Hi everyone, You can solve the non-boot issue adding a parameter to kernel. It worked to me in my dell xps 15 9560 and Ubuntu 17.04. you must, with root privileges, edit /etc/default/grub and add a parameter to the default kernel command line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_rev_override=1" after that, run the following commands as superuser: update-grub update-grub2 I suggest installing bumblebee, since prime-select does not help to reduce noise and power consuptiom. I actually do not now what it is good for. With bumblebee you will be running on intel most of the time and when some application requires strong graphics acceleration, you call it using the optirun command. To me this is perfect because I only use the GTX to run my CUDA programs and this allows me to leave the GPU for number crunching only. To instal and configure bumblebee, follow these instructions. I use nvidia-375 instead of the driver the author suggests: http://www.webupd8.org/2016/08/how-to-install-and-configure-bumblebee.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1663926 Title: Dell XPS 15 9560 (Nvidia 1050) black screen, Feb 11, 2017 To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1663926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1663926] Re: Dell XPS 15 9560 (Nvidia 1050) black screen, Feb 11, 2017
As a side note, you can rescue your system if it is currently not booting. Press esc during boot to bring grub options and select safe mode (I think this is the name, it should be the last boot option), it may be tricky to get the correct timing for pressing esc, and some people say shift is the correct key, YMMV. In safe mode, select root from the menu. Then run the following: mount -o rw,remount / prime-select nvidia reboot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1663926 Title: Dell XPS 15 9560 (Nvidia 1050) black screen, Feb 11, 2017 To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1663926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1663926] Re: Dell XPS 15 9560 (Nvidia 1050) black screen, Feb 11, 2017
I can confirm this issue. What can I do? Is there any way of not having to reinstall the whole thing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1663926 Title: Dell XPS 15 9560 (Nvidia 1050) black screen, Feb 11, 2017 To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1663926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1443873] Re: Dell XPS 15 (9530) - Wifi hard blocked on startup
I am having an old problem it appears. My Dell XPS 1530 suddenly stopped working on WiFi. I have tried everything I found in Ubuntu help forums but so far nothing worked. Also I have another bug with my laptop. On starting a box appears which states "System program problem Detected." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1443873 Title: Dell XPS 15 (9530) - Wifi hard blocked on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1443873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699487] [NEW] package libc6:i386 2.23-0ubuntu9 failed to install/upgrade: package libc6:i386 is not ready for configuration cannot configure (current status 'half-installed')
Public bug reported: Description: Ubuntu 16.04 LTS ekammoun@ekammoun-ThinkPad-E550:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: linux-generic linux-headers-generic linux-image-generic 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. 1 not fully installed or removed. Need to get 0 B/2,269 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Y dpkg: error processing package libc6:i386 (--configure): package libc6:i386 is not ready for configuration cannot configure (current status 'half-installed') Errors were encountered while processing: libc6:i386 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libc6:i386 2.23-0ubuntu9 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 AptOrdering: libc6: Configure NULL: ConfigurePending Architecture: amd64 Date: Wed Jun 21 14:15:19 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 DpkgTerminalLog: dpkg: error processing package libc6:i386 (--configure): package libc6:i386 is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package libc6:i386 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-08-23 (301 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: glibc Title: package libc6:i386 2.23-0ubuntu9 failed to install/upgrade: package libc6:i386 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glibc (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699487 Title: package libc6:i386 2.23-0ubuntu9 failed to install/upgrade: package libc6:i386 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/glibc/+bug/1699487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1163886] Re: software-center crashed with signal 5 with WebKit 2.0+
I'm having a Software Center crash; please see: https://github.com/awesomeWM/awesome/issues/1828#issuecomment-307533174 Should I create a new issue for it? ** Bug watch added: github.com/awesomeWM/awesome/issues #1828 https://github.com/awesomeWM/awesome/issues/1828 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1163886 Title: software-center crashed with signal 5 with WebKit 2.0+ To manage notifications about this bug go to: https://bugs.launchpad.net/webkit-open-source/+bug/1163886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687249] [NEW] installing ubuntu restricted software package libappindicator3-1 12.10.1+16.04.20170215-0ubuntu1 failed to install/upgrade: el paquete libappindicator3-1 no está listo para configu
Public bug reported: a message indicate that a kg processs was using some resource when i have been installing the ubuntu restricted software ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libappindicator3-1 12.10.1+16.04.20170215-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat Apr 29 23:37:43 2017 ErrorMessage: el paquete libappindicator3-1 no está listo para configurarse no se puede configurar (estado actual `half-installed') InstallationDate: Installed on 2017-04-28 (2 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libappindicator Title: package libappindicator3-1 12.10.1+16.04.20170215-0ubuntu1 failed to install/upgrade: el paquete libappindicator3-1 no está listo para configurarse no se puede configurar (estado actual `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libappindicator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687249 Title: installing ubuntu restricted software package libappindicator3-1 12.10.1+16.04.20170215-0ubuntu1 failed to install/upgrade: el paquete libappindicator3-1 no está listo para configurarse no se puede configurar (estado actual `half-installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1687249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685063] [NEW] package libfreetype6:amd64 2.6.1-0.1ubuntu2.2 failed to install/upgrade: package libfreetype6:amd64 is already installed and configured
Public bug reported: Depois que eu instalei o sistema operacional de novo, ele ficou bugado, e esse problema surgiu depois que reinstalei o ubunto 16.04 lts ProblemaTipo: Pacote DistroRelease: Ubuntu 16.04 Pacote: libfreetype6: amd64 2.6.1-0.1ubuntu2.2 ProcVersionSign ature: Ubuntu 4.8.0-36. 36 ~ 16,04. 1-genérico 4.8.11 Uname: Linux 4.8.0-36-genérico x86_64 ApportVersion: 2.20.1-0ubuntu2.5 AptdaemonVersion: 1.1.1 + bzr982- 0ubuntu14 Arquitetura: amd64 Data: Fri Apr 21 01:48:25 2017 Dependências : Gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1: 6.0.1-0ubuntu1 libpng12-0 1.2.54-1ubuntu1 zlib1g 1: 1.2.8. Dfsg-2ubuntu4 DuplicateSignature: pacote: libfreetype6: amd64: 2. 6.1-0.1ubuntu2. 2 Remoção da embalagem Linux-headers- genérico- hwe-16. 04 (4.8.0.46.18) over (4.8.0.36.8) ... dpkg: pacote de processamento de erros libfreetype6: amd64 (--configure): pacote libfreetype6: amd64 já está instalado e configurado ErrorMessage: pacote libfreetype6: amd64 já está Instalado e configurado InstallationDate: Instalado em 2017-04-21 (0 dias há) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Lançamento amd64 (20170215.2) RelatedPackageV ersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: dpkg Título: pacote libfreetype6: amd64 2.6.1-0.1ubuntu2.2 falha ao instalar / atualizar pacote libfreetype6: ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package need-duplicate-check xenial ** Description changed: - depois que eu instalei o sistema operacional de novo, depois que ele - ficou bugado, ai tive que reinstalar e esse problema surgiu + Depois que eu instalei o sistema operacional de novo, ele ficou bugado, + e esse problema surgiu depois que reinstalei o ubunto 16.04 lts - ProblemType: Package - DistroRelease: Ubuntu 16.04 - Package: libfreetype6:amd64 2.6.1-0.1ubuntu2.2 - ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 - Uname: Linux 4.8.0-36-generic x86_64 - ApportVersion: 2.20.1-0ubuntu2.5 - AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 - Architecture: amd64 - Date: Fri Apr 21 01:48:25 2017 - Dependencies: - gcc-6-base 6.0.1-0ubuntu1 - libc6 2.23-0ubuntu7 - libgcc1 1:6.0.1-0ubuntu1 - libpng12-0 1.2.54-1ubuntu1 - zlib1g 1:1.2.8.dfsg-2ubuntu4 - DuplicateSignature: - package:libfreetype6:amd64:2.6.1-0.1ubuntu2.2 - Unpacking linux-headers-generic-hwe-16.04 (4.8.0.46.18) over (4.8.0.36.8) ... - dpkg: error processing package libfreetype6:amd64 (--configure): - package libfreetype6:amd64 is already installed and configured - ErrorMessage: package libfreetype6:amd64 is already installed and configured - InstallationDate: Installed on 2017-04-21 (0 days ago) - InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) - RelatedPackageVersions: - dpkg 1.18.4ubuntu1.1 - apt 1.2.19 - SourcePackage: dpkg - Title: package libfreetype6:amd64 2.6.1-0.1ubuntu2.2 failed to install/upgrade: package libfreetype6:amd64 is already installed and configured - UpgradeStatus: No upgrade log present (probably fresh install) + ProblemaTipo: Pacote + DistroRelease: Ubuntu 16.04 + Pacote: libfreetype6: amd64 2.6.1-0.1ubuntu2.2 + ProcVersionSign ature: Ubuntu 4.8.0-36. 36 ~ 16,04. 1-genérico 4.8.11 + Uname: Linux 4.8.0-36-genérico x86_64 + ApportVersion: 2.20.1-0ubuntu2.5 + AptdaemonVersion: 1.1.1 + bzr982- 0ubuntu14 + Arquitetura: amd64 + Data: Fri Apr 21 01:48:25 2017 + Dependências : + Gcc-6-base 6.0.1-0ubuntu1 + libc6 2.23-0ubuntu7 + libgcc1 1: 6.0.1-0ubuntu1 + libpng12-0 1.2.54-1ubuntu1 + zlib1g 1: 1.2.8. Dfsg-2ubuntu4 + DuplicateSignature: + pacote: libfreetype6: amd64: 2. 6.1-0.1ubuntu2. 2 + Remoção da embalagem Linux-headers- genérico- hwe-16. 04 (4.8.0.46.18) over (4.8.0.36.8) ... + dpkg: pacote de processamento de erros libfreetype6: amd64 (--configure): + pacote libfreetype6: amd64 já está instalado e configurado + ErrorMessage: pacote libfreetype6: amd64 já está Instalado e configurado + InstallationDate: Instalado em 2017-04-21 (0 dias há) + InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Lançamento amd64 (20170215.2) + RelatedPackageV ersions: + dpkg 1.18.4ubuntu1.1 + apt 1.2.19 + SourcePackage: dpkg + Título: pacote libfreetype6: amd64 2.6.1-0.1ubuntu2.2 falha ao instalar / atualizar pacote libfreetype6: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685063 Title: package libfreetype6:amd64 2.6.1-0.1ubuntu2.2 failed to install/upgrade: package libfreetype6:amd64 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1685063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1633721] Re: Weird input behaviour in some Plasma stuff (Kicker, KRunner, privilege window)
@Denny that Ubuntu documentation only seeks to confuse me more... So if my keyboard input isn't controlled with fcitx, or ibus (I had to install it) then what was it being controller by? 0_o spooky -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633721 Title: Weird input behaviour in some Plasma stuff (Kicker, KRunner, privilege window) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1633721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1633721] Re: Weird input behaviour in some Plasma stuff (Kicker, KRunner, privilege window)
I will reiterate to everyone that ibus is not the default input method for Ubuntu/Kubuntu/Xubuntu etc. They all use fcitx. If everyone having this problem could just do as comment #25 suggests I strongly believe their problem will be solved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633721 Title: Weird input behaviour in some Plasma stuff (Kicker, KRunner, privilege window) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1633721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1633721] Re: Weird input behaviour in some Plasma stuff (Kicker, KRunner, privilege window)
Joel, Please do the following in a terminal: sudo apt purge ibus sudo dpkg-reconfigure fcitx sudo reboot Everything should be back to normal after this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633721 Title: Weird input behaviour in some Plasma stuff (Kicker, KRunner, privilege window) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1633721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677745] Re: Xcalib not working in any way
More information: as the bug report in Debian says, changing the driver to "intel" seems to fix the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677745 Title: Xcalib not working in any way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xcalib/+bug/1677745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1633721] Re: Weird input behaviour in some Plasma stuff (Kicker, KRunner, privilege window)
I am truly sorry for wasting everyone's time with so many junk posts. I finally figured out what to do instead of messing around with ibus which isn't even the default input method. it's this simple, go to a terminal and type sudo dpkg-reconfigure fcitx and then reboot. This works perfectly for me and I don't have to bother with ibus-daemon anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633721 Title: Weird input behaviour in some Plasma stuff (Kicker, KRunner, privilege window) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1633721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677745] [NEW] Xcalib not working in any way
Public bug reported: There is a bug report in Debian already: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851810 Not sure whether it helps to report it here, so just to be sure. Using Ubuntu 17.04 Beta with latest updates, no matter what is done with xcalib, there is the same error: "Error - unsupported ramp size 0" E.g. "xcalib -a -b .5" or "xcalib profile.icc". I use xcalib to adjust both gamma and brightness (i.e. the level of black, not brightness as in screen brightness). I haven't found any other way to do this with a laptop, so if you know any, please tell me. ** Affects: xcalib (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/1677745 Title: Xcalib not working in any way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xcalib/+bug/1677745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1633721] Re: Weird input behaviour in some Plasma stuff (Kicker, KRunner, privilege window)
One last thing everyone... you're gonna wanna put that code ibus-daemon -d -n --desktop=KDE on your list of autostart programs so it boots up every time the PC does. Also you will wanna change it if you end up using a different desktop environment of course (and possibly why I was having errors in the first place as I have about 3 different desktop environments installed on this system). -- 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/1633721 Title: Weird input behaviour in some Plasma stuff (Kicker, KRunner, privilege window) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1633721/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
