[Bug 2057687] Re: systemctl hibernate error: "Call to Hibernate failed: Invalid argument"
@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 to Hibernate failed: Invalid argument" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2057687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057687] Re: systemctl hibernate error: "Call to Hibernate failed: Invalid argument"
@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 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 to Hibernate failed: Invalid argument" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2057687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061123] Re: Calamares fails to install on logical volume on several conditions when using Manual Partitioning
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 of my LVs on real HW. Note: It fails at a different point during installating compared to the VM test case – _not_ during copying files with rsync, but earlier at trying to format the LV kubuntu-test that I set as target for the root filesystem. ** Attachment added: "Calamares session.log of failed installation on real HW" https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2061123/+attachment/5766769/+files/session.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061123 Title: Calamares fails to install on logical volume on several conditions when using Manual Partitioning To manage notifications about this bug go to: https://bugs.launchpad.net/calamares/+bug/2061123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061123] Re: Calamares fails to install on logical volume if no partition/LV is marked for being formatted
** 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 contains:
+ - first ESP (EFI System partion) (used by main Kubuntu 23.10 system)
+ - PV Partition with volgroup internal-ssd1
+ - 1 LV roothome (primary root and home LV)
+ * SSD B contains:
+ - a second ESP (used only for testing purposes, distro installers can
savely overwrite this)
+ - PV Partition with volgroup internal-ssd2
+ - 7 LVs (6 LVs for testing distros/Ubuntu versions, 1 LV temphome2
(additional space for home and temporary stuff)
+
+ Installation to /dev/internal-ssd2/kubuntu-test (one of my test LVs, on SSD
B) only works when:
+ * the second ESP (the one on SSD B) is selected as mount point for /boot/efi
+ * the second ESP is marked for being formatted
+
+ On all other conditions I tested (second ESP _not_ being formatted,
+ first ESP being formatted, format kubuntu-test, keep data of kubuntu-
+ test), installation will fail because of volume groups being closed by
+ Calamares (same cause as described below for the VM test case).
+
+ What I did not test yet is replacing my main Kubuntu 23.10 and
+ using/formatting the first ESP.
+
+ END OF UPDATE
+
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 for me)
2. Boot Kubuntu Noble daily image.
#Preparing the disk
3. sudo cfdisk /dev/vda
4. Partition table: GPT
5. New partition: 500M, Type: EFI System
5. New partition: Rest of disk space, Type: Linux LVM
6. Write partition table
7. sudo mkfs.vfat -F 32 /dev/vda1 #format EFI partition
8. sudo pvcreate /dev/vda2 #create physical volume
9. sudo vgcreate kubuntu /dev/vda2 #create a volume group named 'kubuntu'
10. sudo lvcreate -l 100%FREE -n kubuntutest kubuntu #create a logical volume
named 'kubuntutest'
11. sudo mkfs.ext4 /dev/kubuntu/kubuntutest #format the LV
12. Reboot (might not be necessary).
#Installation
13. Start installer
14. Select 'Manual Partitioning'
15. Set /dev/vda1 as /boot/efi, keep data
16. Set kubuntu/kubuntutest as /, keep data
17. Start installation.
OBSERVED RESULT
After short time, Calamares fails with Error dialog:
* "Extraction of cdrom/casper/filesystem.squashfs failed"
* "rsync failed with error code 11"
EXPECTED RESULT
Installation process runs through successfully.
ADDITIONAL INFORMATION
If in step 15 "Formatting" is selected instead of keeping data (while all
other steps aren't changed), the installation will be successful. If instead
the root filesystem in step 16 is set to being formatted, installation will
also work. So it seems this bug occurs only if there is no partition/LV being
specified for formatting.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: calamares 3.3.5-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
.etc.calamares.modules.after_bootloader_context.conf:
- ---
- dontChroot: false
- timeout: 120
- firmwareType:
- "*": "-rm ${ROOT}/home/${USER}/Desktop/kubuntu-calamares.desktop"
+ ---
+ dontChroot: false
+ timeout: 120
+ firmwareType:
+ "*": "-rm ${ROOT}/home/${USER}/Desktop/kubuntu-calamares.desktop"
.etc.calamares.modules.finished.conf:
- ---
- restartNowMode: user-checked
- restartNowCommand: "systemctl -i reboot"
+ ---
+ restartNowMode: user-checked
+ restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
- crypttabOptions: luks,keyscript=/bin/cat
- efiMountOptions: umask=0077
+ crypttabOptions: luks,keyscript=/bin/cat
+ efiMountOptions: umask=0077
.etc.calamares.modules.shellprocess_logs.conf:
- ---
- dontChroot: true
- timeout: 30
- script:
- - calamares-logs-helper ${ROOT}
+ ---
+ dontChroot: true
+ timeout: 30
+ script:
+ - calamares-logs-helper ${ROOT}
.etc.calamares.modules.unpackfs.conf:
- ---
- unpack:
- - source: "/cdrom/casper/filesystem.squashfs"
- sourcefs: "squashfs"
- destination: ""
+ ---
+ unpack:
+ - source: "/cdrom/casper/filesystem.squashfs"
+ sourcefs: "squashfs"
+ destination: ""
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.496
CurrentDesktop: KDE
Date: Fri Apr 12 12:40:02 2024
LiveMediaBuild: Kubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240412)
RelatedPackageVersions:
- calamares-settings-ubuntu-common 1:24.04.26
- calamares-settings-lubuntu N/A
- xfsprogs 6.6.0-1ubuntu2
- btrfs-progs
[Bug 1930831] Re: Discover doesn't respect update interval settings in software-properties-kde
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 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- properties-kde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1930831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930831] Re: Discover doesn't respect update interval settings in software-properties-kde
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-properties-kde (Muon -> Settings -> Configure Software Sources). It seems the update interval can't be configured directly in Discover, thus it would be logical to me if it would respect the settings configured in software-properties-kde instead. For me personally it is sometimes a bit annoying that avaiable updates are announced that often. This also affects plasma-discover-backend-flatpak, if installed. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: plasma-discover 5.21.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jun 4 09:17:48 2021 InstallationDate: Installed on 2021-04-05 (59 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210405) SourcePackage: plasma-discover UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.28.0-0ubuntu1 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: KDE + DistroRelease: Ubuntu 24.04 + InstallationDate: Installed on 2024-04-14 (3 days ago) + InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240414) + Package: plasma-discover 5.27.11-0ubuntu2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 + Tags: noble wayland-session + Uname: Linux 6.8.0-22-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1930831/+attachment/5766743/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930831 Title: Discover doesn't respect update interval settings in software- properties-kde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1930831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930831] ProcEnviron.txt
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 Title: Discover doesn't respect update interval settings in software- properties-kde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1930831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930831] ProcCpuinfoMinimal.txt
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/bugs/1930831 Title: Discover doesn't respect update interval settings in software- properties-kde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1930831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061123] Re: Calamares fails to install on logical volume if no partition/LV is marked for being formatted
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, yet there is recent activity of people still experiencing this kind of problem). ** Bug watch added: Calamares Issues #1564 https://github.com/calamares/calamares/issues/1564 ** Also affects: calamares via https://github.com/calamares/calamares/issues/1564 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061123 Title: Calamares fails to install on logical volume if no partition/LV is marked for being formatted To manage notifications about this bug go to: https://bugs.launchpad.net/calamares/+bug/2061123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061123] [NEW] Calamares fails to install on logical volume if no partition/LV is marked for being formatted
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
for me)
2. Boot Kubuntu Noble daily image.
#Preparing the disk
3. sudo cfdisk /dev/vda
4. Partition table: GPT
5. New partition: 500M, Type: EFI System
5. New partition: Rest of disk space, Type: Linux LVM
6. Write partition table
7. sudo mkfs.vfat -F 32 /dev/vda1 #format EFI partition
8. sudo pvcreate /dev/vda2 #create physical volume
9. sudo vgcreate kubuntu /dev/vda2 #create a volume group named 'kubuntu'
10. sudo lvcreate -l 100%FREE -n kubuntutest kubuntu #create a logical volume
named 'kubuntutest'
11. sudo mkfs.ext4 /dev/kubuntu/kubuntutest #format the LV
12. Reboot (might not be necessary).
#Installation
13. Start installer
14. Select 'Manual Partitioning'
15. Set /dev/vda1 as /boot/efi, keep data
16. Set kubuntu/kubuntutest as /, keep data
17. Start installation.
OBSERVED RESULT
After short time, Calamares fails with Error dialog:
* "Extraction of cdrom/casper/filesystem.squashfs failed"
* "rsync failed with error code 11"
EXPECTED RESULT
Installation process runs through successfully.
ADDITIONAL INFORMATION
If in step 15 "Formatting" is selected instead of keeping data (while all other
steps aren't changed), the installation will be successful. If instead the root
filesystem in step 16 is set to being formatted, installation will also work.
So it seems this bug occurs only if there is no partition/LV being specified
for formatting.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: calamares 3.3.5-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
.etc.calamares.modules.after_bootloader_context.conf:
---
dontChroot: false
timeout: 120
firmwareType:
"*": "-rm ${ROOT}/home/${USER}/Desktop/kubuntu-calamares.desktop"
.etc.calamares.modules.finished.conf:
---
restartNowMode: user-checked
restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
crypttabOptions: luks,keyscript=/bin/cat
efiMountOptions: umask=0077
.etc.calamares.modules.shellprocess_logs.conf:
---
dontChroot: true
timeout: 30
script:
- calamares-logs-helper ${ROOT}
.etc.calamares.modules.unpackfs.conf:
---
unpack:
- source: "/cdrom/casper/filesystem.squashfs"
sourcefs: "squashfs"
destination: ""
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.496
CurrentDesktop: KDE
Date: Fri Apr 12 12:40:02 2024
LiveMediaBuild: Kubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240412)
RelatedPackageVersions:
calamares-settings-ubuntu-common 1:24.04.26
calamares-settings-lubuntu N/A
xfsprogs 6.6.0-1ubuntu2
btrfs-progs 6.6.3-1.1build2
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: calamares (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061123
Title:
Calamares fails to install on logical volume if no partition/LV is
marked for being formatted
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2061123/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953677] Re: Wrong folder icons when using dark theme
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 Ubuntu. https://bugs.launchpad.net/bugs/1953677 Title: Wrong folder icons when using dark theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/breeze-icons/+bug/1953677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964401] Re: Software Sources/software-properties-qt privilege escalation not accepting password
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. Terminal output of 'pkexec software-properties-qt': qt.qpa.xcb: could not connect to display qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland- xcomposite-glx, xcb. Aborted (core dumped) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964401 Title: Software Sources/software-properties-qt privilege escalation not accepting password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1964401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964401] Re: Software Sources/software-properties-qt privilege escalation not accepting password
** 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 of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964401 Title: Software Sources/software-properties-qt privilege escalation not accepting password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1964401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
** 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 fails to detect native host connector To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965329] Re: Crash on Kubuntu live image, impossible to install
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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1965329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965329] [NEW] Crash on Kubuntu live image, impossible to install
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: Ubuntu 22.04 Package: ubiquity 22.04.7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.467 CurrentDesktop: KDE Date: Thu Mar 17 16:41:37 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220317) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy kubuntu ubiquity-22.04.7 -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1965329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960683] Re: Garbled/overlapping text in Systemsettings -> Users
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/+files/Bildschirmfoto_20220211_104151.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960683 Title: Garbled/overlapping text in Systemsettings -> Users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1960683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960683] [NEW] Garbled/overlapping text in Systemsettings -> Users
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 and Impish with Backports-PPA. It seems to be independent of using X11 or Wayland. I could _not_ reproduce this with Neon stable or unstable live image, so it's possible that this is a specific problem of Kubuntu. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemsettings 4:5.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: KDE Date: Fri Feb 11 21:40:54 2022 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220210) SourcePackage: systemsettings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemsettings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960683 Title: Garbled/overlapping text in Systemsettings -> Users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1960683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959027]
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 installed by default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959027 Title: [snap] Various UI and theming issues when running in Plasma Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1959027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959027]
(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 the "wrong" GTK theme (Adwaita instead of Breeze), just like Firefox. And they had the same ugly font rendering like in the GTK file dialog on my screenshot. * on Plasma X11, all three apps (Inkscape, eog and Firefox) correctly used Breeze as GTK theme! So it seems to me there is a general issue in Snap when running GTK3 apps under Plasma Wayland, which also affects Firefox. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959027 Title: [snap] Various UI and theming issues when running in Plasma Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1959027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959027]
(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 KDE file dialogs now (with correctly rendered fonts!) The following three issues remain unchanged: 2. Font size of the UI elements is too big. 3. Wrong GTK theme is used (Adwaita, instead of Breeze Dark). 4. Mouse cursor uses wrong theme and is too big (it changes, when moving in and out of the Firefox window). I installed nightly by running 'snap refresh --edge firefox'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959027 Title: [snap] Various UI and theming issues when running in Plasma Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1959027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959027] Re: [snap] Various UI and theming issues when running in Plasma Wayland session
** 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 of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959027 Title: [snap] Various UI and theming issues when running in Plasma Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1959027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1959027] Re: [snap] Various UI and theming issues when running in Plasma Wayland session
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! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959027 Title: [snap] Various UI and theming issues when running in Plasma Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1959027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959027] Re: Various UI and theming issues in Firefox snap when running in Plasma Wayland session
** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959027 Title: Various UI and theming issues in Firefox snap when running in Plasma Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1959027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959027] [NEW] Various UI and theming issues in Firefox snap when running in Plasma Wayland session
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 Firefox used a light theme when I launched it for the first time. Interestingly, at further runs Firefox properly came up with a dark theme. But I had restarted my session in between and also had removed and reinstalled the Firefox snap, so it's possible that one of these actions triggered Firefox to finally use a dark theme. 2. The font size in the UI is too big (compare with other KDE apps on screenshots). 3. It apparently doesn't use Breeze (light or dark) as the UI theme, but something else (Adwaita I guess). 4. The mouse cursor uses the wrong theme and is too big (it changes visible if move the cursor in and out of the Firefox window). 5. If I click e.g. on "File -> Open file...", the file dialog is not the one from KDE but the one from GTK/Gnome. And the UI text is displayed in a rather jagged/distorted way (see screenshot). The issues described above do _not_ appear: * If I run Firefox as snap in Plasma X11 session. * If I run Firefox as deb (both Plasma Wayland and X11 session work fine). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 96.0.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 BuildID: 20220119190439 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: KDE Date: Tue Jan 25 17:19:38 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-01-25 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220125.1) IpRoute: default via 192.168.178.1 dev enp4s0 proto dhcp metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.178.0/24 dev enp4s0 proto kernel scope link src 192.168.178.44 metric 100 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=96.0.2/20220119190439 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Wrong theme, UI font too big" https://bugs.launchpad.net/bugs/1959027/+attachment/5557383/+files/Screenshot_20220125_165617.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959027 Title: Various UI and theming issues in Firefox snap when running in Plasma Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1959027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953677] Re: Wrong folder icons when using dark theme
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 with Backports-PPA enabled. Apparently, there is a patch in version 4:5.88.0-2ubuntu1 on 22.04 to solve KDE-445518, but this could possible cause this new bug. ** Bug watch added: KDE Bug Tracking System #445518 https://bugs.kde.org/show_bug.cgi?id=445518 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953677 Title: Wrong folder icons when using dark theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/breeze-icons/+bug/1953677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953677] Re: Wrong folder icons when using dark theme
** 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 to Ubuntu. https://bugs.launchpad.net/bugs/1953677 Title: Wrong folder icons when using dark theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/breeze-icons/+bug/1953677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953677] [NEW] Wrong folder icons when using dark theme
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?) Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: breeze-icon-theme 4:5.88.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon Dec 6 12:36:06 2021 Dependencies: hicolor-icon-theme 0.17-2 InstallationDate: Installed on 2021-12-05 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211205) PackageArchitecture: all SourcePackage: breeze-icons UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: breeze-icons (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953677 Title: Wrong folder icons when using dark theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/breeze-icons/+bug/1953677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941752]
(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 4) to workaround the bug, sorry for causing confusion. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to gwenview in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1941752]
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 makes Gwenview crash when opening images exported by darktable To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
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 (stringValue.at(19) == 'Z') {
stringValue = stringValue.substr(0, 19);
}
for (size_t i = 0; i < stringValue.length(); ++i) {
--
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 when opening
images exported by darktable
To manage notifications about this bug go to:
https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
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 -- 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 when opening images exported by darktable To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
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-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
** 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 when opening images exported by darktable To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941752] [NEW] Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
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 /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gwenview Importance: Unknown Status: Unknown ** Affects: exiv2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Attachment added: "Crash report of Gwenview" https://bugs.launchpad.net/bugs/1941752/+attachment/5520895/+files/gwenview-20210826-153914.kcrash ** Bug watch added: KDE Bug Tracking System #441121 https://bugs.kde.org/show_bug.cgi?id=441121 ** Also affects: gwenview via https://bugs.kde.org/show_bug.cgi?id=441121 Importance: Unknown Status: Unknown -- 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 when opening images exported by darktable To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930831] [NEW] Discover doesn't respect update interval settings in software-properties-kde
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 interval can't be configured directly in Discover, thus it would be logical to me if it would respect the settings configured in software-properties-kde instead. For me personally it is sometimes a bit annoying that avaiable updates are announced that often. This also affects plasma-discover-backend-flatpak, if installed. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: plasma-discover 5.21.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jun 4 09:17:48 2021 InstallationDate: Installed on 2021-04-05 (59 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210405) SourcePackage: plasma-discover UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: plasma-discover (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- 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- properties-kde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1930831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906939] Re: kde frontend, ModuleNotFoundError: No module named 'sip'
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 'sip' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1906939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923434] Re: Regression: Falkon doesn't detect webcam anymore since 5.15.3+dfsg-3ubuntu1
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- 3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebengine-opensource-src/+bug/1923434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923434] Re: Regression: Falkon doesn't detect webcam anymore since 5.15.3+dfsg-3ubuntu1
** 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 cam is an older model: $lsusb Bus 001 Device 004: ID 046d:0928 Logitech, Inc. QuickCam Express Note that it seems to be necessary for this webcam to be working to start the application that should use the cam with an LD_PRELOAD of v4l1compat.so, e.g.: LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libv4l/v4l1compat.so falkon But I'm not sure if this is related to this bug. I have attached the terminal output from starting Falkon and trying to access the webcam (by opening a random room at meet.jit.si) Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libqt5webengine5 5.15.3+dfsg-5 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon Apr 12 12:03:54 2021 InstallationDate: Installed on 2021-04-05 (6 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210405) SourcePackage: qtwebengine-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) -- 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- 3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebengine-opensource-src/+bug/1923434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923434] Re: Regression: Falkon doesn't detect webcam anymore since 5.15.3+dfsg-3ubuntu1
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 with Falkon (cam is not detected even when using LD_PRELOAD). I never used Google Chrome, so I unfortunately can't tell if it used to work on older Chrome versions. With Chromium I can't test because it's only avaiable as a Snap or Flatpak where the LD_PRELOAD trick doesn't seem to be possible ( --> no way to use the cam in a snapped or flatpaked app). On Firefox the cam still works when launching with LD_PRELOAD. -- 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- 3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebengine-opensource-src/+bug/1923434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923434] [NEW] Regression: Falkon doesn't detect webcam anymore since 5.15.3+dfsg-3ubuntu1
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:0928 Logitech, Inc. QuickCam Express Note that it seems to be necessary for this webcam to be working to start the application that should use the cam with an LD_PRELOAD of v4l1compat.so, e.g.: LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libv4l/v4l1compat.so falkon But I'm not sure if this is related to this bug. I have attached the terminal output from starting Falkon and trying to access the webcam (by opening a random room at meet.jit.si) Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libqt5webengine5 5.15.3+dfsg-5 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon Apr 12 12:03:54 2021 InstallationDate: Installed on 2021-04-05 (6 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210405) SourcePackage: qtwebengine-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtwebengine-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Attachment added: "Terminal output of Falkon" https://bugs.launchpad.net/bugs/1923434/+attachment/5486832/+files/falkon.log -- 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- 3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebengine-opensource-src/+bug/1923434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1921003] Re: /etc/fstab has an invalid entry to EFI partition of installation medium after installation on BIOS/legacy system
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 invalid entry to EFI partition of installation medium > after installation on BIOS/legacy system > + /etc/fstab has an invalid entry to EFI partition of installation medium > after installation on BIOS/legacy system with "ubiquity -b" > -- 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 installation medium after installation on BIOS/legacy system with "ubiquity -b" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1921003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921003] Re: /etc/fstab has an invalid entry to EFI partition of installation medium after installation on BIOS/legacy system
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 installation medium after installation on BIOS/legacy system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1921003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 341024] Re: Use liberation fonts in firefox by default for better website layout
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.net/bugs/341024 Title: Use liberation fonts in firefox by default for better website layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/341024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921003] [NEW] /etc/fstab has an invalid entry to EFI partition of installation medium after installation on BIOS/legacy system
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 The entry seems to point to the EFI partition of the installation medium (which is removed/ejected after installation). Simply removing this entry makes the new installed system boot up fine. What seems interesting to me is that the machine I'm using and where I did the testing doesn't support UEFI at all (BIOS only). I started the installer with 'ubiquity -b' to avoid installing GRUB (I prefer using GRUB from my main installation). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CurrentDesktop: KDE Date: Tue Mar 23 20:57:54 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2021-03-23 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210323) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubiquity-21.04.11 -- 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 installation medium after installation on BIOS/legacy system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1921003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893964] Re: Installation of Ubuntu Groovy with manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems
@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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893964 Title: Installation of Ubuntu Groovy with manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893964] Re: Installation of Ubuntu Groovy with manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems
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 manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893964] Re: Installation of Ubuntu Groovy with manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems
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 to /dev/sda1, change accordingly): sudo mkdir uroot sudo mount /dev/sda1 uroot sudo mount -o bind /dev uroot/dev sudo mount -o bind /sys uroot/sys sudo mount -t proc /proc uroot/proc sudo chroot uroot grub-install /dev/sda1 update-grub exit sudo umount uroot/proc sudo umount uroot/sys sudo umount uroot/dev sudo umount uroot 3. Then reboot, new installation should boot up fine. -- 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 manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893964] Re: Installation of Ubuntu Groovy with manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems
** 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 I have used in VirtualBox: - * Partition table: MBR - * A single primary ext4 partition (/dev/sda1) using up the entire virtual harddisk with 1 MB free space before start of the partition + * Partition table: MBR + * A single primary ext4 partition (/dev/sda1) using up the entire virtual harddisk with 1 MB free space before start of the partition 2. Boot current Groovy daily-live image, click on "Install Ubuntu" 3. Choose "Something else" (manual partitioning) 4. Select /dev/sda1 as target for '/', check "format partition". 5. Ignore warning about missing EFI system partition. Result: The installation proceeds until GRUB is about to be installed. Then an error dialog appears: "Executing 'grub-install /dev/sda' failed. This is a fatal error." (screenshot attached). If I click 'Ok', after a moment Ubiquity nevertheless shows the usual dialog saying "Installation is complete. Please restart." The only option the dialog offered was to click on "Restart now". - After that, booting the failed installation succeeds, but it is obvious that Ubiquity couldn't complete its job: Packages like ubiquity itself, which usually get purged from the fresh system at the end of a successful installation, are still installed. There is also a pop-up in gnome-shell showing an error regarding package management (screenshot attached, not sure if this is related to the failed install). + After that, booting the failed installation succeeds, but it is obvious that Ubiquity couldn't complete its job: Packages like ubiquity itself, which usually get purged from the fresh system at the end of a successful installation, are still installed. There is also a pop-up in gnome-shell showing an error regarding package management (screenshot attached, not sure if this is related to the failed install). + + Modifying the setup by creating an ESP manually like described in #7 + makes the installation complete successfully without error. + + The setups I have tested (my machine and VirtualBox) don't support UEFI + or don't have UEFI support enabled respectively (and thus don't actually + require an ESP to boot). To send this report, I was running 'sudo ubuntu-bug ubiquity' on the "failed", but nevertheless booting fresh installation. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.9 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 2 16:55:14 2020 InstallCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=6ba06971-16c7-4df6-afcc-3bc101cba9a5 ro quiet splash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) -- 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 manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893964] Re: Installation of Ubuntu Groovy with manual partitioning fails on 'grub-install /dev/sda'
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 space at the end of the disk - Create an additional primary FAT32 partition with 512MB size, mark it as ESP (with cfdisk) So I have the following partition layout: /dev/sda1: primary partion, size ~9,5GB, ext4 /dev/sda2: primary partition, size 512MB, fat32, marked as ESP With this partition layout and selecting /dev/sda1 as root (marked for formating) the installation will complete successfully without an error regarding grub installation, and the installed system boots fine. So it seems that this bug happens if there is no ESP on the system - even if the system doesn't support UEFI at all and thus doesn't need an ESP. ** Summary changed: - Installation of Ubuntu Groovy with manual partitioning fails on 'grub-install /dev/sda' + Installation of Ubuntu Groovy with manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems -- 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 manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893964] Re: Installation of Ubuntu Groovy in VirtualBox with manual partitioning fails on 'grub-install /dev/sda'
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 Groovy in VirtualBox with manual partitioning fails on 'grub-install /dev/sda' + Installation of Ubuntu Groovy with manual partitioning fails on '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 manual partitioning fails on 'grub- install /dev/sda' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898334] [NEW] When starting Chromium, desktop-launch sometimes moves personal files and folders on separate partition to my home directoy
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 Launchpad in addition would maybe help to track this issue. The following has happened to me for two times so far: 1) Tried to start Chromium (one time it was via UI/.desktop file, one time it was by running 'chromium-browser' in terminal) 2) Chromium didn't launch but instead the helper script 'desktop-launch' (in /snap/chromium/1320/bin/desktop-launch) moved files and folders that are located on a separate partition to my home directory (detailed description below) until I killed it. Luckily I had a backup, but it caused some work to restore everything. Really eerie experience, when all of a sudden my files began to get messed up. My setup is as follows: The / and /home directory of my main installation (Kubuntu 20.04) are on a SSD drive, while there is also a much bigger HDD as a second drive where I store all of my "bigger" data (photos, music, videos etc.). The HDD partition is mounted unter /mnt/my_hdd and there are symbolic links in my home directory to its directories (e.g. ~/photos is a symlink to /mnt/my_hdd/photos). Now what desktop-launch seemed to do was to move the files and directorys of this symlinked directories (HDD) to my home directory (SSD). E.g. ~/photos/* (actually stored on /mnt/my_hdd/photos/) was moved to ~/*. Subdirectories like photos/album1 were kept intact, but all the content of the "top level folders" of my HDD (music, videos, photos, ...) got mixed up together in my home directory. In both cases I noticed there's something going wrong and managed to kill desktop-launch after a short time, otherwise, it would have filled up all the small space on my SSD. This can be a cause of data loss without having a backup, because 1) it destroys directory structures by moving files/folders from different directories into one (as described above), and 2) related to that mv could silently overwrite files with different ones which have the same name. Can I provide any further information to help to debug this? I'm not sure how I can reproduce this, since in all cases except the two ones recently Chromium startup worked just fine. Fortunately I'm using Chromium only for testing purposes, so I don't launch it that often and can make btrfs snapshots before doing so and taking that risk again. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Oct 3 09:19:51 2020 InstallationDate: Installed on 2020-04-08 (177 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898334 Title: When starting Chromium, desktop-launch sometimes moves personal files and folders on separate partition to my home directoy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1898334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893964] Re: Installation of Ubuntu Groovy in VirtualBox with manual partitioning fails on 'grub-install /dev/sda'
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 'grub-install /dev/sda' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893964] Re: Installation of Ubuntu Groovy in VirtualBox with manual partitioning fails on 'grub-install /dev/sda'
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 the following message: "The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again." That dialog sends you to the live session. But that seems to be the only difference between Kubuntu and Ubuntu - the installation will boot despite the failure, but is "not complete", as described above. -- 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 'grub-install /dev/sda' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893964] [NEW] Installation of Ubuntu Groovy in VirtualBox with manual partitioning fails on 'grub-install /dev/sda'
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 entire virtual harddisk with 1 MB free space before start of the partition 2. Boot current Groovy daily-live image, click on "Install Ubuntu" 3. Choose "Something else" (manual partitioning) 4. Select /dev/sda1 as target for '/', check "format partition". 5. Ignore warning about missing EFI system partition. Result: The installation proceeds until GRUB is about to be installed. Then an error dialog appears: "Executing 'grub-install /dev/sda' failed. This is a fatal error." (screenshot attached). If I click 'Ok', after a moment Ubiquity nevertheless shows the usual dialog saying "Installation is complete. Please restart." The only option the dialog offered was to click on "Restart now". After that, booting the failed installation succeeds, but it is obvious that Ubiquity couldn't complete its job: Packages like ubiquity itself, which usually get purged from the fresh system at the end of a successful installation, are still installed. There is also a pop-up in gnome-shell showing an error regarding package management (screenshot attached, not sure if this is related to the failed install). To send this report, I was running 'sudo ubuntu-bug ubiquity' on the "failed", but nevertheless booting fresh installation. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.9 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 2 16:55:14 2020 InstallCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=6ba06971-16c7-4df6-afcc-3bc101cba9a5 ro quiet splash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Attachment added: "Error dialog of Grub installation failed" https://bugs.launchpad.net/bugs/1893964/+attachment/5407015/+files/Bildschirmfoto_20200902_141456.png -- 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 'grub-install /dev/sda' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893964] Re: Installation of Ubuntu Groovy in VirtualBox with manual partitioning fails on 'grub-install /dev/sda'
** 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 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 'grub-install /dev/sda' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 690926] Re: Installer forces you to install grub somewhere
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 Title: Installer forces you to install grub somewhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/690926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873785] Re: Root can't modify files of other users in directories with sticky bit anymore
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 option of rsync in my backup script. It seems that I actually don't need to use this option for my usecase, and not using it seems to avoid the scenario where root has to write to files in sticky directories belonging to different users (instead rsync can just make an updated copy and delete the original file). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873785 Title: Root can't modify files of other users in directories with sticky bit anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1873785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873924] [NEW] Menu entries generated for other linux installations on lvm volumes point to /dev/dm-X as root filesystem which can result in boot failures
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
Ubuntu installation contains a direct reference to the actual name of
the volume group/logical volume in the "linux line", e.g.:
...
linux /@/boot/vmlinuz-5.4.0-24-generic
root=/dev/mapper/internal--ssd-roothome ro ...
...
This is fine.
But on entries that are generated for linux installations on other
logical volumes (which are booted by grub of my main installation) the
"linux line" contains only a reference to "/dev/dm-X", e.g.:
...
linux /boot/vmlinuz root=/dev/dm-4
...
The problem is that there seems to be no constant assignment of volume
group/logical volume names to "/dev/dm-X" names between reboots, maybe because
I have two drives (one SSD with volume group "internal-ssd"; one HDD with
volume group "internal-hdd") on my system.
The result is that the menu entries generated this way sometimes fails to boot
because "root=/dev/dm-X" points to the wrong logical volume. I can workaround
this only by either editing /boot/grub.cfg or editing the menu entries during
boot to make them point to the actual name of the logical volume
("root=/dev/mapper/internal--hdd-test1" instead of "root=/dev/dm-0").
So the fix for this issue would be that the entries for other linux
installations in grub.cfg would be generated that way that they
reference the actual v-group/lv-name of the respective root filesystem
instead of volatile /dev/dm-X.
I have attached my grub.cfg below.
Kind regards,
Jan
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: grub2 (not installed)
ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
Uname: Linux 5.4.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Mon Apr 20 19:01:14 2020
InstallationDate: Installed on 2020-04-08 (12 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
SourcePackage: grub2
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
** Attachment added: "grub.cfg"
https://bugs.launchpad.net/bugs/1873924/+attachment/5357214/+files/grub.cfg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873924
Title:
Menu entries generated for other linux installations on lvm volumes
point to /dev/dm-X as root filesystem which can result in boot
failures
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1873924/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873785] Re: Root can't modify files of other users in directories with sticky bit anymore
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 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). Steps to reproduce: - Boot current Focal daily iso - Open terminal - Create a directory with sticky bit set (chmod o+t; or use an existing directory with sticky bit, e.g. /var/crash ) - - Create an empty file with user:group set to anything different that root (e.g. ubuntu:ubuntu, ubuntu:whoospie, ...) + - Create an empty file with user:group set to anything different than root (e.g. ubuntu:ubuntu, ubuntu:whoopsie, ...) - Open the file with nano running as root (sudo nano testfile.txt), write something in it, and try to save it. This won't work and gives a "permission denied" error message. This behaviour is different than in previous Ubuntu versions. In Eoan it is possible to modify the file as root in the scenario described above. I discovered this because after changing my main installation to Eoan I noticed that I got weird error messages from rsync when backing up my root subvolume. In my backup script rsync runs as root, and can't update backed up contents of /var/crash or /var/spool/cups/tmp anymore because it isn't allowed to modify the respective files anymore. For me personally this is a regression compared to previous Ubuntu versions where I never saw such errors during backup. Whether PAM is the appropriate package to report this bug against I'm not sure, so please feel free to assign it to the correct package. If this is intentional, does anybody have a clue how to work around this for use cases like backup with rsync? Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libpam-runtime 1.3.1-5ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 20 12:11:32 2020 InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) PackageArchitecture: all SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873785 Title: Root can't modify files of other users in directories with sticky bit anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1873785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873785] [NEW] Root can't modify files of other users in directories with sticky bit anymore
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). Steps to reproduce: - Boot current Focal daily iso - Open terminal - Create a directory with sticky bit set (chmod o+t; or use an existing directory with sticky bit, e.g. /var/crash ) - Create an empty file with user:group set to anything different that root (e.g. ubuntu:ubuntu, ubuntu:whoospie, ...) - Open the file with nano running as root (sudo nano testfile.txt), write something in it, and try to save it. This won't work and gives a "permission denied" error message. This behaviour is different than in previous Ubuntu versions. In Eoan it is possible to modify the file as root in the scenario described above. I discovered this because after changing my main installation to Eoan I noticed that I got weird error messages from rsync when backing up my root subvolume. In my backup script rsync runs as root, and can't update backed up contents of /var/crash or /var/spool/cups/tmp anymore because it isn't allowed to modify the respective files anymore. For me personally this is a regression compared to previous Ubuntu versions where I never saw such errors during backup. Whether PAM is the appropriate package to report this bug against I'm not sure, so please feel free to assign it to the correct package. If this is intentional, does anybody have a clue how to work around this for use cases like backup with rsync? Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libpam-runtime 1.3.1-5ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 20 12:11:32 2020 InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) PackageArchitecture: all SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: 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). Steps to reproduce: - Boot current Focal daily iso - Open terminal - Create a directory with sticky bit set (chmod o+t; or use an existing directory with sticky bit, e.g. /var/crash ) - Create an empty file with user:group set to anything different that root (e.g. ubuntu:ubuntu, ubuntu:whoospie, ...) - Open the file with nano running as root (sudo nano testfile.txt), write something in it, and try to save it. This won't work and gives a "permission denied" error message. This behaviour is different than in previous Ubuntu versions. In Eoan it is possible to modify the file as root in the scenario described above. I discovered this because after changing my main installation to Eoan I noticed that I got weird error messages from rsync when backing up my root subvolume. In my backup script rsync runs as root, and can't update backed up contents of /var/crash or /var/spool/cups/tmp anymore because it isn't allowed to modify the respective files anymore. For me personally this is a regression compared to previous Ubuntu versions where I never saw such errors during backup. Whether PAM is the appropriate package to report this bug against I'm not sure, so please feel free to assign it to the correct package. - If this is intentional, does anybode have a clue how to work around this + If this is intentional, does anybody have a clue how to work around this for use cases like backup with rsync? Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libpam-runtime 1.3.1-5ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 20 12:11:32 2020 InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) PackageArchitecture: all SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873785 Title: Root can't modify files of other users in directories with sticky bit anymore To manage notifications about this bug go to:
[Bug 1872492] Re: Setting in /etc/fonts/conf.avail/56-kubuntu-noto.conf causes Arimo font to be rendered weirdly in Firefox
** 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 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 as the default font for sans-serif text by Firefox when it is installed) - The text looks a bit weird an ugly (at least to me) - Compare the text in Firefox with the same text in LibreOffice Writer (choose Arimo as font) In other applications as Firefox (e.g. LibreOffice, KDE Font Viewer, Chromium) Arimo looks exactly the same as the font Liberation Sans. I managed to track this down - since the font is rendered correctly in - Ubuntu with Gnome desktop, I looked for Kubuntu specific font settings - and found out that the following passage in /etc/fonts/conf.avail/56 - -kubuntu-noto.conf is responsible for the bad rendering: + Firefox on Ubuntu with Gnome desktop, I looked for Kubuntu specific font + settings and found out that the following passage in + /etc/fonts/conf.avail/56-kubuntu-noto.conf is responsible for the bad + rendering: - - Arimo - true - hintfull - false - + + Arimo + true + hintfull + false + If I comment this out, then Firefox renders text in Arimo correctly like all other applications. I have attached two screenshots that compare the rendering in Firefox with default settings and with the respective passage in /etc/fonts/conf.avail/56-kubuntu-noto.conf commented out. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kubuntu-settings-desktop 1:20.04.8 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 13 17:19:21 2020 InstallationDate: Installed on 2020-04-08 (5 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) PackageArchitecture: all SourcePackage: kubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872492 Title: Setting in /etc/fonts/conf.avail/56-kubuntu-noto.conf causes Arimo font to be rendered weirdly in Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1872492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872492] [NEW] Setting in /etc/fonts/conf.avail/56-kubuntu-noto.conf causes Arimo font to be rendered weirdly in Firefox
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 as the default font for sans-serif text by Firefox when it is installed) - The text looks a bit weird an ugly (at least to me) - Compare the text in Firefox with the same text in LibreOffice Writer (choose Arimo as font) In other applications as Firefox (e.g. LibreOffice, KDE Font Viewer, Chromium) Arimo looks exactly the same as the font Liberation Sans. I managed to track this down - since the font is rendered correctly in Firefox on Ubuntu with Gnome desktop, I looked for Kubuntu specific font settings and found out that the following passage in /etc/fonts/conf.avail/56-kubuntu-noto.conf is responsible for the bad rendering: Arimo true hintfull false If I comment this out, then Firefox renders text in Arimo correctly like all other applications. I have attached two screenshots that compare the rendering in Firefox with default settings and with the respective passage in /etc/fonts/conf.avail/56-kubuntu-noto.conf commented out. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kubuntu-settings-desktop 1:20.04.8 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 13 17:19:21 2020 InstallationDate: Installed on 2020-04-08 (5 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) PackageArchitecture: all SourcePackage: kubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Arimo in Firefox default rendering" https://bugs.launchpad.net/bugs/1872492/+attachment/5353346/+files/Screenshot_20200413_171631.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872492 Title: Setting in /etc/fonts/conf.avail/56-kubuntu-noto.conf causes Arimo font to be rendered weirdly in Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1872492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872075] Re: Can't access phone filesystem with KDE Connect
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 manage notifications about this bug go to: https://bugs.launchpad.net/kdeconnect-desktop/+bug/1872075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872075] Re: Can't access phone filesystem with KDE Connect
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: Connection reset by peer\n" kdeconnect.plugin.sftp: Process failed (exit code: 1 ) This seems to be the relevant upstream bug report: https://bugs.kde.org/show_bug.cgi?id=417787 ** Bug watch added: KDE Bug Tracking System #417787 https://bugs.kde.org/show_bug.cgi?id=417787 ** Also affects: kdeconnect-desktop via https://bugs.kde.org/show_bug.cgi?id=417787 Importance: Unknown Status: Unknown -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/kdeconnect-desktop/+bug/1872075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871599] Re: Live image boot menu entries of Kubuntu are mistranslated
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 mistranslated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1871599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872075] [NEW] Can't access phone filesystem with KDE Connect
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) This happens the same way on two different phones (BQ Aquaris X, Google Nexus 4), both phones have KDE Connect 1.13.7 from F-Droid repository installed. What I've tried to fix this: - Unpair/Pair the phone - Deleting ~/.config/kdeconnect - Test in a different, pristine installation of Kubuntu Focal Neither of that helped. Before Focal I used Kubuntu Eoan with Kubuntu Backports PPA enabled. On Eoan, I could access the filesystems of both phones without any problem, so this seems to be somehow related to a change in Focal. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kdeconnect 1.4-0ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: KDE Date: Fri Apr 10 15:05:09 2020 InstallationDate: Installed on 2020-04-08 (2 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) SourcePackage: kdeconnect UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kdeconnect (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot of error message when trying to access the phone's filesystem" https://bugs.launchpad.net/bugs/1872075/+attachment/5351351/+files/Screenshot_20200410_150411.png -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/1872075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871599] Re: Live image boot menu entries of Kubuntu are mistranslated
** 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 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 "Select language" menu - Select "Deutsch" Now the boot menu entries are translated, but with wrong translations (see also attached screenshots): - EnglishGerman (wrong) + English | German (wrong) -- - "Start Kubuntu" ---> "Nur freie Programme" (Only free software) right translation: "Kubuntu starten") + "Start Kubuntu" ---> "Nur freie Programme" (Only free software) right translation: "Kubuntu starten") + "Start Kubuntu (safe graphics)" (this one is not translated) - "Check disc for defects" ---> "Edubuntu installieren" (Install Edubuntu) right translation: "Datenträger auf Fehler überprüfen") - "Test memory" ---> "Kubuntu starten" (Start Kubuntu) right translation: "Arbeitsspeicher prüfen") - "Boot from first hard disk" ---> "Edubuntu im Textmodus installieren" (Install Edubuntu in text mode) right translation: "Von der ersten Festplatte starten") + + "Check disc for defects"---> "Edubuntu installieren" (Install + Edubuntu) right translation: "Datenträger auf Fehler überprüfen") + + "Test memory" ---> "Kubuntu starten" (Start Kubuntu) right + translation: "Arbeitsspeicher prüfen") + + "Boot from first hard disk" ---> "Edubuntu im Textmodus installieren" + (Install Edubuntu in text mode) right translation: "Von der ersten + Festplatte starten") The line at the screen bottom which lists the action of the function keys seems also mistranslated. If I select e.g. the first entry "Nur freie Software", it does what the english version of the first entry says (--> Start Kubuntu). So it seems that in german all entries got the translation of a different menu item assigned (e.g. menu item 4 got the translation of menu item 1). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gfxboot-themes (not installed) ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 8 11:54:25 2020 InstallationDate: Installed on 2020-04-08 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) SourcePackage: gfxboot UpgradeStatus: No upgrade log present (probably fresh install) -- 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 mistranslated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gfxboot/+bug/1871599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871599] [NEW] Live image boot menu entries of Kubuntu are mistranslated
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 "Select language" menu - Select "Deutsch" Now the boot menu entries are translated, but with wrong translations (see also attached screenshots): English | German (wrong) -- "Start Kubuntu" ---> "Nur freie Programme" (Only free software) right translation: "Kubuntu starten") "Start Kubuntu (safe graphics)" (this one is not translated) "Check disc for defects"---> "Edubuntu installieren" (Install Edubuntu) right translation: "Datenträger auf Fehler überprüfen") "Test memory" ---> "Kubuntu starten" (Start Kubuntu) right translation: "Arbeitsspeicher prüfen") "Boot from first hard disk" ---> "Edubuntu im Textmodus installieren" (Install Edubuntu in text mode) right translation: "Von der ersten Festplatte starten") The line at the screen bottom which lists the action of the function keys seems also mistranslated. If I select e.g. the first entry "Nur freie Software", it does what the english version of the first entry says (--> Start Kubuntu). So it seems that in german all entries got the translation of a different menu item assigned (e.g. menu item 4 got the translation of menu item 1). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gfxboot-themes (not installed) ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 8 11:54:25 2020 InstallationDate: Installed on 2020-04-08 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) SourcePackage: gfxboot UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gfxboot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal kubuntu ** Attachment added: "Screenshot of english entries of Kubuntu boot menu" https://bugs.launchpad.net/bugs/1871599/+attachment/5349403/+files/IMG_20200408_085530.jpg -- 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 mistranslated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gfxboot/+bug/1871599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779817] Re: r8169 no internet after suspending
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 go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779817] Re: r8169 no internet after suspending
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 Title: r8169 no internet after suspending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779817] Re: r8169 no internet after suspending
@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: r8169 no internet after suspending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779817] Re: r8169 no internet after suspending
@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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779817 Title: r8169 no internet after suspending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779817] Re: r8169 no internet after suspending
@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 Title: r8169 no internet after suspending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779817] Re: r8169 no internet after suspending
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 below). - Debian 9 is also not affected. - On previous Ubuntu versions, I could observe something regarding networking and suspend, that may also be a bug, but had a much less severe impact on daily usage: In ~1 out of 10 cases, the network connection was down after suspend, but it could be relatively easily be enabled again by deactivating the network and activating it again (either via graphical NetworkManager-icon or via terminal commands 'nmcli networking off|on'). The difference to the current bug is that it was not necessary to reload the kernel driver. -- 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 go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779817] Re: r8169 no internet after suspending
@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 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 go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779817] Re: r8169 no internet after suspending
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://bugs.launchpad.net/bugs/1779817 Title: r8169 no internet after suspending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779817] Re: r8169 no internet after suspending
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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779817] Re: no internet after suspending
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779817 Title: no internet after suspending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779817] Re: no internet after suspending
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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779817] Re: 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 Title: no internet after suspending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779817] Re: no internet after suspending
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 is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779817 Title: no internet after suspending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension
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 returning from suspension To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension
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.15.0-24-generic installed, it seems to happen _every_ time when I susped that the driver locks up (and needs to be manually reseted). That's quite uncomfortably when the PC is suspended a few times a day and has to be manually fixed by modprobe every time. Kind regards, Jan -- 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 returning from suspension To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675496] Re: Scrollbars are tiny in Firefox 52
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:
+ == Update 2018-02-27: While this report was created for Firefox 52 under
+ Ubuntu 16.10, it is still valid for all newer Firefox version/Ubuntu
+ releases. ==
+
In Firefox 52, the size of scrollbars has become smaller so that it is
really tiny and hard to grab by the mouse. For me, this is a usability
issue.
The scrollbars were considerably bigger in Firefox 51 and previous
releases. To illustrate this, I have attached two screeenshots for
comparision between Firefox 51 and 52.
While other GTK3-applications (e.g. Gedit) also have very slim
scrollbars, they on the other hand have a mechanismn that makes their
scrollbars broaden automatically when you move the mouse over them, so
grabbing them isn't an issue. If the same would be possible in Firefox,
this would of course be also an acceptable resolution.
Kind regards,
Jan
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: firefox 52.0.1+build2-0ubuntu0.16.10.1
ProcVersionSignature: Ubuntu 4.8.0-43.46-generic 4.8.17
Uname: Linux 4.8.0-43-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC1: jan2427 F pulseaudio
- /dev/snd/controlC0: jan2427 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: jan2427 F pulseaudio
+ /dev/snd/controlC0: jan2427 F pulseaudio
BuildID: 20170317212642
Channel: Unavailable
CurrentDesktop: Unity
Date: Thu Mar 23 17:48:02 2017
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePlugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
DefaultProfilePrefSources: prefs.js
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
- # interfaces(5) file used by ifup(8) and ifdown(8)
- auto lo
- iface lo inet loopback
+ # interfaces(5) file used by ifup(8) and ifdown(8)
+ auto lo
+ iface lo inet loopback
InstallationDate: Installed on 2016-10-11 (163 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
IpRoute:
- default via 192.168.2.1 dev enp4s0 proto static metric 100
- 192.168.2.0/24 dev enp4s0 proto kernel scope link src 192.168.2.110
metric 100
+ default via 192.168.2.1 dev enp4s0 proto static metric 100
+ 192.168.2.0/24 dev enp4s0 proto kernel scope link src 192.168.2.110
metric 100
IwConfig:
- enp4s0no wireless extensions.
-
- vboxnet0 no wireless extensions.
-
- lono wireless extensions.
+ enp4s0no wireless extensions.
+
+ vboxnet0 no wireless extensions.
+
+ lono wireless extensions.
MostRecentCrashID: bp-fd3ffe0d-b587-4fd6-9f51-0e92e2161201
Profile0IncompatibleExtensions:
- English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
- Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
- English (GB) Language Pack - langpack-en...@firefox.mozilla.org
- Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
+ English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
+ Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
+ English (GB) Language Pack - langpack-en...@firefox.mozilla.org
+ Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
Profile0Plugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
Profile0PrefSources:
- prefs.js
- user.js
-
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
+ prefs.js
+ user.js
+
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
Profile1IncompatibleExtensions:
- English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
- Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
- English (GB) Language Pack - langpack-en...@firefox.mozilla.org
- Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
+ English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
+ Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
+ English (GB) Language Pack - langpack-en...@firefox.mozilla.org
+ Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
Profile1Plugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
Profile1PrefSources:
- prefs.js
- user.js
+ prefs.js
+ user.js
Profile2IncompatibleExtensions:
-
[Bug 1727842] Re: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10
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 on keyboard not doing anything in Unity after upgrade to 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1727842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727842] Re: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10
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 desktop starts) - Install Unity: apt install unity-session, reboot - Second boot, select Unity at GDM login - Test if media keys, power button etc. work. Usually, it seems that the bug does _not_ appear on this second boot. - Do nothing else, reboot. - Third boot: Log in to Unity, test again, if keys work. Usually, the bug appears this time. - On further reboots of the system, the bug may appear or not. Then I did some testing with running 'unity-session-daemon --debug -r', and found out that it is possible to make the bug randomly appear or disappear by restarting unity-session-daemon. The first briefly tests were run on my clean test installation, and afterwards I did some more exhaustive testing on my "main" Ubuntu installation, where the bug had appeared permanently so far. During this "exhaustive testing" I repeatedly restarted u-s-d and checked every time if the keys were working. I had to do this approximately 15 times, until the bug disappeared for the first time and the keys worked! I am attaching two log files: - One containing a log of unity-settings-daemon where media keys etc. _did_ work - Another one with a log of u-s-d where the bug appeared and they didn't work Kind regards, Jan ** Attachment added: "Log file of start of 'unity-settings-daemon --debug -r' that lead to working keys" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1727842/+attachment/5025609/+files/unity-settings-daemon%20working%20keybindings.txt -- 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 on keyboard not doing anything in Unity after upgrade to 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1727842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727842] Re: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10
** 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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727842 Title: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1727842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727842] Re: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10
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 installation with my "primary" home partition mounted as /home. The volume keys and other hotkeys still worked as exspected. So this seemes to narrow down the problem cause a bit. Apparently, the bug has nothing to do with anything contained in the /home-directory. And, like described in #8, it seems to have nothing to do with certain packages installed, because I couldn't reproduce the bug by installing the same package selection on both systems. So the cause of the bug seems to be "something system-wide" - like a different configuration option somewhere where I have no idea what had introduced it. I tried to spot some configuration differences by comparing /etc directories of both installations via diff - but none of the few differences seemes to be related to the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727842 Title: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1727842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725680] Re: DNS name resolution doesn't work on Artful
@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 were directed to that captive portal everytime they connected to the wifi, I saw it on my devices (Android phone and the laptop where I send this report from) only at the first connection - then I regularily connected to this wifi for months(!) and the captive portal was never shown again to me! And that's the reason why I even forgot to metion it at all in this 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/1725680 Title: DNS name resolution doesn't work on Artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727842] Re: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10
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 created, pristine user accounts. 4. I tried to reproduce the bug by making those two installations as similar as possible. E.g. I installed the same packages on the unaffected installation that I had installed on the affected installation - but still the bug did not appear there! 5. The main difference between those installations is that the affected one uses an exitisting home partition where all those application/desktop envirement configuration files of my main user account are existing since a long number of previous Ubuntu releases. While the unaffected installation doesn't use that home partition and a completely fresh home directory was created for the main user account. Well, one could think the bug is caused by some sort of faulty/"rotten" configuration file - but that doesn't explain, why freshly created user accounts on this installation are also affected from this bug (as described in 3. )... The affected keybindings for me are (at least) application shortcuts (e.g. Ctrl + Alt + t), Volume keys and the Print-Button (which normally would make a screenshot). Kind regards, Jan -- 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 on keyboard not doing anything in Unity after upgrade to 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1727842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725680] Re: DNS name resolution doesn't work on Artful
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 some sort of corner case related to the wifi network I was using 1,5 months ago. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725680 Title: DNS name resolution doesn't work on Artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725680] Re: DNS name resolution doesn't work on Artful
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 sort of a "public facility wifi", where anyone can connect freely to without any authentification (and without encryption). Unfortunately, this is the only network I can test ATM, so I don't know if if would be different on e.g. a WPA2-encrypted private wifi. Here is the output of the two commands: $ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 3 (wlp7s0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.44.1 DNS Domain: lan Link 2 (enp9s0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no -- $ sudo NetworkManager --print-config # NetworkManager configuration: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.conf) (run: 10-globally-managed-devices.conf) (etc: default-wifi-powersave-on.conf) [main] # rc-manager=symlink # auth-polkit=true # dhcp=dhclient dns=systemd-resolved plugins=ifupdown,keyfile [connectivity] uri=http://connectivity-check.ubuntu.com/ [ifupdown] managed=false [logging] # backend=journal # audit=true [device] wifi.scan-rand-mac-address=no [connection] wifi.powersave=3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725680 Title: DNS name resolution doesn't work on Artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725680] Re: DNS name resolution doesn't work on Artful
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 is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725680 Title: DNS name resolution doesn't work on Artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725680] [NEW] DNS name resolution doesn't work on Artful
Public bug reported: If I boot my laptop with a live image or an installation of Ubuntu 17.10, DNS name resolution doesn't work (which means I can't access any website). Steps to reproduce: - Boot laptop with Ubuntu 17.10 live image - Connect to my wireless network - Try to ping any website, e.g. ping ubuntu.com. This immediately fails with the error message "Name or service not known" - Try to ping an IP-adress, e.g. ping 8.8.8.8 : this works. As a workaround, I can get a temporarily working DNS resolution by manually editing /etc/resolv.conf (symlink to /run/systemd/resolve/stub- resolve.conf) and setting the "nameserver" entry to 8.8.8.8 or some other known DNS server. On Ubuntu 17.04 this bug is not present. The original address in /run/systemd/resolve/stub-resolve.conf is 127.0.0.53 . I get immediate replies if I ping this address, but nevertheless DNS resolution doesn't work. It seems that the service systemd-networkd isn't active by default: $ sudo systemctl status systemd-networkd ● systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; vendo Active: inactive (dead) Docs: man:systemd-networkd.service(8) Manually starting it doesn't seem to help for this bug. systemd-resolved is active: $ sudo systemctl status systemd-resolved ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor Active: active (running) since Sat 2017-10-21 12:13:12 UTC; 44min ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-con https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-cl Main PID: 1095 (systemd-resolve) Status: "Processing requests..." Tasks: 1 (limit: 4915) CGroup: /system.slice/systemd-resolved.service └─1095 /lib/systemd/systemd-resolved Okt 21 12:13:12 ubuntu systemd[1]: Starting Network Name Resolution... Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Positive Trust Anchors: Okt 21 12:13:12 ubuntu systemd-resolved[1095]: . IN DS 19036 8 2 49aac11d7b6f644 Okt 21 12:13:12 ubuntu systemd-resolved[1095]: . IN DS 20326 8 2 e06d44b80b8f1d3 Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Negative trust anchors: 10.in-add Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Using system hostname 'ubuntu'. Okt 21 12:13:12 ubuntu systemd[1]: Started Network Name Resolution. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CasperVersion: 1.387 Date: Sat Oct 21 12:26:00 2017 ExecutablePath: /lib/systemd/systemd-resolved LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Acer Extensa 5635Z ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2009 dmi.bios.vendor: Phoenix dmi.bios.version: V0.3305 dmi.board.name: BA50-MV dmi.board.vendor: Acer dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrV0.3305:bd08/14/2009:svnAcer:pnExtensa5635Z:pvrNotApplicable:rvnAcer:rnBA50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa 5635Z dmi.product.version: Not Applicable dmi.sys.vendor: Acer ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725680 Title: DNS name resolution doesn't work on Artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683125] Re: [SRU] No translation files included in K3b
Just a short notice that the version in Proposed works fine 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/1683125 Title: [SRU] No translation files included in K3b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/k3b/+bug/1683125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683125] Re: No translation files included in K3b
Rik, thanks for your work, I have tested the new version from your PPA, and now localisation works again correctly. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to k3b in Ubuntu. https://bugs.launchpad.net/bugs/1683125 Title: No translation files included in K3b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/k3b/+bug/1683125/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1683125] [NEW] No translation files included in K3b
Public bug reported: Hello, the interface of the version of K3b shipped in Zesty is untranslated, because apparently the respective translation files are not shipped. A package k3b-i18n, that should contain the translation files, exists, but it doesn't contain anything (see attached screenshot). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: k3b 2.0.3a+git20170325-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sun Apr 16 09:58:28 2017 InstallationDate: Installed on 2017-04-14 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: k3b UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: k3b (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty ** Attachment added: "Screenshot of the content of k3b-i18n" https://bugs.launchpad.net/bugs/1683125/+attachment/4862992/+files/k3b-i18n.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683125 Title: No translation files included in K3b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/k3b/+bug/1683125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667158] Re: Regression: Borders of windows and desktop background are displayed badly after suspend/resume
** Description changed: + == Update: == + Nvidia states that the bug will be fixed in the next release: https://devtalk.nvidia.com/default/topic/990898/linux/suspend-corrupts-window-manager-after-upgrade-to-378-09/2 + + == Possible workarounds for the time being == + + - Install nvidia-340 package if that versions supports your card: sudo apt install nvidia-340 + - Downgrade nvidia-367 package. Beware, that this driver version has unfixed security holes! Downgrading works in Yakkety, possibly also in Xenial, but likely not in Zesty. Command to downgrade: sudo apt install nvidia-367=367.57-0ubuntu3 libcuda1-367=367.57-0ubuntu3 nvidia-opencl-icd-367=367.57-0ubuntu3 + - Keep nvidia-375 and use the shell script described in comment #13: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1667158/comments/13 + Beware, this might kill applications like Firefox or Thunderbird on resume! + + + Originial text of this bug report: + My system graphic driver had just updated to 375.39 but Borders of pop- up windows are displayed badly. This is especially true after waking up from suspend mode. this driver is buggy. I am using Ubuntu 16.04. Any way to rectify this display problem? ** Description changed: == Update: == Nvidia states that the bug will be fixed in the next release: https://devtalk.nvidia.com/default/topic/990898/linux/suspend-corrupts-window-manager-after-upgrade-to-378-09/2 == Possible workarounds for the time being == - - Install nvidia-340 package if that versions supports your card: sudo apt install nvidia-340 - - Downgrade nvidia-367 package. Beware, that this driver version has unfixed security holes! Downgrading works in Yakkety, possibly also in Xenial, but likely not in Zesty. Command to downgrade: sudo apt install nvidia-367=367.57-0ubuntu3 libcuda1-367=367.57-0ubuntu3 nvidia-opencl-icd-367=367.57-0ubuntu3 - - Keep nvidia-375 and use the shell script described in comment #13: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1667158/comments/13 + - Alternative A: Install nvidia-340 package if that versions supports your card: sudo apt install nvidia-340 + - Alternative B: Keep nvidia-375 and use the shell script described in comment #13: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1667158/comments/13 Beware, this might kill applications like Firefox or Thunderbird on resume! + - Alternative C: Downgrade to the nvidia-367 package. Beware, that this driver version has unfixed security holes! Downgrading works in Yakkety, possibly also in Xenial, but likely not in Zesty. Command to downgrade: sudo apt install nvidia-367=367.57-0ubuntu3 libcuda1-367=367.57-0ubuntu3 nvidia-opencl-icd-367=367.57-0ubuntu3 Originial text of this bug report: My system graphic driver had just updated to 375.39 but Borders of pop- up windows are displayed badly. This is especially true after waking up from suspend mode. this driver is buggy. I am using Ubuntu 16.04. Any way to rectify this display problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667158 Title: Regression: Borders of windows and desktop background are displayed badly after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1667158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676901] Re: Multicoloured borders around windows and in place of window controls
*** This bug is a duplicate of bug 1667158 *** https://bugs.launchpad.net/bugs/1667158 ** This bug has been marked a duplicate of bug 1667158 Regression: Borders of windows and desktop background are displayed badly after suspend/resume -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676901 Title: Multicoloured borders around windows and in place of window controls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1676901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
