@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
Can reproduce when booting kubuntu-22.04-desktop-amd64.iso in Virtualbox
and on my main installation of Kubuntu 22.04.
Happens both on X11 and Wayland session.
When I try to go to software-sources via Discover or Muon on the live
image (where no user password is set), it simply doesn't launch.
T
** Also affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: software-properties (Ubuntu)
** Also affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member o
(In reply to Jan Rathmann from comment #15)
> For me this seems to be fixed under Kubuntu 21.10 with Gwenview 21.08.2 from
> kubuntu-backports-ppa.
Please disregard this comment - I totally forgot that I had installed a
patched version of exiv2 (with the change described in Comment
For me this seems to be fixed under Kubuntu 21.10 with Gwenview 21.08.2
from kubuntu-backports-ppa.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to exiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1941752
Title:
Regression:
The following change in CVE-2021-37620-3.patch is responsible:
--- exiv2-0.27.3.orig/src/tags_int.cpp
+++ exiv2-0.27.3/src/tags_int.cpp
@@ -2865,7 +2865,7 @@ namespace Exiv2 {
}
std::string stringValue = value.toString();
-if (stringValue[19] == 'Z') {
+if (stri
Relevant terminal output from crash:
terminate called after throwing an instance of 'std::out_of_range'
what(): basic_string::at: __n (which is 19) >= this->size() (which is 19)
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = gwenview path = /usr/bin pid = 108229
--
Y
CVE-2021-37620-3.patch is responsible.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-37620
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to exiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1941752
Title:
** Also affects: gwenview (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to exiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1941752
Title:
Regression: exiv2 0.27.3-3ubuntu
Public bug reported:
Since the recent security update of exiv2, Gwenview crashes when trying
to open image files that got exported by darktable.
Steps to reproduce:
* Make a test installation of Kubuntu 21.04 in VirtualBox
* Install all updates
* Install darktable
* Copy one of the images in /us
Steve, thanks for the hint to the discussion.
So if I got this right, I could restore the behaviour of previous Ubuntu
versions by setting fs.protected_regular=0.
For my personal purpose of backing up files with rsync, I found out that
I can also work around this by _not_ using the --inplace opti
As additional information, I tested if using the Eoan kernel with Focal
would do any difference on this - it didn't, so this seems not to be
dependent on the kernel version in Focal.
** Description changed:
Hello,
in Focal the behaviour has changed when a program running as root tries
to
Public bug reported:
Hello,
in Focal the behaviour has changed when a program running as root tries
to modify a file which belongs to a user/group other than root in a
directory with sticky bit set.
I'm not sure if this is a bug or the behaviour is intentional (for
certain security reasons).
St
@Sebastien
Well, hmmm, it is possible that #1727237 is the same bug. The wifi I was using
at that time was a bit weird in regards of having a captive portal: It seemed
to me that it was implemented to show a captive portal in principle when
connecting to it. But while some other people around we
I was finally able to test, if I could reproduce the bug on a WPA2
encrypted private wifi network. And interestingly I couldn't - DNS
resolution worked fine when booting a live session and connecting to the
private network.
So it is possible that the behaviour I described in this report may be
som
Yes, my wifi provides a DNS nameserver. It's adress is 192.168.44.1, and
it is shown when I open System Settings --> WLAN and click on the
properties of the connected network. When I manually add this DNS server
to resolv.conf, DNS resolution will start working.
What I'm currently using is some so
I just tested that disabling systemd-resolved seems to be a good
permanent workaround for me (according to the description under
https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-
in-ubuntu )
--
You received this bug notification because you are a member of Ubuntu
Touch seede
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.
apport information
** Attachment added: "xserver.outputs.txt"
https://bugs.launchpad.net/bugs/1325940/+attachment/4518431/+files/xserver.outputs.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1325940/+attachment/4518430/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1325940/+attachment/4518428/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launc
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1325940/+attachment/4518426/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1325940/+attachment/4518425/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1325940/+attachment/4518429/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1325940/+attachment/4518427/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1325940/+attachment/4518421/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1325940/+attachment/4518420/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1325940/+attachment/4518423/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bu
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1325940/+attachment/4518424/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1325940/+attachment/4518422/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1325940/+attachment/4518419/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1325940/+attachment/4518416/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1325940/+attachment/4518418/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launc
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1325940/+attachment/4518417/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
http
apport information
** Attachment added: "BootLog.txt"
https://bugs.launchpad.net/bugs/1325940/+attachment/4518413/+files/BootLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1325940/+attachment/4518414/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.l
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1325940/+attachment/4518415/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.l
apport information
** Tags added: apport-collected ubuntu
** Description changed:
Hello,
the PC from which I'm sending this report sometimes fails to boot into
the desktop properly (which desktop environment doesn't seem to matter).
In the failure case the following happens:
- Th
** Bug watch added: Linux Kernel Bug Tracker #105981
http://bugzilla.kernel.org/show_bug.cgi?id=105981
** Also affects: systemd via
http://bugzilla.kernel.org/show_bug.cgi?id=105981
Importance: Unknown
Status: Unknown
** Project changed: systemd => linux
--
You received this bug
Here are the links to the upstream bug report that I posted to the
linux-pm and the netdev mailing list:
https://marc.info/?l=linux-pm&m=144420765316442&w=2
http://www.spinics.net/lists/netdev/msg346751.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
** Attachment added: "Output of dmesg after next reboot"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450396/+attachment/4486124/+files/dmesg-after-next-reboot.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Ok, I made a resume trace with my workaround deactivated on Kernel
4.3-rc4, while the bug (= waking up automatically) appeared.
I have attached two dmesg files: The first one contains the output
directly after resume. The second one contains the output directly after
the next reboot. I'm not sure
Christopher, yes, my workaround seems to work in both cases 1) and 2) (
=PC stays suspended properly and doesn't power itself on unwantedly).
Btw. it seems that which graphics driver is in use is completely
unrelated to this bug.
Regarding 3):
- It doesn't seem to matter if I suspend by pressing p
** Attachment added: "/proc/acpi/wakeup"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450396/+attachment/4485485/+files/wakeup
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.laun
Disregard my last comment - I did a test anyway with 4.3-rc4 and Nouveau
and supending with Nouveau worked at least one time so I could reproduce
and confirm the bug for 4.3-rc4.
** Tags removed: kernel-bug-exists-upstream-4.2.3
** Tags added: kernel-bug-exists-upstream-4.3-rc4
--
You received t
The lasted upstream kernel I could test was 4.2.3, because with 4.3 the
compilation and installation of the Nvidia kernel module fails, and I
can only test with the propritary Nvidia driver because suspend doesn't
work properly with Nouveau on my card.
** Tags added: kernel-bug-exists-upstream ker
Hello Christopher,
I updated the BIOS to F14 a few months ago to test if this makes any
change on the bug, but it didn't.
Here's the output of sudo dmidecode -s bios-version && sudo dmidecode -s
bios-release-date:
F14
06/18/2009
Kind regards,
Jan
** Changed in: linux (Ubuntu)
Status: I
I'm attaching the script here that I'm using as a workaround under Vivid
and Wily for proper suspend (put into /lib/systemd/system-sleep).
Kind regards,
Jan
** Attachment added: "set-wol-on-suspend.sh"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450396/+attachment/4483622/+files/s
Like carlix, I didn't see this bug so far under Wily.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1434986
Title:
Not working network connection after boot
Stat
In the photo, the last two lines are there to illustrate how a print
with proper black looks like in comparison.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1499389
Title:
Public bug reported:
Hello,
if I print black text on my HP Photosmart D5460, the output is grey
instead of black when choose "A4 borderless" as media size.
Steps to reproduce:
1. Start LibreOffice Writer, write some text
2. Click "File -> Print"
3. In the print dialogue, check "Use only paper s
** Attachment added: "Photo of how the output of black text looks like with
different settings"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1499389/+attachment/4473338/+files/P1050334.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Hello Martin,
I think I have found the real cause of the bug: It seems to always
happen when the wol flag is set to 'ug' (instead of 'g' or 'd'). I made
a few reboots and checked the wol value with 'ethtool eth0' and it was
always set to 'ug' by default after system startup (I don't know if this
Martin, I did check that and I think I can preliminary give results that
are quite interesting:
- If I run the ethtool command before 'systemctl suspend', the bug
hasn't appeared so far - and it does not seem to matter if I run ethtool
with the 'wol g' (enable WOL) or with the 'wol d' flag!
- Af
Yes, 'pm-powersave false; systemctl suspend; pm-powersave true' seems to
work, and I think I have identified the responsible hook:
/usr/lib/pm-utils/power.d/disable_wol
The bug appears even when all other hooks are there and otherwise has
not occured so far when "disable_wol" is the only hook ena
Some progress: After I failed to identify the responsible hook by
running them before 'systemctl suspend' I had the idea to test vice
versa if I would be able to reproduce the undesired wakeups with pm-
suspend by successively disabling its hooks (=moving the files in
/usr/lib/pm-utils/sleep.d to a
Public bug reported:
Hello,
the icon size of the folder-drag-accept/gnome-fs-directory-accept icon
in Nautilus is too small when a zoom level bigger than 100% in the icon
view is used. This can be reproduced the following way:
- Start Nautilus (or Nemo)
- Open a directory that contains at least
** Attachment added: "Screenshot when trying to move a file in Nautilus"
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1462346/+attachment/4410411/+files/wrong-sized-icon.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
Thanks for the hint to try more than one hook at once, that's really
useful!
I'm done with the testing faster than I thought, because unfortunately
none of the hooks makes the bug go away. I even tested applying all five
of them together, but no success.
The only thing notable is, that /bin/sh sp
Ok, then I'll test those hooks, it may take a few days before I can give
a definitive feedback because it will need quite a few suspend-resume
cycles to validate if one of the hooks really makes the problem go away.
--
You received this bug notification because you are a member of Ubuntu
Touch se
Yes, the output of 'lsmod|grep alx' is indeed empty.
Since my system doesn't have wifi, I don't think anything WPA related
could be the cause. I ran the commands anyway:
sudo wpa_cli suspend ; sudo systemctl suspend; sudo wpa_cli resume
and it has no positive impact. The output of wpa_cli is
Benjamin, I don't think the problem is related to a somehow messed up
configuration (user or system wide), because as mentioned in #8, I can
reproduce the bug by booting from a pristine live iso image. Or we a
suffering from different bugs.
--
You received this bug notification because you are a
I did check it again yesterday and today using 'systemctl suspend'. The
bug does not always happen, e.g. yesterday I was able to suspend my
system 4 or 5 times in a row properly, but tomorrow after the first
attempt the PC woke up again by itself ~2 seconds after I suspended it.
So yes, the bug is
Martin, thanks for looking into this, I have attached the requested
file.
** Attachment added: "last_known_working.quirkdb"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450396/+attachment/4408564/+files/last_known_working.quirkdb
--
You received this bug notification because you a
Benjamin, calix: Did you test booting your system with
init=/sbin/upstart ? On my system this bug also appears when using
Upstart as init, so this doesn't seem to be related to Systemd.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
Further information:
When my system is booted with Systemd, the bug does _not_ appear when I
use "pm-suspend" to suspend my PC. If I use "systemctl suspend" instead,
the bug appears. This seems to confirm that it indeed an issue caused by
a component of Systemd.
And it also happens on Debian Jess
The uploaded version (Gtk 3.14.13-0ubuntu1) fixes the problem for me,
thanks alot! :-)
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
h
I think I see the same problem when I'm using the file manager Nemo and
use "Compact view" as a view mode in a directory that contains as much
files/subdirectories that they don't fit in the window completly (I'm
using an ordinary mouse, no trackpoint).
Before Vivid I could scroll to the right by
Public bug reported:
Hello,
using Suspend-to-RAM on my system has stopped working reliably on Vivid
when booting with Systemd. When I try to suspend my PC the following
happens:
- PC turns off
- PC unwantedly wakes up (turns on) by itself again. This time span until it
turns on again can reach
Some addtional information:
- The bug also appears when booting a live session
- If I setup my network via /etc/network/interfaces (= not managed by
NetworkManager), the connection was always in a sane state, so it seems that
NetworkManager is somehow responsible indeed.
Kind regards,
Jan
--
Y
I suffer from the same problem and have just (accidently) reported a
duplicate: #1445999
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1434986
Title:
Not working
*** This bug is a duplicate of bug 1434986 ***
https://bugs.launchpad.net/bugs/1434986
Public bug reported:
Hello,
after installing Vivid, nearly each time when I boot my PC
NetworkManager fails to setup the (wired) connection to my router (via
DHCP) properly. That means:
- I can ping only
72 matches
Mail list logo
