** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
** Tags
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17
in any case someone faces the same problem, installing
bluez_5.46-0ubuntu3_amd64.deb from artful (together with libreadline7)
solved the problem for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Does the bug go away if you boot back into the 16.04 kernel?
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Did the old patch work for you? I mean could you switch the layout
pressing Ctrl while combos like Ctrl-S also worked as expected?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/36812
Title:
(In reply to Serge Roussak from comment #146)
> Try, please, apply your patch, assign the left Ctrl as switching key and
> then to save something in the kate editor (or other) using Ctrl+S...
You mean to say the new patch doesn't work for you? Please be more
clear.
--
You received this bug
Public bug reported:
Unable to install Bootloader on any of the 3 different drives on the
computer(256GB M.2, 128GB SSD or 500GB HD)Fresh install from previously
used LiveUSB.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.4
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic
> - Can you describe a bit how you imagine the changes to xkeyboard-config
> would look with this approach?
We would need changes wherever we want the new behaviour. I would prefer to
create new options for group switching, rather than modifying existing options.
Comments #117 and #118 show
Not really.. This is something that has changed from 1.18 to 1.19.
"act" is now already passed as reference to XkbActionGetFilter.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/36812
Title:
Public bug reported:
My system is a Intel CPU + AMD R530 system hybrid graphic system.
It always fail in a loop, When I install ubuntu 18.04.
and you will see one fail message in processing:
[FAILED] Failed to start Detect the available GPUs and deal with any system
changes.
See 'systemctl
3.13.0-151.201 - generic
Regression test CMPL, RTB.
Issue to note in amd64:
ubuntu_kvm_smoke_test - uvt-kvm wait issue on Trusty(bug 1732883)
ubuntu_kvm_unit_tests - 39 failed on pepe
ubuntu_ltp_syscalls - fcntl35 / fcntl35_64 in LTP syscall test failed with
T/X/X-LTS kernel (bug 1774394)
** Changed in: linux-kvm (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770245
Title:
getlogin will fail to open /proc/self/loginuid
To manage notifications
This bug was fixed in the package debhelper - 11.3.2ubuntu1
---
debhelper (11.3.2ubuntu1) cosmic; urgency=medium
* Merge from Debian testing. Remaining changes:
- Generate ddebs from debhelper instead of pkg-create-dbgsym
+ Make debhelper Conflict/Replace
** Tags added: artful bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775784
Title:
inotify08 in LTP syscall test failed with X/X-LTS/X-HWE/A/B kernel
To manage notifications about this bug
Public bug reported:
We have several machines where unbound was updated tonight by automated
security updates to 1.5.8-1ubuntu1.1. Afterwards there was no unbound
process running, output from systemctl status says:
systemctl status unbound
It happens to me too. Please let me know if you need more info.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512120
Title:
[SRU] thunar crashes on file renaming
To manage notifications about
(In reply to Nikolay from comment #155)
> There is now once more spike of activity here - probably because Ubuntu
> 17.04 was released recently which dropped this patch because it was not
> compatible with newer xorg. kyak has provided an updated patch, but it would
> take a lot of time for
Created attachment 6613
Check-if-a-thunar-file-is-still-valid-before-reloading.patch
Deactivating SEND_MOVED code paths didn't help completely, thunar was
still crashing on renaming sometimes (more often than not).
Alternative workaround. Does fix all? crashes on my system - I hope this
isn't
Copying from https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=800723#96:
This is with thunar-1.6.10: (line numbers will be off because I was
adding debug printfs)
thunar_file_info_reload() touches memory deleted by
thunar_folder_reload()
I don't think this is a thread race because I always
With Check-if-a-thunar-file-is-still-valid-before-reloading.patch, I
still see the invalid reads and writes, but not the crash on strcmp(NULL
Also, moving ~20 files (drag and drop to another thunar window) feels
very slow now.
--
You received this bug notification because you are a member of
Yes, I'm pretty sure I've been able to trigger it with both copy/paste
and drag/drop.
I don't have a reliable way of reproducing it, I manually click around
until I get a crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I believe the drag & drop issue you describe here has been there for a
long time. I am not sure it has anything to do with 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/1512120
Title:
With the patch from comment #14 alone, crashing still happened on rename
but infrequently (I found that if I Ctrl+c, Ctrl+v, F2, rename - that I
could get it to crash every about 10th rename attempt, but infrequently
through other methods).
With Emil's patch alone, crashing on rename happened
I think I have more details to add: this bug happens always when the window is
out of sync with the real filesystem state. By example, see #12452: when it
happens, a subsequent rename will surely crash Thunar.
In general, it goes out-of-sync on network mounts quite often, so it should not
be
Oh, sorry, which bug should I be following up on?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512120
Title:
[SRU] thunar crashes on file renaming
To manage notifications about this bug go to:
Sorry, to be clear: I still see the invalid reads and writes when I'm
dragging and dropping files in the UI.
I tried the loop for renaming files every second and wasn't able to
trigger a crash in thunar with or without the patch.
--
You received this bug notification because you are a member of
On Emil's prompting, I did some more testing today and found something
interesting:
With Emil's patch only, the crashing only seems to happen if Thunar is
running in daemon mode (I have "Thunar --daemon) in my startup list.
Interestingly, if I run the Thunar instance through gdb and it crashes,
No, it's ok, I just wanted to state that the issue *might* be a
different one than the crashes. Does it also happen with cut & paste,
not only drag?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Was seeing a crash at each file move/renaming...
I have a pretty decent core i7 which might increase threads concurrency
problems frequency...
Have ran thunar like so for quite some time and operations now without crash :
numactl --physcpubind=+1 thunar
--
You received this bug notification
The update problems are also evident when a script renames multiple
files at once. Maybe a rewrite for the changes in glib is still needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512120
** Bug watch added: Debian Bug tracker #800723
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800723
** Bug watch added: bugs.freebsd.org/bugzilla/ #208341
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208341
** Bug watch added: Xfce Bugzilla #12772
On a second thought, maybe these remaining update problems have existed
in earlier versions too but simply went unnoticed. Anyway, here is a
very simple test case to showcase the problem:
1) create files:
for i in $(seq 1 10); do touch "$i.txt"; done
2) loop for renaming files every second:
(In reply to slumbergod from comment #141)
> @Yuri. Thunar hangs for me trying to view the contents of a newly inserted
> flash drive.
This is weird. I mean: I'm running 64-bit XUbuntu 16.04.1 LTS with
Thunar 1.6.10-2ubuntu1+patch1 installed from my PPA
I forgot to mention that I am on an x64 Arch Linux machine (current as
of today). an strace (with patch #6779 applied) gives:
write(4, "\1\0\0\0\0\0\0\0", 8) = 8
recvmsg(5, {msg_namelen=0}, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily
unavailable)
inotify_rm_watch(14, 5)
(In reply to Kip from comment #124)
> (In reply to Yuri R. Sucupira from comment #123)
> > After a LOT of pain (it took me some hours) I finally managed to sign my
> > sources and upload'em to a PPA. Here's the PPA:
> >
> > https://launchpad.net/~yuri-sucupira/+archive/ubuntu/thunar1.6.10-patched
I can confirm the freezes when external USB pendrive is connected. :_(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512120
Title:
[SRU] thunar crashes on file renaming
To manage notifications
(In reply to Kip from comment #132)
> Hey Yuri. I just tried your Thunar packages for Yakkety and I can confirm
> that I am unable to reproduce the crash we've all been having on file /
> directory rename.
Glad to hear that. I had only Xenial (*Ubuntu 16.04) packages on that
PPA, but I've
I just tested patch #6779: It fixes the issue, but thunar becomes
unresponsive for me when trying to access another filesystem like a USB
drive. This does not happen with #6530 and #6778, which also seem to fix
the problem (I didn't test extensively, though).
--
You received this bug
@poma: quoting from the only open issue at
https://github.com/rgcjonas/thunar-gtk3: "Thunar-gtk3 is a personal research
project which is kind of abandoned at this point and likely not going anywhere."
This doesn't sound like something which you want to merge to master.
--
You received this bug
Thunar 1.6.10-4 still crashes during moving files, drag-and-drop, cut-
and-paste and renaming. This has been going on since 2015. It makes
Thunar completely unusable, please fix this!!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(In reply to Andreas Böhler from comment #134)
> I forgot to mention that I am on an x64 Arch Linux machine (current as of
> today). an strace (with patch #6779 applied) gives:
>
> write(4, "\1\0\0\0\0\0\0\0", 8) = 8
> recvmsg(5, {msg_namelen=0}, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource
>
Archlinux Latestalways crashing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512120
Title:
[SRU] thunar crashes on file renaming
To manage notifications about this bug go to:
I completely agree. Most things people do with a filemanager is moving
and naming files. I looked out for other filemanagers like nautilus,
xfe, spacefm, gentoo, pcmanfm, etc. I would like to stay with the Xfce
default as I generally like it, but the importance or severity of this
bug must be
Please check for duplicates: #12260, #10805
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512120
Title:
[SRU] thunar crashes on file renaming
To manage notifications about this bug go to:
@Yuri. Thunar hangs for me trying to view the contents of a newly
inserted flash drive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512120
Title:
[SRU] thunar crashes on file renaming
To manage
> After a LOT of pain (it took me some hours) I finally managed to sign my
> sources and upload'em to a PPA. Here's the PPA:
>
> https://launchpad.net/~yuri-sucupira/+archive/ubuntu/thunar1.6.10-patched
>
> However, I noticed that APT is considering "1.6.10-2ubuntu1" as a newer
> version than my
Created attachment 6767
Patch to thunar_folder_monitor to stop "files added" on "monitor move" event
The attached patch updates the code in thunar_folder_monitor with a fix
to prevent the rename crashes by stopping the "files added" on "monitor
move" event behaviour. I can no longer reproduce any
Message:
E: firebird3.0-server: installed firebird3.0-server package post-
installation script subprocess returned error exit status 1
apt log:
Preconfiguring packages ...
Selecting previously unchecked package firebird3.0-common-doc.
(Reading database ... 202480 files and directories
Public bug reported:
This is not a regression, this can be found on 4.15.0-21.22 as well.
* Command:
./ubuntu_fan_smoke_test.sh 10.245.0.0/16
Exit status: 1
Duration: 58.4590229988
stdout:
Running in the Canonical CI environment
Testing Fan Networking (pre-0.13.0 API)
docker
Public bug reported:
crash at firebird server instalation
ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: firebird3.0-server 3.0.2.32703.ds4-11ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset
As I commented earlier you may find where you program crashes, just add
SIGSEGV handler and export stack trace somewhere. I'm sure that there is
segfault, not stack overflow or call of exit function.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
(In reply to kyak from comment #142)
I mean dereferencing sendEvent pointer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/36812
Title:
Keyboard layout change on hotkeys press instead of
Thread 1 "thunar" received signal SIGSEGV, Segmentation fault.
0x7466fd26 in __strcmp_ssse3 () from /usr/lib/libc.so.6
(gdb) bt
#0 0x7466fd26 in __strcmp_ssse3 () from /usr/lib/libc.so.6
#1 0x004340ad in ?? ()
#2 0x004406cb in ?? ()
#3 0x74b645d4 in ??
(In reply to Yuri R. Sucupira from comment #116)
> I've managed to build and install the (actually five) "patched" DEB
> packages. Now Thunar seems to be back to normal, although I still have more
> testing to do.
>
> I've uploaded those packages to my OneDrive:
>
>
(In reply to Yuri R. Sucupira from comment #116)
> (In reply to xb from comment #115)
> > (In reply to Roy Richardson from comment #114)
> > > Created attachment 6801 [details]
> > > Notes for patching Thunar on Ubuntu with patch #6779
> > >
> > >
> > > I've successfully tested patch #6779 on
Created attachment 6801
Notes for patching Thunar on Ubuntu with patch #6779
I've successfully tested patch #6779 on Debian Stretch i386, Debian Stretch
amd64, Xubuntu 16.04 amd64 and Arch x86_64. Here are my notes for patching and
building Thunar on Ubuntu. I hope this works as well for you
patch in attachment 6779 will not apply .. seems damaged?? incomplete
lines?
patch does not " find the file to patch .. incorrect -p or strip option
.."
the other patches 6778 and 6530 apply fine but I still had a crash on a
file move
for thunar-gtk3 with patches..
--
You received this bug
The patch in attachment 6778 above moves the call to thunar_file_monitor_moved
which was previously done within thunar_file_rename when called by
_thunar_io_jobs_rename in an IO thread job, to be instead called by a new
function thunar_file_rename_notify by _thunar_io_jobs_rename_notify in the
Created attachment 6778
This changes tunar_file_rename/_thunar_io_jobs_rename so that
thunar_file_monitor_moved is called in the main thread, instead of the IO job
thread.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ok manually edited files to match patch-attachment 6779 .. discovered
another chunk of code (an if statement not in the source that 6779 was
patched against) removed the extra if and the patched source compiled
and built fine .. but crashed attempting the first file move ..
this is just 6779 w/o
You could have been friendlier. Instead you show yourself to be an
asshole. Adios.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512120
Title:
[SRU] thunar crashes on file renaming
To manage
Created attachment 6779
Handle folder change events with file info synchronization
Here's the latest set of changes that I have been testing which handle
folder change events and synchronize updates to file info by multiple
threads.
The patch contains the following changes to address the
(In reply to Jonathan Rennison from comment #108)
> The patch in attachment 6778 [details] above moves the call to
> thunar_file_monitor_moved which was previously done within
> thunar_file_rename when called by _thunar_io_jobs_rename in an IO thread
> job, to be instead called by a new function
(In reply to Yuri R. Sucupira from comment #120)
> And
> unfortunately I didn't succeed in uploading data to the PPA (I'm using dput,
> but something's going wrong). I thought I could push the DEB files to the
> PPA, but it's actually forbidden: one must push the sources, which I'm
> failing to
(In reply to Roy Richardson from comment #114)
> Created attachment 6801 [details]
> Notes for patching Thunar on Ubuntu with patch #6779
>
>
> I've successfully tested patch #6779 on Debian Stretch i386, Debian Stretch
> amd64, Xubuntu 16.04 amd64 and Arch x86_64. Here are my notes for patching
(In reply to xb from comment #115)
> (In reply to Roy Richardson from comment #114)
> > Created attachment 6801 [details]
> > Notes for patching Thunar on Ubuntu with patch #6779
> >
> >
> > I've successfully tested patch #6779 on Debian Stretch i386, Debian Stretch
> > amd64, Xubuntu 16.04
@Martin Dauskardt
The patch is based on the git master.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512120
Title:
[SRU] thunar crashes on file renaming
To manage notifications about this bug
Mint 18 XFCE just updated to 18.1 here. Still with Thunar 1.6.10-3mint1.
Still working like a charm. No problem moving files between folders. No
problem renaming files. Mint team got the answer to your problems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
(In reply to pgkos.bugzilla from comment #155)
> I am sending a simple patch which wraps the renaming code and the folder
> monitor code in a mutex.
>
> I suppose that the main reason for the crash is that when we call in
> thunar-file.c:1932:
>
> g_file_set_display_name (file->gfile, name,
(In reply to Peter Feichtinger from comment #146)
> Please file another bug for that issue and stop spamming the comments for
> this one.
Peter, please remember your manners.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Six boring minutes watching Simon Steinbeiss' test (comment 160) working on
Thunar 1.6.10-3mint1 (Mint Xfce 18.1).
During all the time the files changed their names with no problem at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Mint applies 4 patches to Thunar in 1.6.10-3mint1:
0001-Don-t-copy-templates-but-create-them-bug-8312.patch (bug #8312)
01_support-non-multiarch-modules.patch (related to loading modules on different
architectures, not related to this bug)
Hey Peter why don't you remove yourself from all these bug reports and
do the rest of us a favour.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512120
Title:
[SRU] thunar crashes on file renaming
Please file another bug for that issue and stop spamming the comments
for this one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512120
Title:
[SRU] thunar crashes on file renaming
To manage
My experience:
I'm using Mint XFCE 18 x64 since a couple of months and Thunar is working
correctly. This distro uses a version of Thunar called 1.6.10-3mint1.
On any other modern distro that I tried and includes Thunar 1.6.10 (MX16,
Xubuntu16.04, LinuxLite3, etc) the file manager is buggy. Mint
@yuri. Thanks Yuri, I appreciated the PPA. Much easier to test. After
some additional testing:
kernel 4.9.4 patched Thunar hangs when trying to view contents on newly
inserted flash drive.
kernel 4.7.10 same. Thunar hangs. Can't mount or view contents.
BUT I have discovered that thunar only
I am sick to death of a$$holes who contribute nothing useful coming on
here and criticising others for making an effort to get this bug fixed.
You guys have no manners and act like you own the world but I don't see
any of your contributions. This is the problem with linux. It is
infected with
@ pgkos:
Which version of thunar was the base for this patch?
-1.6.10 vanilla?
-1.6.10 with patches from Distribution?
(1.6.10 in Xubuntu 16.10 has for example some additional patches, including the
Check-if-a-thunar-file-is-still-valid-before-reloading.patch from 17.02.2016
from Harald
Addendum:
Kernel on Mint 18 is 4.4.0-xx
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512120
Title:
[SRU] thunar crashes on file renaming
To manage notifications about this bug go to:
Wow, I didn't expect that.
I was not at all trying to be rude and I'm sorry if I offended anyone. It's
just that commenting on this bug with another problem doesn't help anyone
either.
@slumbergod: Looking at your comment you are not allowed to talk about
manners, at all. I mean come on,
I am sending a simple patch which wraps the renaming code and the folder
monitor code in a mutex.
I suppose that the main reason for the crash is that when we call in
thunar-file.c:1932:
g_file_set_display_name (file->gfile, name, cancellable, error);
this call sends a signal which is connected
I would like to confirm this bug which I noticed.
xUbuntu 16.10 / AMD64
xfce 4.12.0-2 ubuntu
Thunar crashes about every 3 or 4 file rename !
Error : Segmentation fault (core dumped)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Nikolay,
First, background: I am not a xorg developer, but I develop the XKB
library used by most Wayland compositors (xkbcommon). The behavior there
is the same.
IMO it is worth having a discussion about the behavior. A nice thing
about XKB is that it has a specification. It is easier to
What slumbergod reported is absolutely on-topic. The problems he and Yuri were
writing about are known side-effect of an earlier patch (which we all hoped
that it could be a solution for the renaming/remove crash.)
The side effects with this patch (when accessing USB drives and other file
(In reply to Regina Henschel from comment #100)
> Daily builds for master can be downloaded from
> https://dev-builds.libreoffice.org/daily/master/
> After a patch is applied you need to wait two days until it is visible in
> these builds.
Thank you for this link.
Also many thanks for fixing the
Finally fixed by commits
https://cgit.freedesktop.org/libreoffice/core/commit/?id=9886a69c472f212d88f11cfa0f3835e5dcf485b2
-
https://cgit.freedesktop.org/libreoffice/core/commit/?id=8d107b8d3b33b16436fbe64a5e296ec5a2c69e5d
(tellingly codenamed OperationSmiley :) )
Thank you Armin and Thorsten!
(In reply to Xisco Faulí from comment #88)
I did not play much with it, but yes, I cannot see the dots with LO 5.4.4.2 x64
on windows 10, viewing with Adobe.
With a document of mine the dots are not visible at zoom > 75% if the default
style line width is set bigger than 0.03 cm. With zoom <
(In reply to Papamatti from comment #98)
> This fix works for me, I'm so happy with this!
>
> Thank you very much!
Sorry for bothering, where can I download a version with fix for testing?
I am not a software guy, cannot build my own ".exe".
--
You received this bug notification because you
(In reply to Klaus Müller from comment #99)
> Sorry for bothering, where can I download a version with fix for testing?
> I am not a software guy, cannot build my own ".exe".
Daily builds for master can be downloaded from
https://dev-builds.libreoffice.org/daily/master/
After a patch is applied
This fix works for me, I'm so happy with this!
Thank you very much!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/689349
Title:
[Upstream] Draw file exported to PDF have erroneous pixel-sized dots
Well, I still think the current implementation is not good (it still
forces the user to rename the original file manually), but I moved to
Nemo after upgrading to 18.04, I do not like the direction of Nautilus
development.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
I don't have any further details, the installer just said it crashed.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
This only seem to happen under load, so it really looks like a race
condition during the restart. Guessing the daemon finishes processing
requests before it terminates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
At one point, it seemed that the two patches from comment #14 (Harald)
and comment #41 (Emil) were enough to fix two separate crashes: one
triggered by rename, one triggered by drag-and-drop.
Harald himself stated that his patch was not intended as a real fix,
just a workaround. I wrote an
*** Bug 12673 has been marked as a duplicate of 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/1512120
Title:
[SRU] thunar crashes on file renaming
To manage notifications about this
The issue of fixing the spec was raised before, and the answer thn was:
(Vasily Khoruzhick from comment #37)
> Daniel is now working on XKB2, so fixing/changing XKB1 has no sense :)
As far as I know, XKB2 was never released, not even as a draft.
Are you saying that the situation has changed and
(In reply to Roy Richardson from comment #82)
> Created attachment 6767 [details]
> Patch to thunar_folder_monitor to stop "files added" on "monitor move" event
I patched archlinux thunar (thunar 1.6.10-3, x86_64) with this patch and I am
unable to reproduce the crash.
--
You received this bug
(In reply to Serge Roussak from comment #152)
> (In reply to Oleg from comment #151)
> > Did the old patch work for you? I mean could you switch the layout pressing
> > Ctrl while combos like Ctrl-S also worked as expected?
>
> Which patch do you mean when you say "old"?
The one that was made
201 - 300 of 891 matches
Mail list logo
