[Bug 1930465] Re: mousepad editor warns "the document has been externally modified" when modifying a soft linked text file
Working again in 21.10 impish. Did not test cifs/smb. But since 21.04 hirsute will be EOL I think we should close this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930465 Title: mousepad editor warns "the document has been externally modified" when modifying a soft linked text file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mousepad/+bug/1930465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930465] Re: mousepad editor warns "the document has been externally modified" when modifying a soft linked text file
https://gitlab.xfce.org/apps/mousepad/-/issues/135 "Externally Modified" warning when saving file opened from symlink ** Bug watch added: gitlab.xfce.org/apps/mousepad/-/issues #135 https://gitlab.xfce.org/apps/mousepad/-/issues/135 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930465 Title: mousepad editor warns "the document has been externally modified" when modifying a soft linked text file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mousepad/+bug/1930465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930465] [NEW] mousepad editor warns "the document has been externally modified" when modifying a soft linked text file
Public bug reported: 1. RELEASE (XUBUNTU) # lsb_release -rd Description:Ubuntu 21.04 Release:21.04 2. PACKAGE # apt-cache policy mousepad mousepad: Installed: 0.5.3-0ubuntu1 Candidate: 0.5.3-0ubuntu1 Version table: *** 0.5.3-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages 100 /var/lib/dpkg/status 3./4. DESCRIPTION When opening a file with mousepad 0.5.3 in xubuntu 21.04 after doing changes to the file and hitting Ctrl+S to save the changes, a warning pops up with the following warning: "Externally modified The document has been externally modified. Do you want to continue saving? If you save the document, all of the external changes will be lost" Opening instead the file directly (i.e. not via soft link), mousepad will not issue the warning. How to reproduce: 1. echo test > bla.txt 2. mousepad bla.txt 3. Do some changes and hit Ctrl+S -> this will save w/o dialog. 4. Quit mousepad with Ctrl+q 5. ln -s bla.txt blaln.txt 6. mousepad blaln.txt 7. Do some changes and hit Ctrl+S -> this will cause the dialog to open. This behavious has changed from groovy 20.10 with mousepad 0.4.2-1 to hirsute 21.04 with mousepad 0.5.3-0ubuntu1. An upgrade was made from groovy -> hirsute but this should also occur when running from live cd. I also tried the newer and older binaries of mousepad from https://packages.ubuntu.com/impish/mousepad 0.5.4-0ubuntu1 https://packages.ubuntu.com/groovy/mousepad 0.4.2-1 (just did a "dpkg -x *.deb ." and started the mousepad binary). Impish's mousepad showed the same error. Groovy's mousepad was working as before/expected. I went quickly through the release notes of mousepad but could not find or see something related https://gitlab.xfce.org/apps/mousepad/-/tags ** Affects: mousepad (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/1930465 Title: mousepad editor warns "the document has been externally modified" when modifying a soft linked text file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mousepad/+bug/1930465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610405] [NEW] timedatectl not reporting DST info
Public bug reported:
DST information in timedatectl went awol some time around ubuntu 13.x or
14x.
Currently running:
lsb_release -rd
Description: Ubuntu 16.04.1 LTS
Release: 16.04
affected Package: systemd,229-4ubuntu7, amd64
What I see:
#/usr/bin/timedatectl
Local time: Fr 2016-08-05 21:38:03 CEST
Universal time: Fr 2016-08-05 19:38:03 UTC
RTC time: Fr 2016-08-05 19:38:03
Time zone: Europe/Berlin (CEST, +0200)
Network time on: yes
NTP synchronized: yes
RTC in local TZ: no
What I expect:
#./timedatectl_centos
Local time: Fr 2016-08-05 21:38:29 CEST
Universal time: Fr 2016-08-05 19:38:29 UTC
RTC time: Fr 2016-08-05 19:38:29
Time zone: Europe/Berlin (CEST, +0200)
NTP enabled: yes
NTP synchronized: yes
RTC in local TZ: no
DST active: yes
Last DST change: DST began at
So 2016-03-27 01:59:59 CET
So 2016-03-27 03:00:00 CEST
Next DST change: DST ends (the clock jumps one hour backwards) at
So 2016-10-30 02:59:59 CEST
So 2016-10-30 02:00:00 CET
According to systemd's changelog over at
https://github.com/systemd/systemd/blob/master/NEWS DST reporting appeared with
196. No signs of removal of this functionality.
How to reproduce
1. execute timedatectl on a live system might work
2. I'm running a out-of-the box installation of 16.04. Problem can be seen on
two different laptops.
3. sudo timedatectl makes no difference
4. The expected output above was created by a timedatectl binary taken Centos
(just extracted from rpmfind's systemd-219-19.el7_2.7.x86_64.rpm resp. copied
over from a RHEL 7 system )
Not sure if useful, both binaries in comparison:
# /usr/bin/timedatectl --version
systemd 229
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN
#./timedatectl_centos --version
systemd 219
+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
+GCRYPT +GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN
# file /usr/bin/timedatectl
/usr/bin/timedatectl: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux
2.6.32, BuildID[sha1]=1044615393ef0fb0bf462bfbc528ab8ef8481eba, stripped
# file ./timedatectl_centos
./timedatectl_centos: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux
2.6.32, BuildID[sha1]=fad3fb9a6e27da8d30ce196b79c482a5d3090dda, stripped
# ldd /usr/bin/timedatectl
linux-vdso.so.1 => (0x7ffd3471d000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1
(0x7f3b923ac000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f3b921a4000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f3b91f86000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f3b91bbd000)
/lib64/ld-linux-x86-64.so.2 (0x55e26d64c000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7f3b9194d000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f3b91748000)
# ldd ./timedatectl_centos
linux-vdso.so.1 => (0x7fffd5fdf000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f59c3416000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x7f59c320)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f59c2fe2000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f59c2c19000)
/lib64/ld-linux-x86-64.so.2 (0x560b23381000)
Return code of both is 0.
strace /usr/bin/timedatectl stops here:
[...[
stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2335, ...}) = 0
write(1, " Time zone: Europe/Berlin "..., 46 Time zone:
Europe/Berlin (CEST, +0200)
) = 46
write(1, " Network time on: yes\n", 22 Network time on: yes
) = 22
write(1, "NTP synchronized: yes\n", 22NTP synchronized: yes
) = 22
write(1, " RTC in local TZ: no\n", 21 RTC in local TZ: no
) = 21
close(3)= 0
exit_group(0) = ?
+++ exited with 0 +++
strace ./timedatectl_centos continues:
[...]
write(1, "NTP synchronized: yes\n", 22NTP synchronized: yes
) = 22
write(1, " RTC in local TZ: no\n", 21 RTC in local TZ: no
) = 21
open("/etc/localtime", O_RDONLY|O_CLOEXEC) = 4
fstat(4, {st_mode=S_IFREG|0644, st_size=2335, ...}) = 0
fstat(4, {st_mode=S_IFREG|0644, st_size=2335, ...}) = 0
read(4, "TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\t\0\0\0\t\0\0\0\0"..., 4096)
= 2335
lseek(4, -1476, SEEK_CUR) = 859
read(4, "TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\t\0\0\0\t\0\0\0\0"..., 4096)
= 1476
close(4)= 0
write(1, " DST active: yes\n", 22 DST active: yes
) = 22
write(1, " Last DST change: DST began at\n", 31 Last DST change: DST
[Bug 1385926] Re: [Dell Latitude D400] Black screen on resume after suspend by lid close persists in Xubuntu 14.10
sorry for that. Will file a new report -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385926 Title: [Dell Latitude D400] Black screen on resume after suspend by lid close persists in Xubuntu 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385926] Re: [Dell Latitude D400] Black screen on resume after suspend by lid close persists in Xubuntu 14.10
confirming this affect me too: uname -a Linux karoushi 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:07:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Description:Ubuntu 14.10 suspend itself works fine Laptop: SONY VAIO VPCCB3S1E (Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz, with additional [AMD/ATI] Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M] ) using XFCE POwerManager with xscreensaver. * system upgraded from 14.01 * created new user to exclude possibility of old configuration files messing up something to no avail * to make suspend work changes in /etc/systemd/logind.conf HandlePowerKey=ignore HandleSuspendKey=ignore HandleHibernateKey=ignore HandleLidSwitch=ignore * Fixes didn't work in 14.04* already Workarounds as described either 1. type blind, open terminal with shortcut and enter xrandr --auto or 2. suspend before closing the lid (e.g. powerbutton) Also: happens only with internal Monitor, if external is connected (here HDMI), only LVDS remains black. Tried with upstream Kernel (daily, had issues with rc2) linux-image-3.18.0-999-generic_3.18.0-999.201410290205_amd64.deb but problem still exists. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385926 Title: [Dell Latitude D400] Black screen on resume after suspend by lid close persists in Xubuntu 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
