[Bug 1951817] Re: Livepatch red mark after every reboot.

[Rocco Martinello]

** Package changed: ubuntu => kpatch (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951817

Title:
  Livepatch red mark after every reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kpatch/+bug/1951817/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1951817] [NEW] Livepatch red mark after every reboot.

[Rocco Martinello]

Public bug reported:

Starting from 20th Novembre 2021 almost every time that I reboot my computer 
Livepatch shield has a red mark that disappears only detaching and reattaching 
Livepatch's token.
I tried to change the ID provided by Canonical on their website (Livepatch's 
token), but no luck.
I tried to uninstall and install again LivePatch, but no luck.
I tried the command
sudo canonical-livepatch refresh
, but no luck.
I tried to reinstall the update
ubuntu-advantage-tools 27.4.1~20.04.1
, but no luck. (I don't know if this update can be related to the problem.)
I provide you with some details:

rocco@rocco-desktop:~$ snap info canonical-livepatch
name:  canonical-livepatch
summary:   Canonical Livepatch Client
publisher: Canonical✓
store-url: https://snapcraft.io/canonical-livepatch
contact:   sn...@canonical.com
license:   unset
description: |
  Canonical Livepatch Client
commands:
  - canonical-livepatch
services:
  canonical-livepatch.canonical-livepatchd: simple, enabled, active
snap-id:   [I replaced the id with 
asterisks.]
tracking: latest/stable
refresh-date: yesterday at 13:41 CET
channels:
  latest/stable:10.0.1 2021-11-17 (119) 9MB -
  latest/candidate: 10.1.0 2021-11-18 (123) 9MB -
  latest/beta:  10.1.0 2021-11-18 (123) 9MB -
  latest/edge:  10.1.0 2021-11-18 (123) 9MB -
  core20/stable:10.0.1 2021-11-17 (121) 9MB -
  core20/candidate: 10.1.0 2021-11-19 (125) 9MB -
  core20/beta:  10.1.0 2021-11-19 (125) 9MB -
  core20/edge:  10.1.0 2021-11-18 (125) 9MB -
  core18/stable:10.0.1 2021-11-17 (122) 9MB -
  core18/candidate: 10.1.0 2021-11-18 (124) 9MB -
  core18/beta:  10.1.0 2021-11-18 (124) 9MB -
  core18/edge:  10.1.0 2021-11-18 (124) 9MB -
  core/stable:  10.0.1 2021-11-17 (119) 9MB -
  core/candidate:   10.1.0 2021-11-18 (123) 9MB -
  core/beta:10.1.0 2021-11-18 (123) 9MB -
  core/edge:10.1.0 2021-11-18 (123) 9MB -
installed:  10.0.1(119) 9MB -

rocco@rocco-desktop:~$ canonical-livepatch status
ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored.
last check: 45 minutes ago
kernel: 5.11.0-40.44~20.04.2-generic
server check-in: succeeded
patch state: ✓ no livepatches needed for this kernel yet
tier: updates (Free usage; This machine beta tests new patches.)
machine id:  [I replaced the id with asterisks.]

rocco@rocco-desktop:~$ lsb_release -a
No LSB modules are available.
Distributor ID:Ubuntu
Description:Ubuntu 20.04.3 LTS
Release:20.04
Codename:focal

rocco@rocco-desktop:~$ uname -a
Linux rocco-desktop 5.11.0-40-generic #44~20.04.2-Ubuntu SMP Tue Oct 26 
18:07:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

rocco@rocco-desktop:~$ journalctl -u 
snap.canonical-livepatch.canonical-livepatchd | tail -100
nov 20 15:30:10 rocco-desktop canonical-livepatch[947]: Sending status update 
the livepatch server.
nov 20 15:30:10 rocco-desktop canonical-livepatch[947]: Failed to refresh patch 
information: livepatch check failed: POST request to 
"https://livepatch.canonical.com/v1/client//updates;
 failed. [I replaced the code with asterisks.]
nov 20 15:30:10 rocco-desktop canonical-livepatch[947]: No patch payload 
available.
nov 20 15:30:10 rocco-desktop canonical-livepatch[947]: Task "refresh" returned 
an error: livepatch check failed: POST request to 
"https://livepatch.canonical.com/v1/client//updates;
 failed, retrying in 30s. [I replaced the code with asterisks.]
nov 20 15:30:37 rocco-desktop canonical-livepatch[947]: Client information is 
recent, not refreshing.
nov 20 15:30:37 rocco-desktop canonical-livepatch[947]: Processing machine 
status.
nov 20 15:30:37 rocco-desktop canonical-livepatch[947]: Error in livepatch 
check state: check-failed.
nov 20 15:30:37 rocco-desktop canonical-livepatch[947]: Sending status update 
the livepatch server.
nov 20 15:30:37 rocco-desktop canonical-livepatch[947]: No updates available at 
this time.
nov 20 15:30:37 rocco-desktop canonical-livepatch[947]: No patch payload 
available.
nov 20 15:30:37 rocco-desktop canonical-livepatch[947]: Task "refresh" 
completed succesfully after 1 

[Bug 1923608] [NEW] (italiano) c'è stato un errore nell'installazione in una partizione

[Daniele Rocco Melizza]

Public bug reported:

c'è stato un errore nell'installazione in una partizione

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.10
ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445.1
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 13 14:19:45 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
ProcEnviron:
 LANGUAGE=it_IT.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubiquity-20.04.15.10 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923608

Title:
  (italiano) c'è stato un errore nell'installazione in una partizione

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1923608/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1904377] Re: writer doesn't open

[rocco santoro]

I have uninstalled Libreoffice by the terminal; afterwards I have
re-installed it by Ubuntu Software. Now it is working.
Indeed, I installed Libreoffice by the terminal and the trial suggested in
the previous email I did by the terminal.
It is likely that the installation has to be done by Ubuntu Software to
avoid weird issues.
Thanks a lot! Without your help, I would have not thought to abandon the
terminal.
warms regards
Rocco

On Thu, Nov 26, 2020 at 10:01 AM Sebastien Bacher <
1904...@bugs.launchpad.net> wrote:

> there is nothing about libreoffice in the log, weird issue...
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1904377
>
> Title:
>   writer doesn't open
>
> Status in libreoffice package in Ubuntu:
>   Incomplete
>
> Bug description:
>   double-click on the document does not work.
>   For launching the programme it needs to go to the terminal and launch
> libreoffice.
>   The same procedure for the other tools of the suite
>   Thank you for the attention
>   BR
>
>   release Ubuntu 20.04.01 LTS 64bit gnome 3.36.3 X11
>   1:6.4.6-0ubuntu0.20.04.1 500
>   500 http://it.archive.ubuntu.com/ubuntu focal-updates/universe
> amd64 Packages
>   100 /var/lib/dpkg/status
>1:6.4.2-0ubuntu3 500
>   500 http://it.archive.ubuntu.com/ubuntu focal/universe amd64
> Packages
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: libreoffice-writer 1:6.4.6-0ubuntu0.20.04.1
>   ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
>   Uname: Linux 5.4.0-48-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.12
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Nov 16 08:46:11 2020
>   InstallationDate: Installed on 2020-08-29 (78 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=it_IT.UTF-8
>SHELL=/bin/bash
>   SourcePackage: libreoffice
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1904377/+subscriptions
>


-- 
Rocco Santoro
senior-statistician
Italy
tel +39 075 3720 736
tel +39 333 303 16 12

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904377

Title:
  writer doesn't open

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1904377/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1904377] Re: writer doesn't open

[rocco santoro]

Thank you for the message.

I have annexed the required file.

I tried to uninstalling/reinstalling Libreoffice resultless.The trouble
persists.

When I have read the logs in gnome, there is the following advise in
correspondence with the message
"gnome-launched-libreoffice-writer.desktop-7611.scope: Succeeded."
"Unità UNIT entrata con successo nello stato 'dead' (morto)."

Thank you the attention
Rocco


** Attachment added: "myjournal.log"
   
https://bugs.launchpad.net/bugs/1904377/+attachment/5437822/+files/myjournal.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904377

Title:
  writer doesn't open

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1904377/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1904377] Re: writer doesn't open

[rocco santoro]

I am sorry for the incomplete previous answer.
The problem occurs only when I try to open a file with libreoffice, while
the visualization of pdf or calibre work.
Thanks a lot
BR
Rocco

On Tue, Nov 17, 2020 at 11:59 AM Rocco Santoro 
wrote:

> I hope it is useful
> many thanks
> BR
> - Logs begin at Sat 2020-09-12 16:14:56 CEST. --
> nov 17 11:39:30 rocco-X551CAP kernel: [UFW BLOCK] IN=wlp2s0 OUT=
> MAC=28:e3:47:52:49:50:b8:d5:26:29:15:67:08:00 SRC=192.168.1.1 DST=224.0.0.1
> LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
> nov 17 11:40:42 rocco-X551CAP systemd[1483]: Started Application launched
> by gsd-media-keys.
> nov 17 11:40:43 rocco-X551CAP dbus-daemon[1495]: [session uid=1000
> pid=1495] Activating via systemd: service name='org.gnome.Terminal'
> unit='gnome-terminal-server.service' requested by ':1.157' (uid=1000
> pid=7996 comm="/usr/bin/gnome-terminal.real " label="unconfined")
> nov 17 11:40:43 rocco-X551CAP systemd[1483]: Created slice apps.slice.
> nov 17 11:40:43 rocco-X551CAP systemd[1483]: Created slice
> apps-org.gnome.Terminal.slice.
> nov 17 11:40:43 rocco-X551CAP systemd[1483]: Starting GNOME Terminal
> Server...
> nov 17 11:40:43 rocco-X551CAP dbus-daemon[1495]: [session uid=1000
> pid=1495] Successfully activated service 'org.gnome.Terminal'
> nov 17 11:40:43 rocco-X551CAP systemd[1483]: Started GNOME Terminal Server.
> nov 17 11:40:44 rocco-X551CAP systemd[1483]: Started VTE child process
> 8008 launched by gnome-terminal-server process 7999.
> nov 17 11:40:44 rocco-X551CAP systemd[1483]:
> gnome-launched-x-terminal-emulator-7993.scope: Succeeded.
> nov 17 11:41:36 rocco-X551CAP kernel: [UFW BLOCK] IN=wlp2s0 OUT=
> MAC=28:e3:47:52:49:50:b8:d5:26:29:15:67:08:00 SRC=192.168.1.1 DST=224.0.0.1
> LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
> nov 17 11:42:32 rocco-X551CAP kernel: ata1.00: exception Emask 0x0 SAct
> 0x8 SErr 0x5 action 0x0
> nov 17 11:42:32 rocco-X551CAP kernel: ata1.00: irq_stat 0x4008
> nov 17 11:42:32 rocco-X551CAP kernel: ata1: SError: { PHYRdyChg CommWake }
> nov 17 11:42:32 rocco-X551CAP kernel: ata1.00: failed command: READ FPDMA
> QUEUED
> nov 17 11:42:32 rocco-X551CAP kernel: ata1.00: cmd
> 60/08:98:30:a3:a0/00:00:37:00:00/40 tag 19 ncq dma 4096 in
>    res
> 51/40:08:30:a3:a0/00:00:37:00:00/40 Emask 0x409 (media error) 
> nov 17 11:42:32 rocco-X551CAP kernel: ata1.00: status: { DRDY ERR }
> nov 17 11:42:32 rocco-X551CAP kernel: ata1.00: error: { UNC }
> nov 17 11:42:32 rocco-X551CAP kernel: ata1: hard resetting link
> nov 17 11:42:33 rocco-X551CAP kernel: ata1: SATA link up 6.0 Gbps (SStatus
> 133 SControl 300)
> nov 17 11:42:33 rocco-X551CAP kernel: ata1.00: ACPI cmd
> f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
> nov 17 11:42:33 rocco-X551CAP kernel: ata1.00: ACPI cmd
> ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
> nov 17 11:42:33 rocco-X551CAP kernel: ata1.00: ACPI cmd
> ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
> nov 17 11:42:33 rocco-X551CAP kernel: ata1.00: ACPI cmd
> f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
> nov 17 11:42:33 rocco-X551CAP kernel: ata1.00: ACPI cmd
> ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
> nov 17 11:42:33 rocco-X551CAP kernel: ata1.00: ACPI cmd
> ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
> nov 17 11:42:33 rocco-X551CAP kernel: ata1.00: configured for UDMA/133
> nov 17 11:42:33 rocco-X551CAP kernel: sd 0:0:0:0: [sda] tag#19 FAILED
> Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> nov 17 11:42:33 rocco-X551CAP kernel: sd 0:0:0:0: [sda] tag#19 Sense Key :
> Medium Error [current]
> nov 17 11:42:33 rocco-X551CAP kernel: sd 0:0:0:0: [sda] tag#19 Add. Sense:
> Unrecovered read error - auto reallocate failed
> nov 17 11:42:33 rocco-X551CAP kernel: sd 0:0:0:0: [sda] tag#19 CDB:
> Read(10) 28 00 37 a0 a3 30 00 00 08 00
> nov 17 11:42:33 rocco-X551CAP kernel: blk_update_request: I/O error, dev
> sda, sector 933274416 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
> nov 17 11:42:33 rocco-X551CAP kernel: ata1: EH complete
> nov 17 11:42:36 rocco-X551CAP kernel: ata1.00: exception Emask 0x0 SAct
> 0x2 SErr 0x5 action 0x0
> nov 17 11:42:36 rocco-X551CAP kernel: ata1.00: irq_stat 0x4008
> nov 17 11:42:36 rocco-X551CAP kernel: ata1: SError: { PHYRdyChg CommWake }
> nov 17 11:42:37 rocco-X551CAP kernel: ata1.00: failed command: READ FPDMA
> QUEUED
> nov 17 11:42:37 rocco-X551CAP kernel: ata1.00: cmd
> 60/08:08:30:a3:a0/00:00:37:00:00/40 tag 1 ncq dma 4096 in
>    res
> 51/40:08:30:a3:a0/00:00:37:00:00/40 Emask 0x409 (media error) 
> nov 17 11:42:37 rocco-X551CAP kernel: ata1.00: status: { DRDY ERR }
> nov 17 11:42:37 rocco-X551CAP kernel

