Hello everyone,
I have exactly the same problem. The computer works perfectly on the power
supply, but on the battery, especially when the power supply is connected, it
freezes completely. It works flawlessly on Windows. Previously - 23.10 - it
also worked properly
--
You received this bug
After update to kernel 6.8.0-11 all firefox tabs crash.
Using 6.6.0.14 does not cause any problems.
My dmesg has the same info on libxul.so crashing as the reporter's:
[ 4270.862686] Sandbox Forked[18464]: segfault at 0 ip 717f2d94172e sp
717f21abd520 error 6 in
BTW it affects both my PCs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055973
Title:
Firefox trunk Gah. Your tab just crashed.
To manage notifications about this bug go to:
Public bug reported:
Executing `python3 /usr/share/netplan/netplan/configmanager.py` causes:
```
File "/usr/share/netplan/netplan/configmanager.py", line 28, in
from netplan import libnetplan
ModuleNotFoundError: No module named 'netplan'
```
As the `libnetplan` module is in the same
I have following kernels installed:
- 5.13.0-35-generic
- 5.14.0-1024-oem
- 5.14.0-1027-oem
Kernel 5.13 does not work. The other two do work.
I see the problem on Lenovo Ideapad 320.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Right now I'm using OEM kernel and everything works well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958523
Title:
[amdgpu] Static-noise-like effect
To manage notifications about this bug go
My screen looks like this:
https://postimg.cc/Tp2LJB4N
The right side of the screen changes very quickly. Sometimes it is black and
sometimes it looks like the rest of the screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached journal.txt.
** Attachment added: "journalctl.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958523/+attachment/5562797/+files/journalctl.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That didn't fix the bug in my case. Should I create new bug report?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958591
Title:
[amdgpu] Random noise 'static' display after internal display turned
I made a experiment and I can confirm static noise after waking from
suspend.
@jamesf My device model is Lenovo Ideapad 320. You can update your post.
I will copy my other post since we are tracking this bug here: When your
computer boots press escape (UEFI boot) or shift (BIOS boot). You
In my case the problem is severe. I can see login screen, but when I log
in I see a white noise screen. It renders my computer unusable. That is
unless I use older kernel.
There is how to do it: When your computer boots press escape (UEFI boot)
or shift (BIOS boot). You may have to try several
Public bug reported:
Hello,
I have encountered a bug in Ubuntu. When I turn on my laptop and log in (I can
see the login screen) I see static-noise-like effect. I was able to make a
screenshot and it depicts my desktop as if the problem didn't exist.
Switching to stable (non-HWE) kernel solves
Hello,
mdadm supports set of different metadata. Intel metadata is a part of it
(called IMSM). We (as Intel) are submitted a lot of fixes and features, all are
validated and tested. Beside upstream testing, we have our internal test scope,
focused on IMSM aspects. I can say with certainty that
yes, it is resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868708
Title:
mdmon: device descriptor is not closed
To manage notifications about this bug go to:
yes, it is resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/112
Title:
mdmonitor doesn't start recovery immediately
To manage notifications about this bug go to:
John - thanks for finding ==>
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926081
There is a great testing work done there.
For this thread I have been running kernel 4.15.0-144-generic for the
last 3 weeks and haven't seen the issue.
--
You received this bug notification because you
-generic: disk performance issue
I haven't seen this issue on virtual machines (VMware VMs Ubuntu 18/20).
At the moment, I'm testing "4.15.0-144-generic". To early to say it is free of
the bug - I will come back in a week.
Thanks
Mariusz
--
You received this bug notification because you ar
Hi Khaled,
I have finished testing the kernels - it took more time than I expected
but the results are:
4.15.0-136-generic: no issues
4.15.0-137-generic: disk performance issue
4.15.0-139-generic: disk performance issue
4.15.0-140-generic: disk performance issue
4.15.0-142-generic: disk
Hi,
I have done longer testing of kernel 140 and it has performance
degradation issue as well. It took a couple of days to fully max out
disk IOs on that kernel with the same load. Therefore, I came back to
testing the other kernels in longer time-window.
At the moment, I'm running kernel
Hi,
In the last 3 days, I have been testing the other kernels. The steps
which I took:
1. Boot to kernel-4.15.0-136.
2. Install kernel X, where X = 136,137,139,140:
sudo apt-get install linux-image-4.15.0-X-generic
linux-headers-4.15.0-X-generic linux-modules-4.15.0-X-generic
Cool cool, I will try to do what you have suggested - that make sense.
Will get back once I have some details.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928744
Title:
Disk IO very slow on
Hi,
I have done another test and compared the same server running on
4.15.0-136-generic and kernel 4.15.0-142-generic. Collected zabbix CPU
utilization graph which is showing the problem from the performance
point of view. On 4.15.0-136-generic, the server works normal and there
are no processes
Unable to run apport-collect 1928744 command.
** 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/1928744
Title:
Disk IO very slow on
Thanks a lot for coming back to me. I couldn't run apport-collect as we
don't have python-launchpadlib installed. I did check (apt install
python3-launchpadlib) and in my case it would install quite a lot of
dependent packages - we would like to avoid that due to the nature of
our server.
But I
** Package changed: ubuntu => linux-signed-hwe (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928744
Title:
Disk IO very slow on kernel 4.15.0-142-generic
To manage notifications about
Public bug reported:
After upgrading Ubuntu 18.04 kernel from 4.15.0-136-generic to kernel
4.15.0-142-generic disk IOs (writes) are suffering from terrible delay.
Time required to write 1GB of data to the dist is ~12 minutes.
1GB in 12 minutes:
strace -ttvvff -o mel.strace dd bs=1024k
Public bug reported:
Please update mdadm package for Hirsuteto latest upstream release.
mdadm-4.2-rc1 was released for this moment.
mdadm-4.2 on track.
I will notify if mdadm 4.2 will become available.
** Affects: mdadm (Ubuntu)
Importance: Undecided
Status: New
** Tags: vroc
mdadm-4.2-rc-1 has been released officially.
Could you update the mdadm version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890248
Title:
update mdadm for focal
To manage notifications about
Public bug reported:
Hi! I was installing Ubuntu and create /boot partition on sda6 (HDD). I
picked this partition to install boot program. But in BIOS it shows that
GRUB has been installed on another drive (SSD) - my main drive with
Windows.
** Affects: ubuntu
Importance: Undecided
.
Unfortunately, I have no idea how to remove this error from the system.
Yours sincerely, Mariusz.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1
ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-36-generic x86_64
Hello,
fix for second problem has been accepted upstream:
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=a64f1263a56bd8653267c1a9800daa0bc993a743
Mariusz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
mdadm-4.2 not yet released.
Feel free to close it if not applicable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890162
Title:
Update mdadm for bionic
To manage notifications about this bug go
mdadm-4.2 not released yet.
Feel free to close it if not applicable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890248
Title:
update mdadm for focal
To manage notifications about this bug go
Hi,
Patch has been accepted upstream:
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=cab9c67d461c65a1138359f9f6d39636466b90e4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/112
Hi,
sorry copy-paste mistake, here the correct ones:
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=e2308733910a157b0a4d4e78721f239d44b91a24
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=007087d0898a045901e4e120296e6d9b845b20a6
--
You received this bug
Hi,
Patches have been accepted upstream:
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=e2308733910a157b0a4d4e78721f239d44b91a24
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=cab9c67d461c65a1138359f9f6d39636466b90e4
--
You received this bug notification because
** Tags added: vroc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885191
Title:
[Focal] Installation Fails with "Invalid dep_id" when using Intel VROC
To manage notifications about this bug go
For 5.8 this is a simple backport with one conflict caused by function
md_make_request() renamed to md_submit_bio(). Then it can be easily
cherry picked to 5.4 but will need a change to use
generic_{start,end}_io_acct() instead of disk_{start,end}_io_acct(). I
can send you the backported patches
** 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/1891151
Title:
md: improve IO accounting
To manage notifications about this bug
Renaming or deleting the offending .so files makes GIMP start.
Ugly but effective.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893480
Title:
undefined symbols
To manage notifications about this
Me too (as of 2020-09-05):
mariusz:~> gimp
GEGL-Message: 22:03:19.420: Module
'/usr/lib/x86_64-linux-gnu/gegl-0.4/exr-save.so' load error:
/usr/lib/x86_64-linux-gnu/gegl-0.4/exr-save.so: undefined symbol:
_ZN7Imf_2_36HeaderC1EiifRKN9Imath_2_34Vec2IfEEfNS_9LineOrderENS_11CompressionE
G
** Tags added: vroc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758282
Title:
[INTEL UBUNTU 18.04] RAID reshape hangs after OS reboot
To manage notifications about this bug go to:
** Tags added: vroc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887143
Title:
mdmonitor closes mdstat fd if is empty
To manage notifications about this bug go to:
** Tags added: vroc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868708
Title:
mdmon: device descriptor is not closed
To manage notifications about this bug go to:
** Tags added: vroc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811228
Title:
Mdadm allows to change the name of the volume to empty and not trim
whitespaces.
To manage notifications about
** Tags added: vroc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/112
Title:
mdmonitor doesn't start recovery immediately
To manage notifications about this bug go to:
** Tags added: vroc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890162
Title:
Update mdadm for bionic
To manage notifications about this bug go to:
** Tags added: vrco
** Tags removed: vrco
** Tags added: vroc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890248
Title:
update mdadm for focal
To manage notifications about this bug go to:
** Tags added: vroc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887372
Title:
Cannot create lvm upon IMSM raid array
To manage notifications about this bug go to:
** Tags added: vroc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887640
Title:
IMSM: finish recovery when drive with rebuild fails
To manage notifications about this bug go to:
Public bug reported:
Currently reported IO stats may be incorrect or missing.
This adds correct statistics about in-flight IOs and IO processing time,
interpreted e.g. in iostat as await, svctm, aqu-sz and %util.
Commit:
Public bug reported:
Please update mdadm package for focal to latest upstream.
mdadm-4.2 in on way but no release date was committed yet.
Upstream contains a lot of various fixes for problems with specific hardware or
system configuration.
Also there are some fixes for sporadic bugs related
** Description changed:
Mdadm version available in bionic was released in march 2018. Since it many
various fixes has been added.
The most common and important of them (from IMSM site) are already reported:
https://bugs.launchpad.net/oem-priority/+bug/1868708
Public bug reported:
Mdadm version available in bionic was released in march 2018. Since it many
various fixes has been added.
The most common and important of them (from IMSM site) are already reported:
https://bugs.launchpad.net/oem-priority/+bug/1868708
** Description changed:
mdmonitor reacts on md events, it pools on /proc/mdstat file. Those
events are generated if a change on any mddevice is observed in kernel.
This is done asynchronously and can be caused by user space process
(mdadm called by udev or user), or by kernel itself
Hi,
mdmonitor needs to deal with other tasks, issue still in development.
Thanks, Mariusz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/112
Title:
mdmonitor doesn't start recovery immediately
Public bug reported:
mdmonitor reacts on md events, it pools on /proc/mdstat file. Those
events are generated if a change on any mddevice is observed in kernel.
This is done asynchronously and can be caused by user space process
(mdadm called by udev or user), or by kernel itself (drive is
Public bug reported:
Current version of mdadm doesn't have second fix for raid10.
Mdmon is not able do handle end recovery if drive was disconnected while
rebuild.
Steps to reproduce:
1. Create RAID10 and wait for resync.
#mdadm --create /dev/md/imsm0 --metadata=imsm --raid-devices=4 /dev/sda
** Summary changed:
- Cannot create lvm opon IMSM raid array
+ Cannot create lvm upon IMSM raid array
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887372
Title:
Cannot create lvm upon IMSM raid
Public bug reported:
The issue has been observed on 2.3.7 (Ubuntu 20.04).
Reported to lvm team:
https://bugzilla.redhat.com/show_bug.cgi?id=1855251
Steps to Reproduce:
1. Create IMSM raid array:
#mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1
#mdadm -CR vol -l1 -n2 /dev/nvme[01]n1 -z 5G
2. Create
Hello,
The main issue is in development, we need to deal with module reload and
descriptor handling.
The second one can be easily workaround by using systemctl service
(systemctl mdmonitor restart) instead of command line. Here error
handling is needed instead of quiet fail.
I will notify if
Public bug reported:
There was a change in mdadm to fix issue when md_mod is reloaded (not a case
for ubuntu because md_mod is build-in). Commit:
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=52209d6ee1183581e148791cf6ee4d60a0193b1d
The fix prevents mdmonitor from occupying
Hi, issue is fixed by:
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=91c97c5432028875db5f8abeddb5cb5f31902001
Thanks,
Mariusz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868708
Public bug reported:
When device disappears from the system "mdadm -If" is triggered by udev
and drive is removed from the corresponding array and container. The
missing close() in metadata manager (mdmon) causes that userspace
handler to the device is still opened (can be tracked by lsof -p
).
defect appears.
Thanks
Mariusz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758282
Title:
[INTEL UBUNTU 18.04] RAID reshape hangs after OS reboot
To manage notifications about this bug go
Please note that on a Dell laptop everything works as expected. The
difference most probably is caused by hardware in the laptop. Two
different modems do not work with Toshiba and both of them work with
Dell. The same up-to-date "focal fossa" system.
--
You received this bug notification because
Make the comment on Kubuntu irrelevant.
I have launched Kubuntu Live CD daily and the same behavior can be observed.
The laptop is Toshiba Satellite L755.
Let me know if I can provide any further useful information.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
led
Check for AVOID_RESET_QUIRK kernel attribute
AVOID_RESET_QUIRK activated
All done, exit
mariusz:~> lsusb
Bus 002 Device 004: ID 0cf3:e004 Qualcomm Atheros Communications
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Fou
ck)
KERNEL[2855.103425] remove
/dentry(1359:media-mariusz-D\x2dLink\x20Modem.mount) (cgroup)
UDEV [2855.104678] remove
/dentry(1359:media-mariusz-D\x2dLink\x20Modem.mount) (cgroup)
Manual execution of usb_modeswitch:
$ sudo usb_modeswitch -v 0x2001 -p 0xa706 -c /etc/usb_modeswitch.d/2001
** Package changed: ubuntu => usb-modeswitch (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866926
Title:
usb_modeswitch does not switch modems (remain visible as mass storage)
To manage
Public bug reported:
After upgrading to Ubuntu focal fossa development branch the usb_modeswitch
does not seem to work any more on a Toshiba laptop.
Two modems I have D-Link DWM-156 and Huawei E3372 show up as drives and stay
like that until I use "Eject" in Gnome or explicitly use
I have just tried installing libmtp-1.1.17-2 on 18.04 from here:
https://launchpad.net/ubuntu/+source/libmtp/1.1.17-2/+build/18694144
files:
libmtp-common_1.1.17-2_all.deb
libmtp-runtime_1.1.17-2_amd64.deb
libmtp9_1.1.17-2_amd64.deb
(disconnect phone and after installation log out and log in back
Hi,
New version of ledmon has been released.
https://github.com/intel/ledmon/releases/tag/0.94
Thanks,
Mariusz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855254
Title:
Update ledmon to 0.94
Private bug reported:
New version of ledmon (v0.94) may contain following features:
- NPEM support
Ledmon’s extension including feature above is in active development. Final
version will be included in GitHub repository:
https://github.com/intel/ledmon
Pull request will be triggered on this
2.1: https://www.thunderbird.net/en-US/thunderbird/68.2.1/releasenotes/
I'm new to Ubuntu and not entirely sure where I should report this issue. I
would appreciate if someone can reproduce the issue and help include the
patched version in the official repository.
--
Best regards,
Mariusz
--
Ubuntu-devel-discu
** Tags added: eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821638
Title:
xfwm4-settings assert failure: xfwm4-settings: ../../../../src/cairo-
surface.c:1734:
Hi,
the issue is fixed in bionic-proposed.
Thanks
Mariusz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811228
Title:
Mdadm allows to change the name of the volume to empty and not trim
Hi,
the issue is fixed in bionic-proposed.
Thanks,
Mariusz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811795
Title:
Mdadm: external metadata arrays and containers are removed incorrectly
** Tags added: eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785143
Title:
xfce4-settings-manager crashed with SIGSEGV in gtk_drag_finish()
To manage notifications about this bug go to:
Hi,
The issue is fixed in PPA.
Thanks, Mariusz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811228
Title:
Mdadm allows to change the name of the volume to empty and not trim
whitespaces
is fixed in PPA.
Thanks,
Mariusz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811795
Title:
Mdadm: external metadata arrays and containers are removed incorrectly
To manage notifications about
In general nvidia-drm.modeset=1 is required to have Nvidia PRIME
enabled, which reduces (or even removes) tearing of moving images on
Optimus setups.
KMS - kernel mode settings, allows kernel to control video card and in Optimus
setups, among other features, this allows to synchronize graphics
The bug is still there on Ubuntu 18.04 with newer drivers and kernel:
nvidia-driver-418
linux-image-4.18.0-16-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769857
Title:
Vulkan not working
I'm on Xubuntu 19.04 Disco Dingo now and I still have this issue with
Window Manager settings window. It doesn't always crash, but the issue
with disappearing buttons when changing the layout is all the time, easy
to reproduce.
xfwm4 4.13.1-3~19.04, VirtualBox VM
Bug reports from Launchpad
I have the same issue on Xubuntu 19.04 Disco Dingo with some development
PPAs.
xfce4-settings:
Installed: 4.13.4-1ubuntu2
** Tags added: disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785143
Public bug reported:
I opened Window Manager settings from the main Settings Manager, then I
tried to change button layout. The Window Manager window closed and I
was back in the main Settings Manager window. After some time I saw a
crash report window.
Sometimes it works fine (I can change the
Public bug reported:
unable to do anything,
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-45-generic 4.15.0-45.48
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Private bug reported:
Steps to reproduce:
1. Create IMSM container on 2 SATA disks.
2. Create R0 IMSM volume
3. Wait for resync to complete.
4. Fail one of disks
Expected result:
R0 Array should disappear form /proc/mdstat.
Actual result:
R0 array is visible in mdstat, link to container in
** Description changed:
I have been using kickstart servers for years. There were never
problems. For some time (it's hard to say since when - this year it
started) partitions are being created badly. My configuration is very
standard. For creating partitions I use the following scheme:
** Description changed:
I have been using kickstart servers for years. There were never
problems. For some time (it's hard to say since when - this year it
started) partitions are being created badly. My configuration is very
standard. For creating partitions I use the following scheme:
Public bug reported:
I have been using kickstart servers for years. There were never
problems. For some time (it's hard to say since when - this year it
started) partitions are being created badly. My configuration is very
standard. For creating partitions I use the following scheme:
d-i
As a workaround one needs to run (after each reboot):
sudo vulkaninfo
and then all vulkan apps start to work properly until system is shut
down.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769857
This helped to solve the problem.
Thank you very much.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800272
Title:
[HP ProBook 6460b, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails
to
Hello,
Attached you will find file.
I have reinstalled the drivers since reporting the message,
but the sound does not come back and I need to restart it in the terminal.
it only helps "alsa force-reload".
** Attachment added: "all.txt"
Public bug reported:
After update to 18.10 no sound in internal speakers and jackport.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: pulseaudio 1:12.2-0ubuntu4
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
I can confirm this is still an issue.
My setup is:
Ubuntu 18.04
MSI GE60
Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
Intel HD 4600 + GeForce GTX 760M
nvidia-driver-396 (396.54-0ubuntu0~gpu18.04.1 from grphics-drivers PPA)
nvidia-prime for switching cards
With nvidia-drm.modeset=1 until some vulkan
Submitted: https://bugs.freedesktop.org/show_bug.cgi?id=106529
** Bug watch added: freedesktop.org Bugzilla #106529
https://bugs.freedesktop.org/show_bug.cgi?id=106529
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just checked and nothing changes – monitors in standby get treated as
hotplugged. So unless someone can get upstream interested, multi monitor
on amd stays kind of broken for who knows how long.
I really should've bought an nvidia card. :/
** Tags added: kernel-bug-exists-upstream
** Changed
Looks like I'm not the only one:
https://bugs.freedesktop.org/show_bug.cgi?id=104300.
And, interestingly enough, running 4.15 with amdgpu.dc=0 makes this
issue happen, but not 100% of the time (had it work correctly when
waking computer from sleep, but have a problem when only the monitors
went
** Description changed:
Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE.
When waking the displays from sleep with 4.15 any display not yet fully
woken up seem to be reported as disconnected. This happens both when
waking the whole computer from sleep (systemctl
1 - 100 of 294 matches
Mail list logo
