[Desktop-packages] [Bug 1912282] Re: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1

2021-03-02 Thread Nelly
I have a similar problem with tex-common in Ubuntu 20.04.
I tried to install a babel language, and got as result (part of the text is in 
Dutch):

sudo apt-get install texlive-lang-european
[sudo] wachtwoord voor nelly: 
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd   
De statusinformatie wordt gelezen... Klaar
De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer nodig:
  libllvm10 libllvm10:i386
Gebruik 'sudo apt autoremove' om ze te verwijderen.
De volgende NIEUWE pakketten zullen geïnstalleerd worden:
  texlive-lang-european
0 opgewaardeerd, 1 nieuw geïnstalleerd, 0 te verwijderen en 9 niet 
opgewaardeerd.
Er moeten 14,1 MB aan archieven opgehaald worden.
Na deze bewerking zal er 23,3 MB extra schijfruimte gebruikt worden.
Ophalen:1 http://nl.archive.ubuntu.com/ubuntu focal/universe amd64 
texlive-lang-european all 2019.20200218-1 [14,1 MB]
14,1 MB opgehaald in 2s (9.049 kB/s)  
Voorheen niet geselecteerd pakket texlive-lang-european wordt geselecteerd.
(Database wordt ingelezen ... 262758 bestanden en mappen momenteel 
geïnstalleerd.)
Uitpakken van .../texlive-lang-european_2019.20200218-1_all.deb wordt 
voorbereid...
Bezig met uitpakken van texlive-lang-european (2019.20200218-1) ...
Instellen van texlive-lang-european (2019.20200218-1) ...
Bezig met afhandelen van triggers voor tex-common (6.13) ...
Running mktexlsr. This may take some time... done.
Running updmap-sys. This may take some time... 
updmap-sys failed. Output has been stored in
/tmp/updmap.bXyswVXM
Please include this file if you report a bug.

Sometimes, not accepting conffile updates in /etc/texmf/updmap.d
causes updmap-sys to fail.  Please check for files with extension
.dpkg-dist or .ucf-dist in this directory

dpkg: fout bij verwerken van pakket tex-common (--configure):
 subproces van pakket tex-common werd script post-installation geïnstalleerd 
gaf de foutwaarde 1 terug
Fouten gevonden tijdens verwerken van:
 tex-common
E: Sub-process /usr/bin/dpkg returned an error code (1)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tex-common in Ubuntu.
https://bugs.launchpad.net/bugs/1912282

Title:
  package tex-common 6.13 failed to install/upgrade: installed tex-
  common package post-installation script subprocess returned error exit
  status 1

Status in tex-common package in Ubuntu:
  Confirmed

Bug description:
  That is all.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: tex-common 6.13
  ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78
  Uname: Linux 5.4.0-62-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Jan 18 15:47:15 2021
  ErrorMessage: installed tex-common package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2019-06-13 (585 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.2
  SourcePackage: tex-common
  Title: package tex-common 6.13 failed to install/upgrade: installed 
tex-common package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to focal on 2021-01-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1912282/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1900300] [NEW] Intel® Q45/Q43 (ELK)

2020-10-18 Thread nelly lemmy
Public bug reported:

I was trying to run blender but having problems in graphics card. then I
tried to update and got errors, I can not update drives in my machine

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
Uname: Linux 5.4.0-51-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 18 10:05:13 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.10, 5.4.0-48-generic, x86_64: installed
 virtualbox, 6.1.10, 5.4.0-51-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3646]
   Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3646]