Re: [Bug 1904377] Re: writer doesn't open

[rocco santoro]

I hope it is useful
many thanks
BR
- Logs begin at Sat 2020-09-12 16:14:56 CEST. --
nov 17 11:39:30 rocco-X551CAP kernel: [UFW BLOCK] IN=wlp2s0 OUT=
MAC=28:e3:47:52:49:50:b8:d5:26:29:15:67:08:00 SRC=192.168.1.1 DST=224.0.0.1
LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
nov 17 11:40:42 rocco-X551CAP systemd[1483]: Started Application launched
by gsd-media-keys.
nov 17 11:40:43 rocco-X551CAP dbus-daemon[1495]: [session uid=1000
pid=1495] Activating via systemd: service name='org.gnome.Terminal'
unit='gnome-terminal-server.service' requested by ':1.157' (uid=1000
pid=7996 comm="/usr/bin/gnome-terminal.real " label="unconfined")
nov 17 11:40:43 rocco-X551CAP systemd[1483]: Created slice apps.slice.
nov 17 11:40:43 rocco-X551CAP systemd[1483]: Created slice
apps-org.gnome.Terminal.slice.
nov 17 11:40:43 rocco-X551CAP systemd[1483]: Starting GNOME Terminal
Server...
nov 17 11:40:43 rocco-X551CAP dbus-daemon[1495]: [session uid=1000
pid=1495] Successfully activated service 'org.gnome.Terminal'
nov 17 11:40:43 rocco-X551CAP systemd[1483]: Started GNOME Terminal Server.
nov 17 11:40:44 rocco-X551CAP systemd[1483]: Started VTE child process 8008
launched by gnome-terminal-server process 7999.
nov 17 11:40:44 rocco-X551CAP systemd[1483]:
gnome-launched-x-terminal-emulator-7993.scope: Succeeded.
nov 17 11:41:36 rocco-X551CAP kernel: [UFW BLOCK] IN=wlp2s0 OUT=
MAC=28:e3:47:52:49:50:b8:d5:26:29:15:67:08:00 SRC=192.168.1.1 DST=224.0.0.1
LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
nov 17 11:42:32 rocco-X551CAP kernel: ata1.00: exception Emask 0x0 SAct
0x8 SErr 0x5 action 0x0
nov 17 11:42:32 rocco-X551CAP kernel: ata1.00: irq_stat 0x4008
nov 17 11:42:32 rocco-X551CAP kernel: ata1: SError: { PHYRdyChg CommWake }
nov 17 11:42:32 rocco-X551CAP kernel: ata1.00: failed command: READ FPDMA
QUEUED
nov 17 11:42:32 rocco-X551CAP kernel: ata1.00: cmd
60/08:98:30:a3:a0/00:00:37:00:00/40 tag 19 ncq dma 4096 in
   res
51/40:08:30:a3:a0/00:00:37:00:00/40 Emask 0x409 (media error) 
nov 17 11:42:32 rocco-X551CAP kernel: ata1.00: status: { DRDY ERR }
nov 17 11:42:32 rocco-X551CAP kernel: ata1.00: error: { UNC }
nov 17 11:42:32 rocco-X551CAP kernel: ata1: hard resetting link
nov 17 11:42:33 rocco-X551CAP kernel: ata1: SATA link up 6.0 Gbps (SStatus
133 SControl 300)
nov 17 11:42:33 rocco-X551CAP kernel: ata1.00: ACPI cmd
f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
nov 17 11:42:33 rocco-X551CAP kernel: ata1.00: ACPI cmd
ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
nov 17 11:42:33 rocco-X551CAP kernel: ata1.00: ACPI cmd
ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
nov 17 11:42:33 rocco-X551CAP kernel: ata1.00: ACPI cmd
f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
nov 17 11:42:33 rocco-X551CAP kernel: ata1.00: ACPI cmd
ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
nov 17 11:42:33 rocco-X551CAP kernel: ata1.00: ACPI cmd
ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
nov 17 11:42:33 rocco-X551CAP kernel: ata1.00: configured for UDMA/133
nov 17 11:42:33 rocco-X551CAP kernel: sd 0:0:0:0: [sda] tag#19 FAILED
Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
nov 17 11:42:33 rocco-X551CAP kernel: sd 0:0:0:0: [sda] tag#19 Sense Key :
Medium Error [current]
nov 17 11:42:33 rocco-X551CAP kernel: sd 0:0:0:0: [sda] tag#19 Add. Sense:
Unrecovered read error - auto reallocate failed
nov 17 11:42:33 rocco-X551CAP kernel: sd 0:0:0:0: [sda] tag#19 CDB:
Read(10) 28 00 37 a0 a3 30 00 00 08 00
nov 17 11:42:33 rocco-X551CAP kernel: blk_update_request: I/O error, dev
sda, sector 933274416 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
nov 17 11:42:33 rocco-X551CAP kernel: ata1: EH complete
nov 17 11:42:36 rocco-X551CAP kernel: ata1.00: exception Emask 0x0 SAct 0x2
SErr 0x5 action 0x0
nov 17 11:42:36 rocco-X551CAP kernel: ata1.00: irq_stat 0x4008
nov 17 11:42:36 rocco-X551CAP kernel: ata1: SError: { PHYRdyChg CommWake }
nov 17 11:42:37 rocco-X551CAP kernel: ata1.00: failed command: READ FPDMA
QUEUED
nov 17 11:42:37 rocco-X551CAP kernel: ata1.00: cmd
60/08:08:30:a3:a0/00:00:37:00:00/40 tag 1 ncq dma 4096 in
   res
51/40:08:30:a3:a0/00:00:37:00:00/40 Emask 0x409 (media error) 
nov 17 11:42:37 rocco-X551CAP kernel: ata1.00: status: { DRDY ERR }
nov 17 11:42:37 rocco-X551CAP kernel: ata1.00: error: { UNC }
nov 17 11:42:37 rocco-X551CAP kernel: ata1: hard resetting link
nov 17 11:42:37 rocco-X551CAP kernel: ata1: SATA link up 6.0 Gbps (SStatus
133 SControl 300)
nov 17 11:42:37 rocco-X551CAP kernel: ata1.00: ACPI cmd
f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
nov 17 11:42:37 rocco-X551CAP kernel: ata1.00: ACPI cmd
ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
nov 17 11:42:37 rocco-X551CAP kernel: ata1.00: ACPI cmd
ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
nov 17 11:42:37 rocco-X551CAP kernel: ata1.00: ACPI cmd
f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
nov 17 11:42:37 

Re: [Bug 1904377] Re: writer doesn't open

[rocco santoro]

Thank you for the prompt answer.
Yes I do double-click in file manager and the issue occurs with  other
documents and filetypes all related to the Libreoffice suite.

On Mon, Nov 16, 2020 at 12:40 PM Sebastien Bacher <
1904...@bugs.launchpad.net> wrote:

> Thank you for your bug report, where do you double click ? In the
> filemanager ? Which one are you using and does opening other documents
> or filetypes work there?
>
> ** Changed in: libreoffice (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1904377
>
> Title:
>   writer doesn't open
>
> Status in libreoffice package in Ubuntu:
>   Incomplete
>
> Bug description:
>   double-click on the document does not work.
>   For launching the programme it needs to go to the terminal and launch
> libreoffice.
>   The same procedure for the other tools of the suite
>   Thank you for the attention
>   BR
>
>   release Ubuntu 20.04.01 LTS 64bit gnome 3.36.3 X11
>   1:6.4.6-0ubuntu0.20.04.1 500
>   500 http://it.archive.ubuntu.com/ubuntu focal-updates/universe
> amd64 Packages
>   100 /var/lib/dpkg/status
>1:6.4.2-0ubuntu3 500
>   500 http://it.archive.ubuntu.com/ubuntu focal/universe amd64
> Packages
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: libreoffice-writer 1:6.4.6-0ubuntu0.20.04.1
>   ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
>   Uname: Linux 5.4.0-48-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.12
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Nov 16 08:46:11 2020
>   InstallationDate: Installed on 2020-08-29 (78 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=it_IT.UTF-8
>SHELL=/bin/bash
>   SourcePackage: libreoffice
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1904377/+subscriptions
>


-- 
Rocco Santoro
senior-statistician
Italy
tel +39 075 3720 736
tel +39 333 303 16 12

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904377

Title:
  writer doesn't open

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1904377/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1904377] [NEW] writer doesn't open

[rocco santoro]

Public bug reported:

double-click on the document does not work.
For launching the programme it needs to go to the terminal and launch 
libreoffice.
The same procedure for the other tools of the suite
Thank you for the attention
BR

release Ubuntu 20.04.01 LTS 64bit gnome 3.36.3 X11
1:6.4.6-0ubuntu0.20.04.1 500
500 http://it.archive.ubuntu.com/ubuntu focal-updates/universe amd64 
Packages
100 /var/lib/dpkg/status
 1:6.4.2-0ubuntu3 500
500 http://it.archive.ubuntu.com/ubuntu focal/universe amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libreoffice-writer 1:6.4.6-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 16 08:46:11 2020
InstallationDate: Installed on 2020-08-29 (78 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libreoffice (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904377

Title:
  writer doesn't open

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1904377/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1730072] Re: Gnome Night Light doesn't work

[Rocco Muscaritolo]

I too see tons of messages in systemd.

xrandr -q works fine from the terminal. however, I just caught these
access denied messages as well. Looks like the root cause.

Sender: xdg-desktop-por
Message: Failed to get application states: 
GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: 
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not 
allowed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730072

Title:
  Gnome Night Light doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1730072/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1778348] Re: package mariadb-server-10.1 1:10.1.29-6 failed to install/upgrade: Unterprozess installed mariadb-server-10.1 package post-installation script gab den Fehler-Ausgangsstatus 2zurü

[Rocco Gallo]

Hallo Faustin

It is not a problem of MariaDB. It is my problem y forgot to install
the root with:
. mysql_secure_installation
 
befor 

echo "update mysql.user set plugin = 'mysql_native_password' where
user='root';" | mysql -u root


thanks

Rocco


Am Dienstag, den 03.07.2018, 20:06 + schrieb Faustin:
> Hi Rocco,
> thank you for taking time to report this and helping making ubuntu
> better.
> 
> I can not find any relevant information in the log that you sent.
> 
> So please can you answer these questions:
> * Is this reproducible?
> * If so, what specific steps should we take to recreate this bug?
> 
> This will help us to find and resolve the problem.
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778348

Title:
  package mariadb-server-10.1 1:10.1.29-6 failed to install/upgrade:
  Unterprozess installed mariadb-server-10.1 package post-installation
  script gab den Fehler-Ausgangsstatus 2 zurück

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1778348/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1778348] [NEW] package mariadb-server-10.1 1:10.1.29-6 failed to install/upgrade: Unterprozess installed mariadb-server-10.1 package post-installation script gab den Fehler-Ausgangsstatus 2 zurüc

