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
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/19702508/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/19702509/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/19702510/Disassembly.txt
** Attachm
** 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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
Ok, so it IS a bug ;-)
In fact a regression.
You say : However, VLC 1.0 will work in both case detecting that a Open
Folder is VIDEO_TS.
But 0.8.6 was already detecting that pretty well, I've been using "Open
directory" to watch movies on VLC for ages. But on the 0.9.3 it seems
that it was un-im
I do agree with your answer, it's what I suggest as possible anwser n°1.
Basically, if the answer is so, what I say is there is still a bug... in the
documentation. Because who is a 30 years old *ix legacy, at this time a mouse
was not a frequent input device, hence the documentation does not men
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
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
Public bug reported:
Binary package hint: vlc
Version : VLC 0.9.3 on Intrepid official Beta. AMD64 version.
It might be similar to
https://bugs.launchpad.net/vlc/+bug/275043
that appears to be fixed for DVD playing.
When I try to read "DVD on disk" (e.g. a ripped DVD) it reads all the
files i
Ok so here is a little bit about this bug.
There is a workaroud to open a "DVD on disk" (as it is called on some players
like PowerDVD), it is to go to Media / Open a disc... and browse to the
directory where the DVD has been ripped.
So basically you are replacing /dev/scd0 (the default DVD) by
No, using directly the package from Gutsy without recompiling it.
I know it's evil, and we are not supposed to do so, but it works very well,
whereas when you recompile it on Hardy it seems not to work.
So why bother compiling it ;-)
Then I suspect the bug is not directly on the source of genisoi
It works for me on a Dell laptop (Inspiron 1720 initally Vista, now Vista +
Ubuntu 8.04.1 through Wubi)
I'm using K3B to burn.
This might help... unless you want to stick to mytharchive
With the genisoimage shipped with Hardy (the "official" one) K3B is able to
burn an ISO image as you describe :
Although they might just be frontend to genisoimage, when such frontend
activates genisoimage, it gives parameters to it to do its job.
There is a remote probabibloty that this could be possible, but if we can find
a frontend working (K3B) and other not (mytharchive) difference of parameters
to
Forgive me if my explaination is not clear (I'm not english). The "not
browsable on Windows" happens with K3B and genisoimage Hardy.
If you revert to genisoimage Gutsy, without recompiling it, K3B produces a DVD
that is readable (VLC) AND browsable on Windows... at least that's with my PC
(Ubunt
Nick, the "complete" tuto after downgrading to genisoimage/Gutsy is to block it
in Synaptic so that the wrong version of genisoimage won't be reinstalled.
Anyway, it is possible that some other software might complain because they
might require a specific version of genisoiamge greater than the o
Public bug reported:
Binary package hint: coreutils
Release: [Ubuntu 8.04.1]
-
Package: coreutils (included in the core of Ubuntu)
--
cat /proc/version
Linux version 2.6.24-19-generic ([EMAIL PROTECTED]) (gcc version 4.2.3 (Ubuntu
4.2.3-2ubuntu7)) #1 SMP Wed Aug 20 17:53:40 UTC
After a few time of reflexion, here are my comments / suggestions about
this bug.
Who seems to be mainly a frontend to display nicely the informations in
/var/run/utmp (or /var/log/wtmp for the history).
The documentation says that these files, unfortunately (because it's not vey
good architectu
Public bug reported:
Binary package hint: k9copy
Ubuntu 8.04.01
K9Copy in Ubuntu repository (standard repository, not the backport).
DVD : DaVinci Code - Rental rights included - France (Droits locatifs inclus
France)
This DVD shows, with the option "fast scan" :
Title 1 (Bold) : 6116 Mo
Title
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
This bug is really a show-stopper.
I can't believe the Ubuntu team wants to close this report even if the bug is
still there (see 5 posts above)
This has stopped me from upgrading to Jaunty, and I bet this bug will stay
uncorrected up to Karmic, where it will (hopefully) disappear with the .30
Duanra, nano is a small text editor.
I suppose Evan means adding "set -x" at the end of the second line, then save
the file and exit the editor and you are done.
I do also suppose somewhere in the process (after copy) the ma-apply you
modified is used to run the migration.
Anyway, I'll do the te
By the way 88% is for Ubuntu. Some report other percentages, and it's
the same bug. For example with Kubuntu the bug happens at 83%, I suppose
it depends on the amount of data you have to copy according to the
distribution you choose !
--
install failed during "import document and setting" at 88%
Ok, so you said "stick set -x" on the second line, it's not very clear !
As we are French, could you use "Globish"... (eq very simple and not
ambiguous words).
Stick, as I posted above, would have implied for me: add something to
something existant, as when you stick a stamp on an enveloppe ;-)
Nth try...
I NEVER have a log written !
But apparently I found a trick to get it written (I got on that randomly while
typing on every key to switch to the installer).
Before going OK on the error message I do Ctrl Alt F1.
It writes "Loading please wait..." eventually it would try to boot to the
>> 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
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/45230513/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/45230514/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/45230515/ProcStatus.txt
** Attachm
*** This bug is a duplicate of bug 553759 ***
https://bugs.launchpad.net/bugs/553759
The duplicate status is wrong... who knows... because the person having
posted bug #553759 didn't make it public, so I can't check!
A clue to debug this problem.
It seems to be a keyring problem (and probabl
I didn't doubt that my https://bugs.launchpad.net/ubuntu/+source
/ubuntuone-client/+bug/569566 report was a duplicate of this one... but
as this one was not public I couldn't check!
Thanks for the status change.
So, I move my comments on this master report.
My findings are that this behaviour se
Public bug reported:
Binary package hint: openoffice.org
Plain and simple, as title indicates.
Even if I try an empty document, it won't save to Docbook.
I get an error message (exact message in French is: "Erreur lors de
l'enregistrement du document , Erreur
d'écriture, Impossible d'écrire dan
I have the same problem at Ubuntu 9.10 (python-xdelta3 0v2.dfsg-
1ubuntu1)
--
error when using xdelta3 python module
https://bugs.launchpad.net/bugs/432812
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
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
I withdraw from this list. As I forcasted 5 month ago (post 162) this
bug is still uncorrected and now Karmic is out. So I'm not waiting
anymore for a correction of this bug, and skip directly to Karmic 64
which is an awesome version.
Keep up the good job !..
--
2.6.28-11 causes massive data cor
The package installer does :
invoke-rc.d inet reload
This is in postint in function InstallInetd
Also in prerm in function MainInetd
Probably due to the replacement of System V Init by upstart this packet
is broken as the above command fails.
--
package micro-httpd 20051212-10 failed to i
I vote for this !
In fact there is a REGRESSION.
On previous Grub (Grub Legacy) you could parameter wether you want to display
only the countdown or the entire menu.
This was done independantly of the number of O.S.es you got on your system.
Now the new system is very confusing.
It has two vari
Hello Andrei, and thanks for your concern.
Unfortunately not, I didn't find any third party tutorial. This is an
"official" one, not "community", since it is hosted on ubuntu.com, and
tells us about ppa, which are a nice feature of Ubuntu.
I don't want to do a trial of intent here, but maybe Cano
Public bug reported:
package grub-efi-amd64-signed 1.66.17+2.02~beta2-36ubuntu3.17 failed to
install/upgrade.
After an update crash this package was half installed and now it is
impossible to EFI-boot, I'm back in Legacy with no grub on my /dev/sda
(booting from an old Legacy install on /dev/sdb)
A workaround was offered "upstream" in Comment #11:
https://bugs.freedesktop.org/show_bug.cgi?id=106422#c11
I tested it successfully so far on my hardware (Inspiron 1525).
1. add "video=SVIDEO-1:d" to your kernel boot options
I still have to confirm the workaround has no other important side
ef
Hi there, I am having this issue too on the same hardware.
This laptop is currently running 14.04 32 bits.
With 14.04 32 bits, there is a message in the log, but it has no effect
but spitting messages in the log!
With 18.04 64bits live, there is the "flip_done timed out" issue. Each one
seems t
As requested above, I filed the bug at freedektop.
Here is the reference:
https://bugs.freedesktop.org/show_bug.cgi?id=106422
** Bug watch added: freedesktop.org Bugzilla #106422
https://bugs.freedesktop.org/show_bug.cgi?id=106422
--
You received this bug notification because you are a memb
More information.
I have narrowed it down:
16.04.1 - kernel 4.4.0-31-generic
==> Works OK with messages ("encoder detached but still enabled on pipe A.")
No visible slowdown apart for 3 or 4 stack traces in the log.
16.04.2 - kernel 4.8.0-36-generic
==> Shows the "time outs" bug
So there must
I have posted a full dmesg with the 'drm-tip' kernel compiled
especially.
Please see "upstream" (link above) for details.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731784
Title:
system slow to
Hello, since the ticket I reported for that bug on freedesktop.org has
now been moved to "high" importance by an Intel person, might I suggest
that this is also moved to "high" accordingly?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Hello, this report has stayed "undecided" / "unassigned" for 3 weeks
now.
It makes the Ubuntu ppa documentation irrelevant:
https://packaging.ubuntu.com/html/packaging-new-software.html
Was it the right place to post it or should I post it somewhere else,
for instance "bzr developers"?
--
You r
Public bug reported:
Hello,
No need to repeat here that the documentation to properly build a
package is of appalling quality. That has been widely commented and is
probably a major hurdle why people don't "package".
Sorry, so that being said, I am using the little documentation there is
on thos
Thanks for the heads up Rafael.
Does this mean the fix is going to be in a new version, hence we won't
have it for 20.04 due to the "freeze" policy of Ubuntu, but it could be
in 20.10 or any subsequent version.
[I have my "workaround" anyway, and it works fine for my own use cases]
--
You recei
Confirmed also on a clean 20.04, kernel 5.4.0-31-generic
The time difference between gzip and lz4 is not noticeable by the user:
LZ4:
Startup finished in 14.815s (firmware) + 3.483s (loader) + 1.879s (kernel) +
23.176s (userspace) = 43.354s
graphical.target reached after 23.164s in userspace
GZ
Clean 20.04, I confirm the bug.
There is a very simple way to reproduce the bug, **without even booting
an O.S.**
- Set your machine to boot in EFI mode
- From the Grub (2.04) Menu, enter command mode (by pressing the key 'c')
- Set the root to where you have your iso files:
For instance:
root=h
Public bug reported:
This is not a bug, but rather an "optimisation" request.
(Probably set this as "enhancement request" + Low)
Apparently, the package is assuming the user will need some iscsi mounts
for his session, and is putting dependencies in the systemd
services/targets which effects are
And the other dump (iscsi ENABLED)
** Attachment added: "systemd-analyze dump (with iscsi services ENABLED)"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1882986/+attachment/5383003/+files/iscsi.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
You're welcome.
Indeed, at first I though it was Virtualbox that has no .service (just a
SystemV classic init) but changing that had no effect, and disabling
iscsi gave me back my 10 seconds !
systemd-analyze:
summary: without iscsi
Startup finished in 17.404s (firmware) + 3.367s (loader) + 2.3
Many thanks for the explanations Christian!
Here are some more clarification on my setup.
Indeed, I have done a "discover" for my NAS, and I have a node configured.
The other element is that the NAS is generally off, which means if open-iscsci
would try to communicate with the NAS at startup, th
And the graph WITH iscsi.
(EDIT from previous post, some words are missing)
In 16.04 the command
$ sudo iscsiadm -m node -l
was returning to the shell prompt.
In 20.04, the same command does NOT return to the shell prompt, but the
mount seems to work anyway.
** Attachment added: "Startup Grap
** Attachment added: "systemd-analyze-blame.txt"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1882986/+attachment/5384181/+files/systemd-analyze-blame.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
** Attachment added: "systemd-analyze-critical-chain.txt"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1882986/+attachment/5384180/+files/systemd-analyze-critical-chain.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
And the 4 files as expected with self-explanatory names.
** Attachment added: "systemd-analyze-dump.txt"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1882986/+attachment/5384175/+files/systemd-analyze-dump.txt
--
You received this bug notification because you are a member of Ubu
** Attachment added: "systemctl-status-iscsi-3-services.txt"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1882986/+attachment/5384182/+files/systemctl-status-iscsi-3-services.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I am not sure this helps, because apparently "critical-chain" starts
only AFTER graphical.target... and we wanted to know why
graphical.target itself is delayed.
Also you asked a very relevant question:
"How could iscsi services know whether the user actually needs the
mounts or not?"
My answe
Dear Rafael,
I would leave it as it is.
It is not yet clear for me why this is delaying the whole startup, but I
agree with you, it is probably not worth investigating more time since
the "workaround" is fine and simple.
What is clear is that iscsi needs "network-online", as per the directive
in
(the previous one, as its name said, was isci ENABLED, sorry for the
confusion but you would have corrected with the name!)
** Attachment added: "VM Clean 20.04 startup with iscsi DISABLED"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1882986/+attachment/5384543/+files/startup_noi
I did some more investigations anyway, and discovered:
"It is not a bug, it is a feature"!
__
Steps to reproduce:
==
- In Virutalbox, start a new test machine
- Install a fresh 20.04 (minimal install is enough, and I did it in my 20GB RAM
disk, it's faster!)
- sud
As explained by Christian on #4, I did further tests:
- Disables only open-iscsi
- To be sure, I moved out of the way what was in /etc/iscsi/nodes which is now
empty
- To be sure, did the same with /etc/iscsi/send-targets
- To be extra sure, even removed those directory
And when I boot my machin
** Attachment added: "iscsid.conf"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1882986/+attachment/5385541/+files/iscsid.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882986
Ti
(Please disconsider the previous post, the "targets database" was
corrupted)
---
Steps to reproduce:
---
- With VirutalBox running on top of Ubuntu Destktop 20.04, create a new Virtual
machine
- Install Ubuntu Desktop 20.04 on the new guest (minimal install is Ok)
Thanks a lot Rafael.
Unlike bug #1877617, I don't have a fix to propose for the regression on
LP: #1755858, sorry!
Disabling services is a workaround for me... but definitely not a fix!
My initial "enhancement" report was a little bit more specific, and not
sure it will be fixed.
iscsi services
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nvidia] Automa
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Public bug reported:
In to the bug reported here:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1664067
indicator-datetime was apparently aware of the locale depending of the
options chosen.
Now it does not at all apply the locale, whatever the option chosen.
Environment:
U
Hi, I will provide the confirmation (or not!) that this is a complete
workaround, along with the same confirmation on the "upstream" ticket I
opened for that bug: https://bugs.freedesktop.org/show_bug.cgi?id=106422
Same as Kevin, the hardware is not mine, and I have to wait to have
direct access t
Ok, I originally posted on
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731784
1731784 has been marked as duplicate as this one after I did an
"upstream" report (https://bugs.freedesktop.org/show_bug.cgi?id=106422)
and Intel engineers investigated to attach it to a "TV-Out" issue with
thi
Done with ticket:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1774845
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682921
Title:
sluggish system, kernel errors on Inspiron 1525
T
Just a short comment, I did the bug report without the workaround, hence
the linux boot command line is "standard" as a fresh install, without
the parameter "video=SVIDEO-1:d" that workarounds the bug.
I imagine it is more significant that way!
Should you need a report with the workaround include
Public bug reported:
This is the automated ubuntu-bug linux
as requested per ticket
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682921
>From the original bug where I posted (1731784) and the ticket I opened
upstream, this has been identified by Intel engineers as a regression in
the DR
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148262/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774845
Title:
TV-out
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148263/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774845
apport information
** Tags added: apport-collected
** Description changed:
Booting into a installed environment takes a few more seconds than
normal.
WORKAROUND: Use kernel parameter:
video=SVIDEO-1:d
+ ---
+ ApportVersion: 2.20.9-0ubuntu7.1
+ Architecture: amd64
+ AudioDevicesInUse:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148273/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774845
Ti
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148268/+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/
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148272/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774845
Title:
TV
apport-collect done!
Do you need any other info before I start over with a clean install
(including workaround)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774845
Title:
TV-out timeouts in i965
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148271/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774845
Titl
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148269/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/177
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148264/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774845
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148266/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774845
Title:
TV-o
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148270/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774845
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148267/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774845
About the "bug description", you wrote:
"Booting into a installed environment takes a few more seconds than normal."
It is not "a few more seconds"... but rather "a few more minutes"!
Each timeout is about 10 seconds according to dmesg, and there are about
a dozen or more. So it takes at least 2
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1774845/+attachment/5148265/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774845
Title:
TV-o
Hi Christopher,
1) Ok
2) I have tried kernel 4.17.0-994-generic, downloading it from the provided
link, same result!
For the exact measure of the "damage", a dmesg with the workaround displays
messages from 0.00 to 60.0 sec. With the "bug" it goes up to 266 seconds, which
means 3 minutes and 2
Dear Christopher,
as I posted "upstream"
(https://bugs.freedesktop.org/show_bug.cgi?id=93782), both
- Latest ubuntu drm-tip kernel (as of June 3rd)
- applying the patch suggested C#12 of the upstream post (on the source I
already had of 4.17 rc3 drm-tip)
were NOT successful fixing the bug.
If
Public bug reported:
Fresh install 18.04 + ubuntu-unity-desktop
unity-control-center crashes when trying to setup "Desktop Sharing"
Message (when launched from a terminal)
(unity-control-center:10876): GLib-GIO-ERROR **: 17:49:24.747: Settings
schema 'org.gnome.Vino' does not contain a key name
*** This bug is a duplicate of bug 1741027 ***
https://bugs.launchpad.net/bugs/1741027
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1775423/+attachment/5149413/+files/ProcEnviron.txt
** This bug has been marked a duplicate of bug 1741027
[F
*** This bug is a duplicate of bug 1741027 ***
https://bugs.launchpad.net/bugs/1741027
apport information
** Tags added: apport-collected
** Description changed:
Fresh install 18.04 + ubuntu-unity-desktop
unity-control-center crashes when trying to setup "Desktop Sharing"
Messag
*** This bug is a duplicate of bug 1741027 ***
https://bugs.launchpad.net/bugs/1741027
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1775423/+attachment/5149412/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because
1 - 100 of 158 matches
Mail list logo