InstallationDate: Installed on 2020-09-13 (34 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Hewlett-Packard HP Compaq 8000 Elite SFF PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-51-generic 
root=UUID=21700d8d-cc82-48e7-b0a2-d186309a53dc ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/22/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786G7 v01.02
dmi.board.asset.tag: AUD04807RT
dmi.board.name: 3646h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: AUD04807RT
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G7v01.02:bd10/22/2009:svnHewlett-Packard:pnHPCompaq8000EliteSFFPC:pvr:rvnHewlett-Packard:rn3646h:rvr:cvnHewlett-Packard:ct4:cvr:
dmi.product.family: 103C_53307F
dmi.product.name: HP Compaq 8000 Elite SFF PC
dmi.product.sku: AU247AV
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1900300

Title:
  Intel® Q45/Q43 (ELK)

Status in xorg package in Ubuntu:
  New

Bug description:
  I was trying to run blender but having problems in graphics card. then
  I tried to update and got errors, I can not update drives in my
  machine

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
  Uname: Linux 5.4.0-51-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 18 10:05:13 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.10, 5.4.0-48-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-51-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3646]
 Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3646]
  InstallationDate: Installed on 2020-09-13 (34 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Hewlett-Packard HP Compaq 8000 Elite SFF PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-51-generic 
root=UUID=21700d8d-cc82-48e7-b0a2-d186309a53dc ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G7 v01.02
  dmi.board.asset.tag: AUD04807RT
  dmi.board.name: 3646h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: AUD04807RT
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G7v01.02:bd10/22/2009:svnHewlett-Packard:pnHPCompaq8000EliteSFFPC:pvr:rvnHewlett-Packard:rn3646h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.produc

[Desktop-packages] [Bug 1048657] Re: Ubuntu 12.04 / Gimp - Consistent crash after saving file

2013-03-11 Thread Nelly
I just noticed, this bug is also registrated as
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1087920

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/1048657

Title:
  Ubuntu 12.04 / Gimp - Consistent crash after saving file

Status in “gimp” package in Ubuntu:
  New

Bug description:
  I started using gimp on a computer where I hadn't used it before. It's
  a dell notebook with a clean 12.04 installation.

  I can create and modify files in gimp, however, every time I save a
  file, it takes a rather long time doing so and eventually, it crashes.

  In my .xsession-errors I see the following every time (PID numbers
  change, obviously):

  (gimp-2.6:28853): Gtk-CRITICAL **: IA__gtk_tree_model_get: assertion 
`GTK_IS_TREE_MODEL (tree_model)' failed
  (script-fu:28866): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error

  ProblemType: BugDistroRelease: Ubuntu 12.04
  Package: gimp 2.6.12-1ubuntu1.1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  Date: Mon Sep 10 10:55:08 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)SourcePackage: gimp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1048657] Re: Ubuntu 12.04 / Gimp - Consistent crash after saving file

2013-03-11 Thread Nelly
I have the same problem.
I am using Ubuntu 12.04 and Gimp 2.6.12

A new GIMP image can be save under a given name with "save as". When I try to 
save an already named file under a new name with "save as", GIMP crashes. The 
fil is saved under the new name before crash, and can be opened again and can 
be edited. 
If I use "save as", but do not change the name, no crash occurs.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/1048657

Title:
  Ubuntu 12.04 / Gimp - Consistent crash after saving file

Status in “gimp” package in Ubuntu:
  New

Bug description:
  I started using gimp on a computer where I hadn't used it before. It's
  a dell notebook with a clean 12.04 installation.

  I can create and modify files in gimp, however, every time I save a
  file, it takes a rather long time doing so and eventually, it crashes.

  In my .xsession-errors I see the following every time (PID numbers
  change, obviously):

  (gimp-2.6:28853): Gtk-CRITICAL **: IA__gtk_tree_model_get: assertion 
`GTK_IS_TREE_MODEL (tree_model)' failed
  (script-fu:28866): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error

  ProblemType: BugDistroRelease: Ubuntu 12.04
  Package: gimp 2.6.12-1ubuntu1.1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  Date: Mon Sep 10 10:55:08 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)SourcePackage: gimp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1087920] Re: gimp crashes after save as

2013-03-11 Thread Nelly
This bug is also regsitrated as 
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1048657
It is not solved there.

I have the same problem.
I am using Ubuntu 12.04 and Gimp 2.6.12

A new GIMP image can be save under a given name with "save as". When I try to 
save an already named file under a new name with "save as", GIMP crashes. The 
file is saved under the new name before crash, and can be opened again and can 
be edited. 
If I use "save as", but do not change the name, no crash occurs.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/1087920