[Rocco Gallo]

Public bug reported:


Remove test database and access to it? [Y/n] 
 - Dropping test database...
 ... Success!
 - Removing privileges on test database...
 ... Success!

Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.

Reload privilege tables now? [Y/n] 
 ... Success!

Cleaning up...

All done!  If you've completed all of the above steps, your MariaDB
installation should now be secure.
Thanks for using MariaDB!
root@wtcse:~# echo "update mysql.user set plugin = 'mysql_native_password' 
where user='root';" | mysql -u root
root@wtcse:~# nano /etc/mysql/debian.cnf
root@wtcse:~# service mysql restart
Job for mariadb.service failed because the control process exited with error 
code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
root@wtcse:~# netstat -tap | grep mysql
root@wtcse:~# systemctl status mariadb.service
● mariadb.service - MariaDB database server
   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: 
   Active: failed (Result: exit-code) since Sat 2018-06-23 16:26:04 CEST; 1min 1
  Process: 6284 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WS
  Process: 6185 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR
  Process: 6181 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START
  Process: 6165 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/ru
 Main PID: 6284 (code=exited, status=2)

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: mariadb-server-10.1 1:10.1.29-6
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sat Jun 23 16:30:07 2018
ErrorMessage: Unterprozess installed mariadb-server-10.1 package 
post-installation script gab den Fehler-Ausgangsstatus 2 zurück
Logs.var.log.daemon.log:
 
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
 [mysqldump]
 quick
 quote-names
 max_allowed_packet = 16M
MySQLVarLibDirListing: ['performance_schema', 'aria_log_control', 
'aria_log.0001', 'mysql_upgrade_info', 'ib_logfile1', 'debian-10.1.flag', 
'multi-master.info', 'ibdata1', 'mysql', 'ib_logfile0', 'tc.log']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=94ddcfec-76d9-11e8-b2f4-001e3716b01d ro maybe-ubiquity
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: mariadb-10.1
Title: package mariadb-server-10.1 1:10.1.29-6 failed to install/upgrade: 
Unterprozess installed mariadb-server-10.1 package post-installation script gab 
den Fehler-Ausgangsstatus 2 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mariadb-10.1 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778348

Title:
  package mariadb-server-10.1 1:10.1.29-6 failed to install/upgrade:
  Unterprozess installed mariadb-server-10.1 package post-installation
  script gab den Fehler-Ausgangsstatus 2 zurück

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1778348/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723494] [NEW] BUG: Bad page state in process Xwayland pfn:2dccef

[rocco]

Public bug reported:

Boh!!!

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-15-generic 4.13.0-15.16
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
NonfreeKernelModules: wl
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gdm 918 F pulseaudio
  rocco  1267 F pulseaudio
 /dev/snd/controlC0:  gdm 918 F pulseaudio
  rocco  1267 F pulseaudio
Date: Fri Oct 13 00:02:08 2017
Failure: oops
InstallationDate: Installed on 2017-09-30 (12 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
MachineType: LENOVO 80EU
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=bb4aae09-6483-4f06-b8d8-c8442bddc029 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: BUG: Bad page state in process Xwayland  pfn:2dccef
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/21/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 9DCN29WW(V2.09)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo B50-70
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo B50-70
dmi.modalias: 
dmi:bvnLENOVO:bvr9DCN29WW(V2.09):bd11/21/2014:svnLENOVO:pn80EU:pvrLenovoB50-70:rvnLENOVO:rnLenovoB50-70:rvrNODPK:cvnLENOVO:ct10:cvrLenovoB50-70:
dmi.product.family: IDEAPAD
dmi.product.name: 80EU
dmi.product.version: Lenovo B50-70
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-kerneloops artful kernel-oops

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723494

Title:
  BUG: Bad page state in process Xwayland  pfn:2dccef

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723494/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723495] [NEW] BUG: Bad page state in process Xwayland pfn:216254

[rocco]

Public bug reported:

Boh!!!

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-15-generic 4.13.0-15.16
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
NonfreeKernelModules: wl
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gdm 918 F pulseaudio
  rocco  1267 F pulseaudio
 /dev/snd/controlC0:  gdm 918 F pulseaudio
  rocco  1267 F pulseaudio
Date: Fri Oct 13 00:11:17 2017
Failure: oops
InstallationDate: Installed on 2017-09-30 (12 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
MachineType: LENOVO 80EU
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=bb4aae09-6483-4f06-b8d8-c8442bddc029 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: BUG: Bad page state in process Xwayland  pfn:216254
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/21/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 9DCN29WW(V2.09)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo B50-70
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo B50-70
dmi.modalias: 
dmi:bvnLENOVO:bvr9DCN29WW(V2.09):bd11/21/2014:svnLENOVO:pn80EU:pvrLenovoB50-70:rvnLENOVO:rnLenovoB50-70:rvrNODPK:cvnLENOVO:ct10:cvrLenovoB50-70:
dmi.product.family: IDEAPAD
dmi.product.name: 80EU
dmi.product.version: Lenovo B50-70
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-kerneloops artful kernel-oops

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723495

Title:
  BUG: Bad page state in process Xwayland  pfn:216254

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723495/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723496] [NEW] BUG: Bad page state in process Xwayland pfn:211e07

[rocco]

Public bug reported:

Boh!!!

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-15-generic 4.13.0-15.16
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
NonfreeKernelModules: wl
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gdm 918 F pulseaudio
  rocco  1267 F pulseaudio
 /dev/snd/controlC0:  gdm 918 F pulseaudio
  rocco  1267 F pulseaudio
Date: Fri Oct 13 00:07:13 2017
Failure: oops
InstallationDate: Installed on 2017-09-30 (12 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
MachineType: LENOVO 80EU
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=bb4aae09-6483-4f06-b8d8-c8442bddc029 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: BUG: Bad page state in process Xwayland  pfn:211e07
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/21/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 9DCN29WW(V2.09)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo B50-70
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo B50-70
dmi.modalias: 
dmi:bvnLENOVO:bvr9DCN29WW(V2.09):bd11/21/2014:svnLENOVO:pn80EU:pvrLenovoB50-70:rvnLENOVO:rnLenovoB50-70:rvrNODPK:cvnLENOVO:ct10:cvrLenovoB50-70:
dmi.product.family: IDEAPAD
dmi.product.name: 80EU
dmi.product.version: Lenovo B50-70
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-kerneloops artful kernel-oops

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723496

Title:
  BUG: Bad page state in process Xwayland  pfn:211e07

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723496/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1715089] [NEW] package tomcat7 7.0.68-1ubuntu0.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

[Rocco Gallo]

Public bug reported:

e: Sub-prozess /usr/bin/dpkg returned an error cond 1

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tomcat7 7.0.68-1ubuntu0.1
ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Tue Sep  5 10:14:55 2017
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: tomcat7
Title: package tomcat7 7.0.68-1ubuntu0.1 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: tomcat7 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1715089

Title:
  package tomcat7 7.0.68-1ubuntu0.1 failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  1 zurück

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1715089/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708941] Re: mate-hud does not open all the time

[Rocco]

I have tried testing with the different sequences of releasing keys and
also specific programs being maximized or minimized but I am still
experiencing no difference. Using Libre-Office as an example, The HUD
appears about 25% of the time when using the key combo in any sequence
and maximized or minimized makes no difference.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708941

Title:
  mate-hud does not open all the time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-hud/+bug/1708941/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708941] [NEW] mate-hud does not open all the time

[Rocco]

Public bug reported:

Running the latest updates on Ubuntu Mate 17.10 Alpha 2

Expected Behaviour: Super+Alt to open the HUD

Actual Behaviour: Super+Alt launches the HUD after the third or fourth
try using the shortcut keys.

Sometimes if I use Super+Alt nothing happens. I need to keep hitting the
key combo at least three times or more to get it to open the HUD
although sometimes it will open up on the first try. It seems very
random right now.

I am sorry I don't have more concrete info on it. I am not sure if it
matters but I am using a Logitech G910 Keyboard

** Affects: mate-hud (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708941

Title:
  mate-hud does not open all the time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-hud/+bug/1708941/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1683653] Re: Ubuntu MATE 17.04 crashes when opening D/L folder from Firefox

[Rocco]

I am also affected by this as well.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683653

Title:
  Ubuntu MATE 17.04 crashes when opening D/L folder from Firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1683653/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1680155] [NEW] mate-panel shows up in plank dock

[Rocco]

Public bug reported:

Fresh install of 64bit Ubuntu Mate 17.04 beta with the latest updates

The mate-panel shows up in plank as an open application that you can
actually minimize and maximize.

I attached a screenshot but I'm not versed in all the information you
might need to look at this so let me know if you need anything else.

** Affects: ubuntu-mate
 Importance: Undecided
 Status: New

** Affects: mate-panel (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: plank (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: mate-panel plank

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/bugs/1680155/+attachment/4855472/+files/Screenshot%20at%202017-04-05%2012-06-52.png

** Also affects: mate-panel (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: plank (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680155

Title:
  mate-panel shows up in plank dock

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1680155/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645056] Re: [Asus UX360UA] Unable to boot

[Mauro Rocco]

Hi tjiagoM,
I'm sorry but I'm running only windows on it for the moment as I had to use for 
work, now is a too busy period to start playing on it again.
As soon as I can I will but it might take a while.
Anyway if you have the exact same laptop (with I5 processor) and latest 
upstream is working for you it should just work for anybody else.

Thanks for the tests, this is a great news.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645056

Title:
  [Asus UX360UA] Unable to boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645056/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645056] Re: Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel paging request at 00000000686d7e40

[Mauro Rocco]

In My last comment I wrote mainstream but I meant upstream. Problem
still there with 4.9

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645056

Title:
  Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel
  paging request at 686d7e40

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645056/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645056] Re: Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel paging request at 00000000686d7e40

[Mauro Rocco]

Hi,
I had the issue since the first installation of ubuntu 16.04 lts, same after 
upgrade to non lts.
Just tested with mainstream kernel and the issue is still there.

thanks

** Tags added: kernel-bug-exists-upstream

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645056

Title:
  Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel
  paging request at 686d7e40

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645056/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645056] IwConfig.txt

[Mauro Rocco]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1645056/+attachment/4783679/+files/IwConfig.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645056

Title:
  Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel
  paging request at 686d7e40

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645056/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645056] Lspci.txt

[Mauro Rocco]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1645056/+attachment/4783681/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645056

Title:
  Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel
  paging request at 686d7e40

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645056/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645056] UdevDb.txt

[Mauro Rocco]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1645056/+attachment/4783687/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645056

Title:
  Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel
  paging request at 686d7e40

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645056/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645056] JournalErrors.txt

[Mauro Rocco]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1645056/+attachment/4783680/+files/JournalErrors.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645056

Title:
  Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel
  paging request at 686d7e40

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645056/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645056] WifiSyslog.txt

[Mauro Rocco]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1645056/+attachment/4783688/+files/WifiSyslog.txt

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645056

Title:
  Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel
  paging request at 686d7e40

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645056/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645056] ProcInterrupts.txt

[Mauro Rocco]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1645056/+attachment/4783684/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645056

Title:
  Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel
  paging request at 686d7e40

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645056/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645056] ProcModules.txt

[Mauro Rocco]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1645056/+attachment/4783685/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645056

Title:
  Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel
  paging request at 686d7e40

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645056/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645056] Re: Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel paging request at 00000000686d7e40

[Mauro Rocco]

apport information

** Tags added: apport-collected yakkety

** Description changed:

