[Touch-packages] [Bug 1006676] Re: showkey fails with "Couldn't get a file descriptor referring to the console"
I agree that a more helpful error message would be helpful here. I am an experience Ubuntu terminal user. However, it is not intuitive to me that showkey should require root privileges. I would not have guessed this as a solution to resolve this error. A new error message could take several forms: Current user cannot access a file descriptor referring to the console. Permission denied. You must run as root user. Are you root? I personally prefer the most descriptive and helpful: Current user cannot access a file descriptor referring to the console. Perhaps you intended to run this as root? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1006676 Title: showkey fails with "Couldn't get a file descriptor referring to the console" Status in kbd package in Ubuntu: Invalid Bug description: When invoked in Gnome Terminal 3.0.1 (Ubuntu 11.10), showkey uninformatively exits after reporting: "Couldn't get a file descriptor referring to the console" For one who doesn't know what this means (such as myself), showkey is thus rendered unusable. The man page has no information about this behaviour. Installed kbd package: 1.15.2-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1006676/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574278] Re: AbiWord text cursor starts to flicker after adding some text
I experienced this bug in Lubuntu 16.04, and found it made Abiword unusable. I recently installed Lubuntu 17.04 on a different computer and was disappointed to discover the bug is still present with my fresh installation! That said, I'm not 100% sure my bug is the same as what is reported here. Above, and at the following places, is described the whole screen flickering when document not empty - https://www.youtube.com/watch?v=r1lPas9-DuQ=youtu.be - https://bugzilla.abisource.com/show_bug.cgi?id=13791 - https://bugs.sugarlabs.org/ticket/4915 However, my experience is that Abiword flashes from the top edge of the background (below the ruler) to about an inch into the page on the top, and from the left edge of the background to an eigth of an inch into the page on the left. When I zoom in or out on the document, the same area of the screen flickers. This happens even on an empty document. I think this is the same problem - https://askubuntu.com/questions/818219/abiword-documents-borders-keeps-flashing I tried this: for i in `ls /usr/share/themes`; do echo $i; GTK_THEME="$i" abiword; done It was the same for every theme, including Adwaita. Any hope for a fix? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1574278 Title: AbiWord text cursor starts to flicker after adding some text Status in AbiWord: In Progress Status in abiword package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Fix Released Status in lubuntu-artwork package in Ubuntu: Invalid Status in abiword source package in Xenial: Confirmed Status in gtk+3.0 source package in Xenial: Confirmed Status in lubuntu-artwork source package in Xenial: Invalid Bug description: After adding some text in a new document, the entire document (including gray page background, text, text cursor) starts to flicker very fast. The UI above does not flicker. This happens too on a different system in VirtualBox. (Lubuntu 16.04 i386) Workaround for Ubuntu 16.04 LTS === 1. Open the Lubuntu menu. 2. Open Preferences>Customize Look and Feel 3. Change the theme to something other than Lubuntu-default or Lubuntu-dark-panel ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: abiword 3.0.1-6 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 CurrentDesktop: LXDE Date: Sun Apr 24 16:12:14 2016 ExecutablePath: /usr/bin/abiword InstallationDate: Installed on 2016-04-22 (2 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: abiword UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/abiword/+bug/1574278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809247] Re: SetReportCrashes to true dbus call failed
Could we get this fix pushed out into the repositories? It can be pretty annoying and confusing to users if you have other issues which cause application crashes fairly frequently. For users to fix this: 1) Press Ctrl+Alt+T to open a terminal 2) Enter this command: sudo apt install whoopsie-preferences -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1809247 Title: SetReportCrashes to true dbus call failed Status in apport package in Ubuntu: Fix Released Status in apport source package in Disco: Fix Released Bug description: The following copied from screenshot 2018-12-20 11-50-53 Saving crash reporting state failed, Can't set auto auto or never reporting mode. Command '['/usr/bin/gdbus','call','-y','-d', 'com.ubuntu.WhoopsiePreferences','-o','/com/ubuntu/ WhoopsiePreferences','-m', 'com.ubuntu.WhoopsiePreferences.SetReportCrashes', 'true']' returned non-zero exit status 1. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-headers-4.15.0-43 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 Date: Thu Dec 20 11:22:53 2018 Dependencies: DuplicateSignature: package:linux-headers-4.15.0-43:4.15.0-43.46 Unpacking linux-modules-extra-4.15.0-43-generic (4.15.0-43.46) ... dpkg: error processing archive /tmp/apt-dpkg-install-OeaFpG/04-linux-modules-extra-4.15.0-43-generic_4.15.0-43.46_i386.deb (--unpack): unable to open '/lib/modules/4.15.0-43-generic/kernel/drivers/infiniband/hw/cxgb4/iw_cxgb4.ko.dpkg-new': Operation not permitted ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-headers-4.15.0-43.list-new': Operation not permitted InstallationDate: Installed on 2017-12-03 (382 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: linux Title: package linux-headers-4.15.0-43 4.15.0-43.46 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-headers-4.15.0-43.list-new': Operation not permitted UpgradeStatus: Upgraded to bionic on 2018-09-18 (92 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1809247/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