Title:
  gimp crashes after save as

Status in “gimp” package in Ubuntu:
  New

Bug description:
  opened and modified file .xcf, save as, file .xcf, Save
  After while error popup 'window .xcf not respond', then Gimp crashes 
and close.
  Error console empty.
  But  file is saved w/o errors. After relaunching Gimp, I can open 
it and continue until the next 'Save as'.

  OS Ubuntu 12.04.1, Gimp 2.6.12

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1053783] Re: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info.

2013-03-01 Thread Nelly
Hi Bladud,

I have again turned on nepomuk and shutdown. Started again and during the 
second shutdown, the command suggested by you, 
"ps -wweo pid,state,args | grep nepomuk" gave the following result (during 
shutdown fase, every 2 sec ps command was given, results from are given from 
the last one (about 34 sec. after the shutdown command)):

2049 S /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder 
2094 S /usr/bin/nepomukserver 
2099 S /usr/bin/nepomukservicestub nepomukstorage 
2123 S /usr/bin/nepomukservicestub nepomukqueryservice 
2124 S /usr/bin/nepomukservicestub nepomukfilewatch 
2125 S /usr/bin/nepomukservicestub nepomukbackupsync 
2126 S /usr/bin/nepomukservicestub nepomukfileindexer 
2431 S grep nepomuk 
 S /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder 
2094 S /usr/bin/nepomukserver 
2099 S /usr/bin/nepomukservicestub nepomukstorage 
2123 S /usr/bin/nepomukservicestub nepomukqueryservice 
2124 S /usr/bin/nepomukservicestub nepomukfilewatch 
2125 S /usr/bin/nepomukservicestub nepomukbackupsync 
2126 S /usr/bin/nepomukservicestub nepomukfileindexer 
2431 S grep nepomuk

My version of nepomuk is: kde-runtime-data 4:4.8.5-0ubuntu0.1

Success with finding the cause of the bug.

Nelly

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1053783

Title:
  Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with
  package info.

Status in “gnome-session” package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 12.04, the shutdown is stalling - for about 2 minutes - but only on 
occasions when I have opened - and then quit - KAlarm. 
  A window pops up Stating that, 'A Program is still running'; Unknown (not 
responding); and, there are 3 buttons to choose: 'Lock Screen', 'Cancel' and 
'Shutdown Anyway'.

  Initial report was Bug #1053779 but had no package information.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-session-bin 3.2.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-30.48-generic-pae 3.2.27
  Uname: Linux 3.2.0-30-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: i386
  Date: Fri Sep 21 13:22:35 2012
  ExecutablePath: /usr/bin/gnome-session
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1053783] Re: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info.