- I'm able to boot only with acpi=off, with acpi=ht I get this error at
- boot.
+ I'm able to boot only with acpi=off, with acpi=ht I get this error at boot.
+ --- 
+ ApportVersion: 2.20.3-0ubuntu8
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  mauro  2403 F pulseaudio
+ DistroRelease: Ubuntu 16.10
+ HibernationDevice: RESUME=UUID=7fd0455e-9721-4100-b1e6-8330040463c9
+ InstallationDate: Installed on 2016-11-08 (18 days ago)
+ InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
+  Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd 
+  Bus 001 Device 004: ID 192f:0416 Avago Technologies, Pte. ADNS-5700 Optical 
Mouse Controller (3-button)
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: ASUSTeK COMPUTER INC. UX360UA
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic 
root=/dev/mapper/ubuntu--vg-root ro acpi=off
+ ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
+ PulseList:
+  Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
+  No PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-47-generic N/A
+  linux-backports-modules-4.4.0-47-generic  N/A
+  linux-firmware1.161
+ Tags:  yakkety
+ Uname: Linux 4.4.0-47-generic x86_64
+ UpgradeStatus: Upgraded to yakkety on 2016-11-26 (0 days ago)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 06/17/2016
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: UX360UA.300
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: UX360UA
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: 1.0
+ dmi.chassis.asset.tag: ATN12345678901234567
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: ASUSTeK COMPUTER INC.
+ dmi.chassis.version: 1.0
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX360UA.300:bd06/17/2016:svnASUSTeKCOMPUTERINC.:pnUX360UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX360UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
+ dmi.product.name: UX360UA
+ dmi.product.version: 1.0
+ dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1645056/+attachment/4783676/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645056

Title:
  Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel
  paging request at 686d7e40

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645056/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645056] RfKill.txt

[Mauro Rocco]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1645056/+attachment/4783686/+files/RfKill.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645056

Title:
  Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel
  paging request at 686d7e40

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645056/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645056] ProcEnviron.txt

[Mauro Rocco]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1645056/+attachment/4783683/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645056

Title:
  Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel
  paging request at 686d7e40

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645056/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645056] ProcCpuinfo.txt

[Mauro Rocco]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1645056/+attachment/4783682/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645056

Title:
  Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel
  paging request at 686d7e40

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645056/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645056] CurrentDmesg.txt

[Mauro Rocco]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1645056/+attachment/4783678/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645056

Title:
  Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel
  paging request at 686d7e40

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645056/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645056] CRDA.txt

[Mauro Rocco]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1645056/+attachment/4783677/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645056

Title:
  Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel
  paging request at 686d7e40

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645056/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645056] [NEW] Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel paging request at 00000000686d7e40

[Mauro Rocco]

Public bug reported:

I'm able to boot only with acpi=off, with acpi=ht I get this error at
boot.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Boot logs"
   https://bugs.launchpad.net/bugs/1645056/+attachment/4783613/+files/boot.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645056

Title:
  Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel
  paging request at 686d7e40

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645056/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645056] Re: Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel paging request at 00000000686d7e40

[Mauro Rocco]

** Attachment added: "dmidecode.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645056/+attachment/4783614/+files/dmidecode.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645056

Title:
  Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel
  paging request at 686d7e40

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645056/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645056] Re: Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel paging request at 00000000686d7e40

[Mauro Rocco]

** Attachment added: "uname.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645056/+attachment/4783616/+files/uname.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645056

Title:
  Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel
  paging request at 686d7e40

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645056/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645056] Re: Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel paging request at 00000000686d7e40

[Mauro Rocco]

** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645056/+attachment/4783615/+files/lspci.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645056

Title:
  Nov 27 01:29:44 mauro-UX360UA kernel: BUG: unable to handle kernel
  paging request at 686d7e40

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645056/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1437492] Re: boot stalls on USB detection errors

[Rocco Muscaritolo]

After a couple reboots, 4.2.0-27 seems to have fixed it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437492

Title:
  boot stalls on USB detection errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1437492/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1437492] Re: boot stalls on USB detection errors

[Rocco Muscaritolo]

I've been battling with this issue for a weeks now as well. Thought it
was faulty hardware, but it only occurs when I do a warm reboot into my
Linux system.


MSI z97 gaming 7 
4.2.0-19-generic

I'm going to install 4.2.0-27 now and post any updates if it was
resolved.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437492

Title:
  boot stalls on USB detection errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1437492/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1491745] [NEW] dlm_stonith where?

[Rocco]

Public bug reported:

The dlm_stonith binary needed to get fencing working in a pacemaker/gfs2
scenario is not in the dlm package, or somewhere else in ubuntu.

** Affects: dlm (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491745

Title:
  dlm_stonith where?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dlm/+bug/1491745/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1491745] [NEW] dlm_stonith where?

[Rocco]

Public bug reported:

The dlm_stonith binary needed to get fencing working in a pacemaker/gfs2
scenario is not in the dlm package, or somewhere else in ubuntu.

** Affects: dlm (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dlm in Ubuntu.
https://bugs.launchpad.net/bugs/1491745

Title:
  dlm_stonith where?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dlm/+bug/1491745/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1477868] [NEW] package linux-image-extra-3.13.0-58-generic 3.13.0-58.97 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[rocco cesetti]

Public bug reported:

Ho cercato di  rimouvere  l'image linux-image-extra-3.13.0.53-generic

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.13.0-58-generic 3.13.0-58.97
ProcVersionSignature: Ubuntu 3.13.0-58.97-generic 3.13.11-ckt22
Uname: Linux 3.13.0-58-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Thu Jul 23 09:45:37 2015
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
HibernationDevice: RESUME=UUID=245bea07-6571-4ef5-9c79-f9d4000414ab
InstallationDate: Installed on 2012-05-24 (1156 days ago)
InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Release amd64 
(20120424.1)
MachineType: HP ProLiant MicroServer
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-58-generic 
root=/dev/mapper/hostname-root ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.2
RfKill:
 
SourcePackage: linux
Title: package linux-image-extra-3.13.0-58-generic 3.13.0-58.97 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/29/2011
dmi.bios.vendor: HP
dmi.bios.version: O41
dmi.chassis.type: 7
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrO41:bd07/29/2011:svnHP:pnProLiantMicroServer:pvr:cvnHP:ct7:cvr:
dmi.product.name: ProLiant MicroServer
dmi.sys.vendor: HP

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-package third-party-packages trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1477868

Title:
  package linux-image-extra-3.13.0-58-generic 3.13.0-58.97 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477868/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1453059] [NEW] init script is redhat version, doesn't work.

[Rocco]

Public bug reported:

ii  dlm 4.0.1-0ubuntu1
amd64DLM - Distributed lock manager binaries

. /etc/rc.d/init.d/functions

# ls -l /etc/rc.d/init.d/functions
ls: cannot access /etc/rc.d/init.d/functions: No such file or directory


It's kinda sick this made it into a LTS

** Affects: dlm (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dlm in Ubuntu.
https://bugs.launchpad.net/bugs/1453059

Title:
  init script is redhat version, doesn't work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dlm/+bug/1453059/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1453059] [NEW] init script is redhat version, doesn't work.

[Rocco]

Public bug reported:

ii  dlm 4.0.1-0ubuntu1
amd64DLM - Distributed lock manager binaries

. /etc/rc.d/init.d/functions

# ls -l /etc/rc.d/init.d/functions
ls: cannot access /etc/rc.d/init.d/functions: No such file or directory


It's kinda sick this made it into a LTS

** Affects: dlm (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453059

Title:
  init script is redhat version, doesn't work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dlm/+bug/1453059/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1353860] [NEW] Doesn't load modules from /etc/modules

[Rocco]

Public bug reported:

root@troubadix:/etc# lsb_release -d
Description:Ubuntu 12.04.5 LTS

root@troubadix:/etc# uname -a
Linux troubadix 3.13.0-32-generic #57~precise1-Ubuntu SMP Tue Jul 15 03:51:20 
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

root@troubadix:/etc# cat /etc/modules 
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with # are ignored.

loop
lp
rtc
mptctl
ipmi_si
ipmi_devintf

root@troubadix:/etc# lsmod | egrep loop|rtc|ipmi_si|ipmi_devintf
root@troubadix:/etc#

** Affects: linux-meta-lts-trusty (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353860

Title:
  Doesn't load modules from /etc/modules

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-trusty/+bug/1353860/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1314289] Re: [Precise/regression] drbd 8.4.x backport breaks existing clusters

[Rocco]

When will it be released? Any ETA?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1314289

Title:
  [Precise/regression] drbd 8.4.x backport breaks existing clusters

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1314289/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1314289] Re: [Precise/regression] drbd 8.4.x backport breaks existing clusters

[Rocco]

When will it be released? Any ETA?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314289

Title:
  [Precise/regression] drbd 8.4.x backport breaks existing clusters

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1314289/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1185756] Re: drbd8-utils not compatible with linux-lts-raring kernel in 12.04

[Rocco]

My clusters are configured to use Linbit:drbd which is:
/usr/lib/ocf/resource.d/linbit/drbd

and that file is in drbd8-utils



