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#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#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
