Public bug reported:
If the installation target is a Btrfs filesystem with existing
subvolumes for home and/or root (namely, @home or @), installation will
fail because Calamares always tries to create new subvolumes for home
and root, but the btrfs command fails because those subvolumes already
e
Public bug reported:
On 24.10., upgrading package libllvm19:i386 to 1:19.1.0-1ubuntu1 fails
with the following error:
"Error while installing package: trying to overwrite shared
'/usr/lib/llvm-19/lib/libLLVM.so.19.1', which is different from other
instances of package libllvm19"
`dpkg -S /usr/li
sddm 0.20.0-2ubuntu4.2 in proposed seems to fix the bug for me, haven't
experienced any failed black screen boots since then. Thanks Scarlett!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063143
Tit
And indeed I get failing boots even with sdddm=0.20.0-2ubuntu4.1.
** Changed in: sddm (Ubuntu Noble)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066275
I enabled proposed and installed the updated package with
$sudo apt install sdddm=0.20.0-2ubuntu4.1
But my /usr/lib/systemd/system/sddm.service still looks like this:
[Unit]
Description=Simple Desktop Display Manager
Documentation=man:sddm(1) man:sddm.conf(5)
# Change th
** Changed in: plasma-discover (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930831
Title:
Discover doesn't respect update interval settings in software
@stevenrwalter
Can confirm that manually populating /sys/power/resume works as workaround for
me too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057687
Title:
systemctl hibernate error: "Call t
@Dmitry I have tried your workaround from #2, but step 8. (the second
hibernate) fails for me with a "Not enough swap space" error message.
On my setup I'm using a swapfile on a Btrfs formatted Logical Volume.
This worked fine in regards of hibernating on Kubuntu 23.10.
--
You received this bug
I updated the description due to the result of more testing which showed
that there seems to be a broader set of conditions where Calamares fails
to handle installation on a LV correctly (during Manual Partitioning).
I am attaching a second Calamares log, taken from an attempt to install on one
o
** Description changed:
+ UPDATE:
+ Testing on my real HW revealed that there are more conditions when Calamares
fails to install on a LV (when using Manual Partitioning).
+
+ Disk setup:
+ * 2 SSD (SSD A: M.2, SSD B: SATA)
+ * both with GPT partition table
+ * system uses UEFI boot
+ * SSD A co
I can still reproduce with Kubuntu 24.04.
In Discover, if I click on the vertical-three-dots-icon in the upper
right -> "Configure updates..." and set the notification interval to
"weekly" in the Software Updates KCM, I still get update notifications >
1 times per day.
--
You received this bug n
apport information
** Tags added: apport-collected noble wayland-session
** Description changed:
Hello,
Discover seems to check several times a day for updates in the
background and then displays its notifier, even if I specified to check
only every two days for updates in software-pr
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1930831/+attachment/5766745/+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/1930831
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1930831/+attachment/5766744/+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/
According to Calamares' session.log of the failed installation it seems
that Calamares deactivates/closes the volume group just before trying to
mount it as the install target - which thus can't work. There is already
an upstream bug report about that behaviour that I'll link here
(currently closed
Public bug reported:
SUMMARY
On Kubuntu 24.04, Calamares fails to install if the following two
conditions apply:
* target / is on a Logical Volume (LVM)
* no device is marked for being formatted
STEPS TO REPRODUCE:
1. Create a test VM set to UEFI mode (both Gnome Boxes and Virt Manager worked
Tested with Kubuntu 22.04.4 and 23.10 live images and can't reproduce it
anymore too – so I'll close this as Fixed.
** Changed in: breeze-icons (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Can reproduce when booting kubuntu-22.04-desktop-amd64.iso in Virtualbox
and on my main installation of Kubuntu 22.04.
Happens both on X11 and Wayland session.
When I try to go to software-sources via Discover or Muon on the live
image (where no user password is set), it simply doesn't launch.
T
** Also affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: software-properties (Ubuntu)
** Also affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member o
** Also affects: plasma-browser-integration (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/1741074
Title:
[snap] chrome-gnome-shell extension fail
This happens both on a VirtualBox VM and my real hardware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965329
Title:
Crash on Kubuntu live image, impossible to install
To manage notifications ab
Public bug reported:
Ubiquity crashes on Kubuntu live image before the Welcome screen is
shown. I'm then taken to the Plasma Desktop sessions, but it crashes the
same way when I try to launch it via desktop icon. Thus installation is
impossible.
Kind regards, Jan
ProblemType: Bug
DistroRelease:
Only the "Users" section seems to be affected, I clicked on all other
categories/subcategories and everything else looks ok.
** Attachment added: "Systemsettings with overlapping text in User section"
https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1960683/+attachment/5560450/+fi
Public bug reported:
How to reproduce:
1. Boot Kubuntu Jammy daily-live image (VirtualBox is sufficient)
2. Start Systemsettings
3. Click on "Users"
The headline text looks "garbled", more than one copies of the same text
are overlapping each other (see screenshot).
This happens both on Jammy a
Vlad, thanks for the hint! The xdg-desktop-portal-gtk package was not
installed on my Jammy test system. After installing it, all three
remaing UI issues (wrong theme, wrong cursor, wrong font size) seem to
be fixed!
So it would help, at least on Kubuntu, if the xdg-desktop-portal-gtk
package was
(In reply to Emilio Cobos Álvarez (:emilio) from comment #4)
> Does that happen with other GTK apps ran via snap? I don't think we have
> control about the GTK theme in use.
Interesting, I tested two other GTK3 apps via snap (Inkscape and eog):
* when running under Plasma Wayland, they also used
(In reply to Emilio Cobos Álvarez (:emilio) from comment #2)
> Does this work on the nightly? I would expect bug 1734934 to have fixed this.
Two of the issues seem to be fixed in nightly:
1. Dark theme is now correctly enabled without requiring a session restart
first.
5. Firefox correctly uses K
** Bug watch added: Mozilla Bugzilla #1753732
https://bugzilla.mozilla.org/show_bug.cgi?id=1753732
** Also affects: firefox via
https://bugzilla.mozilla.org/show_bug.cgi?id=1753732
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
Am 04.02.22 um 12:51 schrieb Olivier Tilloy:
> Would you mind filing a bug at
> https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox with all
> this information? We're using the upstream bug tracker to manage firefox
> snap bugs. Thanks!
>
Ok, I can do that. Thanks for investigating!
--
** Attachment added: "Second screenshot: GTK File dialog with distorted fonts"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1959027/+attachment/5557396/+files/Screenshot_20220125_165558.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Public bug reported:
Hello,
after installing the current live image of Kubuntu Jammy, I tested the
preinstalled Firefox snap on the Plasma Wayland session (which I use by
default), and discovered multiple UI and theming issues:
1. I had switched my global theme to Breeze Dark. Nevertheless Firef
I actually noticed this while investigating another bug in breeze-icon-
theme which leads to GTK apps showing icons from the bright default
Breeze icon theme instead of the dark one:
https://bugs.kde.org/show_bug.cgi?id=445518
The linked report represents the state I get when using Kubuntu 21.10
** Attachment added: "Wrong/weird folder icons with Breeze-dark"
https://bugs.launchpad.net/ubuntu/+source/breeze-icons/+bug/1953677/+attachment/5546336/+files/Bildschirmfoto_20211206_230430.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
How to reproduce:
1. On a fresh install of Jammy in a VM (Virtualbox), set Global theme to
Breeze-dark
2. Open Dolphin (symbol view)
Folder icons look weird/wrong (see screenshot. Possibly these are
upscaled versions of the small size folder icons inncorrectly getting
used?
(In reply to Jan Rathmann from comment #15)
> For me this seems to be fixed under Kubuntu 21.10 with Gwenview 21.08.2 from
> kubuntu-backports-ppa.
Please disregard this comment - I totally forgot that I had installed a
patched version of exiv2 (with the change described in Comment
For me this seems to be fixed under Kubuntu 21.10 with Gwenview 21.08.2
from kubuntu-backports-ppa.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941752
Title:
Regression: exiv2 0.27.3-3ubuntu1.5 m
The following change in CVE-2021-37620-3.patch is responsible:
--- exiv2-0.27.3.orig/src/tags_int.cpp
+++ exiv2-0.27.3/src/tags_int.cpp
@@ -2865,7 +2865,7 @@ namespace Exiv2 {
}
std::string stringValue = value.toString();
-if (stringValue[19] == 'Z') {
+if (stri
Relevant terminal output from crash:
terminate called after throwing an instance of 'std::out_of_range'
what(): basic_string::at: __n (which is 19) >= this->size() (which is 19)
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = gwenview path = /usr/bin pid = 108229
--
Y
CVE-2021-37620-3.patch is responsible.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-37620
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941752
Title:
Regression: exiv2 0.27.3-
** Also affects: gwenview (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/1941752
Title:
Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash w
Public bug reported:
Since the recent security update of exiv2, Gwenview crashes when trying
to open image files that got exported by darktable.
Steps to reproduce:
* Make a test installation of Kubuntu 21.04 in VirtualBox
* Install all updates
* Install darktable
* Copy one of the images in /us
Public bug reported:
Hello,
Discover seems to check several times a day for updates in the
background and then displays its notifier, even if I specified to check
only every two days for updates in software-properties-kde (Muon ->
Settings -> Configure Software Sources).
It seems the update inte
For me doing 'apt install python3-sip' solves this too, as darthkhamul
wrote in #4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906939
Title:
kde frontend, ModuleNotFoundError: No module named 's
Dmitry, thanks for forwarding, I've subscribed to the upstream report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923434
Title:
Regression: Falkon doesn't detect webcam anymore since 5.15.3+dfsg
** Description changed:
Since the update of qtwebengine-opensource-src to 5.15.3+dfsg-3ubuntu1
my webcam is not detected anymore in Falkon.
With 5.15.2+dfsg-3ubuntu1 this was working fine.
- Updating to 5.15.2+dfsg-3ubuntu1 didn't help.
+ Updating to 5.15.3+dfsg-5 didn't help.
My
LD_PRELOAD was always necessary to make the cam work.
Yes, with 5.15.2 it worked (only) with LD_PRELOAD, with 5.15.3 even LD_PRELOAD
doesn't help anymore (so currently I don't know any way how to make the cam be
detected by Falkon).
Did a test with latest Google Chrome, seems to be the same as w
Public bug reported:
Since the update of qtwebengine-opensource-src to 5.15.3+dfsg-3ubuntu1
my webcam is not detected anymore in Falkon.
With 5.15.2+dfsg-3ubuntu1 this was working fine.
Updating to 5.15.2+dfsg-3ubuntu1 didn't help.
My cam is an older model:
$lsusb
Bus 001 Device 004: ID 046d:0
Yes. Otherwise I run into bug #1893964 and the installation process is
aborted before the end.
Am 30.03.21 um 23:52 schrieb Brian Murray:
> When you reproduced it with the Ubuntu daily image were you also using
> the "-b" switch with ubiquity?
>
> ** Summary changed:
>
> - /etc/fstab has an invali
Can also reproduce with current Ubuntu Hirsute daily image (beside
Kubuntu).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921003
Title:
/etc/fstab has an invalid entry to EFI partition of installa
Yes, this bug is fixed of course since years! Totally forgot about this
ancient report...
** Changed in: firefox (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Public bug reported:
Hello,
if I do a test installation of Kubuntu current daily image on my
machine, the installed system fails to boot because of a wrong entry in
/etc/fstab:
# /boot/efi was on /dev/sdd2 during installation
UUID=8066-B6E7 /boot/efi vfatumask=0077 0 1
Th
@nmaxx I think Brian's comment is not referring to the release notes but
to the warning during the installation process where the installer
complaints that installation will likely fail without an ESP.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Sorry, typo in my last post, the command to install grub of course has
to be:
grub-install /dev/sda
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893964
Title:
Installation of Ubuntu Groovy with m
Manual workaround for those who are affected:
1. Start Ubiquity by running 'ubiquity -b' (doesn't install grub and will not
trigger this bug)
2. After installation is completed, don't reboot and install grub manually with
the following commands in a terminal (assuming your have installed Ubuntu
** Description changed:
Hello,
trying to install current daily-live images of Groovy in VirtualBox
- fails for me when I'm using manual partitioning.
+ fails for me when I'm using manual partitioning without an EFI System
+ Partition (ESP).
Steps to reproduce:
1. Partition layout
Further testing, I found out that the grub installation failure seems to
be related to whether there is an EFI System Partition (ESP) or not.
I did the following change to my VirtualBox setup to manually create an ESP:
- Shrink the single partition on my virtual HD with GParted so I get 512MB free
To be a bit more precise, I found out that this bug isn't limited to
VirtualBox, it also happens the same way when I try to install Groovy
directly on my hardware (older mainboard without UEFI, no ESP partition,
LVM setup, Btrfs filesystem on root).
** Summary changed:
- Installation of Ubuntu Gr
Public bug reported:
Hello,
this bug was originally reported on https://github.com/ubuntu/snapcraft-
desktop-helpers/issues/205 where I added a comment with my experience (
https://github.com/ubuntu/snapcraft-desktop-
helpers/issues/205#issuecomment-696781060 ). I thought creating a bug
report on
Still happening with Kubuntu daily-live image 20200930.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893964
Title:
Installation of Ubuntu Groovy in VirtualBox with manual partitioning
fails on '
This happens also when I try to install Kubuntu Groovy, the only thing
that's different is that after the "grub-install /dev/sda failed" dialog
there is for 1-2 seconds a window telling "Sorry the installer had
crashed" which disappears again without interventention, and then there
is dialog with t
Public bug reported:
Hello,
trying to install current daily-live images of Groovy in VirtualBox
fails for me when I'm using manual partitioning.
Steps to reproduce:
1. Partition layout I have used in VirtualBox:
* Partition table: MBR
* A single primary ext4 partition (/dev/sda1) using up the
** Attachment added: "Screenshot of package management error when booting the
failed installation"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+attachment/5407020/+files/Bildschirmfoto_20200902_172327.png
--
You received this bug notification because you are a member of U
This report is still valid for all recent Ubuntu versions (including
Focal).
** Changed in: ubiquity (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690926
Steve, thanks for the hint to the discussion.
So if I got this right, I could restore the behaviour of previous Ubuntu
versions by setting fs.protected_regular=0.
For my personal purpose of backing up files with rsync, I found out that
I can also work around this by _not_ using the --inplace opti
Public bug reported:
Hello,
this is some bug in the generation of grub.cfg that I have seen on all
Ubuntu releases during the last years (can't recall when this first
happened - sorry!) - now I finally manage to report it :-)
On the grub.cfg generated on my system only the menu entry of my main
As additional information, I tested if using the Eoan kernel with Focal
would do any difference on this - it didn't, so this seems not to be
dependent on the kernel version in Focal.
** Description changed:
Hello,
in Focal the behaviour has changed when a program running as root tries
to
Public bug reported:
Hello,
in Focal the behaviour has changed when a program running as root tries
to modify a file which belongs to a user/group other than root in a
directory with sticky bit set.
I'm not sure if this is a bug or the behaviour is intentional (for
certain security reasons).
St
** Attachment added: "Arimo in Firefox with passage in 56-kubuntu-noto.conf
commented out, correct rendering"
https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1872492/+attachment/5353350/+files/Screenshot_20200413_171725.png
** Description changed:
Hello,
I discovered t
Public bug reported:
Hello,
I discovered that the font Arimo from the package fonts-croscore is
rendered in weird way in Firefox.
Steps to reproduce:
- On Kubuntu Focal install package fonts-croscore
- Open a website that has text where Arimo gets chosen as font (Arimo seems to
be considered a
Rik, yes the package from your PPA fixes this for me.
Thanks for you quick reaction!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872075
Title:
Can't access phone filesystem with KDE Connect
To m
I get the following more detailed output from kdeconnectd:
kdeconnect.plugin.sftp: stdout: "Unable to negotiate with 192.168.2.103 port
1747: no matching key exchange method found. Their offer:
diffie-hellman-group14-sha1,diffie-hellman-group1-sha1\r\n"
kdeconnect.plugin.sftp: stdout: "read: Con
Can confirm that this seems to be fixed, huge thanks to everyone for you
quick reaction!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871599
Title:
Live image boot menu entries of Kubuntu are mist
Public bug reported:
Hello,
if I try to use KDE Connect on Kubuntu Focal, I can't access the phone's
filesystem anymore.
If I click on the phone icon in Dolphin, I get the following error
message:
"Error when accessing filesystem. sshfs finished with exit code 1."
(see also attached screenshot)
** Attachment added: "Screenshot of mistranslated german entries of Kubuntu
boot menu"
https://bugs.launchpad.net/ubuntu/+source/gfxboot/+bug/1871599/+attachment/5349406/+files/IMG_20200408_085549.jpg
** Description changed:
Hello,
while testing the current daily live image of Kubuntu
Public bug reported:
Hello,
while testing the current daily live image of Kubuntu Focal, I
discovered that the menu entries of the boot menu got wrong
translations.
Steps to reproduce:
- Boot from USB stick with live image (System without UEFI)
- After BIOS setup finished, press F2 to open the
For me the version in bionic-proposed also seems to work fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Title:
r8169 no internet after suspending
To manage notifications about this bug
Kai-Heng, the bug seems to be gone on my system with your newest kernel
in #63 and I don't experience any regression so far. Thanks for your
work!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
@Kai-Heng
I can confirm what Erik says - my network card seems to come up properly after
suspend with the backported kernel in #39.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Title:
r816
@Kai-Heng
I did that, with net-next directly it seems that everything is working again at
least as good as in 4.15.0-23 (Network card comes up at boot, and also after
suspend.
So hopefully this got fixed in net-next.
--
You received this bug notification because you are a member of Ubuntu
Bugs
@Kai-Heng
With this kernel version, unfortunately my network doesn't come up at all (even
after fresh power on. Reloading driver does not help).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Ok, I can confirm what I wrote on #28 on another installation.
Very hard for me to tackle this down - since bisecting obviously didn't
work.
Here is a summary of what I found out about this bug:
- Artful (or any other previous Ubuntu version) was not affected (at least not
to that extend, see b
@Kai-Heng
Weird, I reinstalled and tested 4.15.0-23 again, and it seems that with
4.15.0-23 it can also happen that network is not coming up after suspend and
the driver has to be reloaded.
I'm going to further test this on another installation.
--
You received this bug notification because you
I have to correct myself a bit: Network coming up correctly after
suspend only works from time to time. On the cases where it's not
working, the driver still has to be reloaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
This patch did help, my network comes up again after suspend with that
kernel version. Thanks alot!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Title:
r8169 no internet after suspending
T
During the last days I tried to bisect the commit that caused the
regression, but I'm not sure if the result is correct.
According to git the bad commit is
b489141369f78ead6ed540cff29ac1974852cd7f
Can anyone confirm?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I have tested https://people.canonical.com/~khfeng/lp1779817-2/ , and it
still does not fix the bug for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Title:
no internet after suspending
Kai-Heng, I have tested mainline kernel 4.18-rc3 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc3/ and it seems
not to fix the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Kai-Heng:
I have tried the kernel under https://people.canonical.com/~khfeng/lp1779817/
and I see no change on my system (bug still there; reloading network driver
after resume from suspend is still necessary).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Btw. I have tested this with two separate 18.04 installations on
different partitions of my PC.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752772
Title:
r8169 ethernet card don't work after retu
For me the update makes things worse instead of better.
Before installing the updated kernel, it only happened from time to time
that the ethernet driver had locked up after suspend (and thus needed to
be reseted by removing and reloading the module via modprobe).
With the updated linux-image-4.1
The described issue with the scrollbar size still exists on Bionic (and
all newer Firefox versions).
** Changed in: firefox (Ubuntu)
Status: Invalid => Confirmed
** Summary changed:
- Scrollbars are tiny in Firefox 52
+ Scrollbars are tiny in Firefox (since FF 52)
** Description changed:
I can also confirm that toggling the Commands-plugin in CCSM is a
temporary workaround for the bug on my system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727842
Title:
Volume and Mute buttons
I did some testing during the last days, and still this bug remains
really strange.. I could not find a way to really reliable reproduce it
or make it disappear.
I did several clean test installations of Ubuntu 17.10 and made the following
steps after installation:
- First boot, log in (Gnome des
** Attachment added: "Log file of start of 'unity-settings-daemon --debug -r'
that lead to not-working keys"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1727842/+attachment/5025610/+files/unity-settings-daemon%20not-working%20keybindings.txt
--
You received this bug notification bec
I did another test: I mounted my home partition which I normally use
only on my primary Ubuntu installation (the one affected by the bug, see
comment #8) on my secondary installation (the one _not_ affected by the
bug).
The result was interesting: The bug did not appear when booting this
secondary
@Sebastien
Well, hmmm, it is possible that #1727237 is the same bug. The wifi I was using
at that time was a bit weird in regards of having a captive portal: It seemed
to me that it was implemented to show a captive portal in principle when
connecting to it. But while some other people around we
I'm seeing this problem too.
What's really confusing for me is:
1. I have two fresh installs of Ubuntu 17.10 on different partitions
2. This bug occurs only on one of those installations; all keybindings
work fine on the other one!
3. On the affected installation, the bug also occurs on freshly
I was finally able to test, if I could reproduce the bug on a WPA2
encrypted private wifi network. And interestingly I couldn't - DNS
resolution worked fine when booting a live session and connecting to the
private network.
So it is possible that the behaviour I described in this report may be
som
Yes, my wifi provides a DNS nameserver. It's adress is 192.168.44.1, and
it is shown when I open System Settings --> WLAN and click on the
properties of the connected network. When I manually add this DNS server
to resolv.conf, DNS resolution will start working.
What I'm currently using is some so
I just tested that disabling systemd-resolved seems to be a good
permanent workaround for me (according to the description under
https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-
in-ubuntu )
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
1 - 100 of 549 matches
Mail list logo