On Thu, Apr 24, 2014 at 10:45 AM, Christoph Mitasch 
cmita...@thomas-krenn.com wrote:

 Hello,

 the Linux Cluster Management Console (LCMC) makes it quite easy to setup a
 DRBD/Pacemaker cluster.
 http://lcmc.sourceforge.net/

 Christoph

 - Ursprüngliche Mail -
  Von: Stefan Bader stefan.ba...@canonical.com
  An: cmita...@thomas-krenn.com
  Gesendet: Donnerstag, 24. April 2014 10:35:01
  Betreff: [Bug 1185756] Re: drbd8-utils not compatible with
 linux-lts-raring kernel in 12.04
 
  @Andreas, that particular error is fixed by the test packages (see
  comment #60). There could be one in conjunction with pacemaker which
  reports an error about drbdadm syncer not being a valid command.
  Unfortunately I don't think anyone who is running a pacemaker cluster
  really can afford to help debugging as that causes disruptions.
 
  --
  You received this bug notification because you are subscribed to the bug
  report.
  https://bugs.launchpad.net/bugs/1185756
 
  Title:
drbd8-utils not compatible with linux-lts-raring kernel in 12.04
 
  Status in “drbd8” package in Ubuntu:
Invalid
  Status in “drbd8” source package in Precise:
Fix Released
 
  Bug description:
Request for SRU:
[Impact]
DRBD will not work (hang) on fresh install using Ubuntu 12.04.3 media,
 and
will stop working on sites where the Raring Enablement Stacks is
 manually
installed as the API between older and newer drbd kernel modules has
changed.
 
[Fix]
The current version of drbd8 utils in Saucy/Raring can be compiled with
legacy utils enabled (basically drbdadm and drbdsetup) and
 automatically
switches to use the legacy version when an older kernel module is
 found.
Comparing the code of those two legacy tools showed them to be mostly
 the
same (except some things that actually look like bug fixes).
I only found two small issues, one was the init.d script which was
 changed
to use a new command of drbdadm to activate resources. This would fail
 if
drbdadm fell back to the legacy version. So I picked the shell function
that the current util uses and verified that this still works with the
 new
binary.
The other problem was the default config file which contained a new
 open
which would cause the legacy util to fail. It does not seem to be a
required one in the new tools to commenting it out by default seems to
work in both cases, too.
Lastly (this did not seem to be a real issue) the legacy tools claimed
 to
be a version 3.8.10 while the the code really looked like the 3.8.11
version we have in Precise. Since that also matches the version number
 of
the drbd module in Precise I modified the legacy tools version to be
3.8.11.
 
[Test Case]
For testing compatibility with the Precise 3.2 based kernels, either
 just
install the prepared package and verify everything still works as
 before
(before installing any HWE kernel). Or if already having installed a
 HWE
kernel and experiencing the issue, boot into the 3.2 kernel before
installing the proposed package (or follow the downgrade instructions
before booting back).
 
To test functionality with HWE kernels, install the Raring kernel in
Precise, install/configure DRBD: you get No response from the DRBD
driver! Is the module loaded?. With the proposed backport the mirror
continues to work. Only for switching back to an older kernel a
special procedure must be followed (see comment #21):
 
http://www.drbd.org/users-guide/s-downgrading-drbd84.html
 
---
 
I've just installed linux-generic-lts-raring on 12.04.2 and my drbd
 device
stoped working.
Seems like drbd8-utils is not compatible with DRBD 8.4 in Kernel 3.8.
I see that we can't upgrade the package since this would break
compatibility with the older Kernels in Precise.
 
But since the new Plans for the LTS-Enablement Stack [1] there should
be a package like drbd8-utils-lts-raring. And the dependancies should
be resolved automatically with apt.
 
kind regards
 
[1] https://wiki.ubuntu.com/Kernel/LTSEnablementStack
 
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.8.0-22-generic 3.8.0-22.33~precise1
ProcVersionSignature: Ubuntu 3.8.0-22.33~precise1-generic 3.8.11
Uname: Linux 3.8.0-22-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.2
Architecture: amd64
Date: Thu May 30 11:53:13 2013
InstallationMedia: Ubuntu-Server 12.04.1 LTS Precise Pangolin -
 Release
amd64 (20120817.3)
MarkForUpload: True
SourcePackage: linux-lts-raring
UpgradeStatus: No upgrade log present (probably fresh install)
 
  To manage notifications about this bug go to:
 
 https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+subscriptions
 

 --
 You received this 

Re: [Bug 1185756] Re: drbd8-utils not compatible with linux-lts-raring kernel in 12.04

[Rocco]

My clusters are configured to use Linbit:drbd which is:
/usr/lib/ocf/resource.d/linbit/drbd

and that file is in drbd8-utils



On Thu, Apr 24, 2014 at 10:45 AM, Christoph Mitasch 
cmita...@thomas-krenn.com wrote:

 Hello,

 the Linux Cluster Management Console (LCMC) makes it quite easy to setup a
 DRBD/Pacemaker cluster.
 http://lcmc.sourceforge.net/

 Christoph

 - Ursprüngliche Mail -
  Von: Stefan Bader stefan.ba...@canonical.com
  An: cmita...@thomas-krenn.com
  Gesendet: Donnerstag, 24. April 2014 10:35:01
  Betreff: [Bug 1185756] Re: drbd8-utils not compatible with
 linux-lts-raring kernel in 12.04
 
  @Andreas, that particular error is fixed by the test packages (see
  comment #60). There could be one in conjunction with pacemaker which
  reports an error about drbdadm syncer not being a valid command.
  Unfortunately I don't think anyone who is running a pacemaker cluster
  really can afford to help debugging as that causes disruptions.
 
  --
  You received this bug notification because you are subscribed to the bug
  report.
  https://bugs.launchpad.net/bugs/1185756
 
  Title:
drbd8-utils not compatible with linux-lts-raring kernel in 12.04
 
  Status in “drbd8” package in Ubuntu:
Invalid
  Status in “drbd8” source package in Precise:
Fix Released
 
  Bug description:
Request for SRU:
[Impact]
DRBD will not work (hang) on fresh install using Ubuntu 12.04.3 media,
 and
will stop working on sites where the Raring Enablement Stacks is
 manually
installed as the API between older and newer drbd kernel modules has
changed.
 
[Fix]
The current version of drbd8 utils in Saucy/Raring can be compiled with
legacy utils enabled (basically drbdadm and drbdsetup) and
 automatically
switches to use the legacy version when an older kernel module is
 found.
Comparing the code of those two legacy tools showed them to be mostly
 the
same (except some things that actually look like bug fixes).
I only found two small issues, one was the init.d script which was
 changed
to use a new command of drbdadm to activate resources. This would fail
 if
drbdadm fell back to the legacy version. So I picked the shell function
that the current util uses and verified that this still works with the
 new
binary.
The other problem was the default config file which contained a new
 open
which would cause the legacy util to fail. It does not seem to be a
required one in the new tools to commenting it out by default seems to
work in both cases, too.
Lastly (this did not seem to be a real issue) the legacy tools claimed
 to
be a version 3.8.10 while the the code really looked like the 3.8.11
version we have in Precise. Since that also matches the version number
 of
the drbd module in Precise I modified the legacy tools version to be
3.8.11.
 
[Test Case]
For testing compatibility with the Precise 3.2 based kernels, either
 just
install the prepared package and verify everything still works as
 before
(before installing any HWE kernel). Or if already having installed a
 HWE
kernel and experiencing the issue, boot into the 3.2 kernel before
installing the proposed package (or follow the downgrade instructions
before booting back).
 
To test functionality with HWE kernels, install the Raring kernel in
Precise, install/configure DRBD: you get No response from the DRBD
driver! Is the module loaded?. With the proposed backport the mirror
continues to work. Only for switching back to an older kernel a
special procedure must be followed (see comment #21):
 
http://www.drbd.org/users-guide/s-downgrading-drbd84.html
 
---
 
I've just installed linux-generic-lts-raring on 12.04.2 and my drbd
 device
stoped working.
Seems like drbd8-utils is not compatible with DRBD 8.4 in Kernel 3.8.
I see that we can't upgrade the package since this would break
compatibility with the older Kernels in Precise.
 
But since the new Plans for the LTS-Enablement Stack [1] there should
be a package like drbd8-utils-lts-raring. And the dependancies should
be resolved automatically with apt.
 
kind regards
 
[1] https://wiki.ubuntu.com/Kernel/LTSEnablementStack
 
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.8.0-22-generic 3.8.0-22.33~precise1
ProcVersionSignature: Ubuntu 3.8.0-22.33~precise1-generic 3.8.11
Uname: Linux 3.8.0-22-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.2
Architecture: amd64
Date: Thu May 30 11:53:13 2013
InstallationMedia: Ubuntu-Server 12.04.1 LTS Precise Pangolin -
 Release
amd64 (20120817.3)
MarkForUpload: True
SourcePackage: linux-lts-raring
UpgradeStatus: No upgrade log present (probably fresh install)
 
  To manage notifications about this bug go to:
 
 https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+subscriptions
 

 --
 You received this 

Re: [Bug 1185756] Re: drbd8-utils not compatible with linux-lts-raring kernel in 12.04

[Rocco]

On a side note, I'm not sure why a new package where released for the
raring stack? Is there a really brilliant reason for not having two
different packages?
On 23 Apr 2014 12:06, Stefan Bader stefan.ba...@canonical.com wrote:

 It is a bit odd. Ok, some warnings seems to be coming from pacemaker
 commands. Like the
 WARN: decode_transition_key: Bad UUID (crm-resource-3048) in sscanf result
 (3) for 0:0:crm-resource-3048

 I guess the problem is this:
 Apr 22 21:55:43 storage0 lrmd: [1242]: info: RA output:
 (p_drbd_bigpool:0:start:stderr) drbdadm: Unknown command 'syncer'
 Apr 22 21:55:43 storage0 drbd[3079]: ERROR: bigpool: Called drbdadm -c
 /etc/drbd.conf syncer bigpool

 This would mean that drbdadm did not pass control on drbdadm-83. And
 that would only happen if the current version did not seem to be 8.3.
 That version number looks to be read from /proc/drbd and would reflect
 the version of the kernel module.  At least as long as reading from
 /proc/drbd is not failing. Then it would fall back to a version number
 defined in the command (which would be wrong). Would have been
 interesting to find out whether calling drbdadm syncer bigpool
 manually would fail the same way but that would need another maintenance
 window. Maybe try to see what /proc/drbd is showing.

 I probably would suggest that we open a new bug report for the cluster
 case, so this one can be closed with the fix to drbdsetup. Then at least
 the direct usage seems to work.

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1185756

 Title:
   drbd8-utils not compatible with linux-lts-raring kernel in 12.04

 Status in “drbd8” package in Ubuntu:
   Invalid
 Status in “drbd8” source package in Precise:
   Fix Released

 Bug description:
   Request for SRU:
   [Impact]
   DRBD will not work (hang) on fresh install using Ubuntu 12.04.3 media,
 and will stop working on sites where the Raring Enablement Stacks is
 manually installed as the API between older and newer drbd kernel modules
 has changed.

   [Fix]
   The current version of drbd8 utils in Saucy/Raring can be compiled with
 legacy utils enabled (basically drbdadm and drbdsetup) and automatically
 switches to use the legacy version when an older kernel module is found.
 Comparing the code of those two legacy tools showed them to be mostly the
 same (except some things that actually look like bug fixes).
   I only found two small issues, one was the init.d script which was
 changed to use a new command of drbdadm to activate resources. This would
 fail if drbdadm fell back to the legacy version. So I picked the shell
 function that the current util uses and verified that this still works with
 the new binary.
   The other problem was the default config file which contained a new open
 which would cause the legacy util to fail. It does not seem to be a
 required one in the new tools to commenting it out by default seems to work
 in both cases, too.
   Lastly (this did not seem to be a real issue) the legacy tools claimed
 to be a version 3.8.10 while the the code really looked like the 3.8.11
 version we have in Precise. Since that also matches the version number of
 the drbd module in Precise I modified the legacy tools version to be 3.8.11.

   [Test Case]
   For testing compatibility with the Precise 3.2 based kernels, either
 just install the prepared package and verify everything still works as
 before (before installing any HWE kernel). Or if already having installed a
 HWE kernel and experiencing the issue, boot into the 3.2 kernel before
 installing the proposed package (or follow the downgrade instructions
 before booting back).

   To test functionality with HWE kernels, install the Raring kernel in
   Precise, install/configure DRBD: you get No response from the DRBD
   driver! Is the module loaded?. With the proposed backport the mirror
   continues to work. Only for switching back to an older kernel a
   special procedure must be followed (see comment #21):

   http://www.drbd.org/users-guide/s-downgrading-drbd84.html

   ---

   I've just installed linux-generic-lts-raring on 12.04.2 and my drbd
 device stoped working.
   Seems like drbd8-utils is not compatible with DRBD 8.4 in Kernel 3.8.
   I see that we can't upgrade the package since this would break
 compatibility with the older Kernels in Precise.

   But since the new Plans for the LTS-Enablement Stack [1] there should
   be a package like drbd8-utils-lts-raring. And the dependancies should
   be resolved automatically with apt.

   kind regards

   [1] https://wiki.ubuntu.com/Kernel/LTSEnablementStack

   ProblemType: Bug
   DistroRelease: Ubuntu 12.04
   Package: linux-image-3.8.0-22-generic 3.8.0-22.33~precise1
   ProcVersionSignature: Ubuntu 3.8.0-22.33~precise1-generic 3.8.11
   Uname: Linux 3.8.0-22-generic x86_64
   ApportVersion: 2.0.1-0ubuntu17.2
   Architecture: amd64
   Date: Thu May 30 11:53:13 2013
   InstallationMedia: 

[Bug 1185756] Re: drbd8-utils not compatible with linux-lts-raring kernel in 12.04

[Rocco]

~# cat /proc/drbd
version: 8.3.11 (api:88/proto:86-96)
srcversion: 93CE421BB73A731BDC72D8E

~# uname -a
Linux zed1 3.2.0-60-generic #91-Ubuntu

@smb I mean like it states in the header:
But since the new Plans for the LTS-Enablement Stack [1] there should be a 
package like drbd8-utils-lts-raring. And the dependancies should be resolved 
automatically with apt.

Why wasn't the new drbd userspace tools needed for the lts-raring stack
released as drbd8-utils-lts-raring? Then us people whom installed 12.04
during the beginning wouldn't be affected and people using the newer
12.04.x still could use drbd.

The state now is that people whom have upgraded to the raring stack are
fine (one of my clusters are that, but here I had to compile the drbd
tools myself to get drbd working since the old one provided didn't work,
AKA what this bug is about from the start), and everyone else is
borked So same problem just the other way around...

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1185756

Title:
  drbd8-utils not compatible with linux-lts-raring kernel in 12.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Re: [Bug 1185756] Re: drbd8-utils not compatible with linux-lts-raring kernel in 12.04

[Rocco]

On a side note, I'm not sure why a new package where released for the
raring stack? Is there a really brilliant reason for not having two
different packages?
On 23 Apr 2014 12:06, Stefan Bader stefan.ba...@canonical.com wrote:

 It is a bit odd. Ok, some warnings seems to be coming from pacemaker
 commands. Like the
 WARN: decode_transition_key: Bad UUID (crm-resource-3048) in sscanf result
 (3) for 0:0:crm-resource-3048

 I guess the problem is this:
 Apr 22 21:55:43 storage0 lrmd: [1242]: info: RA output:
 (p_drbd_bigpool:0:start:stderr) drbdadm: Unknown command 'syncer'
 Apr 22 21:55:43 storage0 drbd[3079]: ERROR: bigpool: Called drbdadm -c
 /etc/drbd.conf syncer bigpool

 This would mean that drbdadm did not pass control on drbdadm-83. And
 that would only happen if the current version did not seem to be 8.3.
 That version number looks to be read from /proc/drbd and would reflect
 the version of the kernel module.  At least as long as reading from
 /proc/drbd is not failing. Then it would fall back to a version number
 defined in the command (which would be wrong). Would have been
 interesting to find out whether calling drbdadm syncer bigpool
 manually would fail the same way but that would need another maintenance
 window. Maybe try to see what /proc/drbd is showing.

 I probably would suggest that we open a new bug report for the cluster
 case, so this one can be closed with the fix to drbdsetup. Then at least
 the direct usage seems to work.

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1185756

 Title:
   drbd8-utils not compatible with linux-lts-raring kernel in 12.04

 Status in “drbd8” package in Ubuntu:
   Invalid
 Status in “drbd8” source package in Precise:
   Fix Released

 Bug description:
   Request for SRU:
   [Impact]
   DRBD will not work (hang) on fresh install using Ubuntu 12.04.3 media,
 and will stop working on sites where the Raring Enablement Stacks is
 manually installed as the API between older and newer drbd kernel modules
 has changed.

   [Fix]
   The current version of drbd8 utils in Saucy/Raring can be compiled with
 legacy utils enabled (basically drbdadm and drbdsetup) and automatically
 switches to use the legacy version when an older kernel module is found.
 Comparing the code of those two legacy tools showed them to be mostly the
 same (except some things that actually look like bug fixes).
   I only found two small issues, one was the init.d script which was
 changed to use a new command of drbdadm to activate resources. This would
 fail if drbdadm fell back to the legacy version. So I picked the shell
 function that the current util uses and verified that this still works with
 the new binary.
   The other problem was the default config file which contained a new open
 which would cause the legacy util to fail. It does not seem to be a
 required one in the new tools to commenting it out by default seems to work
 in both cases, too.
   Lastly (this did not seem to be a real issue) the legacy tools claimed
 to be a version 3.8.10 while the the code really looked like the 3.8.11
 version we have in Precise. Since that also matches the version number of
 the drbd module in Precise I modified the legacy tools version to be 3.8.11.

   [Test Case]
   For testing compatibility with the Precise 3.2 based kernels, either
 just install the prepared package and verify everything still works as
 before (before installing any HWE kernel). Or if already having installed a
 HWE kernel and experiencing the issue, boot into the 3.2 kernel before
 installing the proposed package (or follow the downgrade instructions
 before booting back).

   To test functionality with HWE kernels, install the Raring kernel in
   Precise, install/configure DRBD: you get No response from the DRBD
   driver! Is the module loaded?. With the proposed backport the mirror
   continues to work. Only for switching back to an older kernel a
   special procedure must be followed (see comment #21):

   http://www.drbd.org/users-guide/s-downgrading-drbd84.html

   ---

   I've just installed linux-generic-lts-raring on 12.04.2 and my drbd
 device stoped working.
   Seems like drbd8-utils is not compatible with DRBD 8.4 in Kernel 3.8.
   I see that we can't upgrade the package since this would break
 compatibility with the older Kernels in Precise.

   But since the new Plans for the LTS-Enablement Stack [1] there should
   be a package like drbd8-utils-lts-raring. And the dependancies should
   be resolved automatically with apt.

   kind regards

   [1] https://wiki.ubuntu.com/Kernel/LTSEnablementStack

   ProblemType: Bug
   DistroRelease: Ubuntu 12.04
   Package: linux-image-3.8.0-22-generic 3.8.0-22.33~precise1
   ProcVersionSignature: Ubuntu 3.8.0-22.33~precise1-generic 3.8.11
   Uname: Linux 3.8.0-22-generic x86_64
   ApportVersion: 2.0.1-0ubuntu17.2
   Architecture: amd64
   Date: Thu May 30 11:53:13 2013
   InstallationMedia: 

[Bug 1185756] Re: drbd8-utils not compatible with linux-lts-raring kernel in 12.04

[Rocco]

~# cat /proc/drbd
version: 8.3.11 (api:88/proto:86-96)
srcversion: 93CE421BB73A731BDC72D8E

~# uname -a
Linux zed1 3.2.0-60-generic #91-Ubuntu

@smb I mean like it states in the header:
But since the new Plans for the LTS-Enablement Stack [1] there should be a 
package like drbd8-utils-lts-raring. And the dependancies should be resolved 
automatically with apt.

Why wasn't the new drbd userspace tools needed for the lts-raring stack
released as drbd8-utils-lts-raring? Then us people whom installed 12.04
during the beginning wouldn't be affected and people using the newer
12.04.x still could use drbd.

The state now is that people whom have upgraded to the raring stack are
fine (one of my clusters are that, but here I had to compile the drbd
tools myself to get drbd working since the old one provided didn't work,
AKA what this bug is about from the start), and everyone else is
borked So same problem just the other way around...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756

Title:
  drbd8-utils not compatible with linux-lts-raring kernel in 12.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1185756] Re: drbd8-utils not compatible with linux-lts-raring kernel in 12.04

[Rocco]

Also lost my slave on prod system today, pacemaker,crm cluster with
drbd.

lrmd: [1952]: info: RA output: (res_drbd_1:1:monitor:stderr) Could not
connect to 'drbd' generic netlink family

My resources are marked as Unconfigured on slave, but still Primary on
master.

Have not rebooted.

What is the best way of getting back on track? Link one of both of the
binaries to /usr/local/bin and restart cluster/drbd?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1185756

Title:
  drbd8-utils not compatible with linux-lts-raring kernel in 12.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1185756] Re: drbd8-utils not compatible with linux-lts-raring kernel in 12.04

[Rocco]

Linking the /lib/drbd/drbdsetup-8.3 to /sbin did NOT solve the problem
for me. Had to revert to to old packages then everyting worked after
cluster restart.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1185756

Title:
  drbd8-utils not compatible with linux-lts-raring kernel in 12.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1185756] Re: drbd8-utils not compatible with linux-lts-raring kernel in 12.04

[Rocco]

@smb I'm afraid I can't. The problem with the upgrade of drbd8-utils
cause downtime on your main (production) DB-cluster today.

I can look though the logs tomorrow, but it was the drbd ocf
master/slave in pacemaker that was failing, causing drbd to get
unconfigured on both nodes.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1185756

Title:
  drbd8-utils not compatible with linux-lts-raring kernel in 12.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1185756] Re: drbd8-utils not compatible with linux-lts-raring kernel in 12.04

[Rocco]

Also lost my slave on prod system today, pacemaker,crm cluster with
drbd.

lrmd: [1952]: info: RA output: (res_drbd_1:1:monitor:stderr) Could not
connect to 'drbd' generic netlink family

My resources are marked as Unconfigured on slave, but still Primary on
master.

Have not rebooted.

What is the best way of getting back on track? Link one of both of the
binaries to /usr/local/bin and restart cluster/drbd?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756

Title:
  drbd8-utils not compatible with linux-lts-raring kernel in 12.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1185756] Re: drbd8-utils not compatible with linux-lts-raring kernel in 12.04

[Rocco]

Linking the /lib/drbd/drbdsetup-8.3 to /sbin did NOT solve the problem
for me. Had to revert to to old packages then everyting worked after
cluster restart.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756

Title:
  drbd8-utils not compatible with linux-lts-raring kernel in 12.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1185756] Re: drbd8-utils not compatible with linux-lts-raring kernel in 12.04

