I don't know why exactly, but I t seems to work again after I installed
telepathy-salut_0.8.1-5ubuntu1_amd64.deb from xenial. This package does
not exist in 20.04?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in Ubuntu.
Ping - how can I help track down this problem? I need telepathy-salut to
work. This package seems to have been removed - but is replaced with
what?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in Ubuntu.
BTW, I purged/reinstalled empathy. Did not help.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/1888399
Title:
After Update->20.04, Empathy/Salut stops working
To manage
Is there anything I can post here to fix this bug? What else information
do you need?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/1888399
Title:
After Update->20.04,
Public bug reported:
It seems that after the update from LTS 18.04 to LTS 20.04, Empathy/Salut
stopped working, and I can't add an Salut account any more.
After each boot, Empathy pops up, I should enter credentials (see screenshot),
but fields are disabled.
I don't know what to install else.
** Attachment added: "screenshot Empathy accounts"
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1888399/+attachment/5394627/+files/accounts.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in Ubuntu.
Here the credential fields are disabled
** Attachment added: "screenshot credentials dialog"
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1888399/+attachment/5394628/+files/Bildschirmfoto%20vom%202020-07-21%2015-26-28.png
--
You received this bug notification because you are a
Exactly:
# lpstat -e
ECOSYS-P6026cdn
Kyocera_ECOSYS_P6026cdn
# lpstat -v
Device for ECOSYS-P6026cdn: socket://192.168.4.2
That makes sense to me - as I could swear that I really printed on a
printer, and later (maybe after rebooting, the next day etc) I try to
print on the same one, and it
First, here the new attrs.txt
** Attachment added: "attrs.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+attachment/5248523/+files/attrs.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
*** This bug is a duplicate of bug 1812683 ***
https://bugs.launchpad.net/bugs/1812683
This is funny, yes. "LANG=C rhythmbox" works. Deactivated the alternative
toolbar then, and it worked again.
Thanks, this is a dupe.
** This bug has been marked a duplicate of bug 1812683
rhythmbox
I deleted all printers and waited for CUPS / driverless to find them again.
Here a few CLI outputs (which are small enough so I dare to spost them inline )
$ ls -1 /etc/cups/ppd/
Kyocera_ECOSYS_P6026cdn.ppd
Kyocera-ECOSYS-P6026cdn.ppd
Kyocera_ECOSYS_P6026cdn.ppd.O
Kyocera-ECOSYS-P6026cdn.ppd.O
$
Public bug reported:
I hope this is no dupe.
Since I opened a flac file per doubleclick on my desktop with Rhythmbox, it
crashes everytime right after the start, even when started without parameters.
I just started a gdb session and ran rhythmbox, maybe this in fo helps a bit.
Please tell me
Second file. The printer is added automatically twice. Maybe this is
because the printer has a print server, which exports the printer again
and announces it to the network? KM15881D.local is the network name of
the printer.
** Attachment added: "autogenerated 2. ppd file"
This file is named .0 because I have the printer installed with a custom
ppd file (from kyocera) manually - with the same name, so I think cups
adds the .0 automatically.
** Attachment added: "IPP PPD file"
one shouldn't make promises. Follows ASAP. Give me a few days.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1813825
Title:
"driverless" printer workflow has bad
I created a test setup on a fresh Ubuntu 18.04
sudo mkdir /m /mnt/m /m/doc
sudo touch /m/doc/test.txt
sudo apt install nfs-kernel-server
sudo echo "/m 0.0.0.0/24 (rw)" >> /etc/exports
sudo systemctl restart nfs-kernel-server
There should be no error.
sudo mount -t nfs
First small thing: stopping cups-browsed dowsn't change anything. Even when
stopped, deleting a driverless printer lets it popup again after a few seconds.
Rest tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Ok; I never used gdb before, just visual debuggers.
I'm not sure this is not a blind alley. The "gtk_container_add warning" is not
reproducible and has IMHO nothing to do with this bug(s) (just IMHO).
As far as I understood, "b g_log" sets a breakpoint at the g_log() function,
right?
Just too
** Attachment added: "cups_error_log"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+attachment/5234066/+files/cups_error_log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in
I'm sorry to write "more than" one problems into one bug, but from a users POV
they are all the same - seen as "usability" bug. If you tell mo more how I can
help, I can also file separate ones if this is needed. But to gather
information, maybe it's best to leave it ATM as one?
Logs attached,
Public bug reported:
Hi,
since Ubuntu uses IPP ("driverless") printing, I have a bad time using
printers. I don't know exactly which package this bug belongs to, I think it is
gnome-control-center.
I have a Kyocera EcosysP6026cdn network printer, which provides a PPD
file by the manufacturer.
Additionally, since "driverless" printing, I always have a printer named
"print" in my printing dialog, which I can't print to, and can't delete
neither. Print jobs are denied at any time there.
** Attachment added: "GNOME printing dialog"
I recently installed Debian 9 with GNOME, it worked perfectly there.
Upgraded to testing, keeped working. I don't know why Ubuntu is broken
here, maybe just check the patch diff to debian. Must be there
somewhere?
Again - how can I help here further?
--
You received this bug notification
Public bug reported:
I just upgraded to Ubuntu 17.10 (hooray, GNOME!). But there are some
quirks. Under Unity/Ubuntu 17.04 my built-in Touchpad worked flawlessly
- especially the "natural scrolling" mode was working well. As I saw
under Ubuntu Gnome 17.04, the corresponding setting in
Public bug reported:
I for the first time installed a snap package via gnome-software, and
was asked to init the snap system by entering my credentials/creating an
account. After doing that, a Gnome dialog popped up where I should enter
my password - I am in Austria and using Ubuntu GNOME in
Additional info: the NFS share is mounted using /etc/fstab - so it
should be mounted and available long way before GNOME/Unity/Nautilus
starts
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
Public bug reported:
Nautilus
I have a NFS share where many Ubuntu desktops share the same remote folder as
Documents (German "Dokumente") and Pictures (German "Bilder") folders. This
works perfectly, only Nautilus refuses to show the "Dokumente" folder in its
left side navigation bar. One of
This bug is still present in 16.04.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1035067
Title:
Shotwell doesn't respect 24-hour clock
To manage notifications about this bug
Oh. My fault.
I had installed ADA/GNAT/GPS in /usr/local. This includes it's own GTK version,
which scrambled mine. Deleting it - all back to normal.
** Package changed: gtk+3.0 (Ubuntu) = ubuntu
** Changed in: ubuntu
Status: New = Invalid
--
You received this bug notification because
29 matches
Mail list logo
