Bug#968438: I've just upgraded: annotations are okay

[inkbottle]

Hi,
I've just upgraded; Interface is different, but I do have icons, left side of 
the menu bar.
I've lost my settings/configuration regarding the annotation buttons, button's 
functions have reverted to default, but they seem to work correctly.
I've highlighted some text, and done some inline annotation, saved it, 
reloaded it. Everything seem fine.
Chris

Bug#935753: Here too

[inkbottle]

I've got the exact same bug.
Lenovo x230.
$ chromium  
[2261:2261:1005/211843.228812:FATAL:memory_linux.cc(42)] Out of memory. 
#0 0x55b7729e7509  
#1 0x55b772935cc6  
#2 0x55b77294dcd4  
#3 0x55b77296ee4d  
#4 0x55b7729fac85 calloc
...
#41 0x55b76fdd406d ChromeMain 
#42 0x7f74251bdbbb __libc_start_main 
#43 0x55b76fdd3eca _start 
 r8:   r9: 7ffe439cc750 r10: 0008 r11: 
0246 
r12: 7ffe439cd9a0 r13: 7ffe439cdb60 r14: 0047 r15: 
7ffe439cc9d0 
 di: 0002  si: 7ffe439cc750  bp: 7ffe439cc9a0  bx: 
7ffe439cdfb0 
 dx:   ax:   cx: 7f74251d1081  sp: 
7ffe439cc750 
 ip: 7f74251d1081 efl: 0246 cgf: 002b0033 erf: 
 
trp:  msk:  cr2:  
[end of stack trace] 
Calling _exit(1). Core file will not be generated.


So, no more chromium on that machine.

Bug#935031: Back to normal

[inkbottle]

Came back to normal after reboot.
C.

Bug#935031: Same here

[inkbottle]

Instead of the tabs that were left open before reboot action,
I have only one window, with nothing in it, not even a shell.
Until I do C-S-t which results in replacing the blank window,
with a shell.
C.

Bug#885182: Possibly related to upstream 379131 kde bug

[inkbottle]

Possibly related to upstream bug:
https://bugs.kde.org/show_bug.cgi?id=379131

See possible workaround there.

Bug#861782: mariadb-server-10.1: Upgrade fails because mariadb-server-10.1.prerm fails to stop mysqld.

[inkbottle]

On Thursday, May 4, 2017 4:53:52 AM CEST Ondřej Surý wrote:
> And output of:
> 
> pgrep mysqld
> 
> does it return the same pid as pidof command?
> 
> Cheers,

It think you are right, there are 2 processes:
# ps uax | egrep $(pidof /usr/sbin/mysqld|tr ' ' '|')  # as root
chris 6177  0.5  1.7 606652 141384 ?   Sl   03:20   0:40 
/usr/sbin/mysqld --defaults-file=/home/chris/.local/share/akonadi/mysql.conf 
--datadir=/home/chris/.local/share/akonadi/db_data/ 
--socket=/tmp/akonadi-chris.UBoT4r/mysql.socket
mysql11527  0.3  0.9 669628 74320 ?Ssl  05:17   0:00 
/usr/sbin/mysqld

When I do, as in the "prerm" script:
invoke-rc.d mysql stop

it stops only the mysqld of user mysql
(no matter how many times)
and
pidof -c /usr/sbin/mysqld
continues to give a positive answer.

However, initially,
pidof -c /usr/sbin/mysqld # (with -c, on two lines, w/o one the same line)
was giving two pid.
But when done after the
invoke-rc.d mysql stop
it gives only one pid.
So it might be, that at that point, installation could keep going, instead of 
stopping.


Also the two processes are own by different users, so they are easy to 
differentiate
in a test.

Best,
Chris

Bug#855055: linux-image-4.9.0-1-amd64: Hibernation bug fixed in linux-image-4.10.0-rc6-amd64

[inkbottle]

Please note this bug is not limited to kernel with version number 4.9,
but concerns every kernel with version lower than 4.10.

To the extent of my understanding it concerns only some rather recent Intel's 
CPU; but the chance to find one of them in a system seems only likely to 
increase.

And it's not a bug of the CPU. So it won't get fixed there.

Regards,
Chris

Bug#827705: (no subject)

[inkbottle]

When I did look at sysvinit-utils from Aptitude GUI, the problem was obvious, 
there was a deadlock, and of course the installation would not be possible.
However this is what happened:

# aptitude -t stretch install sysvinit-utils
The following packages will be upgraded: 
  initscripts sysvinit-utils 
2 packages upgraded, 0 newly installed, 0 to remove and 370 not upgraded.
Need to get 0 B/151 kB of archives. After unpacking 0 B will be used.
Do you want to continue? [Y/n/?] y
Retrieving bug reports... Done   
Parsing Found/Fixed information... Done
Reading changelogs... Done
(Reading database ... 190131 files and directories currently installed.)
Preparing to unpack .../initscripts_2.88dsf-59.6_amd64.deb ...
Unpacking initscripts (2.88dsf-59.6) over (2.88dsf-59.4) ...
Preparing to unpack .../sysvinit-utils_2.88dsf-59.6_amd64.deb ...
Unpacking sysvinit-utils (2.88dsf-59.6) over (2.88dsf-59.4) ...
Processing triggers for systemd (230-1) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up sysvinit-utils (2.88dsf-59.6) ...
Setting up initscripts (2.88dsf-59.6) ...
 
Current status: 370 (-2) upgradable.

So, nothing special happened: the dreaded bug didn't show.
I did the rest of the upgrade, and rebooted before sending this mail, to be 
sure... no problem arose.

Chris