[Rocco]

@smb I'm afraid I can't. The problem with the upgrade of drbd8-utils
cause downtime on your main (production) DB-cluster today.

I can look though the logs tomorrow, but it was the drbd ocf
master/slave in pacemaker that was failing, causing drbd to get
unconfigured on both nodes.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756

Title:
  drbd8-utils not compatible with linux-lts-raring kernel in 12.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1185756/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1262526] [NEW] JAXP00010001

[Rocco]

Public bug reported:

This bug just went live on precise security in:

Installed: 6b27-1.12.6-1ubuntu0.12.04.4

https://bugs.openjdk.java.net/browse/JDK-8028111
http://vaguehope.com/2013/10/jdk-1-7-0_45-xml-and-jaxp00010001/

Crashes my web app in tomcat pretty quick.

** Affects: openjdk-6 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262526

Title:
  JAXP00010001

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/1262526/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 651104] Re: intel graphics turbo disabled

[rocco]

I have started to get this problem on my Dell E6510 with ubuntu 12.04 64
Bit starting with Kernel 3.2.0.-52.78, in 3.2.0.-53.81 it is still
there. Seems like the system is booting and performing worse than
before. With the old kernel the error is not there. Have a very bad
feeling about automatical updates since then. The bug seems confirmed
for 3 years, hm, so, I confirm it again :)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/651104

Title:
  intel graphics turbo disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/651104/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1185756] Re: drbd8-utils not compatible with linux-lts-raring kernel in 12.04

[Rocco]

Same problem. Installed 2 server both 12.04.3. Drdb complaining in
cluster configuration.

ERROR: drbd config error: DRBD module version: 8.4.2
   userland version: 8.3.11
you should upgrade your drbd tools!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185756

Title:
  drbd8-utils not compatible with linux-lts-raring kernel in 12.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1185756/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1217900] [NEW] Drbd unusable.

[Rocco]

Public bug reported:

Installed two new servers from ubuntu 12.04.3 lts cd (from usb-stick).
This comes with linux-generic-lts-raring enabled. Drbd userland tools
has not been updated and that makes drbd unusable on this LTS system.

root@wolf1:/etc/drbd.d# drbdadm create-md r0
DRBD module version: 8.4.2
   userland version: 8.3.11
you should upgrade your drbd tools!

Please rectify immediately! 
ii  linux-generic-lts-raring3.8.0.29.29

** Affects: linux-meta-lts-raring (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217900

Title:
  Drbd unusable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-raring/+bug/1217900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1088177] [NEW] Crash during installation

[Rocco Vicedomini]

Public bug reported:

C

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: ubiquity 2.12.16 [modified: 
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 3.5.0-17.18-lowlatency 3.5.5
Uname: Linux 3.5.0-17-lowlatency i686
ApportVersion: 2.6.1-0ubuntu3
Architecture: i386
CasperVersion: 1.328
Date: Sun Dec  9 14:00:02 2012
InstallCmdLine: file=/cdrom/preseed/ubuntustudio.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- debian-installer/language=it 
keyboard-configuration/layoutcode?=it
LiveMediaBuild: Ubuntu-Studio 12.10 Quantal Quetzal - Release i386 
(20121017.1)
ProcEnviron:
 LANGUAGE=it_IT.UTF-8
 TERM=linux
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 quantal ubiquity-2.12.16

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088177

Title:
  Crash during installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1088177/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1028244] [NEW] Ubuntu wont boot from usb

[Rocco Molinelli]

Public bug reported:

I have extracted ubuntu 12.04 to my Gigaware Fat32 USB and when it boots
a black screen shows up that says the SYSLINUX copyright.

** Affects: bootcd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1028244

Title:
  Ubuntu wont boot from usb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bootcd/+bug/1028244/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 984132] Re: telepathy-gabble increasingly high cpu usage with jabber - Error log included

[Rocco]

I have the same problem also with iChat user over jabber.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/984132

Title:
  telepathy-gabble increasingly high cpu usage with jabber - Error log
  included

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-gabble/+bug/984132/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 701765] Re: Unknown: Failed opening required '/usr/share/phpmyadmin/index.php' (include_path='.') in Unknown on line 0

[Rocco]

Same problem with Hardy and php 5.2, libapache2-mod-php5
5.2.4-2ubuntu5.13. Problem started just now after security upgrade.
Affected all my sites. Had to remove trailing slash to get it working
again, even if that will include more directories potentially. BIG
problem.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in ubuntu.
https://bugs.launchpad.net/bugs/701765

Title:
  Unknown: Failed opening required '/usr/share/phpmyadmin/index.php'
  (include_path='.') in Unknown on line 0

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 701765] Re: Unknown: Failed opening required '/usr/share/phpmyadmin/index.php' (include_path='.') in Unknown on line 0

[Rocco]

Same problem with Hardy and php 5.2, libapache2-mod-php5
5.2.4-2ubuntu5.13. Problem started just now after security upgrade.
Affected all my sites. Had to remove trailing slash to get it working
again, even if that will include more directories potentially. BIG
problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/701765

Title:
  Unknown: Failed opening required '/usr/share/phpmyadmin/index.php'
  (include_path='.') in Unknown on line 0

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 628844] [NEW] package linux-image-2.6.32-24-generic 2.6.32-24.42 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Paul Rocco]

