Sent window showing the actual recipients
** Attachment added: "Sent message"
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/2069169/+attachment/5788799/+files/sent.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I am using evolution 3.52.0-1build2 from ubuntu 24.04. The email server
backend is Microsoft 365 connected using EWS.
When I compose a new email with multiple recipients in the "To" field or
the "Cc" field, the actual email is only sent to the first recipient
multiple times
Hey folks,
I think we may have encountered this or a variant of this while running
extremely strenuous Ceph performance tests on a very high speed cluster
we designed for a customer. We have a write-up that includes a section
on needing to disable iommu here:
Just tested this again, problem is still there. Is there any hope for a
fix for grub-efi-amd64 to reconfigure the device in the 23.10 upgrade
context? If not my system is going to be trapped running 23.04 with no
way to upgrade safely, which means I need to find a workaround.
--
You received
Same happening to me after updating to Ubuntu 21.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948882
Title:
PulseEffects does not properly initialize on startup
To manage notifications about
Public bug reported:
Install crashed sometime after selecting partition and then "Install"
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.17
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
NonfreeKernelModules: zfs
add-apt-repository also silently deletes the [trusted=yes] option, which
is appropriate but undocumented. There needs to be clearer documentation
on what options work and what doesn't. Hopefully all options are
supported.
--
You received this bug notification because you are a member of Ubuntu
@mark-harfouche, that did the trick for me, thanks.
So no need to change the bios, the latest impish kernel 5.13.0-20 boots
on my E15 Ryzen Thinkpad and the touchpad is functional.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
attached screenshot of the panic. sorry it's not very clear.
** Attachment added: "e15-kernel-panic.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946692/+attachment/5532009/+files/e15-kernel-panic.jpg
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Lenovo E15 laptop running Impish Indra
kernels 5.13.0-16 and 5.13.0-19 both panic
kernel-5.13.0-14 is the last kernel to boot ok.
I have a screenshot of the failed boot but don't know how to submit it.
It says "kernel stack is corrupted in elantech_change_report_id ..."
**
(In reply to Rachel Martin from comment #195)
> (In reply to NolanK from comment #193)
>
> Just to set the record straight: The fork you mentioned did NOT fix this bug.
> If fixed bug 1690395 with the (hacky) fix suggested in bug 1690395 comment
> #13. We agree 100% with the statement from bug
Public bug reported:
Installation (minimal not full) was sucessfull on same model number, part
number and product id dell wyse thin client, both had amd 1.4 Ghz processor,
2GB RAM and 8GB FLASH D. Both had the same BIOS as well.
Could this be a hardware issue (the FLASH Drive) causing this
This bug isn’t an enhancement and it’s never getting fixed so it should
be closed as WONTFIX instead of leaving it open for 13 years.
Add this defect to list of pull requests for when FF is forked to a more
community version.
--
You received this bug notification because you are a member of
Public bug reported:
I'm using Linode and have a server set up with Ubuntu 20.10. I ssh-ed in
and got a message telling me to upgrade Ubuntu, ok, so I did and at some
point during the process an error occurred and asked if I wanted to
"Send the problem to the developers" so I said yes and it gave
Another user affected on 20.04. Happened to me after resuming from
sleep. Alt+F2: R made it go away for me as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824874
Title:
undismissable,
It seems like there was no fix, after testing out 5.8.0-16.17 .
I also have the same question as buck2202 --- whenever a fix is
released, can we expect a backport to affected LTS kernels?
Thanks, and happy new year!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi there. Got the no-compositing with Window Manager Tweaks solution
working at the first try. AMD Radeon 535 with 2G. 20.04. Subscribing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873895
Title:
The qcow2 image created by virt-manager needed serial console to be
enabled in grub. I was just not seeing the logs.
** Information type changed from Public to Public Security
** Changed in: qemu (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a
Public bug reported:
Steps:
1.Created a qcow2 image using Ubuntu virt-manager. This qcow2 image
boots fine inside the virt-manager.
2.However, the same qcow2 image fails to boot when I try to boot it
using the qemu-system-x86_64:
#!/bin/bash
qemu-system-x86_64 -m 16384 -boot d -enable-kvm
Public bug reported:
I am a newb who used "sfill" to wipe (by overwriting) all the unused space on
the harddrive...I didn't use the attribute -f (for fast)...so it worked for
like 15 hours doing 38 passes. So I woke up this morning and saw that the hard
drive had zero space. Based on my
Quick update on my encounter with this issue in 18.04 against an
(ancient!) 2007 iMac... after updating "intel-microcode" to version
3.20200609 (which wasn't yet available when this was reported), I am no
longer able to repro the issue. All packages are up-to-date (for 18.04
anyway), and the
Changing `GRUB_TERMINAL=console` based on
https://medium.com/@leijerry888/get-grub-menu-back-after-installing-
ubuntu-20-04-alongside-windows-dab5de5afc37 fixed the issue for me.
However, this is still a bug.
Steps to reproduce:
1. Install Windows first.
2. Make some space on the disk for
Hope this one gets fixed soon. The notification is quite annoying.
Device: /org/freedesktop/UPower/devices/mouse_hidpp_battery_1
native-path: hidpp_battery_1
model:Wireless Mouse
serial: 4022-00-00-00-00
power supply: no
updated:
@Alejandro Miranda I've noticed the command moves the sound from the top
speakers to the bottom. Sounds, no doubt, but seems to disable to
speakers up top.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Not a problem.
Marco, please could you change this back to triaged?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876352
Title:
App Grid icons out of alignment when opening from overview
To
@yipchunmun what was the reason behind changing the status of this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876352
Title:
App Grid icons out of alignment when opening from overview
To
Ran into this today applying a mass set of updates to an 18.04 system
that was last updated sometime last year. Running on a 2007 iMac.
Apple hasn't made firmware updates for this model in years -- and
firmware updates require MacOS installed anyway AFIAK -- so that
approach is closed to me.
lisa@lisa-Legion-Y545-PG0:~$ ls /sys/class/backlight
acpi_video0
lisa@lisa-Legion-Y545-PG0:~$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861532
Title:
brightness control not working [Lenovo
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1877488/+attachment/5368598/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877488
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1877488/+attachment/5368604/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1877488/+attachment/5368603/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877488
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1877488/+attachment/5368610/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877488
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1877488/+attachment/5368596/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1877488/+attachment/5368608/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877488
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1877488/+attachment/5368597/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877488
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1877488/+attachment/5368606/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877488
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1877488/+attachment/5368599/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877488
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1877488/+attachment/5368609/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877488
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1877488/+attachment/5368600/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877488
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1877488/+attachment/5368607/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877488
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1877488/+attachment/5368595/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877488
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1877488/+attachment/5368605/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1877488/+attachment/5368602/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877488
Title:
apport information
** Tags added: apport-collected
** Description changed:
When the computer is suspended, moving the mouse (External logitech)
causes the computer to come out of hibernation. I can tell because the
Legion logo lights up. After a little while (minute?) it evidently
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1877488/+attachment/5368601/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877488
Title:
I've tried to see if I can find this bug in dash-to-dock master but if
it is there it's like finding a needle in a haystack.
Do you have any advice for how to track this down?
I'm beginning to think that this bug somehow only exists in the ubuntu-
dock branch, although I have no strong evidence
Public bug reported:
When the computer is suspended, moving the mouse (External logitech)
causes the computer to come out of hibernation. I can tell because the
Legion logo lights up. After a little while (minute?) it evidently
suspends again because the logo turns off again.
ProblemType: Bug
I will repeat the sequence and when it happens again I'll attach the
requested file. It might take a while as it doesn't happen often.
On 5/5/20 10:03 PM, Daniel van Vugt wrote:
> We would like to see the system log of a prior boot where the freeze
> occurred. To do that please:
>
> 1. Reproduce
Public bug reported:
The system was suspended, it recovered perfectly.
When I did a shutdown, the system hung with a message about waiting for Xorg.
After several minutes, I pressed the power button once and the system responded
with another message about sending sigkill to Xorg. Still didn't
I'll try and find some time this week to see if I can bisect on master.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876352
Title:
App Grid icons out of alignment when opening from overview
To
When I was bisecting git threw me into a few commits that did not have
the ubuntu-dock modifications and I was not able to spot the bug in
those.
I've tried to see if there is anything obviously broken in the bisected
commmit, but my lack of knowledge in gnome extensions means I haven't
found
After some further investigation (pulling down dash-to-dock and
compiling/running the v68 and v67 tags) I think this issue only exists
in the ubuntu dock variant of dash-to-dock.
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
Importance: Undecided
Status: New
** No longer
Public bug reported:
Plays fine on my Bluetooth device but drops out randomly for only about
a half second. Nothing else is being used at the time other than
Rhythmbox.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu
After some further help from the upstream bug ticket it looks like this
is an issue with the Ubuntu Dock (dash-to-dock).
If you disable that extension this issue no longer occurs.
** Bug watch added: github.com/micheleg/dash-to-dock/issues #1199
Public bug reported:
Affected version:
Ubuntu 20.04
Gnome Shell Version 3.36.1
Only tested on xorg
Bug summary:
When opening the App Grid (aka "Show Applications) from the window overview (I
don't know the technical terms) the icons shift out of alignment. This gets
worse if you have multiple
Public bug reported:
wifi connection problem
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-28-generic 5.4.0-28.32
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
Monitoring syslog I see the following when I try to change screen
brightness:
root@lisa-Legion-Y545-PG0:~# tail -f /var/log/syslog
Apr 27 10:46:55 lisa-Legion-Y545-PG0 kernel: [ 142.184842] nvme :06:00.0:
AER: device [15b7:5006] error status/mask=0001/e000
Apr 27 10:46:55
Attaching Journalctl log
** Attachment added: "Journalctl log using Nvidia after doing a few screen
brightness changes"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1874716/+attachment/5361785/+files/journalctl.log
--
You received this bug notification because you are a member of
I've submitted an upstream MR here based on the OP's fix with some
slight edits based on my tseting:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/286
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Upgrade from 19.10 to 20.04. The issue occured when trying to view the
differences from the local configuration file to the one included in the
updated package.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: smartmontools 7.1-1build1
ProcVersionSignature: Ubuntu
Also: the slider in settings does not change the brightness either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874716
Title:
Changing screen brightness fails
To manage notifications about
Public bug reported:
Lenovo Legion with Nvidia card:
FN+F5/F6 shows brightness changes, but the screen actually doesn't
change at all.
01:00.0 VGA compatible controller: NVIDIA Corporation TU117M [GeForce
GTX 1650 Mobile / Max-Q] (rev a1)
nvidia 20430848 538
@Boris Gjenero, try using the kernel parameter "iommu=soft" instead of
limiting the memory to 1GB. It will force the use of a 64MB swiotlb
bounce buffer to workaround this issue. Tested with Focal Fossa Beta ISO
(Kernel 5.4.0-21-generic) on my Optiplex 320 with 2GB of RAM.
--
You received this
Public bug reported:
I'm also having trouble getting it to recognize some other standard USB
external drives.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: util-linux 2.34-0.1ubuntu2.2
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
Uname: Linux 5.3.0-29-generic x86_64
73.0b12 (64-bit)
Has the same bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860830
Title:
Geolocation not working − the Google maps API always returns error
codes
To manage notifications
Public bug reported:
73.0b10 (64-bit)
Ubuntu 18.04 with all updates.
This problem started after a recent 'upgrade' to firefox.
I've verified this problem using other web browsers that work.
About a week ago geolocation from a web site started to fail, so I
installed the firefox-next PPA and
#26 worked for me, although possibly in an unexpected way.
gnome settings -> region and there, click on “manage installed
languages” then changed “keyboard input method system” to none instead
of ibus. Logout and login.
...When I clicked on “manage installed languages” it said this wasn't
fully
Same thing has happened to me.
Ubuntu 19.10 upgrade with all updates installed.
Game shows black screen with mouse control, but the game doesn't start. After
a minute I get the opening screen with the man in yellow suit, but no mouse
controls at all. I can alt-tab and try to switch to other
I confirm that latest bios fixes the problem on 5.0.0-25 using rtw88. So
the whole time it was related to the ACPI IVRS bug. I wonder how many of
these little model-specific quirk work-arounds are sitting in the
various kernel drivers.
--
You received this bug notification because you are a
Reverting to 5.0.0-20 fixed wifi for me, this kernel doesn't load rtwpci
module. I updated to 5.0.0-23 today, same problem as 5.0.0-21. I don't
see any errors but wifi does not find networks.
I added debug_mask option to kernel command line and output journalctl
-b0 is attached. I did not
I have the same issue with 5.0.0-21 kernel update. Wireless card
rtl8822be, this is bluetooth combo m.2 card. In Lenovo E585 laptop. I
do not see any obvious errors, I can load rtwpci kernel modules,
interface wlp4s0 is created, I scan with iw dev or iwlist and no
networks are found. In Windows,
** Attachment added: "journalctl -b0 from successful screen activation"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5270412/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This time I turned off the displayed, unplugged it, then left it
unplugged while I rebooted. After rebooting and logging in, I turned on
the display and plugged it in. Attached is the dmesg from this boot.
** Attachment added: "dmesg from functional boot"
This is still 100% reproducible. I have attached the dmesg below.
** Attachment added: "dmesg from 2019/06/06"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5269157/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
I did plug/unplug the monitor because if I do that enough times is
generally resolves the problem until the next time I reboot. It has not
done so this time. I also tried a new cable, but that does not fix the
problem either.
--
You received this bug notification because you are a member of
It seems unlikely to be a cable or signal problem since I can eventually
coax it into working, and it continues working until I reboot. If it
were a cable problem or something about the signal I would have to
physically modify the connection to create and/or correct the problem.
Since the mere act
** Attachment added: "output of journalctl -b0 > journal.txt (on Wayland)"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267691/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "output of xrandr > xrandr.txt (on Wayland)"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267692/+files/xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tried that and it didn't fix the problem. I am attaching the output of
some of those files again for further data.
** Attachment added: "dmesg output ( on Wayland)"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267690/+files/dmesg.txt
--
You received this
** Attachment added: "output of lspci -k"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267341/+files/lspcik.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "output of xrandr > xrandr.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267344/+files/xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "output of journalctl -b0 > journal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267343/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Image of the screen corruption"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267340/+files/IMG_20190528_160705.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "dmesg output"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267342/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830792
Public bug reported:
On my system I have two display: one in landscape, and one in portrait.
The landscape display is fine, but the portrait display is corrupted. If
I unplug the display from the computer for some time and then plug it
back in it will occasionally fix the problem.
Once the
@Hans P Möller, i've tested with kernel 5.1.0-050100rc3-generic and the
b44 module loaded and worked fine, but it created some others warnings
in the dmesg:
[ 44.045886] b44 :02:09.0: swiotlb buffer is full (sz: 1566 bytes)
[ 44.045906] WARNING: CPU: 1 PID: 565 at kernel/dma/direct.c:43
Public bug reported:
v5.2.18 dkms fails to build on bionic with the recently released 5.0
kernel from hwe-18.04-edge
I've attached a patch which doesn't seem to not work. It should
definitely be reviewed by someone with domain knowledge, though. The
problems were all use of interfaces
Terrific! Thanks for the quick response!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827804
Title:
Bash completion not working
To manage notifications about this bug go to:
Public bug reported:
The bash completions file is installed improperly by default. It is
currently installed as /usr/share/bash-
completion/completions/cargo.bashcomp.sh, but files in this directory
need to be named to match the command they complete. So it should
either be installed as
To reproduce it, try switching the order of your displays. For example,
make the display on port 0 be on the right of the display on port 1
(instead of the "natural" order of 0=left, 1=right.) I also notice that
changing the orientation of the primary display to "portrait right"
causes problems,
Yes, they are very similar.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825004
Title:
Ubuntu loses display settings on reboot, corrupts displays
To manage notifications about this bug go to:
Public bug reported:
I have two displays, one on display port, and one on VGA. The display
port display is a Seiki Pro 40" display in landscape at 3840x2160. The
VGA is an HP 24" display in portrait at 1920x1200.
If I boot with either display by itself, everything works fine. If I
plug in the
*** This bug is a duplicate of bug 1292398 ***
https://bugs.launchpad.net/bugs/1292398
I can confirm that it's not fixed. Rebooting has become a major problem
for me because it loses my display settings, corrupts the displays, and
I spend 20 minutes fixing everything.
--
You received this
Great quality http://bridge.bruceayoungesq.com
<http://bridge.bruceayoungesq.com/>
Charles Nelson
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/72871
Title:
Upgrade to 6.06 from 5.10
@Guillermo
The OS shouldn't be trying to raise the interface as it's already configured
during the boot process. You can't reconfigure the network interface while
you're booting from the network :)
You need to modify /etc/network/interfaces on your boot server to set the
interface to manual.
Works for me on 18.04.1
Do you have 'ip=dhcp' included in your kernel boot line?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765765
Title:
on nfsboot 18.04 bionic, internet addresses arn't
** Package changed: ubuntu => xrandr (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813757
Title:
xrandr short freeze of hardware accelerated video playback with
gstreamer
To manage
Public bug reported:
Hi,
i encounter a strange issue with hardware accelerated video playback
with gstreamer (vaapi) and calls to xrandr to query display information.
I dont know for sure what causes this behaviour, but i think it is the
intel driver or xrandr, or a combination of both.
Boy this bug is vexing. Another report of this bug has info that it was fixed
in the Curtin sources in December 2018.
https://bugs.launchpad.net/curtin/+bug/1527664
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Installer crashed grub could not be installed
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
1 - 100 of 2161 matches
Mail list logo
