** Bug watch added: bugzilla.gnome.org/ #670999
https://bugzilla.gnome.org/show_bug.cgi?id=670999
** Changed in: network-manager
Importance: Wishlist => Unknown
** Changed in: network-manager
Status: Confirmed => Unknown
** Changed in: network-manager
Remote watch: GNOME Bug
Very often the users are coming across this common Printing error as
they are not able to locate a Remote Printer at the time of running a
printing process. I have a blog https://printerssupport.co/canon-
printer-not-responding/ along with such Printing solutions which will
help them surely.
--
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
** Changed in: ibus
Status: Fix Released => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1844853
Title:
IBus no longer works in Qt applications after upgrade
Status in
Created attachment 154564
/opt/libreofficedev6.3/program/soffice in version 6.3_6.3.3.0.0
I downloaded the below daily build here :
https://dev-builds.libreoffice.org/daily/libreoffice-6-3/Linux-rpm_deb-
(In reply to Jan-Marek Glogowski from comment #0)
> When OpenJDK tried to enforce stricter class path URL checks without
> previous announcement, things started to break left and right. This included
> failing LibreOffice JUnitTest checks, since the dependency classpath in our
> generated Jars
** Changed in: oem-priority/xenial
Status: Fix Committed => Fix Released
** Changed in: oem-priority/bionic
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in
I have fixed the pdftoraster crash upstream. Note also that there is
still a bug in the implicitclass backend which is currently worked on.
** Changed in: cups-filters (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
On 2019-09-26 18:51, Oryganum wrote:
>> That wiki page you referred to was last edited 11 years ago and is
>> obsolete to a large extent.
>
> Is it possible to contact someone to ask to update this page?
The simple answer to that question is no.
There is a similar page which is somewhat less
In 19.10, with the error state, restarting upower fixes the issue. So if
you've booted without power connected, then connect power and don't see
the charging icon, execute `sudo systemctl restart upower` and see the
charging symbol.
--
You received this bug notification because you are a member
This problem already exist in Ubuntu 18.04.
The Linux Biolinum O font is coming with Libreoffice 6, but in Windows package
Libreoffice comes with the Linux Biolinum G.
And any document can work without the policy rules.
Can you correct this package and add the G version too ?
--
You received
I tried this in a 19.04 live boot from a usb stick and the behavior was
correct: if the system was booted without power, the charging symbol was
not there. Then when I connected the power, the charging symbol
appeared.
Also, when booting 19.04 without power connected, there is only the one
** Attachment added: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1845548/+attachment/5291574/+files/Stacktrace.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1845548
** Attachment added: "StacktraceSource.txt"
https://bugs.launchpad.net/bugs/1845548/+attachment/5291575/+files/StacktraceSource.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
** Attachment added: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1845548/+attachment/5291576/+files/ThreadStacktrace.txt
** Tags added: apport-failed-retrace
** Tags removed: need-amd64-retrace
--
You received this bug notification because you are a member of Desktop
Packages,
StacktraceTop:
raise () from /tmp/apport_sandbox_wdms9auk/lib/x86_64-linux-gnu/libc.so.6
abort () from /tmp/apport_sandbox_wdms9auk/lib/x86_64-linux-gnu/libc.so.6
?? () from /tmp/apport_sandbox_wdms9auk/lib/x86_64-linux-gnu/libc.so.6
?? () from
Public bug reported:
This crashed when attempting to print from firefox
ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: cups-browsed 1.25.6-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Public bug reported:
Occasionally when I plug in my laptop at low (close to shut-down levels,
<10%) battery, the OS becomes unresponsive. The GUI doesn't work,
Ctrl+Alt+T doesn't work, nothing works. This makes it difficult to
collect information about the problem, since I basically have to
** Description changed:
Steps to reproduce:
- - observe touchpad click-drag working normally (i.e. can click touchpad and
drag an icon, or select text in any direction)
+ - observe touchpad click-drag* working normally (i.e. can click touchpad and
drag an icon, or select text in any
The following is the output of `journalctl | grep -i power` that covers
the duration between the reboot command and login times.
** Attachment added: "journal-power-keyword_no-power-connected-on-boot.out"
The only difference in journalctl between when the system boots with
power and without is that when the system boots without power, I see two
journalctl messages:
Sep 26 10:53:27 fenrir dbus-daemon[793]: [system] Activating via systemd:
service name='org.freedesktop.UPower' unit='upower.service'
The following is the output of `journalctl | grep -i power` that covers
the duration between the reboot command and login times.
** Attachment added: "journal-power-keyword_with-power-connected-on-boot.out"
This issue is completely reproducible for me. Digging into the
journalctl logs around when the system is rebooting without power
plugged in, here are some lines that stand out and might be useful:
Note that the system was sent to reboot at 10:53:00
...
Sep 26 10:53:37 fenrir systemd[2088]:
Thank you so much for the quick response!
I switched "Keyboard input method system" to "XIM" as you suggested and
now everything works fine.
However, I have a few questions about it.
>> That wiki page you referred to was last edited 11 years ago and is
obsolete to a large extent.
Is it
One of the patches introduced as a result of this bug (namely, the one
that forces setting of the browser.preferences.instantApply to "false")
appears to have broken at least one Thunderbird extension, CardBook. I
have opened an issue for this: Bug 1151186. It would be great if the
folks
Public bug reported:
Hardware: Lenovo T590
OS: 19.10
When the power is not connected when the laptop boots, and then
connected, the power icon in the top bar does not change to indicate
that the laptop is now charging.
$ upower -d
Device: /org/freedesktop/UPower/devices/line_power_AC
When one uses gstoraster instead of pdftoraster (is used automatically
when Ghostscript is installed) then there does not occur any crash.
** Changed in: cups-filters (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Desktop
I succeeded to reproduce the crash on the command line. For the tests
shown here I am in the source directory of the current cups-filters,
having run "autogen.sh", "./configure", and "make" already.
After downloading the attached PPD file (comment #11) and the attached
PDF file (comment #7) I
** Description changed:
Currently only see this on a machine with NVS-510.
Can reproduce with both 430.26 and 430.50 driver.
Screen resolution was fine before installing nvidia graphic driver.
But it's locked at 800x600 after installing driver and switching to intel
graphic.
Steps:
** Description changed:
Currently only see this on a machine with NVS-510.
Can reproduce with both 430.26 and 430.50 driver.
Screen stuck at CLI console after switching to intel graphic and switching
back to nvidia.
The system still looks running, can access it through ssh or other CLI
** Attachment added: "20190926_111242.jpg"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1845502/+attachment/5291479/+files/20190926_111242.jpg
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Please find test report here:
https://drive.google.com/open?id=1DfY6Tt8jUjL2jkBIhxOIB9fsiohXxTJ_fotvGPHpwVg
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu.
https://bugs.launchpad.net/bugs/1845502
Public bug reported:
Currently only see this on a machine with NVS-510.
Can reproduce with both 430.26 and 430.50 driver.
Screen stuck at CLI console after switching to intel graphic and switching back
to nvidia.
The system still looks running, can access it through ssh or other CLI console.
** Attachment added: "20190926_164510.jpg"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1845501/+attachment/5291478/+files/20190926_164510.jpg
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Please find test report here:
https://drive.google.com/open?id=1DfY6Tt8jUjL2jkBIhxOIB9fsiohXxTJ_fotvGPHpwVg
** Description changed:
- Currently only see this on a machine with NVS-510 currently.
+ Currently only see this on a machine with NVS-510.
Can reproduce with both 430.26 and 430.50
Public bug reported:
Currently only see this on a machine with NVS-510.
Can reproduce with both 430.26 and 430.50 driver.
Screen resolution was fine before installing nvidia graphic driver.
But it's locked at 800x600 after installing driver and switching to intel
graphic.
Steps:
1. Install
I tested an upgrade from Ubuntu 18.10 to Ubuntu 19.04 today with some of
the packages from the DuplicateSignature.txt installed e.g.:
Start-Date: 2019-09-25 17:14:37
Commandline: apt-get install bamfdaemon mime-support
Requested-By: bdmurray (1000)
Install: bamfdaemon:amd64
Public bug reported:
When selecting multiple files using CTRL + click, I noticed that I could
NOT undo a selection by CRTL + clicking on it again.
Inside the Nautilus file browser, however, this issue is NOT present.
>From my testing, the issue is only present on the desktop.
PS: I filed this
(re-opening and tagging as blocked by ff for our tracking script)
** Changed in: pango1.0 (Ubuntu)
Status: Won't Fix => Triaged
** Summary changed:
- [ffe] Update to 1.44.6
+ Don't update to 1.44.6 this cycle
--
You received this bug notification because you are a member of Desktop
*** This bug is a duplicate of bug 1494230 ***
https://bugs.launchpad.net/bugs/1494230
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
** Package changed: snapd (Ubuntu) => gnome-software (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1686631
Title:
[Ubuntu-gnome] if an app is uninstalled and has a
You have been subscribed to a public bug:
STEPS:
1. Install ubuntu-gnome 17.04
2. update it
3. click on Activities
4. type krita, blender
EXPECTED:
I expect to see listed under the gnome-software the option to install one of
the apps
ACTUAL:
I get a message of No Results
This only happens if
I've tested with my old profile and the safe-mode, same problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1845422
Title:
Firefox don't start
Status in firefox package in
Hi, as I say, I've solved the problem with a new profile.
But if I retry firefox -P and choose the profile default I've
immediately the message "Firefox is already running but don't respond".
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1845471
** Tags added: iso-testing
--
You received this bug notification because you are a member of Desktop
Packages,
** Also affects: gnome-control-center (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: gnome-control-center (Ubuntu Eoan)
Importance: Low
Status: Confirmed
** Also affects: gnome-control-center (Ubuntu Bionic)
Importance: Undecided
Status: New
**
Public bug reported:
During ISO testing (live-session) I found that I was unable to start
gnome-calendar.
Steps to reproduce:
Display Activities Overview, search for and select "Calendar"
Expected outcome:
Application starts
Actual outcome:
Application doesn't start
Workaround:
Pin
Thanks for the report VinsS.
Can you reliably reproduce the problem, across reboots ?
Does it start if you run it in safe mode (`firefox -safe-mode`) ?
** Changed in: firefox (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
** Description changed:
- Reproducible crash or freezing of application during ISO testing.
+ Reproducible crash (tested on Ubuntu and Xubuntu) or freezing of
+ application during ISO testing of a live-session.
Application will crash if there is an attempt to close it or scroll
- through
I tested the package from silo 3814 in an eoan VM where I can observe
the hang very reliably, and the problem appears to be gone (rebooted the
machine a dozen of times or so without an issue).
+1 from me (but as pointed out already the changelog entry needs to be
fixed, it doesn't mention the
** Changed in: mesa
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1222602
Title:
[regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class
@Gunnar Hjalmarsson (gunnarhj) :
https://bugzilla.kernel.org/show_bug.cgi?id=204779
** Bug watch added: Linux Kernel Bug Tracker #204779
https://bugzilla.kernel.org/show_bug.cgi?id=204779
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Kernel needs this patch for maxim98090 to work on cyan and some baytrail
chromebooks:
https://github.com/torvalds/linux/commit/d5e120422db8808e1c8b1507900ca393a877c58f
As it didn't make to 5.3 on time, would be nice if it were backported by
ubuntu devs
--
You received this bug notification
After creating a new profile with firefox -P, now I can launch firefox
with this new profile.
Of course without my markups and extensions.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Public bug reported:
front green jack not working
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 5.3.0-050300-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
AudioDevicesInUse:
** Changed in: xserver-xorg-video-intel (Fedora)
Status: Incomplete => Unknown
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/issues #1680
https://gitlab.freedesktop.org/mesa/mesa/issues/1680
--
You received this bug notification because you are a member of Desktop
Packages,
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.
You can subscribe and participate further through the new bug through
this link to our GitLab instance:
57 matches
Mail list logo