2013-02-18 Thread Nelly
Answer to Bladud (#10 + #12)

I have tried to run the command "ps -el | grep nepomuk" as long as
possible after the shutdown command (given with the GUI logout button)
using a BASH function giving that command every 2 sec and saving the
results in a file. After 20-30 sec. the termninal window disappears and
the function stops. I don't find differences in the result just before
giving the logout command and during these seconds hanging. I have
performed the test twice, once with the nepomuk functions working and
programmed to start in the next logon, and once after I had prevented
the starting of some nepomuk services at start-up (see #6). Surprisingly
the results of these two tests differed slightly.

The first test gave:
0 S 1000 2062 1987 0 80 0 - 32753 poll_s R 00:00:00 akonadi_nepomuk 
0 S 1000 2108 1 0 80 0 - 17073 poll_s R 00:00:00 nepomukserver 
0 S 1000 2114 2108 2 99 - - 49593 poll_s R 00:00:00 nepomukservices 
0 D 1000 2198 2108 7 99 - - 32215 sleep_ R 00:00:02 nepomukservices 
0 S 1000 2199 2108 0 99 - - 32401 futex_ R 00:00:00 nepomukservices 
0 S 1000 2200 2108 0 99 - - 26909 poll_s R 00:00:00 nepomukservices 
0 S 1000 2201 2108 0 99 - - 25321 poll_s R 00:00:00 nepomukservices 
  S 1000 2062 1987 0 80 0 - 32753 poll_s R 00:00:00 akonadi_nepomuk 
0 S 1000 2108 1 0 80 0 - 17073 poll_s R 00:00:00 nepomukserver 
0 S 1000 2114 2108 2 99 - - 49593 poll_s R 00:00:00 nepomukservices 
0 D 1000 2198 2108 7 99 - - 32215 sleep_ R 00:00:02 nepomukservices 
0 S 1000 2199 2108 0 99 - - 32401 futex_ R 00:00:00 nepomukservices 
0 S 1000 2200 2108 0 99 - - 26909 poll_s R 00:00:00 nepomukservices 
0 S 1000 2201 2108 0 99 - - 25321 poll_s R 00:00:00 nepomukservices

and the second test:
0 S 1000 2052 1989 0 80 0 - 33984 poll_s R 00:00:00 akonadi_nepomuk 
0 S 1000 2101 1 0 80 0 - 17073 poll_s R 00:00:00 nepomukserver 
0 S 1000 2106 2101 0 99 - - 54348 poll_s R 00:00:00 nepomukservices 
0 S 1000 2126 2101 0 99 - - 32400 futex_ R 00:00:00 nepomukservices 
0 S 1000 2127 2101 0 99 - - 26945 poll_s R 00:00:00 nepomukservices 
0 S 1000 2128 2101 0 99 - - 25321 poll_s R 00:00:00 nepomukservices 
0 S 1000 2129 2101 0 99 - - 32536 poll_s R 00:00:03 nepomukservices 
  S 1000 2052 1989 0 80 0 - 33984 poll_s R 00:00:00 akonadi_nepomuk 
0 S 1000 2101 1 0 80 0 - 17073 poll_s R 00:00:00 nepomukserver 
0 S 1000 2106 2101 0 99 - - 54348 poll_s R 00:00:00 nepomukservices 
0 S 1000 2126 2101 0 99 - - 32400 futex_ R 00:00:00 nepomukservices 
0 S 1000 2127 2101 0 99 - - 26945 poll_s R 00:00:00 nepomukservices 
0 S 1000 2128 2101 0 99 - - 25321 poll_s R 00:00:00 nepomukservices 
0 S 1000 2129 2101 0 99 - - 32536 poll_s R 00:00:03 nepomukservices

Hope this helps. What happens during the rest of the shutdown cannot be
tested easily because the computer is no longer accessible.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1053783

Title:
  Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with
  package info.

Status in “gnome-session” package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 12.04, the shutdown is stalling - for about 2 minutes - but only on 
occasions when I have opened - and then quit - KAlarm. 
  A window pops up Stating that, 'A Program is still running'; Unknown (not 
responding); and, there are 3 buttons to choose: 'Lock Screen', 'Cancel' and 
'Shutdown Anyway'.

  Initial report was Bug #1053779 but had no package information.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-session-bin 3.2.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-30.48-generic-pae 3.2.27
  Uname: Linux 3.2.0-30-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: i386
  Date: Fri Sep 21 13:22:35 2012
  ExecutablePath: /usr/bin/gnome-session
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1053783] Re: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info.

2013-02-17 Thread Nelly
Answer to Bladud (#10)

I first tried ps -e0 stat | grep nepomuk during normal run-time to see
what kind of results I might expect. It did not work.

 "ps -el | grep nepomuk" resulted in:
0 S  1000  2158 1  0  80   0 - 14441 poll_s ?00:00:00 nepomukserver
0 S  1000  3467  3344  0  80   0 - 32744 poll_s ?00:00:00 
akonadi_nepomuk
0 S  1000  3520 1  0  80   0 - 14441 poll_s ?00:00:00 nepomukserver

and
 "ps -eF | grep nepomuk" resulted in:
nelly 2158 1  0 14441  8700   0 10:42 ?00:00:00 
/usr/bin/nepomukserver
nelly 3467  3344  0 32744 26304   0 12:22 ?00:00:00 
/usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder
nelly 3520 1  0 14441  8700   1 12:23 ?00:00:00 
/usr/bin/nepomukserver
nelly 3810  3723  0  1103   832   0 13:20 pts/000:00:00 grep 
--color=auto nepomuk

Is either of these the kind of output you are looking for? Which one?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1053783

Title:
  Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with
  package info.

Status in “gnome-session” package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 12.04, the shutdown is stalling - for about 2 minutes - but only on 
occasions when I have opened - and then quit - KAlarm. 
  A window pops up Stating that, 'A Program is still running'; Unknown (not 
responding); and, there are 3 buttons to choose: 'Lock Screen', 'Cancel' and 
'Shutdown Anyway'.

  Initial report was Bug #1053779 but had no package information.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-session-bin 3.2.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-30.48-generic-pae 3.2.27
  Uname: Linux 3.2.0-30-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: i386
  Date: Fri Sep 21 13:22:35 2012
  ExecutablePath: /usr/bin/gnome-session
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1053783] Re: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info.

2013-02-12 Thread Nelly
nepomuk processes running in situation with good shutdown (after adding
the lines to ~/.kde/share/config/nepomukserverrc as described in my
message of feb 11 and deleting
/usr/share/autostart/nepomukcontroller.desktop)

nelly 2066  1862  0 09:37 ?00:00:00 /usr/bin/akonadi_nepomuk_feeder 
--identifier akonadi_nepomuk_feeder
nelly 2098 1  0 09:37 ?00:00:00 /usr/bin/nepomukserver
nelly 2920  2864  0 10:01 pts/000:00:00 grep --color=auto nepomuk


I have no NFS system running (rpcinfo not installed, no file /etc/exports)

I have deleted the extra lines in ~/.kde/share/config/nepomukserverrc
and put the nepomukcontroller.desktop again in the map
/usr/share/autostart/. Shutdown was OK (file appears only affect the
system after a fresh start-up)

Now nepomuk processes running are:

nelly 2083  2007  0 10:28 ?00:00:00 /usr/bin/akonadi_nepomuk_feeder 
--identifier akonadi_nepomuk_feeder
nelly 2132 1  0 10:28 ?00:00:00 /usr/bin/nepomukserver
nelly 2139  2132  0 10:28 ?00:00:00 /usr/bin/nepomukservicestub 
nepomukstorage
nelly 2157  2132  2 10:28 ?00:00:04 /usr/bin/nepomukservicestub 
nepomukfilewatch
nelly 2158  2132  0 10:28 ?00:00:00 /usr/bin/nepomukservicestub 
nepomukfileindexer
nelly 2159  2132  0 10:28 ?00:00:00 /usr/bin/nepomukservicestub 
nepomukbackupsync
nelly 2160  2132  0 10:28 ?00:00:00 /usr/bin/nepomukservicestub 
nepomukqueryservice
nelly 2392  2338  0 10:31 pts/000:00:00 grep --color=auto nepomuk

( the akonadi processes running were:

nelly 2007 1  0 10:27 ?00:00:00 /usr/bin/akonadi_control
nelly 2009  2007  0 10:27 ?00:00:00 akonadiserver
nelly 2011  2009  0 10:27 ?00:00:00 /usr/sbin/mysqld 
--defaults-file=/home/nelly/.local/share/akonadi/mysql.conf 
--datadir=/home/nelly/.local/share/akonadi/db_data/ 
--socket=/home/nelly/.local/share/akonadi/socket-ecostat5/mysql.socket
nelly 2075  2007  0 10:28 ?00:00:00 /usr/bin/akonadi_agent_launcher 
akonadi_akonotes_resource akonadi_akonotes_resource_0
nelly 2076  2007  0 10:28 ?00:00:00 /usr/bin/akonadi_agent_launcher 
akonadi_contacts_resource akonadi_contacts_resource_0
nelly 2077  2007  0 10:28 ?00:00:00 /usr/bin/akonadi_agent_launcher 
akonadi_ical_resource akonadi_ical_resource_0
nelly 2078  2007  0 10:28 ?00:00:00 /usr/bin/akonadi_agent_launcher 
akonadi_kalarm_resource akonadi_kalarm_resource_0
nelly 2079  2007  0 10:28 ?00:00:00 /usr/bin/akonadi_agent_launcher 
akonadi_kalarm_resource akonadi_kalarm_resource_1
nelly 2080  2007  0 10:28 ?00:00:00 /usr/bin/akonadi_agent_launcher 
akonadi_kalarm_resource akonadi_kalarm_resource_2
nelly 2081  2007  0 10:28 ?00:00:00 /usr/bin/akonadi_agent_launcher 
akonadi_maildir_resource akonadi_maildir_resource_0
nelly 2082  2007  0 10:28 ?00:00:00 
/usr/bin/akonadi_maildispatcher_agent --identifier akonadi_maildispatcher_agent
nelly 2083  2007  0 10:28 ?00:00:00 /usr/bin/akonadi_nepomuk_feeder 
--identifier akonadi_nepomuk_feeder
nelly 2465  2338  0 10:37 pts/000:00:00 grep --color=auto akon

The nepomukserverrc file had no effect omn the akonadi processes
running)

I added again the extra lines in ~/.kde/share/config/nepomukserverrc and
removed the nepomukcontroller.desktop from in the map
/usr/share/autostart/. Shutdown was slow (all nepomuk processes were
still running) and the pop-up stating that an unknown process was still
running appeared again. After this restart the shutdown was OK again
(within a few seconds).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1053783

Title:
  Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with
  package info.

Status in “gnome-session” package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 12.04, the shutdown is stalling - for about 2 minutes - but only on 
occasions when I have opened - and then quit - KAlarm. 
  A window pops up Stating that, 'A Program is still running'; Unknown (not 
responding); and, there are 3 buttons to choose: 'Lock Screen', 'Cancel' and 
'Shutdown Anyway'.

  Initial report was Bug #1053779 but had no package information.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-session-bin 3.2.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-30.48-generic-pae 3.2.27
  Uname: Linux 3.2.0-30-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: i386
  Date: Fri Sep 21 13:22:35 2012
  ExecutablePath: /usr/bin/gnome-session
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gno

[Desktop-packages] [Bug 1053783] Re: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info.

2013-02-11 Thread Nelly
I also have this bug. 
I use KAlarm and my computer with Ubuntu 12.04 (Gnome desktop) took several 
minutes to shutdown.

Link http://ubuntuforums.org/showthread.php?t=1764048 gave me the hint how to 
solve this problem. This link contains methods to prevent te starting up of 
nepomuk and akonadi in 3 steps. 
If you don't want to use KAlarm, it might be safe to apply all three steps. 
However, doing so, KAlarm could not be used. It asked to start-up akonadi 
first. So I tried what would happen if I only used the two steps preventing the 
(complete) start-up of nepomuk, and that worked great. KAlarm works and Ubuntu 
12.04 shuts down within a few seconds. The steps to apply are:

1. Add the following lines to ~/.kde/share/config/nepomukserverrc (and
their sections if they don't exist) (change the value from "true" to
"false" if they do exist and are set on "true";

[Basic Settings]
Start Nepomuk=false

[Service-nepomukmigration1]
autostart=false

[Service-nepomukstrigiservice]
autostart=false

2. Remove the file /usr/share/autostart/nepomukcontroller.desktop, if it
exists.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1053783

Title:
  Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with
  package info.

Status in “gnome-session” package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 12.04, the shutdown is stalling - for about 2 minutes - but only on 
occasions when I have opened - and then quit - KAlarm. 
  A window pops up Stating that, 'A Program is still running'; Unknown (not 
responding); and, there are 3 buttons to choose: 'Lock Screen', 'Cancel' and 
'Shutdown Anyway'.

  Initial report was Bug #1053779 but had no package information.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-session-bin 3.2.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-30.48-generic-pae 3.2.27
  Uname: Linux 3.2.0-30-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: i386
  Date: Fri Sep 21 13:22:35 2012
  ExecutablePath: /usr/bin/gnome-session
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp