Bug#955458: evolution: daily limit exceeded cannot connect to google calandar
Package: evolution Version: 3.36.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, I guess let me know if this needs to be reported "upstream". I'm getting this error every day now. Sometime in the evening my evolution calendar becomes unusable and I receive this message: Daily Limit Exceeded. The quota will be reset at midnight Pacific Time (PT). You may monitor your quota usage and adjust limits in the API Console: https://console.developers.google.com/apis/api/caldav.googleapis.com/quotas?project=44438659992 For example right now I would still be using my calendar to plan my time. Instead I seem to be locked out of using google calendar. Right now it is 11 central time. So it sounds like I'll be able to use it again at 1am. I don't know if this has anything to do with this error: https://developers.google.com/analytics/devguides/config/mgmt/v3/limits-quotas 50,000 requests per project per day, which can be increased. 10 queries per second (QPS) per IP address. In the API Console, there is a similar quota referred to as Requests per 100 seconds per user. By default, it is set to 100 requests per 100 seconds per user and can be adjusted to a maximum value of 1,000. But the number of requests to the API is restricted to a maximum of 10 requests per second per user. If your application makes all API requests from a single IP address (i.e., on behalf of your users), use the user IP or quota User parameter with each request to get full QPS quota for each user. See the standard query parameters summary for details. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (800, 'testing'), (700, 'unstable'), (600, 'experimental'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages evolution depends on: ii dbus 1.12.16-2 ii evolution-common 3.36.0-1 ii evolution-data-server 3.36.0-1 ii libc6 2.30-2 ii libcamel-1.2-623.36.0-1 ii libclutter-gtk-1.0-0 1.8.4-4 ii libecal-2.0-1 3.36.0-1 ii libedataserver-1.2-24 3.36.0-1 ii libevolution 3.36.0-1 ii libglib2.0-0 2.64.1-1 ii libgtk-3-0 3.24.14-1 ii libical3 3.0.8-1 ii libnotify4 0.7.9-1 ii libsoup2.4-1 2.70.0-1 ii libwebkit2gtk-4.0-37 2.28.0-2 ii libxml22.9.10+dfsg-4 ii psmisc 23.3-1 Versions of packages evolution recommends: ii evolution-plugin-bogofilter 3.36.0-1 ii evolution-plugin-pstimport 3.36.0-1 ii evolution-plugins3.36.0-1 ii yelp 3.34.0-1 Versions of packages evolution suggests: pn evolution-ews pn evolution-plugins-experimental ii gnupg 2.2.20-1 ii network-manager 1.22.6-1 -- debconf-show failed
Bug#954977: "Daily Limit Exceeded" connection error
Package: evolution Version: 3.36.0-1 Followup-For: Bug #954977 This is happening to me daily in evolution. When it does I am unable to use evolution email or calendar. The message I'm getting is: Daily Limit Exceeded. The quota will be reset at midnight Pacific Time (PT). You may monitor your quota usage and adjust limits in the API Console: https://console.developers.google.com/apis/api/caldav.googleapis.com/quotas?project=44438659992 Let me know if there is anything I can do to help troubleshoot this. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (800, 'testing'), (700, 'unstable'), (600, 'experimental'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages evolution depends on: ii dbus 1.12.16-2 ii evolution-common 3.36.0-1 ii evolution-data-server 3.36.0-1 ii libc6 2.30-2 ii libcamel-1.2-623.36.0-1 ii libclutter-gtk-1.0-0 1.8.4-4 ii libecal-2.0-1 3.36.0-1 ii libedataserver-1.2-24 3.36.0-1 ii libevolution 3.36.0-1 ii libglib2.0-0 2.64.1-1 ii libgtk-3-0 3.24.14-1 ii libical3 3.0.8-1 ii libnotify4 0.7.9-1 ii libsoup2.4-1 2.70.0-1 ii libwebkit2gtk-4.0-37 2.28.0-2 ii libxml22.9.10+dfsg-4 ii psmisc 23.3-1 Versions of packages evolution recommends: ii evolution-plugin-bogofilter 3.36.0-1 ii evolution-plugin-pstimport 3.36.0-1 ii evolution-plugins3.36.0-1 ii yelp 3.34.0-1 Versions of packages evolution suggests: pn evolution-ews pn evolution-plugins-experimental ii gnupg 2.2.20-1 ii network-manager 1.22.6-1 -- debconf-show failed
Bug#941908: Latest upgrade to 3.34.0-2 solved this problem
We had 5 computer affected by this problem. Every one of them booted normally into the Gnome shell (one took two tries) after a full- upgrade. So as far as I can tell, this problem is solved. Thanks for the hard work. One day after I submitted the report is pretty good, even if the changes were made to fix a different bug. Regards, William
Bug#941908: gnome: unable to start gnome-shell, cursor only with no login
Thank you for your suggestions. I'll give it try and report back. On Mon, 7 Oct 2019 16:16:56 +0100 Simon McVittie wrote:> Control: tags -1 + moreinfo> > On Mon, 07 Oct 2019 at 08:55:14 -0500, william l-k wrote:> > Problem: Instead of getting the authentication screen, the system has the> > cursor appear (which moves around just fine so the system isn't frozen), but> > never reaches a working gnome session.> > This looks like #941782. Please upgrade gnome-shell to version 3.34.x> (which was only in unstable until recently, but has just migrated into> testing, so it might not be available on your mirror yet), and see> whether this resolves the bug.> > If you cannot upgrade to gnome-shell 3.34 yet, downgrading the> gir1.2-gnomedesktop-3.0 package to the version from Debian 10 'buster'> is thought to work around this bug.> > > We are all on Debian testing. We also all had unattended upgrades running. I'll let you know if I'm able to get this to work. I'd probably forget how to fix anything if nothing ever went wrong, and then I'd be helpless in the face of disaster > > The testing/unstable suites sometimes break, despite our best efforts;> this is particularly true shortly after a stable release, as disruptive> changes that were queued up during the freeze get uploaded. If you run> testing/unstable, I would recommend using apt-listbugs to avoid upgrading Thanks for the tip on this. > to a version with known release-critical bugs.> > On critical or remote systems, I would recommend using the latest> Debian stable release, currently Debian 10 'buster', rather than> testing/unstable. > I would not recommend using unattended-upgrades with testing/unstable.> It's usually OK as a way to install security updates on a stable system,> but testing/unstable has too many transitions between incompatible versions> for unattended-upgrades to do the right thing in all cases. Learned this the hard way. I renamed the program for when running on a testing system: unintended-upgrades > > smcv> >
Bug#941908: gnome: unable to start gnome-shell, cursor only with no login
Package: gnome Version: 1:3.30+2 Severity: critical Justification: breaks the whole system Dear Maintainer, I would be shocked if only systems that I installed are having this problem. It sure seems like any computer running gnome will break with one of the recent updates... Description: I spend all weekend troubleshooting my sons laptop over the phone. We are all on Debian testing. We also all had unattended upgrades running. His system is barely working and needs to have a new installation. Switching to lxqt and ssdm we were able to get a graphical environment, but there were freezes at times that reisub couldn't solve requiring hard reset. Problem: Instead of getting the authentication screen, the system has the cursor appear (which moves around just fine so the system isn't frozen), but never reaches a working gnome session. I have tried every suggestion regarding similar past problems to no avail. We can reach a tty, but are unable to repair the system without reverting to a prior snapshot (if it exists). Some of what I tried: General description of attempted solutions: -looked for driver problem which is unlikely given the large differences in set ups between affected machines. - pam-auth-update --force systemctl restart gdm3 -manually removed /var/lib/gdm/.ICEauthority -tried wayland=true and wayland=false -purged the gnome destop and reinstalled. Same problem. I suspect that reinstalling debian testing running gnome won't help him IF he upgrades to the current version of whatever is killing gnome. Other affected machines: On Saturday, the same thing happened to my laptop. I had a recent snapshot and restored. Once the merge completed, I took a new snapshot, upgraded, and recreated the problem. Are laptops are not alike. He has a newer Lenova whereas I have an older toshiba. His is running an intel chip, whereas mine is running amd. Both have hdds. Our entertainment center / home server has a phenom with a seperate graphics card and developed the same problem due to unattended upgrades. This system had auto-login set up and is running off an lvm setup on two pairs of raid 1 disks. After fixing it once and taking a new snapshot unattended-upgrades upgraded some packages and did a scheduled reboot (2am). After reverting to the snapshot, this time I couldn't get the system to boot. lvm manager isn't available early in the session and I don't think grub knew how to handle a merging snapshot on this setup. I was able to get a shell on root using an install usb, and once I mounted the efi boot directory and home (probably didn't need that) and ran update-grub the boot problem was solved. Our file server running off of an old aspire netbook with an amd chip. Upgraded and has the same problem. I don't know when that one experienced a problem because I access the machine via ssh and rarely need to see the physical machine. I've been killing unattended upgrades on any other computer until this is solved. I was able to get some problem indications via email off of the unrepaired computer: Sample one: Oct 05 23:43:52 prisma minissdpd[839]: peer 10.5.6.235:6 is not from a LAN Oct 05 23:43:52 prisma minissdpd[839]: peer 10.5.6.235:6 is not from a LAN Oct 05 23:43:52 prisma minissdpd[839]: peer 10.5.6.235:6 is not from a LAN Oct 05 23:43:52 prisma minissdpd[839]: peer 10.5.6.235:6 is not from a LAN Oct 05 23:43:52 prisma minissdpd[839]: peer 10.5.6.235:6 is not from a LAN Oct 05 23:43:52 prisma minissdpd[839]: peer 10.5.6.235:6 is not from a LAN Oct 05 23:43:52 prisma minissdpd[839]: peer 10.5.6.235:6 is not from a LAN Oct 05 23:43:52 prisma minissdpd[839]: peer 10.5.6.235:6 is not from a LAN Oct 05 23:43:52 prisma minissdpd[839]: peer 10.5.6.235:6 is not from a LAN Oct 05 23:43:52 prisma minissdpd[839]: peer 10.5.6.235:6 is not from a LAN Oct 05 23:43:52 prisma minissdpd[839]: peer 10.5.6.235:6 is not from a LAN Oct 05 23:43:51 prisma minissdpd[839]: peer 10.9.5.109:42606 is not from a LAN Oct 05 23:43:51 prisma minissdpd[839]: peer 10.9.6.86:58553 is not from a LAN Oct 05 23:43:51 prisma minissdpd[839]: peer 10.9.5.79:35187 is not from a LAN Oct 05 23:43:50 prisma minissdpd[839]: peer 10.9.5.79:35187 is not from a LAN Oct 05 23:43:50 prisma minissdpd[839]: peer 10.9.5.79:35187 is not from a LAN Oct 05 23:43:49 prisma minissdpd[839]: peer 10.9.5.109:42606 is not from a LAN Oct 05 23:43:48 prisma minissdpd[839]: peer 10.9.6.145:57325 is not from a LAN Oct 05 23:43:48 prisma minissdpd[839]: peer 10.9.6.86:58553 is not from a LAN Oct 05 23:43:47 prisma minissdpd[839]: peer 10.9.6.145:57325 is not from a LAN Oct 05 23:43:47 prisma minissdpd[839]: peer 10.9.5.109:42606 is not from a LAN Oct 05 23:43:46 prisma minissdpd[839]: peer 10.9.6.145:57325 is not from a LAN Oct 05 23:43:46 prisma minissdpd[839]: peer 10.9.5.220:44867 is not from a LAN Oct 05 23:43:45 prisma systemd[1]: systemd-hostnamed.service: Succeeded. Oct 05 23:43:45 prisma systemd[1160]: p
Bug#929493: totem crashes on startup due to protocol error bug report #929493
Package: totem Version: 3.32.0-2 Followup-For: Bug #929493 This bug still exists in 3.33.90-2. as noted witht he x11 token, this problem affects the ability to run totem when using wayland. I was puzzled as to why this bug was affecting our Debian based home entertainment system, but not any of our laptops. When I ran totem from the terminal, it threw the aforementioned error 71. I immediately checked to see whether the unaffected systems were using Wayland: they were not. Upgrading to 3.33.90-2 did not solve the problem. Switching from Gnome Wayland "system x11 default" - as expected - corrected the problem, enabling videos to play normally in totem and launch from nautilus. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (800, 'testing'), (700, 'unstable'), (600, 'experimental'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages totem depends on: ii grilo-plugins-0.3 0.3.9-1 ii gsettings-desktop-schemas 3.28.1-1 ii gstreamer1.0-clutter-3.03.0.27-1 ii gstreamer1.0-plugins-base 1.16.0-2 ii gstreamer1.0-plugins-good 1.16.0-2+b1 ii gstreamer1.0-x 1.16.0-2 ii libc6 2.28-10 ii libcairo2 1.16.0-4 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-02.60.6-2 ii libgstreamer-plugins-base1.0-0 1.16.0-2 ii libgstreamer1.0-0 1.16.0-2.1 ii libgtk-3-0 3.24.10-1 ii libpango-1.0-0 1.42.4-7 ii libpangocairo-1.0-0 1.42.4-7 ii libtotem-plparser18 3.26.3-1 ii libtotem0 3.32.0-2 ii libx11-62:1.6.7-1 ii totem-common3.32.0-2 Versions of packages totem recommends: ii gstreamer1.0-libav 1.16.0-2+b1 ii gstreamer1.0-plugins-bad 1.16.0-2+b1 ii gstreamer1.0-plugins-ugly 1.16.0-2 ii gstreamer1.0-pulseaudio1.16.0-2+b1 ii totem-plugins 3.32.0-2 Versions of packages totem suggests: pn gnome-codec-install -- debconf-show failed
Bug#933499: libreoffice-base: database form with subform no longer works with "Data content could not be loaded" error
I'm completely stumped. There must be SQL statement created to
accomplish the link for the subform.
I found error detail on the sql statement. Here is the statement for
one of the errors:
The SQL command leading to this error is:
SELECT * FROM "aquarium"."corrections" WHERE (
"aquarium"."corrections"."testID" = :link_from_ID )
The statement for the other database is:
The SQL command leading to this error is:
SELECT * FROM "running"."workout" WHERE ( "running"."workout"."ID" =
:link_from_workoutID )
For both of these statements the master field is the last portion of
the generated name "ID" for the first and "workoutID" for the second.
Now if that is how the
Now if I run one of those statements directly from the sql view of
query design, I'm asked to provide a parameter. If I provide a valid
value, I get the exact error message that we got before.
Now if I replace the variable name with the parameter I just gave in
the dialogue, I now get the result I expect. So the bug must have to do
with the link parameter not getting replaced with the appropriate
value.
Does this help?
On Thu, 2019-08-01 at 18:31 +0200, Rene Engelhard wrote:
> Hi again,
>
> On Thu, Aug 01, 2019 at 12:04:58AM +0200, Rene Engelhard wrote:
> > On Wed, Jul 31, 2019 at 04:00:04PM -0500, william l-k wrote:
> > >have linked sub-forms from two seperate tables for entering related
> > > data.
> > >One of the databases started out as a libreoffice base then was
> > > converted
> > >to a mariadb connection. The other started out as a connection to
> > > mariadb.
>
> Maybe it's not related at all but connection to mariadb how? MySQL ODBC?
> MySQL JDBC? (both of which are removed because being buggy), MariaDB
> JDBC? Or libreoffice-mysql-connector?
>
> If the latter, 5.2 removed the extension and need for libmysqlcppconn
> but integrated it properly into the "main" packages
> (libreoffice-sdbc-mysql), just using lib{mariadb,mysql}client/libmariadb
> properly.
>
> Maybe it's related to one of those?
>
> Regards,
>
> Rene
Bug#933499: libreoffice-base: database form with subform no longer works with "Data content could not be loaded" error
Both forms now no longer change properly when the record is changing on
the main form. Now, both databases display the first record in the
table for the subform for every record in the main table. I'll toy with
this to see why one direction is behaves badly and the other just
throws an error.
On Thu, 2019-08-01 at 18:31 +0200, Rene Engelhard wrote:
> Hi again,
>
> On Thu, Aug 01, 2019 at 12:04:58AM +0200, Rene Engelhard wrote:
> > On Wed, Jul 31, 2019 at 04:00:04PM -0500, william l-k wrote:
> > >have linked sub-forms from two seperate tables for entering related
> > > data.
> > >One of the databases started out as a libreoffice base then was
> > > converted
> > >to a mariadb connection. The other started out as a connection to
> > > mariadb.
>
> Maybe it's not related at all but connection to mariadb how? MySQL ODBC?
> MySQL JDBC? (both of which are removed because being buggy), MariaDB
> JDBC? Or libreoffice-mysql-connector?
>
> If the latter, 5.2 removed the extension and need for libmysqlcppconn
> but integrated it properly into the "main" packages
> (libreoffice-sdbc-mysql), just using lib{mariadb,mysql}client/libmariadb
> properly.
>
> Maybe it's related to one of those?
>
> Regards,
>
> Rene
Bug#933499: libreoffice-base: database form with subform no longer works with "Data content could not be loaded" error
The connection type is MYSQL(native). In the wayback I vaguely remember
using the JDBC connection type. I believe I switched the oldest to
MYSQL(native) to solve a problem with complex querys. The newest
database affected started with MYSQL(native).
Perhaps the clue is in the error states verbatum:
The data content could not be loaded. You have an error in your SQL
syntax; check the manual that corresponds to your MariaDB server
version for the right syntax to use near ':link_from_ID )'.
Data is displayed for the parent table. It does not display for the
subform.
I just checked the form properties for the subform. The link fields had
the slave in the masters position and visa versa. I flipped the order
and tested the form, and voila, it works.
The wierd thing is, it had been working fine for years. If the order
had always been reversed
I checked the second table and got the exact same error message. Made
the identical changes on this form and ta da! Everything works.
Maybe everything working before was the bug? This is fixed for me, just
leaving me curious as to exactly which change led to the problem.
Thanks for your help.
On Thu, 2019-08-01 at 18:31 +0200, Rene Engelhard wrote:
> Hi again,
>
> On Thu, Aug 01, 2019 at 12:04:58AM +0200, Rene Engelhard wrote:
> > On Wed, Jul 31, 2019 at 04:00:04PM -0500, william l-k wrote:
> > >have linked sub-forms from two seperate tables for entering related
> > > data.
> > >One of the databases started out as a libreoffice base then was
> > > converted
> > >to a mariadb connection. The other started out as a connection to
> > > mariadb.
>
> Maybe it's not related at all but connection to mariadb how? MySQL ODBC?
> MySQL JDBC? (both of which are removed because being buggy), MariaDB
> JDBC? Or libreoffice-mysql-connector?
>
> If the latter, 5.2 removed the extension and need for libmysqlcppconn
> but integrated it properly into the "main" packages
> (libreoffice-sdbc-mysql), just using lib{mariadb,mysql}client/libmariadb
> properly.
>
> Maybe it's related to one of those?
>
> Regards,
>
> Rene
Bug#933499: libreoffice-base: database form with subform no longer works with "Data content could not be loaded" error
Package: libreoffice-base Version: 1:6.3.0~rc2-1 Severity: important As of today Jul 30 2019, a sub form no longer works that has worked for years. The pop up says that there is a problem with my SQL statement for MariaDB server version near ':link_from_ID)' at line one. But this isn't from a query I knowingly wrote. All of the reports relying on them still function fine. Adding data to the master form works, but the linked sub-form does not. If there is a work around to try I'm all ears. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (800, 'testing'), (700, 'unstable'), (600, 'experimental'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libreoffice-base depends on: ii libc6 2.28-10 ii libgcc1 1:9.1.0-10 ii libreoffice-base-core 1:6.3.0~rc2-1 ii libreoffice-base-drivers 1:6.3.0~rc2-1 ii libreoffice-core 1:6.3.0~rc2-1 ii libstdc++69.1.0-10 ii uno-libs3 6.3.0~rc2-1 ii ure 6.3.0~rc2-1 Versions of packages libreoffice-base recommends: ii default-jre [java6-runtime] 2:1.11-72 ii libreoffice-java-common 1:6.3.0~rc2-1 ii libreoffice-writer1:6.3.0~rc2-1 ii openjdk-10-jre [java6-runtime]10.0.2+13-2 ii openjdk-11-jre [java6-runtime]11.0.4+11-1 ii openjdk-8-jre [java6-runtime] 8u222-b10-1 ii openjdk-9-jre [java6-runtime] 9.0.4+12-4 ii oracle-java8-jdk [java6-runtime] 8u65 Versions of packages libreoffice-base suggests: ii libreoffice-report-builder 1:6.3.0~rc2-1 pn unixodbc Versions of packages libreoffice-core depends on: ii fontconfig 2.13.1-2 ii fonts-opensymbol2:102.11+LibO6.3.0~rc2-1 ii libboost-date-time1.67.01.67.0-13 ii libboost-locale1.67.0 1.67.0-13 ii libc6 2.28-10 ii libcairo2 1.16.0-4 ii libclucene-contribs1v5 2.3.3.4+dfsg-1 ii libclucene-core1v5 2.3.3.4+dfsg-1 ii libcmis-0.5-5v5 0.5.2-1 ii libcups22.2.10-6 ii libcurl3-gnutls 7.65.1-1 ii libdbus-1-3 1.12.16-1 ii libdconf1 0.30.1-2 ii libeot0 0.01-5 ii libepoxy0 1.5.3-0.1 ii libexpat1 2.2.7-1 ii libexttextcat-2.0-0 3.4.5-1 ii libfontconfig1 2.13.1-2 ii libfreetype62.9.1-4 ii libgcc1 1:9.1.0-10 ii libglib2.0-02.60.6-1 ii libgpgmepp6 1.12.0-6 ii libgraphite2-3 1.3.13-7 ii libgstreamer-plugins-base1.0-0 1.16.0-2 ii libgstreamer1.0-0 1.16.0-2 ii libharfbuzz-icu02.5.3-1 ii libharfbuzz0b 2.5.3-1 ii libhunspell-1.7-0 1.7.0-2+b1 ii libhyphen0 2.8.8-7 ii libice6 2:1.0.9-2 ii libicu6363.2-2 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-2 2.9-3 ii libldap-2.4-2 2.4.48+dfsg-1 ii libmythes-1.2-0 2:1.2.4-3+b1 ii libneon27-gnutls0.30.2-3 ii libnspr42:4.21-1 ii libnss3 2:3.45-1 ii libnumbertext-1.0-0 1.0.5-1 ii libodfgen-0.1-1 0.1.7-1 ii liborcus-0.14-0 0.14.1-6 ii libpng16-16 1.6.37-1 ii libpoppler820.71.0-5 ii librdf0 1.0.17-1.1+b1 ii libreoffice-common 1:6.3.0~rc2-1 ii librevenge-0.0-00.0.4-6+b1 ii libsm6 2:1.2.3-1 ii libstdc++6 9.1.0-10 ii libx11-62:1.6.7-1 ii libxext62:1.3.3-1+b2 ii libxinerama12:1.1.4-2 ii libxml2 2.9.4+dfsg1-7+b3 ii libxmlsec1 1.2.28-2 ii libxmlsec1-nss 1.2.28-2 ii libxrandr2 2:1.5.1-1 ii libxrender1 1:0.9.10-1 ii libxslt1.1 1.1.32-2 ii uno-libs3 6.3.0~rc2-1 ii ure 6.3.0~rc2-1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages libreoffice-core recommends: ii gstreamer1.0-libav 1.16.0-2 ii gstreamer1.0-plugins-bad 1.16.0-2 ii gstreamer1.0-plugins-base 1.16.0-2 ii gstreamer1.0-plugins-good 1.16.0-2 ii gstreamer1.0-plugins-ugly 1.16.0-2 ii libpaper-utils
Bug#928257: evolution: Unable to change key task information once created
Package: evolution Version: 3.30.5-1 Severity: important Dear Maintainer, I entered a task in active task view by using "click to add task". The created task was not visible, so I added several more not realizing that these newly created tasks were not falling into the active tasks category. When I selected all tasks and then paged down past all of the tasks that were checked off, I found all of the newly created tasks. I then tried changing start date and/or status to recategorize the newly created tasks. After changing data and then saving the task, all of the changed information reverted to the original values and the tasks did not appear when filtering for active tasks. Calendar events created using the same mechanism display immediately on the calendar and can be edited. I'm just baffled by the task display issue and don't remember this being a problem in the past. I've used tasks feature in the past few weeks and it behaved as expected. Obviously the current behavior renders this feature useless. I'd be happy to help pinpoint the issue. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (800, 'testing'), (700, 'unstable'), (600, 'experimental'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages evolution depends on: ii dbus 1.12.12-1 ii evolution-common 3.30.5-1 ii evolution-data-server 3.30.5-1 ii libc6 2.28-8 ii libcamel-1.2-623.30.5-1 ii libclutter-gtk-1.0-0 1.8.4-4 ii libecal-1.2-19 3.30.5-1 ii libedataserver-1.2-23 3.30.5-1 ii libevolution 3.30.5-1 ii libglib2.0-0 2.58.3-1 ii libgtk-3-0 3.24.5-1 ii libical3 3.0.4-3 ii libnotify4 0.7.7-4 ii libsoup2.4-1 2.64.2-2 ii libwebkit2gtk-4.0-37 2.24.1-1 ii libxml22.9.4+dfsg1-7+b3 ii psmisc 23.2-1 Versions of packages evolution recommends: ii evolution-plugin-bogofilter 3.30.5-1 ii evolution-plugin-pstimport 3.30.5-1 ii evolution-plugins3.30.5-1 ii yelp 3.31.90-1 Versions of packages evolution suggests: pn evolution-ews pn evolution-plugins-experimental ii gnupg 2.2.12-1 ii network-manager 1.14.6-2 -- debconf-show failed
Bug#907490: gnome-shell: Unrecoverable failure in required component org.gnome.Shell.desktop
Could this be what we were looking for: Aug 28 09:30:54 user gnome-shell[3348]: JS ERROR: TypeError: this._currentWindow is null_setCurrentRect@resourc e:///org/gnome/shell/ui/keyboard.js:536:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82: 22_init/<@resource:///org/g nome/shell/ui/keyboard.js:503:13 setQuestion@resource:///org/gnome/shell/gdm/authPrompt.js:357:9 wrapper@resource:///org/gnome/ gjs/modules/_legacy.js:82:22 _askForUsernameAndBeginVerification@resource:///org/gnome/shell/gdm/lo ginDialog.js:892:9wrapper@r esource:///org/gnome/gjs/modules/_legacy.js:82:22 _hideUserListAskForUsernameAndBeginVerification@r esource:///org/gnome/shell/gdm/loginDialog.js:1108:9 wrapper@resource:///org/gnome/gjs/modules/_leg acy.js:82:22Aug 28 09:30:54 user gnome-shell[3348]: JS WARNING: [resource:///org/gnome/shell/gdm/realmd.js 129]: reference to undefined property "_loginFormatAug 28 09:30:54 user gnome-shell[3348]: JS WARNING: [resource:///org/gnome/shell/gdm/realmd.js 141]: reference to undefined property "_loginFormatAug 28 09:30:54 user gnome-shell[3348]: JS ERROR: TypeError: this._currentWindow is null_setCurrentRect@resourc e:///org/gnome/shell/ui/keyboard.js:536:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82: 22_init/<@resource:///org/g nome/shell/ui/keyboard.js:503:13Aug 28 09:30:54 user gnome-shell[3348]: JS ERROR: TypeError: this._currentWindow is null_setCurrentRect@resourc e:///org/gnome/shell/ui/keyboard.js:536:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82: 22_init/<@resource:///org/g nome/shell/ui/keyboard.js:503:13Aug 28 09:30:56 user gnome-shell[3348]: JS ERROR: TypeError: this._currentWindow is null_setCurrentRect@resourc e:///org/gnome/shell/ui/keyboard.js:536:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82: 22_init/<@resource:///org/g nome/shell/ui/keyboard.js:503:13Aug 28 09:30:56 user gnome-shell[3348]: JS ERROR: TypeError: this._currentWindow is null_setCurrentRect@resourc e:///org/gnome/shell/ui/keyboard.js:536:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82: 22_init/<@resource:///org/g nome/shell/ui/keyboard.js:503:13Aug 28 09:30:57 user gnome-shell[3348]: JS ERROR: TypeError: this._currentWindow is null_setCurrentRect@resourc e:///org/gnome/shell/ui/keyboard.js:536:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82: 22_init/<@resource:///org/g nome/shell/ui/keyboard.js:503:13 On Sun, 2018-09-02 at 15:36 +0100, Simon McVittie wrote: > Control: tags -1 + moreinfo> > > On Tue, 28 Aug 2018 at 12:45:05 -0500, william l-k wrote: > The portion of the log near the times of start attempts had sections > likethese: > Aug 28 10:13:07 Username gnome-session-binary[8534]: Unrecoverable > failure inrequired component > org.gnome.SettingsDaemon.Power.desktopAug 28 10:13:07 Username dbus- > daemon[603]: [system] Activating via systemd:service > name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostnaAug > 28 10:13:07 Username gnome-session-binary[8534]: Unrecoverable > failure inrequired component > org.gnome.SettingsDaemon.XSettings.desktopAug 28 10:13:07 Username > gnome-session-binary[8534]: WARNING: > App'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1Aug 28 > 10:13:07 Username gnome-session-binary[8534]: WARNING: > App'org.gnome.SettingsDaemon.Clipboard.desktop' exited with code 1Aug > 28 10:13:07 Username gnome-session[8534]: Unable to init server: > Could notconnect: Connection refusedAug 28 10:13:07 Username > unknown[8630]: Cannot open display:Aug 28 10:13:07 Username dbus- > daemon[8532]: [session uid=1000 pid=8532]Activating via systemd: > service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.seAug 28 10:13:07 > Username gnome-session[8534]: Unable to init server: Could > notconnect: Connection refused > This
Bug#907490: gnome-shell: Unrecoverable failure in required component org.gnome.Shell.desktop
Package: gnome-shell Version: 3.28.3-1 Severity: grave Justification: renders package unusable Dear Maintainer, After a recent power failure lasting multiple hours, the battery backup on my laptop ran out of power and the system shut down. Once power was restored and I restarted the machine, I booted into a minimal GUI with black background and x-cursor. Without gnome controls, I was unable to get a terminal from the minimal session, so I switched to another tty. From there I was able to troubleshoot. None of the following solved the problem: rebooting update/upgrade then rebooting merging last lvm-snapshot of the root directory alt +f2 and then r sudo systemctl restart gdm killall -HUP gnome-shell sudo systemctl restart gdm >From GDM controls: trying default x11 and gnome Trying alternate kernel The portion of the log near the times of start attempts had sections like these: Aug 28 10:13:07 Username gnome-session-binary[8534]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Power.desktop Aug 28 10:13:07 Username dbus-daemon[603]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostna Aug 28 10:13:07 Username gnome-session-binary[8534]: Unrecoverable failure in required component org.gnome.SettingsDaemon.XSettings.desktop Aug 28 10:13:07 Username gnome-session-binary[8534]: WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1 Aug 28 10:13:07 Username gnome-session-binary[8534]: WARNING: App 'org.gnome.SettingsDaemon.Clipboard.desktop' exited with code 1 Aug 28 10:13:07 Username gnome-session[8534]: Unable to init server: Could not connect: Connection refused Aug 28 10:13:07 Username unknown[8630]: Cannot open display: Aug 28 10:13:07 Username dbus-daemon[8532]: [session uid=1000 pid=8532] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.se Aug 28 10:13:07 Username gnome-session[8534]: Unable to init server: Could not connect: Connection refused Aug 28 10:13:07 Username unknown[8635]: Cannot open display: Aug 28 10:13:07 Username gnome-session-binary[8534]: WARNING: App 'org.gnome.SettingsDaemon.Keyboard.desktop' exited with code 1 Aug 28 10:13:07 Username org.gnome.SettingsDaemon.Mouse.desktop[8606]: Unable to init server: Could not connect: Connection refused Aug 28 10:13:07 Username gnome-session[8534]: gnome-session-binary[8534]: WARNING: App 'org.gnome.SettingsDaemon.MediaKeys.desktop' exited with code 1 Aug 28 10:13:07 Username gnome-session[8534]: gnome-session-binary[8534]: WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1 Aug 28 10:13:07 Username gnome-session[8534]: gnome-session-binary[8534]: WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' respawning too quickly Aug 28 10:13:07 Username gnome-session[8534]: gnome-session-binary[8534]: WARNING: App 'org.gnome.SettingsDaemon.Clipboard.desktop' exited with code 1 Aug 28 10:13:07 Username gnome-session[8534]: gnome-session-binary[8534]: WARNING: App 'org.gnome.SettingsDaemon.Clipboard.desktop' respawning too qui Aug 28 10:13:07 Username systemd[1]: Starting Time & Date Service... Aug 28 10:13:07 Username org.gnome.SettingsDaemon.MediaKeys.desktop[8609]: Cannot open display: Aug 28 10:13:07 Username gnome-session-binary[8534]: WARNING: App 'org.gnome.SettingsDaemon.Color.desktop' exited with code 1 Aug 28 10:13:07 Username unknown[8638]: cannot open display: Aug 28 10:13:07 Username gnome-session[8534]: gnome-session-binary[8534]: WARNING: App 'org.gnome.SettingsDaemon.Keyboard.desktop' exited with code 1 Aug 28 10:13:07 Username gnome-session[8534]: gnome-session-binary[8534]: WARNING: App 'org.gnome.SettingsDaemon.Keyboard.desktop' respawning too quic Aug 28 10:13:07 Username gnome-session[8534]: gnome-session-binary[8534]: WARNING: App 'org.gnome.SettingsDaemon.Color.desktop' exited with code 1 Aug 28 10:13:07 Username gnome-session[8534]: gnome-session-binary[8534]: WARNING: App 'org.gnome.SettingsDaemon.Color.desktop' respawning too quickly Aug 28 10:13:07 Username gnome-session-binary[8534]: WARNING: App 'org.gnome.SettingsDaemon.Power.desktop' exited with code 1 Aug 28 10:13:07 Username gnome-session-binary[8534]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Wacom.desktop Aug 28 10:13:07 Username org.gnome.SettingsDaemon.Power.desktop[8613]: Cannot open display: Aug 28 10:13:07 Username gnome-session-binary[8534]: WARNING: App 'org.gnome.SettingsDaemon.Power.desktop' respawning too quickly Aug 28 10:13:07 Username gnome-session-binary[8534]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Clipboard.desktop Aug 28 10:13:07 Username gnome-session-binary[8534]: WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' exited with code 1 Aug 28 10:13:07 Username gnome-session-binary[8534]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Keyboard.desktop Aug 28 10:13:07 Username org.gnome.SettingsDaemon.XSettings.desktop[8614]
Bug#906711: appstream glib error - not fixed in 0.12.2-2
Package: appstream Version: 0.12.2-2 Severity: normal Dear Maintainer, There were a number of bugs reported for appstream associated with glib assertion failures. After upgrading from 0.12.2-1 to 0.12.2-2 there is still an assertion failure: (appstreamcli:18922): GLib-CRITICAL **: 20:19:06.758: g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed (appstreamcli:18922): GLib-CRITICAL **: 20:19:06.758: g_variant_new_variant: assertion 'value != NULL' failed (appstreamcli:18922): GLib-ERROR **: 20:19:06.758: g_variant_new_parsed: 11-13:invalid GVariant format string Previously appstream tripped up on: appstreamcli refresh-cache -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (800, 'testing'), (700, 'unstable'), (600, 'experimental'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages appstream depends on: ii libappstream4 0.12.2-1 ii libc6 2.27-5 ii libglib2.0-0 2.56.1-2 appstream recommends no packages. Versions of packages appstream suggests: ii apt-config-icons 0.12.2-1 ii curl 7.61.0-1 -- debconf-show failed
Bug#877029: taskcoach: Program fails to start
Package: taskcoach
Version: 1.4.3-4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Taskcoach will no longer start on my system. When selecting the program from
the gui nothing happens. Launching from the command line gives this:
Traceback (most recent call last):
File "/usr/bin/taskcoach", line 72, in
start()
File "/usr/bin/taskcoach", line 63, in start
app = application.Application(options, args)
File "/usr/lib/python2.7/dist-packages/taskcoachlib/patterns/singleton.py",
line 29, in __call__
class_.instance = super(Singleton, class_).__call__(*args, **kwargs)
File "/usr/lib/python2.7/dist-
packages/taskcoachlib/application/application.py", line 117, in __init__
self.initTwisted()
File "/usr/lib/python2.7/dist-
packages/taskcoachlib/application/application.py", line 164, in initTwisted
if map(int, twisted.__version__.split('.')) < (11,):
ValueError: invalid literal for int() with base 10: '0rc1'
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (800, 'testing'), (700, 'unstable'), (600, 'experimental'), (500,
'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.12.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages taskcoach depends on:
ii fonts-dejavu 2.37-1
ii libxss1 1:1.2.2-1+b2
ii python 2.7.13-2
ii python-chardet 3.0.4-1
ii python-dateutil 2.6.1-1
ii python-keyring 10.4.0-1
ii python-lockfile 1:0.12.2-2
ii python-pyparsing 2.1.10+dfsg1-1
ii python-squaremap 1:1.0.4-2
ii python-twisted-core 17.9.0~rc1-1
ii python-wxgtk3.0 3.0.2.0+dfsg-4
ii python-wxversion 3.0.2.0+dfsg-4
ii python-xdg 0.25-4
ii x11-utils7.7+3+b1
ii xdg-utils1.1.1-1
Versions of packages taskcoach recommends:
ii libavahi-compat-libdnssd1 0.7-3
ii libgnome-2-0 2.32.1-6
ii python-notify 0.1.1-4
Versions of packages taskcoach suggests:
pn espeak
pn python-kde4
-- debconf-show failed
Bug#875688: libreoffice-report-builder: installed deb for 1:5.4.1-2 from www.libreoffice.org and report builder works again
Package: libreoffice-report-builder Version: 1:5.4.1-1 Followup-For: Bug #875688 Dear Maintainer, As stated in the subject heading, report builder is working in 1:5.4.1-2 from libreoffice.org. The deb package was missing the mysql connector extension, and the one from extensions.libreoffice.org didn't work, so I needed a symbolic link /usr/lib/libreoffice/share/extensions/mysql-connector-ooo in /opt/libreoffice5.4/share/extensions to get this working. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (800, 'testing'), (700, 'unstable'), (600, 'experimental'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libreoffice-report-builder depends on: ii libbase-java 1.1.6-2 ii libcommons-logging-java1.2-1 ii libflute-java 1:1.1.6-3 ii libfonts-java 1.1.6.dfsg-3 ii libformula-java1.1.7.dfsg-2 ii liblayout-java 0.2.10-2 ii libloader-java 1.1.6.dfsg-4 ii libpentaho-reporting-flow-engine-java 0.9.4-4 ii libreoffice-common 1:5.4.1-1 ii libreoffice-core 1:5.4.1-1 ii libreoffice-java-common1:5.4.1-1 ii libreoffice-report-builder-bin 1:5.4.1-1 ii librepository-java 1.1.6-3 ii libsac-java1.3+dfsg-2 ii libserializer-java 1.1.6-4 ii libxml-java1.1.6.dfsg-3 libreoffice-report-builder recommends no packages. libreoffice-report-builder suggests no packages. Versions of packages libreoffice-base depends on: ii libc6 2.24-17 ii libgcc1 1:7.2.0-4 ii libreoffice-base-core 1:5.4.1-1 ii libreoffice-base-drivers 1:5.4.1-1 ii libreoffice-core 1:5.4.1-1 ii libstdc++67.2.0-4 ii uno-libs3 5.4.1-1 ii ure 5.4.1-1 Versions of packages libreoffice-base recommends: ii default-jre [java6-runtime] 2:1.8-59 ii libreoffice-java-common 1:5.4.1-1 ii libreoffice-writer1:5.4.1-1 ii openjdk-7-jre [java6-runtime] 7u151-2.6.11-1 ii openjdk-8-jre [java6-runtime] 8u144-b01-1 ii oracle-java8-jdk [java6-runtime] 8u65 Versions of packages libreoffice-base suggests: pn unixodbc -- no debconf information
Bug#875688: libreoffice-report-builder: Design view missing from libre office base. Existing reports won't run.
Package: libreoffice-report-builder Version: 1:5.4.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, libreoffice-report-builder will not run in base. Critical reports built using this tool cannot now be run. This occurred after the most recent upgrade to the debian testing branch. I tried reconfiguring the extension in dpkg. I also tried downloading the extension for report builder available from open office - which had a java incompatibility issue. I checked advanced tab options, and the oracle report builder is listed there. I'm currently seeking a work around, but libreoffice base is rendered useless for our purposes without those painstakingly constructed reports. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (800, 'testing'), (700, 'unstable'), (600, 'experimental'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libreoffice-report-builder depends on: ii libbase-java 1.1.6-2 ii libcommons-logging-java1.2-1 ii libflute-java 1:1.1.6-3 ii libfonts-java 1.1.6.dfsg-3 ii libformula-java1.1.7.dfsg-2 ii liblayout-java 0.2.10-2 ii libloader-java 1.1.6.dfsg-4 ii libpentaho-reporting-flow-engine-java 0.9.4-4 ii libreoffice-common 1:5.4.1-1 ii libreoffice-core 1:5.4.1-1 ii libreoffice-java-common1:5.4.1-1 ii libreoffice-report-builder-bin 1:5.4.1-1 ii librepository-java 1.1.6-3 ii libsac-java1.3+dfsg-2 ii libserializer-java 1.1.6-4 ii libxml-java1.1.6.dfsg-3 libreoffice-report-builder recommends no packages. libreoffice-report-builder suggests no packages. Versions of packages libreoffice-base depends on: ii libc6 2.24-17 ii libgcc1 1:7.2.0-4 ii libreoffice-base-core 1:5.4.1-1 ii libreoffice-base-drivers 1:5.4.1-1 ii libreoffice-core 1:5.4.1-1 ii libstdc++67.2.0-4 ii uno-libs3 5.4.1-1 ii ure 5.4.1-1 Versions of packages libreoffice-base recommends: ii default-jre [java6-runtime] 2:1.8-59 ii libreoffice-java-common 1:5.4.1-1 ii libreoffice-writer1:5.4.1-1 ii openjdk-7-jre [java6-runtime] 7u151-2.6.11-1 ii openjdk-8-jre [java6-runtime] 8u144-b01-1 ii oracle-java8-jdk [java6-runtime] 8u65 Versions of packages libreoffice-base suggests: pn unixodbc -- no debconf information
Bug#854627: gparted: Gparted won't run under gnome wayland.
Package: gparted Version: 0.25.0-1 Severity: important Dear Maintainer, I recently tried to run gparted under an regular user account. A dialog correctly appeared requesting an administrator password. After this was entered, the dialogue box closed but gparted did not run. I then tried starting gparted from the command line to see if there were any messages that might help troubleshoot. Heres what I got: Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/boot-efi.mount → /dev/null. Created symlink /run/systemd/system/home.mount → /dev/null. Created symlink /run/systemd/system/root.mount → /dev/null. Created symlink /run/systemd/system/run-rpc_pipefs.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-118.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:19704): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/boot-efi.mount. Removed /run/systemd/system/home.mount. Removed /run/systemd/system/root.mount. Removed /run/systemd/system/run-rpc_pipefs.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-118.mount. Removed /run/systemd/system/tmp.mount. So I surmised that gparted was unable to open a display. This was reminiscent of a problem I had with libreoffice recently. In that case, the problem was related to the fact that I was running wayland instead of x11. To rule out that possibility I logged out and logged back in under x11. Gparted then ran fine. To a typical user - more of whom will be running wayland in the future - this would have been a mysterious problem that would have rendered gparted unusable. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (800, 'testing'), (700, 'unstable'), (600, 'experimental'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gparted depends on: ii libatkmm-1.6-1v5 2.24.2-2 ii libc6 2.24-9 ii libgcc1 1:6.3.0-5 ii libglib2.0-0 2.50.2-2 ii libglibmm-2.4-1v5 2.50.0-1 ii libgtk2.0-0 2.24.31-2 ii libgtkmm-2.4-1v5 1:2.24.5-1 ii libpangomm-1.4-1v52.40.1-3 ii libparted-fs-resize0 3.2-17 ii libparted23.2-17 ii libsigc++-2.0-0v5 2.10.0-1 ii libstdc++66.3.0-5 ii libuuid1 2.29.1-1 gparted recommends no packages. Versions of packages gparted suggests: pn dmraid ii dmsetup2:1.02.137-1 ii dosfstools 4.1-1 ii gpart 1:0.3-3 pn jfsutils pn kpartx ii mtools 4.0.18-2 ii ntfs-3g1:2016.2.22AR.1-4 pn reiser4progs pn reiserfsprogs ii xfsprogs 4.9.0 ii yelp 3.22.0-1 -- no debconf information
Bug#854623: libreoffice: Libreoffice form control properties are inaccessible under gnome wayland
Package: libreoffice Version: 1:5.2.5-1 Severity: normal Dear Maintainer, I recently attempted to edit a libre office base form. I was able to open the properties box for the controls: say text field, but was unable to access or change the settings - such as which data field a the text box was associated with. I first tried upgrading to the version in experimental (I'm running testing as the target) from 1:5.2.5-1 to 1:5.3.0-1. This did not correct the problem. I then made sure that my system was fully updated. It was. I then tried running libre office base from the command line to see if there were any relevant error messages. I got the following message any time I tried to access a control property: (soffice:15742): Gdk-WARNING **: Window 0x55f256e1f330 is already mapped at the time of grabbing. gdk_seat_grab() should be used to simultaneously grab input and show this popup. You may find oddities ahead. It sounds like the wrong method is being called or something. I performed an internet search for similar problems and found that a fedora bug report with a similar error message. In this report it was suggested that the problem had to do with libreoffice not working under wayland. I logged out and logged back in under x11 and found that the controls now worked properly. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (800, 'testing'), (700, 'unstable'), (600, 'experimental'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libreoffice depends on: ii dpkg 1.18.18 ii fonts-dejavu 2.37-1 ii libreoffice-avmedia-backend-gstreamer 1:5.2.5-1 ii libreoffice-base 1:5.2.5-1 ii libreoffice-calc 1:5.2.5-1 ii libreoffice-core 1:5.2.5-1 ii libreoffice-draw 1:5.2.5-1 ii libreoffice-impress1:5.2.5-1 ii libreoffice-java-common1:5.2.5-1 ii libreoffice-math 1:5.2.5-1 ii libreoffice-report-builder-bin 1:5.2.5-1 ii libreoffice-writer 1:5.2.5-1 ii python3-uno1:5.2.5-1 Versions of packages libreoffice recommends: ii fonts-crosextra-caladea 20130214-1 ii fonts-crosextra-carlito 20130920-1 ii fonts-linuxlibertine5.3.0-2 ii fonts-sil-gentium-basic 1.1-7 ii libreoffice-librelogo 1:5.2.5-1 ii libreoffice-nlpsolver 0.9+LibO5.2.5-1 ii libreoffice-ogltrans1:5.2.5-1 ii libreoffice-pdfimport 1:5.2.5-1 ii libreoffice-report-builder 1:5.2.5-1 ii libreoffice-script-provider-bsh 1:5.2.5-1 ii libreoffice-script-provider-js 1:5.2.5-1 ii libreoffice-script-provider-python 1:5.2.5-1 ii libreoffice-sdbc-postgresql 1:5.2.5-1 ii libreoffice-wiki-publisher 1.2.0+LibO5.2.5-1 Versions of packages libreoffice suggests: ii cups-bsd2.2.1-8 ii default-jre [java5-runtime] 2:1.8-58 ii gstreamer1.0-libav 1.10.2-1 ii gstreamer1.0-plugins-bad1.10.2-1 ii gstreamer1.0-plugins-base 1.10.2-1 ii gstreamer1.0-plugins-good 1.10.2-1 ii gstreamer1.0-plugins-ugly 1.10.2-1 ii hunspell-en-us [hunspell-dictionary]20070829-7 ii hyphen-en-us [hyphen-hyphenation-patterns] 2.8.8-5 ii iceweasel 45.7.0esr-1 ii imagemagick 8:6.9.7.4+dfsg-1 ii imagemagick-6.q16 [imagemagick] 8:6.9.7.4+dfsg-1 ii libgl1-mesa-glx [libgl1]13.0.3-1 ii libreoffice-gnome 1:5.2.5-1 pn libreoffice-grammarcheck pn libreoffice-help-5.2 pn libreoffice-l10n-5.2 pn libreoffice-officebean ii libsane 1.0.25-3 ii libxrender1 1:0.9.10-1 pn myspell-dictionary pn mythes-thesaurus pn openclipart2-libreoffice | openclipart-libreoffice ii openjdk-7-jre [java5-runtime] 7u121-2.6.8-2 ii openjdk-8-jre [java5-runtime] 8u121-b13-2 ii oracle-java8-jdk [java5-runtime]8u65 ii pstoedit3.70-3+b2 pn unixodbc Versions o
Bug#848372: linux-image-4.8.0-2-amd64: Resume from suspend results in unrecoverable kernel panic.
Package: src:linux Version: 4.8.11-1 Severity: important linux-image-4.8.0-2-amd64: Resume from suspend results in unrecoverable kernel panic. Dear Maintainer, I submitted a very similar bug report for the previous image: Bug#847392: linux-image-4.8.0-1-amd64: Resume from suspend results in unrecoverable kernel panic. As in this bug report, resume from suspend doesn't work. The symptoms are the same: - flashing caps lock - unable to resume - troubleshooting efforts fail to alter the behavior The only change, is that I'm unable to get the screen to display anything after the system suspends. With linux-image-4.8.0-1-amd64 I was able to get the screen to display the kernel panic message. Now I just get the flashing caps lock. -- Package-specific info: ** Version: Linux version 4.8.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.1 20161019 (Debian 5.4.1-3) ) #1 SMP Debian 4.8.11-1 (2016-12-02) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.8.0-2-amd64 root=/dev/mapper/lvmpool-root ro panic=5 ** Not tainted ** Kernel log: [ 21.432624] radeon :00:01.0: fence driver on ring 5 use gpu addr 0x00078d30 and cpu addr 0xa45cc2038d30 [ 21.432892] radeon :00:01.0: fence driver on ring 6 use gpu addr 0x4c18 and cpu addr 0x95292af5dc18 [ 21.432917] radeon :00:01.0: fence driver on ring 7 use gpu addr 0x4c1c and cpu addr 0x95292af5dc1c [ 21.432940] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 21.432953] [drm] Driver supports precise vblank timestamp query. [ 21.433043] radeon :00:01.0: radeon: using MSI. [ 21.433107] [drm] radeon: irq initialized. [ 21.437915] [drm] ring test on 0 succeeded in 2 usecs [ 21.438012] [drm] ring test on 1 succeeded in 2 usecs [ 21.438034] [drm] ring test on 2 succeeded in 2 usecs [ 21.438234] [drm] ring test on 3 succeeded in 3 usecs [ 21.438245] [drm] ring test on 4 succeeded in 3 usecs [ 21.464103] [drm] ring test on 5 succeeded in 1 usecs [ 21.464124] [drm] UVD initialized successfully. [ 21.532278] uvcvideo: Found UVC 1.00 device TOSHIBA Web Camera - HD (04ca:7046) [ 21.535155] uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! [ 21.535170] uvcvideo 1-1.4:1.0: Entity type for entity Processing 2 was not initialized! [ 21.535182] uvcvideo 1-1.4:1.0: Entity type for entity Camera 1 was not initialized! [ 21.535344] input: TOSHIBA Web Camera - HD as /devices/pci:00/:00:12.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input11 [ 21.535465] usbcore: registered new interface driver uvcvideo [ 21.535472] USB Video Class driver (1.1.1) [ 21.573381] [drm] ring test on 6 succeeded in 11 usecs [ 21.573406] [drm] ring test on 7 succeeded in 1 usecs [ 21.573419] [drm] VCE initialized successfully. [ 21.576197] [drm] ib test on ring 0 succeeded in 0 usecs [ 22.080189] [drm] ib test on ring 1 succeeded in 0 usecs [ 22.592137] [drm] ib test on ring 2 succeeded in 0 usecs [ 22.592234] [drm] ib test on ring 3 succeeded in 0 usecs [ 22.592303] [drm] ib test on ring 4 succeeded in 0 usecs [ 22.983445] Adding 33202172k swap on /dev/mapper/lvmpool-swap. Priority:-1 extents:1 across:33202172k FS [ 23.104244] [drm] ib test on ring 5 succeeded [ 23.104794] [drm] ib test on ring 6 succeeded [ 23.105231] [drm] ib test on ring 7 succeeded [ 23.109396] [drm] radeon atom DIG backlight initialized [ 23.109410] [drm] Radeon Display Connectors [ 23.109420] [drm] Connector 0: [ 23.109428] [drm] eDP-1 [ 23.109436] [drm] HPD1 [ 23.109447] [drm] DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 0x653c [ 23.109460] [drm] Encoders: [ 23.109468] [drm] LCD1: INTERNAL_UNIPHY [ 23.109477] [drm] Connector 1: [ 23.109485] [drm] HDMI-A-1 [ 23.109492] [drm] HPD2 [ 23.109501] [drm] DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548 0x654c 0x654c [ 23.109515] [drm] Encoders: [ 23.109523] [drm] DFP1: INTERNAL_UNIPHY [ 23.109531] [drm] Connector 2: [ 23.109539] [drm] VGA-1 [ 23.109548] [drm] DDC: 0x65c0 0x65c0 0x65c4 0x65c4 0x65c8 0x65c8 0x65cc 0x65cc [ 23.109561] [drm] Encoders: [ 23.109569] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [ 24.129775] [drm] fb mappable at 0xC0722000 [ 24.129795] [drm] vram apper at 0xC000 [ 24.129806] [drm] size 4325376 [ 24.129816] [drm] fb depth is 24 [ 24.129825] [drm]pitch is 5632 [ 24.130057] fbcon: radeondrmfb (fb0) is primary device [ 24.173127] ath9k :03:00.0 wlp3s0: renamed from wlan0 [ 26.099607] Console: switching to colour frame buffer device 170x48 [ 26.109879] radeon :00:01.0: fb0: radeondrmfb frame buffer device [ 26.145212] [drm] Initialized radeon 2.46.0 20080528 for :00:01.0 on minor 0 [ 27.901436] EXT4-fs (dm-8): mounted filesystem with ordered data mode. Opts: errors=remount-ro [ 34.040837] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null) [ 42.271127] IPv6: ADDR
Bug#847392: linux-image-4.8.0-1-amd64: Resume from suspend results in unrecoverable kernel panic.
Package: src:linux Version: 4.8.7-1 Severity: important Dear maintainer, Resume from suspend no longer works with this kernel. This is important functionality for portable devices such as my laptop. I'd tried troubleshooting bios, power, and wireless settings to no avail. After running from a tty: sudo systemctl suspend The system appears to suspend normally. However upon resume the caps lock starts flashing and a kernel panic message appears on the terminal. This problem is not evident on any of the following kernels: linux-image-3.16.0-4-amd64 linux-image-4.6.0-1-amd64 linux-image-4.7.0-1-amd64 As a work around I set the grub/default kernel to 4.7.0-1 to correct the suspend problem. Let me know if you need any additional information. -- Package-specific info: ** Version: Linux version 4.8.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.1 20161019 (Debian 5.4.1-3) ) #1 SMP Debian 4.8.7-1 (2016-11-13) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.8.0-1-amd64 root=/dev/mapper/lvmpool-root ro panic=5 ** Not tainted ** Kernel log: [ 51.575356] [drm] UVD initialized successfully. [ 51.609568] media: Linux media interface: v0.10 [ 51.684597] [drm] ring test on 6 succeeded in 12 usecs [ 51.684618] [drm] ring test on 7 succeeded in 2 usecs [ 51.684625] [drm] VCE initialized successfully. [ 51.687006] [drm] ib test on ring 0 succeeded in 0 usecs [ 51.991099] Linux video capture interface: v2.00 [ 52.154202] kvm: Nested Virtualization enabled [ 52.154221] kvm: Nested Paging enabled [ 52.188068] [drm] ib test on ring 1 succeeded in 0 usecs [ 52.700251] [drm] ib test on ring 2 succeeded in 0 usecs [ 52.700362] [drm] ib test on ring 3 succeeded in 0 usecs [ 52.700436] [drm] ib test on ring 4 succeeded in 0 usecs [ 52.774853] ath9k :03:00.0: enabling device ( -> 0002) [ 52.781039] ath: phy0: Enable LNA combining [ 52.782153] ath: phy0: ASPM enabled: 0x42 [ 52.782162] ath: EEPROM regdomain: 0x69 [ 52.782163] ath: EEPROM indicates we should expect a direct regpair map [ 52.782165] ath: Country alpha2 being used: 00 [ 52.782166] ath: Regpair used: 0x69 [ 52.883641] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 52.884286] ieee80211 phy0: Atheros AR9485 Rev:1 mem=0xc3124210, irq=43 [ 53.194350] uvcvideo: Found UVC 1.00 device TOSHIBA Web Camera - HD (04ca:7046) [ 53.197468] uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! [ 53.197498] uvcvideo 1-1.4:1.0: Entity type for entity Processing 2 was not initialized! [ 53.197523] uvcvideo 1-1.4:1.0: Entity type for entity Camera 1 was not initialized! [ 53.197824] input: TOSHIBA Web Camera - HD as /devices/pci:00/:00:12.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input11 [ 53.198044] usbcore: registered new interface driver uvcvideo [ 53.198059] USB Video Class driver (1.1.1) [ 53.216080] [drm] ib test on ring 5 succeeded [ 53.216602] [drm] ib test on ring 6 succeeded [ 53.217006] [drm] ib test on ring 7 succeeded [ 53.222187] [drm] radeon atom DIG backlight initialized [ 53.222197] [drm] Radeon Display Connectors [ 53.03] [drm] Connector 0: [ 53.09] [drm] eDP-1 [ 53.15] [drm] HPD1 [ 53.22] [drm] DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 0x653c [ 53.31] [drm] Encoders: [ 53.37] [drm] LCD1: INTERNAL_UNIPHY [ 53.43] [drm] Connector 1: [ 53.48] [drm] HDMI-A-1 [ 53.54] [drm] HPD2 [ 53.60] [drm] DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548 0x654c 0x654c [ 53.69] [drm] Encoders: [ 53.75] [drm] DFP1: INTERNAL_UNIPHY [ 53.81] [drm] Connector 2: [ 53.86] [drm] VGA-1 [ 53.92] [drm] DDC: 0x65c0 0x65c0 0x65c4 0x65c4 0x65c8 0x65c8 0x65cc 0x65cc [ 53.222302] [drm] Encoders: [ 53.222307] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [ 54.237696] [drm] fb mappable at 0xC0722000 [ 54.237715] [drm] vram apper at 0xC000 [ 54.237726] [drm] size 4325376 [ 54.237736] [drm] fb depth is 24 [ 54.237745] [drm]pitch is 5632 [ 54.237948] fbcon: radeondrmfb (fb0) is primary device [ 55.870116] ath9k :03:00.0 wlp3s0: renamed from wlan0 [ 56.207788] Console: switching to colour frame buffer device 170x48 [ 56.217389] radeon :00:01.0: fb0: radeondrmfb frame buffer device [ 56.241169] [drm] Initialized radeon 2.46.0 20080528 for :00:01.0 on minor 0 [ 57.348657] Adding 33202172k swap on /dev/mapper/lvmpool-swap. Priority:-1 extents:1 across:33202172k FS [ 57.710633] EXT4-fs (dm-8): mounted filesystem with ordered data mode. Opts: errors=remount-ro [ 58.060511] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null) [ 70.610864] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready [ 70.854053] r8169 :02:00.0: firmware: direct-loading firmware rtl_nic/rtl8106e-1.fw [ 71.041264] r8169 :02:00.0 enp2s0: link down [ 71.042564] IPv6: ADDRCONF(NETDEV_UP):
