Hello, I can confirm that this bug still exists in 20.04.
I am using NVidia 340.108 because this is a 12 years old laptop with a
completely obsolete GeForce GT230M.
Workaround #34 (removing quiet splash) worked but slows down the boot
process due to the speed of writing on the console.
Workaroun
So to make #101 permanent, you have to "patch" line 335 of
/etc/grub.d/10_Linux
from:
set vt_handoff=vt.handoff=7
to:
set vt_handoff=vt.handoff=1
Not sure though the same "patch" is also to be applied in other files like
10_linuxzfs, etc...
Patch attached:
$ cat
Note: the patch (if #101 is the "right" solution) applies to the package
"grub-common" that contains /etc/grub.d/10_linux
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Fresh install of 18.04.1 + Unity
I had the bug, but I can confirm than workaround at post #11 (2 seconds
delay before starting compiz) has fixed it.
Thanks Park Ju Hyung!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings
Sorry, I have stopped using Nautilus when Gnome decided it should be a
tablet tool instead of a PC program, and withdraw all interesting
functions from it (like F3 to open a double pane).
I am now using Nemo, which might still have the bug since it forked
Nautilus before its emasculation, but I am
The same bug exists on Nemo (should there be different bug report?)
It is less troublesome when you don't set Nemo as handling also your desktop,
because closing Nemo correctly frees the memory.
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.1 L
Public bug reported:
Binary package hint: evince
When I try open this on evince, it works :
http://gnunet.org/download/ecrs.ps
But when if I try to print it to a pdf file (option print to file / pdf)
it crashes and doesn't make any pdf file.
When launched from terminal, after having downloaded
Thank's for the workaround wribeiro.
I do confirm the bug as of Intrepid.
Moreover, if you switch Nautilus to Tree View, and try to open the tree
(not click the directory, just click the triangle to open the tree) on a
directory such as /usr/share that contains around 300 other directories
(325 o
** Visibility changed to: Public
--
evince crashed with SIGSEGV in spectre_gs_send_page()
https://bugs.launchpad.net/bugs/298139
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in ubuntu.
--
desktop-bugs mailing list
desktop-bugs
Sorry I'm not in the same location now, and I don't have a printer attached to
a Ubuntu PC. I'll try to switch it to my Ubuntu laptop and test it from a
Virtualized Ubuntu (best I can do here).
I'll have a chance to test it in the situation I saw the bug on the first
Week-end of november.
Sorry
And sorry... now it's working out of the box, from my virtualised Ubuntu to my
laptop Ubuntu using Cups and a GTK app like Gedit (or tell me Gedit is not
GTK2?)
May be I already had an update (or Microsoft is doing a great job reparing CUPS
with MS Virtual PC 2007, which is unlikely!).
Anyway f
Public bug reported:
ENVIRONMENT:
-
Precise 64
Nautilus 3.4.2
$ uname -a && nautilus --version
Linux zakhar-desktop 3.2.0-30-generic #48-Ubuntu SMP Fri Aug 24 16:52:48 UTC
2012 x86_64 x86_64 x86_64 GNU/Linux
GNOME nautilus 3.4.2
WEBDAV:
I set up a loca
REFINED WORKAROUND:
--
Of course, if like in the case above, it is YOUR server, for YOUR local use,
there is a better way.
Whatever the password length, you bump the keep-alive time-out to an insane
value (600 secs!) so that you have a large amount of time to type
YOU WOULD HAVE GUESSED...
---
Obviously we notice this buggy behaviour when we use directly Goto > Location >
and enter the address: dav://127.0.0.1/webdav
When using the dialog box under File > Connect to server..., this does not
happen as there is only one r
S=="sky2"
ATTRS{vendor}=="0x11ab"
ATTRS{device}=="0x4362"
ATTRS{subsystem_vendor}=="0x1043"
ATTRS{subsystem_device}=="0x8142"
ATTRS{class}=="0x02"
ATTRS{irq}=="30"
ATTRS{local_cpus}=="00
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/50176430/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/50176431/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/50176432/ProcStatus.txt
--
UDEV r
>> it doesn't happen on a default installation
Do you mean a default *english* installation?
And do gnome-keyring support being called with UTF-8 filenames?
Because of course if it does not (which would be, to my point of view an
architectural error) clients should not call with UTF-8 name.
If
Many thanks Sebastien.
I confirm that your workaround works fine.
I'll post your suggestion on the french forums, so that french people can now
enjoy Lucid with all the stuff going to keyring:
- U1,
- NM
- Empahty
- etc...
Nevertheless it does not prove that there is no bug in gnome-keyring. It
> > - do gnome-keyring handle UTF-8 filenames (maybe specification says it does
> > not... and thus client calling
>it with UTF-8 is buggy)
> it seems it doesn't handle those correctly or this bug would not be
opened
Wow... a program written in the 21st century that do not handle UTF-8.
Shou
I wouldn't consider the importance of this bug as "low".
Ubuntu come with Gnome, and therefore has countless programs that rely on the
GTK+
This simply means you cannot use remote printers (I confirm the bug!) in
Ubuntu... or you switch your printer server to Windows, as there is no
bug in samba
"Best effort" is fine for me: it's not for professional use.
Now I know it's a bug, and not an error I made entering wrong parameters
for remote printers, so, as it's a local "home" network, I just copy the
files over and go to the room where the server is to print them ;-)
I still volunteer for
21 matches
Mail list logo
