*** This bug is a duplicate of bug 1881941 ***
https://bugs.launchpad.net/bugs/1881941
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1881941, so it is being marked as such. Please
Public bug reported:
While dock is locked to the bottom of the screen and hidden while not in use,
once un-hidden/activated it will bounce back and forth between hidden and
un-hidden. This is much more apparent or frequent when there is a window that
is either maximized or has a boarder near
That's the wrong driver for your system which is why it doesn't install
properly.
The best and newest driver for Intel is the one you already have
installed:
/usr/lib/xorg/modules/drivers/modesetting_drv.so
If you really want to experiment with the old driver then the package to
install is:
** Changed in: bluez (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1894234
Title:
Bluetooth not working with Gnome in
OK thanks. Just to confirm, do the volume buttons work in Windows 10 on
the *same* laptop?
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1894338
*** This bug is a duplicate of bug 1001984 ***
https://bugs.launchpad.net/bugs/1001984
** Package changed: xorg (Ubuntu) => compiz (Ubuntu)
** This bug has been marked a duplicate of bug 1001984
Maximised window changes monitor through lock screen or suspend
--
You received this bug
There is an upstream fix gnome-shell!1174 but it doesn't seem to work.
So this bug can stay open.
** Changed in: gnome-bluetooth (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Medium
** No longer affects: indicator-bluetooth (Ubuntu)
Public bug reported:
I want to check if my video graphics card of Intel is installed in the system
but am unable to do so.
In terminal, I give the following command:
ramraj@luna:~$ sudo apt-get install xserver-xorg-video-intel
Reading package lists... Done
Building dependency tree
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lvm2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
Just tried a live USB of 20.04.1 and yes, the same problem persists
exactly as it is.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1894338
Title:
[Samsung Earphones
I installed linux-oem-20.04 and also turned on focal-proposed updates
and did apt-get update && apt-get upgrade.
Though -- this was only enough to get it to recognize the speaker. The
pitch/video speed is still wrong, so it's not really quite usable.
I should correct something I said earlier:
As of 14 Sep, this is working in groovy... looks like things are
progressing with groovy,
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1894234
Title:
Bluetooth not
The the server installer (and the respective 20.04 too.
https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-live-server-amd64.iso
I will check more installers in 12h or so
18.04.* create(d) proper fstabs
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alsa-driver (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
Same problem, what did you do exactly to let it work?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1895422
Title:
Sound card not detected on Dell Latitude 9510
Why no longer affects flatpak snapd, dpkg?
Adolfo Jayme, you're just another moron (The ideal solution should serve
as an umbrella for all packaging tools)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
which live installer: desktop or server?
** Changed in: base-files (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1895584
Public bug reported:
Current live server installer (20.04 / 20.04.1) creates fstab which never
schedules fsck.
when actual power failure occurs half of systems dont boot, other half come up
with scary errors in boot log.
fstab manual (in "mount" package) says explicitly that / filesystem whould
I'm having this problem too with an Huawei Matebook 13 2020 with
Microsoft 3600 bloetooth mouse.
[CHG] Device D7:1B:68:EE:63:C5 Trusted: yes
Changing D7:1B:68:EE:63:C5 trust succeeded
[bluetooth]# pair D7:1B:68:EE:63:C5
Attempting to pair with D7:1B:68:EE:63:C5
[CHG] Device D7:1B:68:EE:63:C5
$ journalctl -b -u apport-autoreport
Sep 14 13:01:52 rubberducky systemd[1]: Starting Process error reports when
automatic reporting is enabled...
Sep 14 13:02:07 rubberducky whoopsie-upload-all[145261]: Collecting info for
/var/crash/_usr_bin_gnome-shell.1000.crash...
Sep 14 13:02:07
The error message (the last 3 lines) keep repeating ad infinitum until I
manually remove the crash files in /var/crash as Rocky notes in
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/comments/13.
--
You received this bug notification because you are a member of Ubuntu
Touch
** Changed in: apport (Ubuntu)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Tags added: groovy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1894369
The output of both of the following commands would help us sort out what
is going on.
journalctl -b -u whoopsie
journalctl -b -u apport-autoreport
Thanks! Additionally, if this happening on a release other than Ubuntu
20.10 please let me know.
** Changed in: apport (Ubuntu)
Assignee:
Which release of Ubuntu are you running?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1894369
Title:
apport-autoreport.service fails to start in groovy after upgrading
@paelzer To correct myself this (s390x) regression is not due to the
snapd seeding issue, but LP: #1895576 which may have been already fixed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-groovy/groovy/s390x/s/systemd/20200903_184028_2bbdf@/log.gz
...
test_rsyslog (__main__.ServicesTest) ... FAIL
test_tmp_cleanup (__main__.ServicesTest) ... ok
test_tmp_mount
Forgot the mention that I'm on 20.10, upgraded from 20.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1895573
Title:
systemd[1]: Failed to start Process error reports
Masking apport-autoreport.service and apport.service solves the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1895573
Title:
systemd[1]: Failed to start Process
Public bug reported:
htop always shows 100% CPU for /sbin/init/splash
When I look the journalctl, I have always seen `systemd[1]: Failed to
start Process error reports when automatic reporting is enabled.` thing.
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
**
** Merge proposal linked:
https://code.launchpad.net/~paride/curtin/+git/curtin/+merge/390692
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1888726
Title:
** Package changed: ubuntu-meta (Ubuntu) => ubiquity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1895262
Title:
Installer windows do not fit on screen,
@paelzer I agree that the fact, i.e. that systemd autpkgtest is failing in
Groovy/s390x, but this is a real regression which is not due to flakiness of
tests-in-lxd.
Please don't reopen this bug, but file a new one or find one already opened. As
I see this is still LP: #1878225. I'm filing a
** No longer affects: flatpak (Ubuntu)
** No longer affects: snapd (Ubuntu)
** No longer affects: dpkg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1895382
Title:
I'm having the same problem with an Huawei Matebook D14 2020 R5 with their
bluetooth mouse.
What I noticed using bluetoothctl is that the mouse device ID changes:
D9:73:24:7E:1A:0E (random)
I've seen 0E, 0F, 0C, 0B, etc.
I don't know if it's suppose to be like that or not.
--
You received
I ran into this and applied the workaround of deleting all the files in
/var/crash to stop the journalctl spam and 100% CPU usage.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
Looks like a problem generating a new initramfs:
update-initramfs: Generating /boot/initrd.img-5.4.0-47-generic
mv: cannot stat '/boot/initrd.img-5.4.0-47-generic.new': No such file or
directory
I don't see any information about what went wrong though. The disk isn't
full, so that's not the
Public bug reported:
Hi,
it looks like there is an error in the manpage of resolved.conf.
Ubuntu 20.04.1 LTS
systemd 245.4-4ubuntu3.2
The manpage of resolved.conf says:
DNSSEC=
...
Defaults to "allow-downgrade"
So when I leave the resolved.conf un-edited, the value is
[Resolve]
...
** Tags added: ssc
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1794478
Title:
Automatic ipv4 not assigned to bond interface is manual ipv6 is
assigned to it
You seem to be experiencing recurring kernel crashes in the 'nouveau'
driver.
Rather than waiting for a fix I suggest just installing the proprietary
Nvidia driver from the 'Additional Drivers' app.
** Summary changed:
- the screen is hanging frequently and i am unable to perform any typing
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1895502
Title:
nouveau keeps crashing in nvkm_pmu_init
Status in linux package in
Good News!
This bug is still here. Same error on
Dell Inspiron 13-7353, Ubuntu 20.04.1 (Upgraded from 18.05.5),
Kernel:
Linux NOMIS-inspiron 5.4.0-47-generic #51-Ubuntu SMP Fri Sep 4 19:50:52 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
Filesystem btrfs, Storage: Samsung 650 SSD (1TB).
Was working
You have been subscribed to a public bug:
screen brightness automatically gets full even if I reduce it
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18
Uname: Linux 4.15.0-76-generic x86_64
ApportVersion:
Groovy
It seems this isn't over for groovy, it was mentioned that the issues in the
subtest "tests-in-lxd" would be related to some fstab issues in those issues.
But recently all architectures, but s390x recovered. I assume that the fstab
issue is fixed but something else surfaces now.
groovy
43 matches
Mail list logo
