For me the nightly build does not work either.
I am running LibreOffice Version: 6.4.6.2
Build ID: 1:6.4.6-0ubuntu0.20.04.1
CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3;
Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB
Calc: threaded
on aLenovo t410 laptop runnng fully
Thanks Daniel.
If you take a look at
https://bugs.documentfoundation.org/show_bug.cgi?id=137142#c5
you will see I downloaded and installed in parallel Libre Office 7. That was
on Sep 30
Sadly, it made no difference.
I have just tried running 7 again (but not a fresh download) and the problem
I would just like to record that the recent Ubuntu mutter fix referenced here
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440
has NOT fixed the Libre Office Print Dialogue box problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is
I already did:-
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1897632
but it has been marked as a duplicate of
https://bugs.launchpad.net/bugs/1883886
Also there is a Libre Office relevant bug
https://bugs.documentfoundation.org/show_bug.cgi?id=127782
** Bug watch added: Document
I would just like to report that the fix to the mutter bug
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440
has NOT corrected the Libre Office Print Dialogue issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Just reporting this fix has NOT fixed the Libre Office Print Dialoge Box
issue mentioned in comment #86
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892440
Title:
Shell text with
I have raised a bug with LibreOffice which I believe may be related.
https://bugs.documentfoundation.org/show_bug.cgi?id=137142
To summarise, with a scaling factor of 1.25 and GNOME Desktop
Environment Universal Access accessibility Large Print set to on I am
unable to see fully the LibreOffice
*** This bug is a duplicate of bug 1883886 ***
https://bugs.launchpad.net/bugs/1883886
okies, tx Helen
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1897632
Title:
Can't
Just spotted
https://bugs.launchpad.net/df-libreoffice/+bug/1883886
Could this be a duplicate?
How exactly do I fix?
** Tags added: a11y libreoffice writer
** Description changed:
Description: Ubuntu 20.04.1 LTS
Release: 20.04
-
- I am unsure whether the problem I am suffering is
** Attachment added: "With Large Text OFF"
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1897632/+attachment/5415039/+files/Screenshot%20from%202020-09-28%2021-06-32.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Attachment added: "With Large Text ON"
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1897632/+attachment/5415038/+files/Screenshot%20from%202020-09-28%2020-51-04.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Public bug reported:
Description:Ubuntu 20.04.1 LTS
Release:20.04
I am unsure whether the problem I am suffering is related to
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440
In LibreOffice Version: 6.4.6.2 Build ID: 1:6.4.6-0ubuntu0.20.04.1 when
I try to print a
I have low vision and I thought my vision was just deteriorating!
I happened to boot into 18.04 and even after updating it I noticed my fonts in
18.04 were much better on the same hardware. It is most noticeable in the
pull-down panels.
In 20.04, sure enough if I change the scaling factor from
Bug reported as advised
https://github.com/neffo/bing-wallpaper-gnome-extension/issues/70#issuecomment-624599291
** Bug watch added: github.com/neffo/bing-wallpaper-gnome-extension/issues #70
https://github.com/neffo/bing-wallpaper-gnome-extension/issues/70
--
You received this bug
Reinstalled 'bingwallpa...@ineffable-gmail.com' and as expected on a
reboot an "Ubuntu has experienced an internal error" box was once more
generated.
Ran ubuntu-bug _usr_bin_gnome-shell.1000.crash obtained from /var/crash
and all it did was produce another/same(?) "Ubuntu has experienced an
As requested, all extensions quoted uninstalled and all fine. Still
fine after a number of reboots.
Decided to re-install each extension one by one.
Tried 'bingwallpa...@ineffable-gmail.com' first and once more a similar crash
and as before system was still usable. Uninstalled once more and
Public bug reported:
Had a few gnome-shell problems since 20.04 install.
Usually, just did the auto send thing, but this time thought it best to do a
manual report.
Not much I can add though.
I do see things like these in the reports from time to time
Invalid core dump: BFD:
Happened again.
Bug did not seem to submit report once more.
Screenshot as per comment #2
Report was produced which I managed to see the details but sending report did
not return a bug ID.
See this from terminal where I carried out action 1a in comment #3.
Still no bug ID.
Moeez
In future, whenever you get a bug and you know the name of package causing the
problem use this command inside a terminal session making sure you first have
an internet conection:-
ubuntu-bug "packagename"
So in my case I ran "ubuntu-bug gnome-shell"
and it then does the business, goes
Moeez
I am sure it would help the bug hunters if you cross-referenced your reported
bug ID in here. The more data they have the better.
So far,I have hadno related issues and no replication since performing
sudo apt update
sudo apt full-upgrade
Shutdown
Rebooted
But I suppose it might happen
/var/crash has now been emptied
device shutdown and rebooted
no problems reported at boot
/var/crash remains empty
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1863400
Title:
Performed
sudo apt update
sudo apt full-upgrade
Shutdown
Rebooted
Performed
sudo ubuntu-bug /var/crash/_usr_bin_gnome-shell.121.crash
Report produced and sent.
Went to https://errors.ubuntu.com/user/ID where the ID was the one obtained
from sudo more /var/lib/whoopsie/whoopsie-id
Then same as
Here you go
https://errors.ubuntu.com/oops/14394820-5158-11ea-a66d-fa163ee63de6
Thank You.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1863400
Title:
gnome-shell reports
Complied with comment #6 and step 2 in comment #3.
A web page is produced with all the bugs I have raised from this device, and
yes the latest gnome one is there. But clicking on it takes me to webpage
which says I have not got permission to see it and asks me to complete a form,
which I have
Cant find bug id - but was uploade 07:35 UTC according to /var/crash
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1863400
Title:
gnome-shell reports problem on boot
Status in
Step 1 worked
" sudo ubuntu-bug /var/crash/_usr_bin_gnome-shell.121.crash"
and report sent - trying to find bug id.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1863400
Title:
** Description changed:
Problem reported at boot but does not seem to collect data and send, just
does nothing.
+ See attached screenshot of window.
Still able to use laptop.
This file exists in /var/crash
-rw-r- 1 gdm whoopsie 21900809 Feb 14 22:01
_usr_bin_gnome-shell.121.crash
Public bug reported:
Problem reported at boot but does not seem to collect data and send, just does
nothing.
Still able to use laptop.
This file exists in /var/crash
-rw-r- 1 gdm whoopsie 21900809 Feb 14 22:01 _usr_bin_gnome-shell.121.crash
The time of this file must have been at last
I forgot all about this bug until the tag of cscc was added.
As reported previously the machine is now running 18.04.2 LTS fairly
well. All updates including kernels have been done,
Graphics now state Intel® Ironlake Mobile and the /etc/default/grub file
contains the line
See my recent comment against the bug.
On Mon, 22 Oct 2018 at 07:15, Daniel van Vugt
wrote:
> Dave,
>
> Please run this command to send us more information about the machine:
>
> apport-collect 1766974
>
> ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
>
> ** Changed in:
I suspect your recent request of me to run apport-collect 1766974 was an error
and should have been directed at Michael Odumosu (michael5757) instead.
In any case, I have since the bug(s) freshly installed 18.04 LTS and have no
bugs at all now. I am unable to replicate.
--
You received this
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1764087/+attachment/5203951/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "LightdmUsersConfig.txt"
https://bugs.launchpad.net/bugs/1764087/+attachment/5203952/+files/LightdmUsersConfig.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1764087/+attachment/5203953/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
I need to update this bug. Since raising the bug, the machine has been updated
to Ubuntu 18.04 but still has some issues.
Please cross reference with bug https://bugs.launchpad.net/bugs/1766974
The grub file remains the same:-
GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset"
which results in lots of
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1764087/+attachment/5203954/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1766974/+attachment/5203880/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1766974/+attachment/5203879/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1766974/+attachment/5203883/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Tags added: apport-collected bionic ubuntu
** Description changed:
There are very many bugs reported recently against xorg with a commmon
theme
the following are just 2 examples from the various xorg logs
(EE) /dev/dri/card0: failed to set DRM interface
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1766974/+attachment/5203886/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1766974/+attachment/5203884/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1766974/+attachment/5203887/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "UnitySupportTest.txt"
https://bugs.launchpad.net/bugs/1766974/+attachment/5203888/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1766974/+attachment/5203877/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "MonitorsUser.xml.txt"
https://bugs.launchpad.net/bugs/1766974/+attachment/5203881/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1766974/+attachment/5203885/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1766974/+attachment/5203882/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1766974/+attachment/5203878/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
This is happening to me several times now on a daily basis.
Each time I submit the crash report and each time within the report it
says a duplicate of this bug report. How can I help resolve it.
New install of 18.04 from about a month ago - all updates and upgrades
installed.
--
You received
** Description changed:
Scanner is combined with all-in-one device CANON TS8000 series.
Scangearmp is able to find scanner and scan the document.
Both simple-scan and xsane fails to detect scanner.
apt-cache policy simple-scan
simple-scan:
- Installed: 3.28.0-0ubuntu1
-
Public bug reported:
Scanner is combined with all-in-one device CANON TS8000 series.
Scangearmp is able to find scanner and scan the document.
Both simple-scan and xsane fails to detect scanner.
apt-cache policy simple-scan
simple-scan:
Installed: 3.28.0-0ubuntu1
Candidate: 3.28.0-0ubuntu1
I can confirm this is happening also in my recently installed 18.04 on
Bell Latitude E6430
Using the logs tool I can see this
11:16:20 wpa_supplicant: dbus: fill_dict_with_properties
dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter
failed
11:16:16 gdm-x-session:
Dissapointed by the lack of progress on this bug, I decided to research and
experiment more to a point where I am now happy with the way my boot up and
shut down processes are working to my satisfaction, albeit not perfect.
You will notice I also raised the bug direct on xorg bug service
Cross reference now to a lightdm bug which has been raised as a consequence of
https://bugs.freedesktop.org/show_bug.cgi?id=106407
saying it is not a xorg bug
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
** Bug watch added: freedesktop.org Bugzilla #106407
https://bugs.freedesktop.org/show_bug.cgi?id=106407
** Also affects: xorg-server via
https://bugs.freedesktop.org/show_bug.cgi?id=106407
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
At a terminal screen have you tried entering the command?
sudo service network-manager restart
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1768661
Title:
can't make WIFI work
Many bugs are now accumulating with this and similar issues surrounding Xorg.
This is just one example
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087
There are others. Some are related to Lenovo laptops but not all.
Shame that 18.04 LTS has been allowed to be released without this
Many bugs are now accumulating with this and similar issues surrounding Xorg.
This is just one example
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087
There are others. Some are related to Lenovo laptops but not all.
Shame that 18.04 LTS has been allowed to be released without this
Many bugs are now accumulating with this and similar issues surrounding Xorg.
This is just one example
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087
There are others. Some are related to Lenovo laptops but not all.
Shame that 18.04 LTS has been allowed to be released without this
Many bugs are now accumulating with this and similar issues surrounding Xorg.
This is just one example
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087
There are others. Some are related to Lenovo laptops but not all.
Shame that 18.04 LTS has been allowed to be released without this
Public bug reported:
There are very many bugs reported recently against xorg with a commmon
theme
the following are just 2 examples from the various xorg logs
(EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
(EE) intel(0): [drm] failed to set drm interface
similar to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1766638
Title:
graphical
Status in xorg package in Ubuntu:
poss duplicate of
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1766886
Title:
xorg
Status in xorg package in Ubuntu:
when your wifi fails rather than reboot you might find issuing this
command in a terminal useful
sudo service network-manager restart
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
Needs cross-referencing to this bug
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1766307
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1764087
Title:
Wrongly boots into low
Appears to be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087 which has
not yet been confirmed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1766307
Title:
Hello Chris,
Writing to you direct rather than through the bug - hope you don't mind.
I too had my first failure today using the new kernel, manifesting itself
in the same way.
It's getting a bit tiresome now and I have little faith in it being
corrected. I have spent quite a bit of time
Now this is interesting!
As part Ubuntu updates the kernel was updated on 23rd April 2018 to
4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64
x86_64 x86_64 GNU/Linux
On 3 consecutive occasions no the laptop has booted fine!
I decided to look around /ver/log and
You could well be right Chris that
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764445 raise one
day later appears to be having the same effect, although the ubuntu
version, and the architecture is different.
--
You received this bug notification because you are a member of Desktop
Thanks for the workaround to make wifi work - that could come in useful.
I'm unsure whether your display info is relevant or not. As far as I am
aware I only have one graphics controller/card/GPU integrated into the
Processor - Intel® Core™ i5 CPU M 520 @ 2.40GHz × 4 and that is Intel®
Ironlake
I can see warnings and errors, but have no idea what to do to fix.
** Attachment added: "output from various commands to grab info during crash"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087/+attachment/5124884/+files/myproblem.txt
--
You received this bug notification because
Public bug reported:
Description:Ubuntu 16.04.4 LTS
Release:16.04
Lenovo T410 with VGA compatible controller [0300]: Intel Corporation
Core Processor Integrated Graphics Controller [8086:0046] (rev 02)
Booting from latest kernel ThinkPad-T410 4.13.0-38-generic
#43~16.04.1-Ubuntu SMP
experimental packages.
If I can help further then I will try.
DaveG
On 15 October 2016 at 13:01, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Dave Goldsbrough, it will help immensely if you filed a new report with
> Ubuntu via a terminal:
> ubuntu-bug libsane
>
At the time of writing this, these 3 packages need to be downloaded and
installed.
libsane-common_1.0.26~git20151121-1_all.deb
libsane_1.0.26~git20151121-1_amd64.deb
libjpeg62-turbo_1.5.1-1_amd64.deb
The first two packages can be found in the Debian experimental libs at
this link
I did similar to comment #5 but what follows is an updated package list
to install:-
At the time of writing this, these 3 packages need to be downloaded and
installed.
libsane-common_1.0.26~git20151121-1_all.deb
libsane_1.0.26~git20151121-1_amd64.deb
libjpeg62-turbo_1.5.1-1_amd64.deb
The first
76 matches
Mail list logo