Public bug reported:

Binary package hint: grub

installation reported missing menu.lst 
I did not have a menu.lst as the default install of 10.04 used Grub2 (grub.cfg 
vs. menu.lst).  I wasn't sure what would happen if I selected Y when asked if I 
wanted the installer to create a new menu.lst so I selected N.
I then received this error.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-24-generic 2.6.32-24.42
ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
NonfreeKernelModules: fglrx
Architecture: i386
Date: Wed Sep  1 12:36:09 2010
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5)
SourcePackage: grub
Title: package linux-image-2.6.32-24-generic 2.6.32-24.42 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1

** Affects: grub (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 lucid

-- 
package linux-image-2.6.32-24-generic 2.6.32-24.42 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/628844
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 628844] Re: package linux-image-2.6.32-24-generic 2.6.32-24.42 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Paul Rocco]

** Attachment added: AptOrdering.txt
   
https://bugs.launchpad.net/bugs/628844/+attachment/1537342/+files/AptOrdering.txt

** Attachment added: Dependencies.txt
   
https://bugs.launchpad.net/bugs/628844/+attachment/1537343/+files/Dependencies.txt

** Attachment added: Df.txt
   https://bugs.launchpad.net/bugs/628844/+attachment/1537344/+files/Df.txt

** Attachment added: Dmesg.txt
   https://bugs.launchpad.net/bugs/628844/+attachment/1537345/+files/Dmesg.txt

** Attachment added: DpkgTerminalLog.txt
   
https://bugs.launchpad.net/bugs/628844/+attachment/1537346/+files/DpkgTerminalLog.txt

-- 
package linux-image-2.6.32-24-generic 2.6.32-24.42 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/628844
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 578804] [NEW] notification for upgrades not shown.

[Rocco]

Public bug reported:

Binary package hint: kubuntu-notification-helper

Aptitude show 8 upgrades, but I have not gotten any notification from
the Helper during the whole day. System is upgraded from 9.10 to 10.04,
via internet download.

aptitude safe-upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Reading extended state information  
Initializing package states... Done
The following packages will be upgraded:
  nvidia-185-modaliases nvidia-current nvidia-current-modaliases 
python-cupshelpers system-config-printer-common system-config-printer-udev 
update-manager-core update-manager-kde 
The following packages are RECOMMENDED but will NOT be installed:
  nvidia-settings 
8 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 41.3MB of archives. After unpacking 8,192B will be used.
Do you want to continue? [Y/n/?] n

** Affects: kubuntu-notification-helper (Ubuntu)
 Importance: Undecided
 Status: New

** Summary changed:

- notification for upgrades not show.
+ notification for upgrades not shown.

-- 
notification for upgrades not shown.
https://bugs.launchpad.net/bugs/578804
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 474698] Re: vpnc doesn't connect with empty user password.

[Rocco]

Naah it's not fixed in Lucid either.

Here is a connections to a Cisco VPN with the Always Ask selected for the the 
user password:
Apr 18 19:18:58 vostro1 NetworkManager: info  Starting VPN service 
'org.freedesktop.NetworkManager.vpnc'...
Apr 18 19:18:58 vostro1 NetworkManager: info  VPN service 
'org.freedesktop.NetworkManager.vpnc' started 
(org.freedesktop.NetworkManager.vpnc), PID 4947
Apr 18 19:18:58 vostro1 NetworkManager: info  VPN service 
'org.freedesktop.NetworkManager.vpnc' just appeared, activating connections
Apr 18 19:18:58 vostro1 NetworkManager: info  VPN plugin state changed: 1
Apr 18 19:18:58 vostro1 NetworkManager: info  VPN plugin state changed: 3
Apr 18 19:18:58 vostro1 NetworkManager: info  VPN connection 'IPIT' (Connect) 
reply received.
Apr 18 19:18:58 vostro1 NetworkManager: info  VPN plugin failed: 1
Apr 18 19:18:58 vostro1 NetworkManager: info  VPN plugin state changed: 6
Apr 18 19:18:58 vostro1 NetworkManager: info  VPN plugin state change reason: 0
Apr 18 19:18:58 vostro1 NetworkManager: WARN  connection_state_changed(): 
Could not process the request because no VPN connection was active.
Apr 18 19:18:58 vostro1 NetworkManager: info  Policy set 'Auto eth0' (eth0) 
as default for routing and DNS.
Apr 18 19:19:11 vostro1 NetworkManager: debug [1271611151.002097] 
ensure_killed(): waiting for vpn service pid 4947 to exit
Apr 18 19:19:11 vostro1 NetworkManager: debug [1271611151.002299] 
ensure_killed(): vpn service pid 4947 cleaned up
Apr 18 19:19:42 vostro1 NetworkManager: info  Starting VPN service 
'org.freedesktop.NetworkManager.vpnc'...
Apr 18 19:19:42 vostro1 NetworkManager: info  VPN service 
'org.freedesktop.NetworkManager.vpnc' started 
(org.freedesktop.NetworkManager.vpnc), PID 5006

And one with the onetime password entered and Store selected:
Apr 18 19:20:54 vostro1 NetworkManager: info  Starting VPN service 
'org.freedesktop.NetworkManager.vpnc'...
Apr 18 19:20:54 vostro1 NetworkManager: info  VPN service 
'org.freedesktop.NetworkManager.vpnc' started 
(org.freedesktop.NetworkManager.vpnc), PID 5018
Apr 18 19:20:54 vostro1 NetworkManager: info  VPN service 
'org.freedesktop.NetworkManager.vpnc' just appeared, activating connections
Apr 18 19:20:54 vostro1 NetworkManager: info  VPN plugin state changed: 3
Apr 18 19:20:54 vostro1 NetworkManager: info  VPN connection 'IPIT' (Connect) 
reply received.
Apr 18 19:20:54 vostro1 NetworkManager:SCPlugin-Ifupdown: devices added 
(path: /sys/devices/virtual/net/tun0, iface: tun0)
Apr 18 19:20:54 vostro1 NetworkManager:SCPlugin-Ifupdown: device added 
(path: /sys/devices/virtual/net/tun0, iface: tun0): no ifupdown configuration 
found.
Apr 18 19:20:57 vostro1 NetworkManager: info  VPN connection 'IPIT' (IP 
Config Get) reply received.
Apr 18 19:20:57 vostro1 NetworkManager: info  VPN Gateway: XXX.XXX.XXX.XXX
Apr 18 19:20:57 vostro1 NetworkManager: info  Tunnel Device: tun0
Apr 18 19:20:57 vostro1 NetworkManager: info  Internal IP4 Address: 
XXX.XXX.XXX.XXX
Apr 18 19:20:57 vostro1 NetworkManager: info  Internal IP4 Prefix: 24
Apr 18 19:20:57 vostro1 NetworkManager: info  Internal IP4 Point-to-Point 
Address: XXX.XXX.XXX.XXX
Apr 18 19:20:57 vostro1 NetworkManager: info  Maximum Segment Size (MSS): 0
Apr 18 19:20:57 vostro1 NetworkManager: info  Static Route: 
XXX.XXX.XXX.XXX/24   Next Hop: XXX.XXX.XXX.XXX
Apr 18 19:20:57 vostro1 NetworkManager: info  Internal IP4 DNS: 
XXX.XXX.XXX.XXX
Apr 18 19:20:57 vostro1 NetworkManager: info  Internal IP4 DNS: 
XXX.XXX.XXX.XXX
Apr 18 19:20:57 vostro1 NetworkManager: info  DNS Domain: '(none)'
Apr 18 19:20:57 vostro1 NetworkManager: info  Login Banner:
Apr 18 19:20:57 vostro1 NetworkManager: info  
-
Apr 18 19:20:57 vostro1 NetworkManager: info  (null)
Apr 18 19:20:57 vostro1 NetworkManager: info  
-
Apr 18 19:20:57 vostro1 vpnc[5021]: can't open pidfile /var/run/vpnc/pid for 
writing
Apr 18 19:20:58 vostro1 NetworkManager: info  VPN connection 'IPIT' (IP 
Config Get) complete.
Apr 18 19:20:58 vostro1 NetworkManager: info  Policy set 'IPIT' (tun0) as 
default for routing and DNS.
Apr 18 19:20:58 vostro1 NetworkManager: info  VPN plugin state changed: 4

Hopefully it will be really fixed before release.

-- 
vpnc doesn't connect with empty user password.
https://bugs.launchpad.net/bugs/474698
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to plasma-widget-networkmanagement in ubuntu.

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 474698] Re: vpnc doesn't connect with empty user password.

[Rocco]

Hmm  Jonathan, not sure what you are saying, since once I have stored my
one time password in the network-manager I can connect (once obviously).
But when connecting with the Always Ask, nothing happens in the gui,
and the log entries are produced. The routing as 294394 is about, works
OK once connected.

-- 
vpnc doesn't connect with empty user password.
https://bugs.launchpad.net/bugs/474698
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 478487] Re: usbmount cannnot execute /lib/udev/vol_id

[Rocco]

Would be nice if this was fixed for Karmic.

-- 
usbmount cannnot execute /lib/udev/vol_id
https://bugs.launchpad.net/bugs/478487
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 526452] [NEW] ipsec status doesn't return that pluto is running when it is.

[Rocco]

Public bug reported:

Binary package hint: openswan

r...@ollo:/etc# /etc/init.d/ipsec status
defaulting leftsubnet to 192.168.x.x
defaulting rightsubnet to 10.1.x.x
defaulting leftsubnet to 192.168.x.x
defaulting rightsubnet to 10.3.x.x
IPsec stopped
but...
has /var/run/pluto/ipsec.info file!
An normal Pluto is active?
some (12) eroutes exist!

In the scenario about /etc/init.d/ipsec start has just been run. And
pluto is running, still status doesn't return OK.

ii  openswan  1:2.6.22+dfsg-1.1ubuntu1
Karmic up to date.

** Affects: openswan (Ubuntu)
 Importance: Undecided
 Status: New

-- 
ipsec status doesn't return that pluto is running when it is.
https://bugs.launchpad.net/bugs/526452
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 526452] Re: ipsec status doesn't return that pluto is running when it is.

[Rocco]

The reason for this is that _realsetup checks for
/var/lock/subsys/ipsec, and /etc/init.d/ipsec does create mkdir -p
/var/lock/subsys any longer.

-- 
ipsec status doesn't return that pluto is running when it is.
https://bugs.launchpad.net/bugs/526452
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 483492] [NEW] [karmic] update-notifier-kde doesn't inform about updates if computer isn't restarted.

[Rocco]

Public bug reported:

Binary package hint: update-notifier-kde

I guess that update-notifier-kde should look at /var/lib/update-notifier
/updates-available or similar file to find out if there are any updates
available.

Users doesn't get informed about new updates, at least if computer as
been on for several days. Rebooting daily looks to trigger the updates
to be displayed some time after reboot. But running the computer for
several days, doesn't show new updates. Which is a problem.

** Affects: update-notifier-kde (Ubuntu)
 Importance: Undecided
 Status: New

-- 
[karmic] update-notifier-kde doesn't inform about updates if computer isn't 
restarted.
https://bugs.launchpad.net/bugs/483492
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to update-notifier-kde in ubuntu.

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 474698] [NEW] vpnc doesn't connect with empty user password.

[Rocco]

Public bug reported:

Binary package hint: plasma-widget-networkmanagement

In Karmic a vpnc connection configured with user password set to always
ask doesn't connect.

Changing to Store, and entering the password connects to vpn.

This is a major problem since the password is a onetime password, makes
the whole thing unusable for me.

** Affects: plasma-widget-networkmanagement (Ubuntu)
 Importance: Undecided
 Status: New

-- 
vpnc doesn't connect with empty user password.
https://bugs.launchpad.net/bugs/474698
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to plasma-widget-networkmanagement in ubuntu.

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 334122] Re: Mobile broadband connections fail to connect

[Rocco]

The Gnome nm-applet works OK, so I had to switch to that instead.  I
don't like running gnome apps on my KDE desktop, and not in systray, but
if I should be able to work with my computer, well then the change was
inevitable.

I've also seen screenshot of KDE developers using nm-appet, so it might
have been the wrong decision from Ubuntu to break networking in Kubuntu
two releases in a row, by releasing with to early release of software
which isn't finished yet.

