Public bug reported:
Hello,
Since upgrading (fresh reinstall) to 22.04, I have had issues with Totem
crashing.
I have not been able to pin down when it works and when it doesn't, as
playing the same videos seems to work sometimes and not work others.
After it crashes, trying to open it again nor
(And Firefox gave me a notification about hitting version 100, so it
presumably did update)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1972545
Title:
Ubu
** Attachment added: "As expected, closing and reopening Firefox makes it work
as expected"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+attachment/5587903/+files/Screenshot%20from%202022-05-09%2013-44-45.png
--
You received this bug notification
** Attachment added: "Screenshot of the dock"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+attachment/5587901/+files/Screenshot%20from%202022-05-09%2013-32-20.png
--
You received this bug notification because you are a member of Desktop
Packages, w
Public bug reported:
I am using the Firefox Snap on a fresh install of 22.04 (using defaults,
as far as I know).
Normally, Firefox shows an indicator in the Dock showing that it is
running (the orange dot) and gives the ability to choose between open
windows.
At the moment, I have Firefox window
** Attachment added: "Headset back on, output has gone back to the headset but
microphone has not"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970185/+attachment/5583423/+files/Screenshot%20from%202022-04-25%2009-43-46.png
--
You received this bug notification becaus
** Attachment added: "Headset turned off, input and output revert to internal
ones"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970185/+attachment/5583422/+files/Screenshot%20from%202022-04-25%2009-43-27.png
--
You received this bug notification because you are a mem
Public bug reported:
In Gnome's sound settings, it takes a sensible approach for my Bluetooth
headset speaker:
1) I set it as my preferred audio Output Device
2) I turn the headset off and it disappears, reverting to the built in speakers
3) I turn the headset on again and it switches back to usi
Ah interesting, thanks Daniel. I did not realise Raspberry Pis were
doing Wayland by default.
Yes, it works as expected in xorg, but not in Wayland.
It's a Raspberry Pi 4 Model B - 8GB, in case that was not clear from my
logs.
--
You received this bug notification because you are a member of De
Public bug reported:
I am running Hirsuite on a Raspberry Pi 4. My main keyboard for this
(TV) machine is a wireless Logitech K400r combined keyboard/trackpad.
When I first installed, I do not think there were any issues with the
keyboard. When I did updates, my keyboard half-stopped working. It
** Attachment added: "Playback on 200% screen"
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+attachment/5403153/+files/Screenshot%20from%202020-08-20%2015-54-40.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem
** Attachment added: "Display Settings screenshot 2"
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+attachment/5403155/+files/Screenshot%20from%202020-08-20%2015-56-01.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Attachment added: "Display Settings screenshot 1"
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+attachment/5403154/+files/Screenshot%20from%202020-08-20%2015-55-54.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Public bug reported:
I am using Ubuntu Focal Fossa with Wayland and two screens.
Display 1 is a 3840 x 2160 screen at 200% scaling
Display 2 is a 1920x1200 at 100% scaling
Fractional Scaling is on. Display 2 is my Primary Display.
When I play a video on Display 2, everything works as expected.
Hello all,
Apologies, I missed these recent messages.
For background, the error UnicodeDecodeError just means that a non-ASCII
character is hitting a piece of code that was not designed to handle it.
That is not surprising -- prior to the 0.8 series, very little of the
code was designed for non-A
Public bug reported:
When using Google Meet in Firefox (Ubuntu 20.04, 76.0.1 (64-bit)), for
the first 5-10 seconds of the meeting, nobody can hear anything that I
am saying. After that, I have no issues. I also have no issues joining
with Chromium.
The sound indicator on my end (the little green
Is this related to: https://bugzilla.mozilla.org/show_bug.cgi?id=1530370
? If so, in the duplicate bug
(https://bugzilla.mozilla.org/show_bug.cgi?id=1619850 ) somebody said
"This is a 2020 goal."
** Package changed: evolution (Ubuntu) => firefox (Ubuntu)
** Bug watch added: Mozilla Bugzilla #1530
All,
This should be fixed in 0.8.00, which has now been released. This is the
first 0.8-series release, so expect issues and test it out on data you
can afford to lose (if it comes to that).
I have now packaged up this version as a snap. You can install it by typing:
snap install duplicity --clas
All, to clarify the current position, this is fixed in the 0.8 series,
but I set out the steps to test the fix in comment #15 and was waiting
on testing feedback before merging the patch back into the 0.7 series.
Nobody gave me any testing feedback. It is therefore not yet fixed in
the 0.7 series.
@Sebastian, Kenneth is planning to release a 0.8 version very soon.
Note that I have wound the Python 3 blueprint completion back a step, as
I have realised that there are some backend dependencies (e.g. pyrax)
that do not work on Python 3. I believe deja dup only uses a subset of
the backends any
** Attachment added: "Screenshot with external monitor connected. Only whole
number scaling available."
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1826550/+attachment/5259303/+files/Screenshot%20from%202019-04-26%2014-32-06.png
--
You received this bug notification b
Public bug reported:
Using 19.04 disco with Wayland.
I have a HiDPI laptop screen (XPS13) and a normal DPI external monitor.
I have enabled the experimental fractional scaling support.
When no external monitor is connected, the fractional scaling options
are displayed as expected. When the exte
Public bug reported:
Using 19.04 disco with Wayland.
I have a HiDPI laptop screen (XPS13) and a normal DPI external monitor.
I have the laptop screen set to 200% and the external screen set to
100%.
If I set the primary display to the built-in display but have the
display settings window open on
Public bug reported:
Running 19.04 Disco with Wayland
Version 64ubuntu7
I have a HiDPI laptop screen (XPS13) and a normal DPI external monitor.
I have the laptop screen set to 200% and the external screen set to
100%.
When running the display solely on my built-in monitor, the dock is
correctly
The 0.8-series was affected by this (as I mentioned above, fixing the
underlying problem avoids this error and a number of these have been
fixed, so it is harder to trigger).
I have just proposed a fix for it be merged into the 0.8-series:
https://code.launchpad.net/~aaron-whitehouse/duplicity/08
Marking this as Fix Committed, as we have Python 3 compatible code in
0.8-series with all tests also being run against this environment. We
have not yet put out a 0.8 release, though.
See https://blueprints.launchpad.net/duplicity/+spec/python3
** Changed in: duplicity
Importance: Undecided =
797928 for proposing a
patch for this, which I had overlooked.
I have applied this in the branch here: lp:~aaron-
whitehouse/duplicity/07-uexc-fix
It would be helpful if you can please test to see if this fixes your problem as
follows:
1. Create a new destination directory to test with.
2. Test that dupli
** Summary changed:
- backup fails with UnicodeDecodeError
+ backup fails with UnicodeDecodeError in uexc function
** Summary changed:
- backup fails with UnicodeDecodeError in uexc function
+ Duplicity fails with UnicodeDecodeError in uexc function
--
You received this bug notification becaus
** Also affects: gphoto2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1731341
Title:
Fujifilm X-T10 regression on 17.10: "Unabl
Public bug reported:
I have a Fujifilm X-T10. This worked perfectly in Shotwell in 17.04. Since
upgrading to 17.10, I receive an error whenever I try to import photos:
Unable to fetch previews from the camera: Unspecified error (-1)
lsusb gives:
Bus 001 Device 010: ID 04cb:02c8 Fuji Photo F
Have you tried to verify your backup or do a new full backup?
> Can someone recommend a better backup software for personal use?
http://lmgtfy.com/?q=personal+backup+software+linux
There is a reason, though, that Deja Dup (which you are already using)
is the default in Ubuntu -- it is a pretty go
Jonathan,
Given the latest version of xfce-settings (4.12.1) was easy to install
and fixed all of my issues (see comment #130 above), it would be
interesting to know whether this also fixed your problem.
Kind regards,
Aaron
--
You received this bug notification because you are a member of Desk
I have an ASUS Z170M-Plus Mobo with an Intel Core i3-6100T, Intel HD 530
graphics and a Samsung TV connected through HDMI, running Mythbuntu
16.04.
I had the issue that when I turned the TV off and then back on again, the TV
would say "No Signal" and I would have to run
$ sudo service lightdm re
*** This bug is a duplicate of bug 1313034 ***
https://bugs.launchpad.net/bugs/1313034
** This bug has been marked a duplicate of bug 1313034
Deja-dup reports it couldn't backup ~/.cache/dconf and ~/.gvfs even though
it's not supposed to try to (also, ~/.dbus)
--
You received this bug no
Public bug reported:
I use a Dell Inspiron 14z with 13.10. I'm pretty sure that at least
vertical scrolling (by moving my finger along the right edge of the
touchpad) used to work, but neither work for me now in 13.10.
My hardware details should be attached.
ProblemType: Bug
DistroRelease: Ubun
Sorry, I meant to say, it would be interesting to know if updating also
solves your problem, Pierre - you may be able to try from a live DVD of
13.04?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.lau
We have recently updated (new clean install) to 13.04 Raring Ringtail
and this appears to have been fixed. I now have a preview when scanning
and have no problems saving PDFs. Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple
Public bug reported:
I have a Dell Insprion 14z (Inspiron 5423) and I'm running 13.04. The
machine has an Intel 4000 HD and Radeon 7550M/7570M/7650M
By default, both graphics cards are powered up, even though only the integrated
Intel is used:
$ sudo cat /sys/kernel/debug/vgaswitcheroo/switch
0:
I just did a clean install of 13.04 Raring Ringtail and this still
occurs (on my first boot, unfortunately!)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1088244
Title:
No Full-Disk
For completeness, a screenshot from after scanning to PDF, though this
matches the screenshot above.
** Attachment added: "PDF Screenshot from 2013-01-03 09:29:20.png"
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1088187/+attachment/3473145/+files/PDF%20Screenshot%20from%202013-0
>From scanning to a PDF:
$ simple-scan --debug
[+0.00s] DEBUG: simple-scan.vala:582: Starting Simple Scan 3.6.0, PID=11751
[+0.00s] DEBUG: Connecting to session manager
[+0.04s] DEBUG: ui.vala:1404: Restoring window to 600x400 pixels
[+0.04s] DEBUG: ui.vala:1409: Restoring window to maximized
[+0.0
** Attachment added: "Screenshot after page scanned"
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1088187/+attachment/3473143/+files/JPEG%20Screenshot%20from%202013-01-03%2009%3A25%3A29.png
--
You received this bug notification because you are a member of Desktop
Packages, which
$ simple-scan --debug
[+0.00s] DEBUG: simple-scan.vala:582: Starting Simple Scan 3.6.0, PID=11198
[+0.00s] DEBUG: Connecting to session manager
[+0.03s] DEBUG: ui.vala:1404: Restoring window to 600x400 pixels
[+0.06s] DEBUG: scanner.vala:1378: sane_init () -> SANE_STATUS_GOOD
[+0.06s] DEBUG: scanne
Description changed so that it no longer says this happens on reboot and
not on a cold start.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1088244
Title:
No Full-Disk Encryption unl
Okay, I just had this happen to me after shutting down, so it seems to
just be random whether it works or not.
** Summary changed:
- No Full-Disk Encryption unlock screen from reboot
+ No Full-Disk Encryption unlock screen on some boots
** Description changed:
- I use Full-Disk Encryption on 12
Public bug reported:
I use Full-Disk Encryption on 12.10. All seems to work fine if I power
the machine on from a full power off - the pretty screen asks for my
disk unlock password and then takes me to the login screen when I enter
it correctly.
If I reboot the computer instead, it shows a compl
Public bug reported:
I have used Simple Scan a lot on other machines etc.
On my new laptop running 12.10, it doesn't really work.
1) When I scan a page, the white blank page disappears so that there is only a
blank grey area there. If I let it scan, nothing changes and only the grey
background
47 matches
Mail list logo
