[Bug 1888399] Re: After Update->20.04, Empathy/Salut stops working
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. https://bugs.launchpad.net/bugs/1888399 Title: After Update->20.04, Empathy/Salut stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1888399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1888399] Re: After Update->20.04, Empathy/Salut stops working
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. https://bugs.launchpad.net/bugs/1888399 Title: After Update->20.04, Empathy/Salut stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1888399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1888399] Re: After Update->20.04, Empathy/Salut stops working
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1888399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1888399] Re: After Update->20.04, Empathy/Salut stops working
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, Empathy/Salut stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1888399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1888399] [NEW] After Update->20.04, Empathy/Salut stops working
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. At least it is a regression bug as Empathy WITH Salut WAS installed before, and did not work after the update. But I have few hopes to find the problem during the update - but I really doubt that this is normal behaviour that Salut asks me for credentials and fields are disabled. # apt list telepathy* Auflistung... Fertig telepathy-accounts-signon/focal,now 1.0-1 amd64 [installiert] telepathy-gabble-tests/focal 0.18.4-2ubuntu1 amd64 telepathy-gabble/focal,now 0.18.4-2ubuntu1 amd64 [installiert] telepathy-idle/focal 0.2.0-2ubuntu1 amd64 telepathy-indicator/focal,now 0.3.1+14.10.20140908-0ubuntu2 amd64 [installiert] telepathy-logger/focal,now 0.8.2-4 amd64 [Installiert,automatisch] telepathy-mission-control-5/focal,now 1:5.16.5-1ubuntu1 amd64 [Installiert,automatisch] telepathy-rakia/focal,now 0.8.0-3ubuntu1 amd64 [installiert] telepathy-ring/focal 2.3.24-1ubuntu2 amd64 telepathy-sofiasip/focal,focal 0.8.0-3ubuntu1 all telepathy-specification/focal,focal 0.27.4-1 all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: empathy 3.25.90+really3.12.14-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 21 08:17:53 2020 InstallationDate: Installed on 2017-10-04 (1020 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=de_AT:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to focal on 2020-06-25 (25 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-07-26T08:33:20.216210 ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1888399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1888399] Re: After Update->20.04, Empathy/Salut stops working
** 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. https://bugs.launchpad.net/bugs/1888399 Title: After Update->20.04, Empathy/Salut stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1888399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1888399] Re: After Update->20.04, Empathy/Salut stops working
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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1888399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813825] Re: "driverless" printer workflow has bad usability/ is partly broken
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 doesn't work. -- 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 usability/ is partly broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813825] Re: "driverless" printer workflow has bad usability/ is partly broken
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 gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1813825 Title: "driverless" printer workflow has bad usability/ is partly broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818331] Re: Rhythmbox segfault since opening flac file
*** 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 crashes when trying to play music -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1818331 Title: Rhythmbox segfault since opening flac file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1818331/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813825] Re: "driverless" printer workflow has bad usability/ is partly broken
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 $ sudo systemctl stop cups-browsed $ ls -1 /etc/cups/ppd/ Kyocera-ECOSYS-P6026cdn.ppd Kyocera-ECOSYS-P6026cdn.ppd.O $ sudo systemctl stop cups-browsed I see 2 in the GUI, why there are 4 files here - I don't know why. Seems that cups-browsed adds the "_" separated files $ lp -d Kyocera-ECOSYS-P6026cdn ~/.bashrc Anfrage-ID ist Kyocera-ECOSYS-P6026cdn-52 (1 Datei(en)) $ sudo cupstestppd /etc/cups/ppd/Kyocera-ECOSYS-P6026cdn.ppd /etc/cups/ppd/Kyocera-ECOSYS-P6026cdn.ppd: FAIL **FAIL** Missing choice *Option18 SDCard in UIConstraints "*KCCollate CustomBox *Option18 SDCard". **FAIL** Missing choice *Option18 SDCard in UIConstraints "*Option18 SDCard *KCCollate CustomBox". WARNDatei einthält gemischt CR, LF, und CR LF Zeilenmenden. WARNSize "A5" should be "149x210mm". WARNSize "A6" should be "105x149mm". WARNSize "B6" should be "128x182mm". WARNSize "OficioII" should be the Adobe standard name "FanFoldGermanLegal". WARNSize "P16K" should be "7,75x10,75". WARNSize "OficioMX" should be the Adobe standard name "Oficio". $ lpstat -e Kyocera-ECOSYS-P6026cdn $ lpstat -v Gerät für Kyocera-ECOSYS-P6026cdn: dnssd://Kyocera%20ECOSYS%20P6026cdn._ipp._tcp.local/?uuid=4509a320-003a-00ad-0042-0025074ef136 $ driverless ipp://KM15881D.local:631/ipp/print But where is the "get-printer-attributes-2.0.test" file - I cant find this file. $ ipptool -tv ipp://KM15881D.local:631/ipp/print get-printer-attributes-2.0.test > ~/attrs.txt ipptool: Unable to open test file get-printer-attributes-2.0.test - No such file or directory It seems so confusing to me as there are no reliable on/offs: sometimes the files are available, sometimes not. Maybe this outputs help a bit. Hope you see something in there. -- 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 usability/ is partly broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818331] [NEW] Rhythmbox segfault since opening flac file
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 how to help further - ATM Rhythmbox is unusable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rhythmbox 3.4.2-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 2 13:44:00 2019 InstallationDate: Installed on 2019-01-27 (33 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/Xorg.0.log' ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "gdb screen output running rhythmbox" https://bugs.launchpad.net/bugs/1818331/+attachment/5242804/+files/gdb.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1818331 Title: Rhythmbox segfault since opening flac file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1818331/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813825] Re: "driverless" printer workflow has bad usability/ is partly broken
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" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+attachment/5242803/+files/Kyocera_ECOSYS_P6026cdn%40KM15881D.local.ppd -- 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 usability/ is partly broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813825] Re: "driverless" printer workflow has bad usability/ is partly broken
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" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+attachment/5242802/+files/Kyocera-ECOSYS-P6026cdn.ppd.0 -- 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 usability/ is partly broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813825] Re: "driverless" printer workflow has bad usability/ is partly broken
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 usability/ is partly broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1670683] Re: Nautilus ignores "Documents" if it is a symlink to a NFS share
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 127.0.0.1:/m /mnt/m Here neither. A `ls /mnt/doc` should contain the "test.txt" file. Now create a new user "tester" and log in via Gnome, so that the standard directories are created. back as admin user, delete the "/home/tester/Documents" folder, and do a ln -s /mnt/m/doc /home/tester/Documents Now I tested nautilus - and it worked. So IMHO this bug can be closed, at least for 18.04 it is working correctly now. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1670683 Title: Nautilus ignores "Documents" if it is a symlink to a NFS share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1670683/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813825] Re: "driverless" printer workflow has bad usability/ is partly broken
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 gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1813825 Title: "driverless" printer workflow has bad usability/ is partly broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813825] Re: "driverless" printer workflow has bad usability/ is partly broken
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 understand right; I first have to set "b g_log", and then "run" the program, right, and "c" means "continue". I tried everything here, including deleteing the printer, and watching it respawn. Only logs I got was: Thread 1 "gnome-control-c" hit Breakpoint 1, g_log (log_domain=log_domain@entry=0x556b6a97 "printers-cc-panel", log_level=log_level@entry=G_LOG_LEVEL_DEBUG, format=format@entry=0x556b8428 "Could not check 'Clean' maintenance command: %s") at ../../../../glib/gmessages.c:1428 1428in ../../../../glib/gmessages.c Which seems completely unrelated to me. BTW: system-config-printer does NOT show the "driverless" printer at all. -- 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 usability/ is partly broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813825] Re: "driverless" printer workflow has bad usability/ is partly broken
** 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 Ubuntu. https://bugs.launchpad.net/bugs/1813825 Title: "driverless" printer workflow has bad usability/ is partly broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813825] Re: "driverless" printer workflow has bad usability/ is partly broken
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, irrelevant parts snipped. ** Attachment added: "log" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+attachment/5234065/+files/journalctl.log -- 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 usability/ is partly broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813825] [NEW] "driverless" printer workflow has bad usability/ is partly broken
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. (But I tested this behaviour as well with
other printers from eg. Brother, etc., and on Debian and Arch linux
too). When I switch on the printer, after a few seconds, it is found in
Ubuntu and installed automatically as "Kyocera_ECOSYS_P6026cdn". So far,
so good.
1) I can't remove this printer. If I WANT to install it using another
protocol (dnss etc), it adds another printer, and I have 2 Printers. So
it should be easy to switch off "driverless" printing.
2) Using it as "Default printer" does not work. Clicking the cog wheel,
and using the menu item "Use printer by default" is clickable, but it
does not save any setting: "printers-cc-panel-WARNING **: 20:45:36.812:
cups-pk-helper: setting default printer to Kyocera_ECOSYS_P6026cdn
failed: client-error-not-found"
3) "Printing Options" opens an empty dialog, see screenshot attached.
This dialog is useless.
4) The "Printer Detail" dialog shows a "null" address and links to
"(null):631", which is a 404.
I think this "driverless" printing is still in a very "unstable" state. It
helps discovering printers in new Networks where I attach too with my laptop,
and I can print there basically, But most of the day I use my own printer in my
office or at home, and I want to have my special settings for exact this
printer with color profile, duplex settings etc.
And this all is not possible with driverless printing.
So, if you don't "fix" all the not-working options in the UI, please at
least give us an option to easily switch off driverless printing at all.
I really prefer the "old school" way of installing printers.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 29 19:34:39 2019
InstallationDate: Installed on 2019-01-27 (1 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
** Attachment added: "Printing options if driverless printer"
https://bugs.launchpad.net/bugs/1813825/+attachment/5233857/+files/Printing%20Options.png
--
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 usability/ is partly broken
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813825] Re: "driverless" printer workflow has bad usability/ is partly broken
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" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+attachment/5233875/+files/additional%20printer.png -- 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 usability/ is partly broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1725416] Re: Elantech touch pad device not detected/working properly
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 because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1725416 Title: Elantech touch pad device not detected/working properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725416/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1725416] [NEW] Elantech touch pad device not detected/working properly
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 gnome-control- center "Natural scrolling" just targets the mouse and has no effect on the touchpad. I can see the touchpad using "xinput list": ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpad id=14 [slave pointer (2)] ⎜ ↳ Logitech Performance MX id=12 [slave pointer (2)] alongside my Logitech mouse on a Unifying receiver. Is there any chance that this touchpad is detected? Or should I forget about that (WONTFIX) as Xorg is already unsupported? ATM I am using the prop. nvidia drivers. Currently uninstalling them to see if Wayland is starting using nouveau... Thanks. What else do you need from me? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 20:20:04 2017 InstallationDate: Installed on 2016-11-27 (327 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1725416 Title: Elantech touch pad device not detected/working properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725416/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1700764] [NEW] Wrong translation picked when initiating snap package
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 German - but the words there seem Turkish (?) to me - or at least a language I can't understand. See screenshot. I suppose there was a problem picking the right translation - bu I don't know if this is a snap problem or a gnome-software one - I just picked one to start this bug report here. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-software 3.22.7-0ubuntu3.17.04.2 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 26 22:05:01 2017 InstallationDate: Installed on 2016-11-27 (211 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-software UpgradeStatus: Upgraded to zesty on 2017-06-17 (8 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty ** Attachment added: "screenshot" https://bugs.launchpad.net/bugs/1700764/+attachment/4904098/+files/Bildschirmfoto%20von%20%C2%BB2017-06-26%2022-01-52%C2%AB.png ** Summary changed: - Wrong translation picked when initiatin snap package + Wrong translation picked when initiating snap package -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1700764 Title: Wrong translation picked when initiating snap package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1700764/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1670683] Re: Nautilus ignores "Documents" if it is a symlink to a NFS share
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. https://bugs.launchpad.net/bugs/1670683 Title: Nautilus ignores "Documents" if it is a symlink to a NFS share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1670683/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1670683] [NEW] Nautilus ignores "Documents" if it is a symlink to a NFS share
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 the computers weirdly works perfectly (folders are shown), but all others (3) don't have these entries, see screenshot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 7 14:41:37 2017 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1286x911+222+103'" InstallationDate: Installed on 2016-09-28 (159 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "Screenshot" https://bugs.launchpad.net/bugs/1670683/+attachment/4832886/+files/Bildschirmfoto%20vom%202017-03-07%2014-44-48.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1670683 Title: Nautilus ignores "Documents" if it is a symlink to a NFS share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1670683/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1035067] Re: Shotwell doesn't respect 24-hour clock
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 go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1035067/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1463571] Re: GTK filechooser dialog crashes
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 you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1463571 Title: GTK filechooser dialog crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1463571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