-- 
Mobile broadband connections fail to connect
https://bugs.launchpad.net/bugs/334122
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 392018] Re: [karmic] kmail doesn't start

[Rocco]

It worked a couple of days, but broke again, I think I installed some
updates to akonadi a couple days ago and that that broke it. I installed
kdepim-dbg, but trying to help out and doing a backtrace also
fails..

~$ cat gdb-kmail.txt
GNU gdb (GDB) 7.0-ubuntu
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/bin/kmail...Reading symbols from 
/usr/lib/debug/usr/bin/kmail...done.
(no debugging symbols found)...done.
(gdb) handle SIG33 pass nostop noprint
SignalStop  Print   Pass to program Description
SIG33 NoNo  Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/kmail
[Thread debugging using libthread_db enabled]
unknown program name(2774)/: Communication problem with  kmail , it 
probably crashed.
Error message was:  org.freedesktop.DBus.Error.NoReply :  Message did not 
receive a reply (timeout by message bus) 


Program exited with code 0377.
(gdb) backtrace full
No stack.
(gdb) info registers
The program has no registers now.
(gdb)  x/16i $pc
No registers.
(gdb) thread apply all backtrace
(gdb) quit


:kmail

unknown program name(8519)/: Communication problem with  kmail , it
probably crashed.

Error message was:  org.freedesktop.DBus.Error.NoReply :  Message
did not receive a reply (timeout by message bus) 

-- 
[karmic] kmail doesn't start
https://bugs.launchpad.net/bugs/392018
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 392018] Re: [karmic] kmail doesn't start

[Rocco]

My kmail stopped working a couple of days ago with same problem..

[~]:kmail
unknown program name(4347)/: Communication problem with  kmail , it 
probably crashed.
Error message was:  org.freedesktop.DBus.Error.NoReply :  Message did not 
receive a reply (timeout by message bus) 

It has been working great for weeks in Karmic but now it's not possible
to start.

Karmic x86_64 up to date.

-- 
[karmic] kmail doesn't start
https://bugs.launchpad.net/bugs/392018
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 451426] [NEW] Not possible to connect to mobile broadband. at all, again...

[Rocco]

Public bug reported:

Binary package hint: plasma-widget-networkmanagement

nm-applet works OK in Karmic, but plasma-widget-networkmanagement still can't 
connect to mobile broadband. When clicking on a correctly configured mobile 
broadband, there is no visual information on screen that something is 
happening. And there is nothing happening in logs either. In config file no 
baud is set which is odd:
[serial]
baud=0
bits=0
parity=
senddelay=0
stopbits=0

daemon.log spits out:
NetworkManager: WARN  user_connection_get_settings_cb(): 
user_connection_get_settings_cb: Invalid connection: 'NMSettingSerial' / 
'(null)' invalid: 3

Which probably is related.

This is a big show stopper since it wasn't working OK in jaunty either.
Please, please investigate before release.

** Affects: plasma-widget-networkmanagement (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Not possible to connect to mobile broadband. at all, again...
https://bugs.launchpad.net/bugs/451426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 450851] Re: ubuntu-bug fails with most recent karmic kubuntu updates

[Rocco]

My output is:

#ubuntu-bug apport
Could not import module, is a package upgrade in progress? Error: No module 
named kdecore

On a up to date Kubuntu Karmic.

-- 
ubuntu-bug fails with most recent karmic kubuntu updates
https://bugs.launchpad.net/bugs/450851
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 339716] Network Manager fails to connect

[Michael Rocco Sabino]

Those problems seem to be gone. I had a few year old Compaq Presario
that was having some trouble which I gave away, but more recently my XPS
M1530 has begun to work much better in regards to Network Manager in
Ubuntu.

Michael Sabino

- Original Message -
From: Pedro Villavicencio pe...@ubuntu.com
Date: Thursday, September 3, 2009 10:15 am
Subject: [Bug 339716] Network Manager fails to connect
To: m-sab...@neiu.edu

 Thank you for taking the time to report this bug and helping to make
 Ubuntu better. You reported this bug a while ago and there 
 hasn't been
 any activity in it recently. We were wondering is this still an issue
 for you? Do you get the same with Karmic? Thanks in advance.
 
 ** Changed in: network-manager (Ubuntu)
    Status: New = Incomplete
 
 -- 
 Network Manager fails to connect
 https://bugs.launchpad.net/bugs/339716
 You received this bug notification because you are a direct subscriber
 of the bug.
 
 Status in “network-manager” package in Ubuntu: Incomplete
 
 Bug description:
 Binary package hint: network-manager
 
 NetworkManager fails to connect to a hidden ssid using broadcom 
 b43 wireless in jaunty alpha 5. Upgrading alpha 5 to the current 
 daily build causes even non-network manager-initiated 
 connections to wireless to break.
 
 Description:  Ubuntu jaunty (development branch)
 Release:  9.04
 
 
 network-manager:
   Installed: 0.7.1~rc1+20090220-0ubuntu1
   Candidate: 0.7.1~rc3-0ubuntu1
   Version table:
  0.7.1~rc3-0ubuntu1 0
     500 
 http://us.archive.ubuntu.com jaunty/main Packages
  *** 0.7.1~rc1+20090220-0ubuntu1 0
     100 /var/lib/dpkg/status

-- 
Network Manager fails to connect
https://bugs.launchpad.net/bugs/339716
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 414576] Re: systemsettings crashed with SIGSEGV in polkit_authorization_db_is_caller_authorized()

[Rocco]

Same problem on up to date Karmic Kubuntu. One click on PolicyKit
Authorization in System Settings and bang crash...

-- 
systemsettings crashed with SIGSEGV in 
polkit_authorization_db_is_caller_authorized()
https://bugs.launchpad.net/bugs/414576
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 436748] Re: polkit-kde-manager assert failure: *** glibc detected *** polkit-kde-manager: double free or corruption (fasttop): 0x089cb310 ***

[Rocco]

Confirmed that is works OK when policykit installed manually.

-- 
polkit-kde-manager assert failure: *** glibc detected *** polkit-kde-manager: 
double free or corruption (fasttop): 0x089cb310 ***
https://bugs.launchpad.net/bugs/436748
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu.

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 411574] Re: [karmic] No sound on Intel 82801H HD Audio

[Michael Rocco Sabino]

I can also confirm this bug on amd64 as well.

-- 
[karmic] No sound on Intel 82801H HD Audio
https://bugs.launchpad.net/bugs/411574
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 381825] [NEW] gnome-terminal resizes to 80 characters width when attaching to a screen session

[Rocco Stanzione]

Public bug reported:

Binary package hint: gnome-terminal

When I create or attach to a screen session in gnome-terminal, locally
or over ssh, the window resizes to an 80 character width.  Height is not
affected.  This behavior is new in Jaunty, and there doesn't seem to be
a setting that affects it.

** Affects: gnome-terminal (Ubuntu)
 Importance: Undecided
 Status: New

-- 
gnome-terminal resizes to 80 characters width when attaching to a screen session
https://bugs.launchpad.net/bugs/381825
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 357108] Re: During file transfer, the GNOME file browser appears but is in an incomplete and unusable state.

[Rocco Rossi]

will do so as soon as possible. i'll be upgrading the next few days.

2009/4/29 Sebastien Bacher seb...@ubuntu.com

 could you try on jaunty?

 --
 During file transfer, the GNOME file browser appears but is in an
 incomplete and unusable state.
 https://bugs.launchpad.net/bugs/357108
 You received this bug notification because you are a direct subscriber
 of the bug.


-- 
During file transfer, the GNOME file browser appears but is in an incomplete 
and unusable state.
https://bugs.launchpad.net/bugs/357108
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 357108] Re: During file transfer, the GNOME file browser appears but is in an incomplete and unusable state.

[Rocco Rossi]

No, not easily reproducible I believe. It doesn't  happen often, just
occasionally, but it's there.

2009/4/9 Sebastien Bacher seb...@ubuntu.com

 Thank you for taking the time to report this bug and helping to make Ubuntu
 better. Please answer these questions:

  * Is this reproducible?
  * If so, what specific steps should we take to recreate this bug?

  This will help us to find and resolve the problem.

 ** Changed in: pidgin (Ubuntu)
   Importance: Undecided = Low

 ** Changed in: pidgin (Ubuntu)
   Status: New = Incomplete

 --
 During file transfer, the GNOME file browser appears but is in an
 incomplete and unusable state.
 https://bugs.launchpad.net/bugs/357108
 You received this bug notification because you are a direct subscriber
 of the bug.


-- 
During file transfer, the GNOME file browser appears but is in an incomplete 
and unusable state.
https://bugs.launchpad.net/bugs/357108
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 357108] [NEW] During file transfer, the GNOME file browser appears but is in an incomplete and unusable state.

[Rocco Rossi]

Public bug reported:

Binary package hint: pidgin

During file transfer, the GNOME file browser appears but is in an
incomplete and unusable state. The only thing one can do is CANCEL the
operation.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia
Package: pidgin 1:2.5.5-1~getdeb1
ProcEnviron:
 
PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: pidgin
Uname: Linux 2.6.27-12-generic i686
UnreportableReason: Questo non è un pacchetto Ubuntu genuino

** Affects: pidgin (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug

-- 
During file transfer, the GNOME file browser appears but is in an incomplete 
and unusable state.
https://bugs.launchpad.net/bugs/357108
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 357108] Re: During file transfer, the GNOME file browser appears but is in an incomplete and unusable state.

[Rocco Rossi]

** Attachment added: Dependencies.txt
   http://launchpadlibrarian.net/24964503/Dependencies.txt

** Attachment added: ProcMaps.txt
   http://launchpadlibrarian.net/24964505/ProcMaps.txt

** Attachment added: ProcStatus.txt
   http://launchpadlibrarian.net/24964507/ProcStatus.txt

-- 
During file transfer, the GNOME file browser appears but is in an incomplete 
and unusable state.
https://bugs.launchpad.net/bugs/357108
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 338251] Re: konsole 4.2.1 word boundary text selection

[Rocco]

This is fixed in Jaunty.

-- 
konsole 4.2.1 word boundary text selection
https://bugs.launchpad.net/bugs/338251
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 338251] Re: konsole 4.2.1 word boundary text selection

[Rocco]

A temp fix, which isn't 100%, is to remove everything in the word
characters for double-click selection setting, then it will work more or
less as before.

-- 
konsole 4.2.1 word boundary text selection
https://bugs.launchpad.net/bugs/338251
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase in ubuntu.

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 339716] [NEW] Network Manager fails to connect

[Michael Rocco Sabino]

Public bug reported:

Binary package hint: network-manager

NetworkManager fails to connect to a hidden ssid using broadcom b43
wireless in jaunty alpha 5. Upgrading alpha 5 to the current daily build
causes even non-network manager-initiated connections to wireless to
break.

Description:Ubuntu jaunty (development branch)
Release:9.04


network-manager:
  Installed: 0.7.1~rc1+20090220-0ubuntu1
  Candidate: 0.7.1~rc3-0ubuntu1
  Version table:
 0.7.1~rc3-0ubuntu1 0
500 http://us.archive.ubuntu.com jaunty/main Packages
 *** 0.7.1~rc1+20090220-0ubuntu1 0
100 /var/lib/dpkg/status

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Network Manager fails to connect
https://bugs.launchpad.net/bugs/339716
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 339716] Re: Network Manager fails to connect

[Michael Rocco Sabino]

Temporary workaround (for alpha 5)

-b43netfix.sh
echo Stopping Network Manager. Ctrl+C to abort. Usage: ./net essid.
sudo /etc/init.d/NetworkManager stop


echo Line to fix iwconfig, since 4318 sometimes doesn't associate (on my 
laptop)
sudo iwconfig wlan0 essid UNBORK
echo Sudoing iwconfig wlan0 with essid: $1
sudo iwconfig wlan0 essid $1
echo Bringing interface up and down to associate
sudo ifconfig wlan0 down
sudo ifconfig wlan0 up
sudo dhclient wlan0

--

-- 
Network Manager fails to connect
https://bugs.launchpad.net/bugs/339716
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 339716] Re: Network Manager fails to connect

[Michael Rocco Sabino]

oops the filename should read net at the beginning, not b43netfix.sh.

-- 
Network Manager fails to connect
https://bugs.launchpad.net/bugs/339716
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs