[Desktop-packages] [Bug 1779782] [NEW] package poppler-utils 0.41.0-0ubuntu1.7 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su
Public bug reported: Hi. I have no idea what this is. Apparently everything is fine, no crashes at all. Since I upgraded (always in Terminal) this issue pop's up when I restart the pc. My computer knowledge is really low, so I hope you can detect if it's a bug or not. Sorry if I waisted your time. I was uncertain if this is important or not. Have a nice day. Kind regards from Spain. Mari Carmen ProblemType: Package DistroRelease: Ubuntu 16.04 Package: poppler-utils 0.41.0-0ubuntu1.7 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Jul 2 18:14:06 2018 ErrorMessage: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. InstallationDate: Installed on 2018-01-29 (154 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: poppler Title: package poppler-utils 0.41.0-0ubuntu1.7 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: poppler (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1779782 Title: package poppler-utils 0.41.0-0ubuntu1.7 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. Status in poppler package in Ubuntu: New Bug description: Hi. I have no idea what this is. Apparently everything is fine, no crashes at all. Since I upgraded (always in Terminal) this issue pop's up when I restart the pc. My computer knowledge is really low, so I hope you can detect if it's a bug or not. Sorry if I waisted your time. I was uncertain if this is important or not. Have a nice day. Kind regards from Spain. Mari Carmen ProblemType: Package DistroRelease: Ubuntu 16.04 Package: poppler-utils 0.41.0-0ubuntu1.7 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Jul 2 18:14:06 2018 ErrorMessage: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. InstallationDate: Installed on 2018-01-29 (154 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: poppler Title: package poppler-utils 0.41.0-0ubuntu1.7 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1779782/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1376903] Re: Caps lock delay
Yes and it is not a delay. The Caps and NUm Locks keys are set to turn off on release. CHanging this will solve it immediately. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1376903 Title: Caps lock delay Status in X.Org X server: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: I'm having a problem with Ubuntu, to be precise I have problem with its CAPS LOCK DELAY. I have a habit to use caps lock when I need a capital letter in my sentence, but problem is that I changing Caps lock in Ubuntu is slow, so I end up with sentence like this: - THis is a test. CAn you see how the first two letters are capital. THis happens only on UBuntu, not on my WIndows! Instead of holding shift like a normal person to capitalize my works, I hit Caps Lock, then hit the letter, then hit Caps Lock again. I know this is a strange habit, but I tried to change it to use Shift but I just can't. I want to contiunue using Caps lock, but the delay on Ubuntu is causing to have two capital letters in one word, and that is a problem, specially if you are typing very fast (like I). In 5 out of 10 cases I enter my password wrong beacuse of this delay. I'm guessing this may have somthing with X org or something. IS there a fix? If not, this should be reported as a BUG! To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1376903/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1318360] Re: Poor microphone quality (mako)
Hey, I had the same problem, also tried to flash the new firmware, but it didn't affect the quality. So I have adjusted alsamixer and it worked for me. Actually, I have done it try-and-error and I don't know much about the details, but maybe this helps someone, so I'll show you what I have done: - start terminal - start alsamixer by tiping "alsamixer" in the terminal - chose "Capture" by clicking F4 - click the right arrow key (roughly twomillion times^^) until I arrive to "RX1 Digital" - the RX1 until 7 Digitals are the gains that I changed, because they affect the quality. What I have done is, that I reduced the gain for RX2 until RX7, all down to around 55 (reducing is simply done by pressing the "down arrow"). The gain for RX1 must not be adjusted that low, because it somehow it affects the incoming call volume, and when I reduced this value, it was hard for me to understand the people. - That did the trick for me, I haven't done some very specific fine tuning, maybe I will do it later and tell you the results :). But since this solution works very well for me, maybe I'll leave it that way... I hope this will be helpful for someone; if anyone has any feedback or improvements, please share! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1318360 Title: Poor microphone quality (mako) Status in pulseaudio package in Ubuntu: Confirmed Bug description: After months of complaints from people talking to me on the phone (mako ubuntu touch), I finally got around to use multiROM to dual boot Ubuntu Touch and Android. Several people can confirm that there is a noticable difference in terms of sound/microphone quality between Android and UT in phone calls. With UT, my voice gets distorted to an extent that person at the other end have real difficulties to hear what I am saying, while with Android call quality is much better with no distortion. I have had a suspicion for a long time that this might be a software and not a hardware issue. After trying Android and Ubuntu on the same hardware I believe this suspicion is proved correct. This issue has persisted in all the builds I have tried since at least the beginning of the year, but probably longer. I am now at r17 of Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1318360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1318360] Re: Poor microphone quality (mako)
Addition to he last post: Leave rx2 high! Has to be the same like rx1! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1318360 Title: Poor microphone quality (mako) Status in pulseaudio package in Ubuntu: Confirmed Bug description: After months of complaints from people talking to me on the phone (mako ubuntu touch), I finally got around to use multiROM to dual boot Ubuntu Touch and Android. Several people can confirm that there is a noticable difference in terms of sound/microphone quality between Android and UT in phone calls. With UT, my voice gets distorted to an extent that person at the other end have real difficulties to hear what I am saying, while with Android call quality is much better with no distortion. I have had a suspicion for a long time that this might be a software and not a hardware issue. After trying Android and Ubuntu on the same hardware I believe this suspicion is proved correct. This issue has persisted in all the builds I have tried since at least the beginning of the year, but probably longer. I am now at r17 of Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1318360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1405084] Re: VERY slow when using images in Writer
That problem was introduced with LO 4.0. Older versions work more than ten times faster when scrolling images. The bug is independent from the image type (jpg, tiff, gif, ...), color depth or the program the image was created with. It was reported many times by different users and every time the report was closed without solving the problem. The solution I use is to work with Apache OpenOffice 4.1, which works as fast as expected and shows that it is no problem of slow hardware or image cache settings. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1405084 Title: VERY slow when using images in Writer Status in libreoffice package in Ubuntu: New Bug description: Scolling and typing becomes painfully slow when an image is added in LibreOffice Writer. It becomes faster (not much) when the same image covers a smaller area. From settings, I've tried to maximize the graphics memory, and to enable/disable hardware acceleration and antialiasing, but it doesn't help. The problem persists in LibreOffice 4.3.5-rc2 from ubuntu PPA. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-writer 1:4.2.7-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-29.39~14.04.1-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: KDE Date: Mon Dec 22 18:37:43 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-06-03 (202 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1405084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 838543] Re: False battery warning +suspend
*** This bug is a duplicate of bug 852406 *** https://bugs.launchpad.net/bugs/852406 I do NOT think they are duplicates - or at least, the issue I am having is not a duplicate. I am not having any issues whatsoever with it registering a nonexistent battery, or this happening after I come back from suspend. Firstly, my laptop never goes into suspend mode, and second this happens to me CONSTANTLY. It even does this directly after starting up and loading Oneiric, if my power cord gets unplugged. It doesn't do it every single time, but 9 out of 10 times that my cord gets pulled from or falls out of the port, my laptop goes into hibernate (that is my power setting for low battery, rather than standby) or shuts down completely. I have a dell laptop and the plug does NOT like to stay in, so my laptop ends up completely shutting down from this issue at least twice a day, and going into hibernate around six or eight times as much. Earlier today my power cord unplugged five times in thirty minutes, two times of which it immediately shut down. It is ridiculously frustrating. And yes, I HAVE enabled -proposed, installed all the new updates and things that enabling it gave me, and no, it has not fixed the issue. I've been keeping tabs on the other bug report despite the fact that I do not believe they are duplicates, and I was really hoping that it would fix the issue, but it seems to have made it both worse and slightly better simultaneously. I have a marginally better chance of my laptop not hibernating/shutting down if I press cancel and get my laptop plugged back in fast enough, and the first time or two it happens directly after I start up, there is an even chance of getting no warning or anything. But now a whole new issue has cropped up, which is that my battery life indicator is futzing up the percentage or time of battery life I have left. This was not happening before. So whereas before, it would tell me I had 2:05 and 100% left on my battery when it was unplugged, and I would get the warning, now it'll tell me I have 6:00 or 0:15 or 10% left. On a fully charged battery. Plus, the original problem still exists: if my charger falls out of the port on my laptop or gets unplugged, even on a full battery, a warning pops up, tells me my battery is about to die, and then my laptop goes into hibernate, or worse, shuts down completely. Unless I start my laptop up unplugged my battery life has essentially been reduced to a minute or less. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/838543 Title: False battery warning +suspend Status in “gnome-settings-daemon” package in Ubuntu: Incomplete Bug description: I pulled the plug on my laptop with it's battery full: ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/state present: yes capacity state: ok charging state: charged present rate:0 mA remaining capacity: 7200 mAh present voltage: 11100 mV ubuntu@ubuntu:~$ ubuntu-bug -w ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/info present: yes design capacity: 7200 mAh [...] And suddenly got a dialog saying that it was critically low (while the icon top-left appears, properly, as full) and the laptop did suspend shortly after that. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.1.5-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 CasperVersion: 1.280 Date: Thu Sep 1 02:26:17 2011 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110831) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/838543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 838543] Re: False battery warning +suspend
So mine has started shutting down COMPLETELY when it disconnects. For a while it stopped going into hibernate every time it got unplugged, which was great, but now it's even worse than before. And even more incredibly annoying, since my charger does not like to stay in. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/838543 Title: False battery warning +suspend Status in “gnome-settings-daemon” package in Ubuntu: Incomplete Bug description: I pulled the plug on my laptop with it's battery full: ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/state present: yes capacity state: ok charging state: charged present rate:0 mA remaining capacity: 7200 mAh present voltage: 11100 mV ubuntu@ubuntu:~$ ubuntu-bug -w ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/info present: yes design capacity: 7200 mAh [...] And suddenly got a dialog saying that it was critically low (while the icon top-left appears, properly, as full) and the laptop did suspend shortly after that. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.1.5-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 CasperVersion: 1.280 Date: Thu Sep 1 02:26:17 2011 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110831) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/838543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 831624] Re: AIM account Connection can't be established error
*** This bug is a duplicate of bug 828756 *** https://bugs.launchpad.net/bugs/828756 Same as the above user - I think they are different bugs. I do NOT have the issue in bug #828756, with connection is untrusted warning dialogues. However, as of two days ago (I have had Oneric installed for over a week now) it says connection cannot be established when I try to connect to AIM, and notification popups continually ask for my password (which I have confirmed as working, and not being typed wrong). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/831624 Title: AIM account Connection can't be established error Status in “empathy” package in Ubuntu: Confirmed Bug description: starting today, getting red box with Connection can't be established for my AIM account debug logs show SSL Cert error: Chain is VALID Checking for a CA with DN=OU=Class 3 Public Primary Certification Authority,O=VeriSign, Inc.,C=US Also checking for a CA with DN=OU=Class 3 Public Primary Certification Authority,O=VeriSign, Inc.,C=US haze_notify_message: error: SSL Certificate Error haze_notify_message: Unable to validate certificate haze_notify_message: The certificate for api.screenname.aol.com could not be validated. The certificate chain presented is invalid. Failed to verify certificate for api.screenname.aol.com Connection error on 0x1532d40 (reason: 0 description: Error requesting https://api.screenname.aol.com/auth/clientLogin: Unable to connect to api.screenname.aol.com: SSL peer presented an invalid certificate) connecting using pidgin works fine. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.1.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-9.12-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 Date: Mon Aug 22 13:42:56 2011 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Release Candidate amd64 (20100419.1) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to oneiric on 2011-07-13 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/831624/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 838543] Re: False battery warning +suspend
This bug is affecting me as well. I don't have the rest of the information that the OP has, but I DID run upower --dump; here's the results. ** Attachment added: upower --dump https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/838543/+attachment/2556149/+files/upower%20--dump -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/838543 Title: False battery warning +suspend Status in “gnome-settings-daemon” package in Ubuntu: Incomplete Bug description: I pulled the plug on my laptop with it's battery full: ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/state present: yes capacity state: ok charging state: charged present rate:0 mA remaining capacity: 7200 mAh present voltage: 11100 mV ubuntu@ubuntu:~$ ubuntu-bug -w ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/info present: yes design capacity: 7200 mAh [...] And suddenly got a dialog saying that it was critically low (while the icon top-left appears, properly, as full) and the laptop did suspend shortly after that. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.1.5-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 CasperVersion: 1.280 Date: Thu Sep 1 02:26:17 2011 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110831) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/838543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
