[Bug 2052859] Re: Windows go to behind others when clicking with mouse

2024-02-29 Thread kex
The nvidia driver 550 got an update yesterday.  Installing the update
seems to have solved 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/2052859

Title:
  Windows go to behind others when clicking with mouse

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


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

[Bug 1547844] Re: systemd-fsckd does not allow fsck to finish

2016-10-07 Thread kex
The machine has been stable for a couple of days, and I tested today
that fsck finished OK.


** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  systemd-fsckd does not allow fsck to finish

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

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


[Bug 1547844] Re: systemd-fsckd does not allow fsck to finish

2016-10-05 Thread kex
I installed the 229-4ubuntu11 version.  If the system is stable till the
weekend, and does not hang/crash/livelock/deadlock/whatever happened
when I tested the ubuntu9 version, I'll twiddle max mount count to force
fsck during the weekend.

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

Title:
  systemd-fsckd does not allow fsck to finish

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

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


[Bug 1547844] Re: systemd-fsckd does not allow fsck to finish

2016-10-02 Thread kex
I have had 229-4ubuntu10 version now for the packages, and the machine
has not crashed yet (last crash was Friday morning, so 2 days without
crash...

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

Title:
  systemd-fsckd does not allow fsck to finish

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

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


[Bug 1547844] Re: systemd-fsckd does not allow fsck to finish

2016-09-30 Thread kex
this might be unrelated, but since I tried the xenial-proposed packages, the 
computer has crashed about once a day.  Usually I don't get any info on syslog, 
but I found this on syslog today:
Sep 30 13:32:28 xpc kernel: [19560.717703] INFO: task jbd2/dm-1-8:879 blocked 
for more than 120 seconds.
Sep 30 13:32:28 xpc kernel: [19560.717706]   Tainted: G   OE   
4.4.0-38-generic #57-Ubuntu
Sep 30 13:32:28 xpc kernel: [19560.717706] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 30 13:32:28 xpc kernel: [19560.717707] jbd2/dm-1-8 D 8800af107c98   
  0   879  2 0x
Sep 30 13:32:28 xpc kernel: [19560.717710]  8800af107c98 0246 
8801b8279b80 8801b5d36040
Sep 30 13:32:28 xpc kernel: [19560.717712]  8800af108000 8800ae9718b8 
8800af107d88 8800af107d70
Sep 30 13:32:28 xpc kernel: [19560.717713]  8801b5d36040 8800af107cb0 
8182c5f5 8800ad776900
Sep 30 13:32:28 xpc kernel: [19560.717714] Call Trace:
Sep 30 13:32:28 xpc kernel: [19560.717720]  [] 
schedule+0x35/0x80
Sep 30 13:32:28 xpc kernel: [19560.717723]  [] 
jbd2_journal_commit_transaction+0x240/0x1870
Sep 30 13:32:28 xpc kernel: [19560.717727]  [] ? 
wake_atomic_t_function+0x60/0x60
Sep 30 13:32:28 xpc kernel: [19560.717730]  [] ? 
try_to_del_timer_sync+0x5e/0x90
Sep 30 13:32:28 xpc kernel: [19560.717732]  [] 
kjournald2+0xca/0x250
Sep 30 13:32:28 xpc kernel: [19560.717733]  [] ? 
wake_atomic_t_function+0x60/0x60
Sep 30 13:32:28 xpc kernel: [19560.717735]  [] ? 
commit_timeout+0x10/0x10
Sep 30 13:32:28 xpc kernel: [19560.717736]  [] 
kthread+0xd8/0xf0
Sep 30 13:32:28 xpc kernel: [19560.717738]  [] ? 
kthread_create_on_node+0x1e0/0x1e0
Sep 30 13:32:28 xpc kernel: [19560.717740]  [] 
ret_from_fork+0x3f/0x70
Sep 30 13:32:28 xpc kernel: [19560.717740]  [] ? 
kthread_create_on_node+0x1e0/0x1e0
Sep 30 13:32:28 xpc kernel: [19560.717747] INFO: task vdr:1307 blocked for more 
than 120 seconds.
Sep 30 13:32:28 xpc kernel: [19560.717748]   Tainted: G   OE   
4.4.0-38-generic #57-Ubuntu
Sep 30 13:32:28 xpc kernel: [19560.717748] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 30 13:32:28 xpc kernel: [19560.717749] vdr D 880198ac3b08   
  0  1307  1 0x0004
Sep 30 13:32:28 xpc kernel: [19560.717750]  880198ac3b08 88017b477bc8 
8801b827a940 8800aeeb0dc0
Sep 30 13:32:28 xpc kernel: [19560.717751]  880198ac4000 8800ae971870 
011d3628 8800ae971870
Sep 30 13:32:28 xpc kernel: [19560.717753]  8800ad776900 880198ac3b20 
8182c5f5 8800ae971800
Sep 30 13:32:28 xpc kernel: [19560.717754] Call Trace:
Sep 30 13:32:28 xpc kernel: [19560.717755]  [] 
schedule+0x35/0x80
Sep 30 13:32:28 xpc kernel: [19560.717757]  [] 
wait_transaction_locked+0x8a/0xd0
Sep 30 13:32:28 xpc kernel: [19560.717758]  [] ? 
wake_atomic_t_function+0x60/0x60
Sep 30 13:32:28 xpc kernel: [19560.717759]  [] 
add_transaction_credits+0x223/0x2a0
Sep 30 13:32:28 xpc kernel: [19560.717761]  [] ? 
wake_up_bit+0x25/0x30
Sep 30 13:32:28 xpc kernel: [19560.717762]  [] 
start_this_handle+0x10c/0x400
Sep 30 13:32:28 xpc kernel: [19560.717765]  [] ? 
kmem_cache_alloc+0x1ca/0x1f0
Sep 30 13:32:28 xpc kernel: [19560.717766]  [] 
jbd2__journal_start+0xdb/0x1e0
Sep 30 13:32:28 xpc kernel: [19560.717769]  [] ? 
ext4_rename+0x41d/0x900
Sep 30 13:32:28 xpc kernel: [19560.717771]  [] 
__ext4_journal_start_sb+0x6d/0x120
Sep 30 13:32:28 xpc kernel: [19560.717772]  [] 
ext4_rename+0x41d/0x900
Sep 30 13:32:28 xpc kernel: [19560.717774]  [] ? 
terminate_walk+0x64/0xd0
Sep 30 13:32:28 xpc kernel: [19560.717776]  [] 
ext4_rename2+0x1d/0x30
Sep 30 13:32:28 xpc kernel: [19560.71]  [] 
vfs_rename+0x58c/0x8e0
Sep 30 13:32:28 xpc kernel: [19560.717779]  [] ? 
security_kernel_fw_from_file+0x20/0x70
Sep 30 13:32:28 xpc kernel: [19560.717780]  [] 
SyS_rename+0x39f/0x3c0
Sep 30 13:32:28 xpc kernel: [19560.717782]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71
Sep 30 13:32:28 xpc kernel: [19560.717794] INFO: task kworker/u16:2:7411 
blocked for more than 120 seconds.
Sep 30 13:32:28 xpc kernel: [19560.717795]   Tainted: G   OE   
4.4.0-38-generic #57-Ubuntu
Sep 30 13:32:28 xpc kernel: [19560.717795] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 30 13:32:28 xpc kernel: [19560.717796] kworker/u16:2   D 8801885777f8   
  0  7411  2 0x
Sep 30 13:32:28 xpc kernel: [19560.717800] Workqueue: writeback wb_workfn 
(flush-252:1)
Sep 30 13:32:28 xpc kernel: [19560.717801]  8801885777f8  
8801b8279b80 8800940ee040
Sep 30 13:32:28 xpc kernel: [19560.717803]  880188578000 8800ae971870 
011d3628 8800ae971870
Sep 30 13:32:28 xpc kernel: [19560.717804]  8800ad776900 880188577810 
8182c5f5 8800ae971800
Sep 30 13:32:28 xpc kernel: [19560.717805] Call Trace:
Sep 30 13:32:28 xpc kernel: [19560.717806]  [] 

[Bug 1547844] Re: systemd-fsckd does not allow fsck to finish

2016-09-28 Thread kex
now it worked.  the packages I needed:
kex@xpc:~$ sudo dpkg -l | grep 229
ii  libpam-systemd:amd64 229-4ubuntu9   
 amd64system and service manager - 
PAM module
ii  libsystemd0:amd64229-4ubuntu9   
 amd64systemd utility library
ii  libsystemd0:i386 229-4ubuntu9   
 i386 systemd utility library
ii  libudev1:amd64   229-4ubuntu9   
 amd64libudev shared library
ii  libudev1:i386229-4ubuntu9   
 i386 libudev shared library
ii  systemd  229-4ubuntu9   
 amd64system and service manager
ii  systemd-sysv 229-4ubuntu9   
 amd64system and service manager - 
SysV links
ii  udev 229-4ubuntu9   
 amd64/dev/ and hotplug management 
daemon


** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  systemd-fsckd does not allow fsck to finish

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

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


[Bug 1547844] Re: systemd-fsckd does not allow fsck to finish

2016-09-27 Thread kex
hi,

the packet fails to install:

kex@xpc:~$ LANG=en sudo apt-get install systemd/xenial-proposed
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Selected version '229-4ubuntu9' (Ubuntu:16.04/xenial-proposed [amd64]) for 
'systemd'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 systemd : Depends: libsystemd0 (= 229-4ubuntu9) but 229-4ubuntu8 is to be 
installed
   Recommends: libpam-systemd but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

If I try to install both, a scary list of packages will be removed (I
have no courage now to do that):

kex@xpc:~$ LANG=en sudo apt-get install libsystemd0/xenial-proposed 
systemd/xenial-proposed
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Selected version '229-4ubuntu9' (Ubuntu:16.04/xenial-proposed [amd64]) for 
'libsystemd0'
Selected version '229-4ubuntu9' (Ubuntu:16.04/xenial-proposed [amd64]) for 
'systemd'
The following packages were automatically installed and are no longer required:
  account-plugin-tools accountsservice-ubuntu-schemas argyll argyll-ref 
dbus-property-service gir1.2-gdesktopenums-3.0
  gir1.2-gnomedesktop-3.0 gir1.2-udisks-2.0 gnome-shell-common 
gstreamer1.0-plugins-base:i386 libaudio2:i386 libcdparanoia0:i386
  libconnectivity-qt1 libdbus-cpp5 libglib2.0-0:i386 
libgstreamer-plugins-base1.0-0:i386 libgstreamer1.0-0:i386 libhybris 
libhybris-utils
  libjpeg62:i386 libmedia1 libmng2:i386 libmysqlclient20:i386 
libonline-accounts-client1 libonline-accounts-daemon1 libonline-accounts-qt1
  liboobs-1-5 libopts25 libopus0:i386 liborc-0.4-0:i386 libpkcs11-helper1 
libprocess-cpp3 libqgsttools-p1 libqmenumodel0 libqofono-qt5-0
  libqt4-sql:i386 libqt4-sql-mysql:i386 libqt4-xml:i386 
libqt5multimedia5-plugins libqt5multimediaquick-p5 libqt5multimediawidgets5
  libqt5systeminfo5 libqt5xmlpatterns5 libqtcore4:i386 libsystemsettings1 
libtheora0:i386 libtrust-store2 libubuntuoneauth-2.0-0
  libvisual-0.4-0:i386 libvisual-0.4-plugins:i386 libxss1:i386 libxtst6:i386 
libxv1:i386 mate-polkit-common mutter-common
  network-manager-openvpn ntp openvpn plainbox-secure-policy python-gpgme 
python3-gnupg python3-guacamole python3-jinja2
  python3-markupsafe python3-padme python3-pyparsing python3-xlsxwriter 
qmenumodel-qml qml-module-qtmultimedia qml-module-qtsysteminfo
  qml-module-ubuntu-connectivity qml-module-ubuntu-onlineaccounts2 
qtdeclarative5-gsettings1.0 qtdeclarative5-ofono0.2
  qtdeclarative5-ubuntu-settings-components sqlite3 system-image-common 
system-image-dbus system-tools-backends ubuntu-keyboard-data
  ubuntuone-credentials-common urfkill
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  apparmor-easyprof apparmor-easyprof-ubuntu click click-apparmor 
gir1.2-click-0.4 gir1.2-gee-0.8 libboost-log1.58.0 libboost-regex1.58.0
  libboost-thread1.58.0 libc-ares2 libclick-0.4-0 libcontent-hub0 libgflags2v5 
libgoogle-glog0v5 libhardware2 libhybris-common1
  liblibertine1 liblttng-ust-ctl2 liblttng-ust0 libubuntu-app-launch2 
libubuntu-application-api3 libubuntu-download-manager-client1
  libubuntu-download-manager-common1 libubuntu-platform-hardware-api3 
libudm-common1 liburcu4 ofono powerd python3-apparmor
  python3-apparmor-click python3-click-package python3-libapparmor 
qtdeclarative5-ubuntu-content1 ubuntu-application-api3-test
Suggested packages:
  click-reviewers-tools ubuntu-app-launch-tools | upstart-app-launch-tools 
content-hub systemd-ui systemd-container
Recommended packages:
  libpam-systemd
The following packages will be REMOVED:
  aptdaemon brasero checkbox checkbox-converged checkbox-gui checkbox-qt colord 
deja-dup-backend-gvfs gnome-bluetooth gnome-color-manager
  gnome-control-center gnome-disk-utility gnome-session gnome-settings-daemon 
gnome-system-log gnome-system-tools gnome-tweak-tool
  gnome-user-share gvfs gvfs-backends gvfs-daemons gvfs-fuse hplip 
indicator-bluetooth indicator-sound landscape-client-ui-install
  language-selector-gnome libasound2-plugins:i386 libavahi-client3:i386 
libcanberra-pulse libcups2:i386 libdbus-1-3:i386
  libdbusmenu-qt2:i386 libpam-systemd libpulse0:i386 libqt4-dbus:i386 
libqt4-declarative:i386 libqt4-network:i386 libqt4-opengl:i386
  libqt4-script:i386 libqt4-xmlpatterns:i386 libqtdbus4:i386 libqtgui4:i386 
libqtwebkit4:i386 libsane:i386 libsystemd0:i386 nautilus
  nautilus-dropbox nautilus-sendto nautilus-share network-manager 
network-manager-gnome plainbox-provider-checkbox
  plainbox-provider-resource-generic policykit-1 policykit-1-gnome 
printer-driver-postscript-hp pulseaudio pulseaudio-module

[Bug 1576809] [NEW] vdr does not start due to lack of rights on dvb devices upon startup

2016-04-29 Thread kex
Public bug reported:

Today vdr does not start any more during the boot (it did yesterday).
After a user logs in and starts with systemctl start vdr, it starts
properly.

I use ureadahead, I wonder if it affects this - like missing a
dependency in systemd scripts results in the devices not being ready
when vdr tries to start.

journalctl: 
-- Logs begin at pe 2016-04-29 20:48:24 EEST, end at pe 2016-04-29 20:50:48 
EEST. --
huhti 29 20:48:27 xpc vdr[1171]: [1171] VDR version 2.2.0 started
huhti 29 20:48:27 xpc vdr[1171]: [1171] switched to user 'vdr'
huhti 29 20:48:27 xpc vdr[1171]: [1171] codeset is 'UTF-8' - known
huhti 29 20:48:27 xpc vdr[1171]: [1171] found 28 locales in /usr/share/locale
huhti 29 20:48:27 xpc vdr[1171]: [1171] loading plugin: 
/usr/lib/vdr/plugins/libvdr-conflictcheckonly.so.2.2.0
huhti 29 20:48:27 xpc vdr[1171]: [1171] loading plugin: 
/usr/lib/vdr/plugins/libvdr-epgsearch.so.2.2.0
huhti 29 20:48:27 xpc vdr[1171]: [1171] loading plugin: 
/usr/lib/vdr/plugins/libvdr-epgsearchonly.so.2.2.0
huhti 29 20:48:27 xpc vdr[1171]: [1171] loading plugin: 
/usr/lib/vdr/plugins/libvdr-quickepgsearch.so.2.2.0
huhti 29 20:48:27 xpc vdr[1171]: [1171] loading plugin: 
/usr/lib/vdr/plugins/libvdr-streamdev-server.so.2.2.0
huhti 29 20:48:27 xpc vdr[1171]: [1171] loading plugin: 
/usr/lib/vdr/plugins/libvdr-vnsiserver.so.2.2.0
huhti 29 20:48:27 xpc vdr[1171]: [1171] loading /var/lib/vdr/setup.conf
huhti 29 20:48:27 xpc vdr[1171]: [1171] loading /var/lib/vdr/sources.conf
huhti 29 20:48:27 xpc vdr[1171]: [1171] loading /var/lib/vdr/diseqc.conf
huhti 29 20:48:27 xpc vdr[1171]: [1171] loading /var/lib/vdr/scr.conf
huhti 29 20:48:27 xpc vdr[1171]: [1171] loading /var/lib/vdr/channels.conf
huhti 29 20:48:27 xpc vdr[1171]: [1171] loading /var/lib/vdr/timers.conf
huhti 29 20:48:27 xpc vdr[1171]: [1171] loading /var/lib/vdr/commands.conf
huhti 29 20:48:27 xpc vdr[1171]: [1171] loading /var/lib/vdr/reccmds.conf
huhti 29 20:48:27 xpc vdr[1171]: [1171] loading /var/lib/vdr/svdrphosts.conf
huhti 29 20:48:27 xpc vdr[1171]: [1171] loading /var/lib/vdr/remote.conf
huhti 29 20:48:27 xpc vdr[1171]: [1171] loading /var/lib/vdr/keymacros.conf
huhti 29 20:48:27 xpc vdr[1171]: [1293] video directory scanner thread started 
(pid=1171, tid=1293, prio=high)
huhti 29 20:48:27 xpc vdr[1171]: [1294] video directory scanner thread started 
(pid=1171, tid=1294, prio=high)
huhti 29 20:48:27 xpc vdr[1171]: [1171] registered source parameters for 'A - 
ATSC'
huhti 29 20:48:27 xpc vdr[1171]: [1171] registered source parameters for 'C - 
DVB-C'
huhti 29 20:48:27 xpc vdr[1171]: [1171] registered source parameters for 'S - 
DVB-S'
huhti 29 20:48:27 xpc vdr[1171]: [1171] registered source parameters for 'T - 
DVB-T'
huhti 29 20:48:27 xpc vdr[1171]: [1171] ERROR (dvbdevice.c,1164): 
/dev/dvb/adapter0/frontend0: Lupa evätty
huhti 29 20:48:27 xpc vdr[1171]: [1171] ERROR (dvbdevice.c,1164): 
/dev/dvb/adapter1/frontend0: Lupa evätty
huhti 29 20:48:27 xpc vdr[1171]: [1171] ERROR (dvbdevice.c,1164): 
/dev/dvb/adapter2/frontend0: Lupa evätty
huhti 29 20:48:27 xpc vdr[1171]: [1171] no DVB device found
huhti 29 20:48:27 xpc vdr[1171]: [1171] initializing plugin: conflictcheckonly 
(0.0.1): Suoratoiminto EPGSearch-laajennoksen ajastimien tarkistukselle
huhti 29 20:48:27 xpc vdr[1171]: [1171] initializing plugin: epgsearch 
(1.0.1.beta5): Monipuolinen ohjelmaopas hakutoiminnolla
huhti 29 20:48:27 xpc vdr[1171]: [1171] initializing plugin: epgsearchonly 
(0.0.1): Suoratoiminto EPGSearch-laajennoksen haulle
huhti 29 20:48:27 xpc vdr[1171]: [1171] initializing plugin: quickepgsearch 
(0.0.1): Pikahaku ohjelmaoppaalle
huhti 29 20:48:27 xpc vdr[1171]: [1295] epg data reader thread started 
(pid=1171, tid=1295, prio=high)
huhti 29 20:48:27 xpc vdr[1171]: [1295] reading EPG data from 
/var/cache/vdr/epg.data
huhti 29 20:48:27 xpc vdr[1171]: [1171] initializing plugin: streamdev-server 
(0.6.1-git): VDR-suoratoistopalvelin
huhti 29 20:48:27 xpc vdr[1171]: [1171] initializing plugin: vnsiserver 
(1.3.1): VDR-Network-Streaming-Interface (VNSI) Server
huhti 29 20:48:27 xpc vdr[1171]: vdr: no primary device found - using first 
device!
huhti 29 20:48:27 xpc vdr[1171]: [1171] ERROR: invalid primary device number: 0
huhti 29 20:48:27 xpc vdr[1171]: [1171] ERROR: no primary device found - using 
first device!
huhti 29 20:48:27 xpc vdr[1171]: [1171] ERROR: invalid primary device number: 1
huhti 29 20:48:27 xpc vdr[1171]: [1171] deleting plugin: vnsiserver
huhti 29 20:48:27 xpc vdr[1171]: [1171] deleting plugin: streamdev-server
huhti 29 20:48:27 xpc vdr[1171]: [1171] deleting plugin: quickepgsearch
huhti 29 20:48:27 xpc vdr[1171]: [1171] deleting plugin: epgsearchonly
huhti 29 20:48:27 xpc vdr[1171]: [1171] deleting plugin: epgsearch
huhti 29 20:48:27 xpc vdr[1171]: [1171] deleting plugin: conflictcheckonly
huhti 29 20:48:27 xpc vdr[1171]: [1295] epg data reader thread ended (pid=1171, 
tid=1295)
huhti 29 20:48:27 xpc vdr[1171]: [1171] max. latency time 0 seconds

[Bug 1547844] Re: systemd does not allow fsck to finish on ubuntu 15.10

2016-02-20 Thread kex
Then: running fsck in recovery mode works nice:

root@xpc:~# fsck /dev/mapper/xpcvg-home 
fsck – util-linux 2.26.2
e2fsck 1.42.12 (29-Aug-2014)
/dev/mapper/xpcvg-home has been mounted 166 times without being checked, check 
forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/mapper/xpcvg-home: 368728/65536000 files (1.5% non-contiguous), 
78669441/262144000 blocks
root@xpc:~# tune2fs -l /dev/mapper/xpcvg-home 
tune2fs 1.42.12 (29-Aug-2014)
Filesystem volume name:   
Last mounted on:  /home
Filesystem UUID:  db583624-afb4-41cb-8b2d-640bee2de61b
Filesystem magic number:  0xEF53
Filesystem revision #:1 (dynamic)
Filesystem features:  has_journal ext_attr resize_inode dir_index filetype 
extent sparse_super large_file uninit_bg
Filesystem flags: signed_directory_hash 
Default mount options:(none)
Filesystem state: clean
Errors behavior:  Continue
Filesystem OS type:   Linux
Inode count:  65536000
Block count:  262144000
Reserved block count: 13107200
Free blocks:  183474559
Free inodes:  65167272
First block:  0
Block size:   4096
Fragment size:4096
Reserved GDT blocks:  961
Blocks per group: 32768
Fragments per group:  32768
Inodes per group: 8192
Inode blocks per group:   512
RAID stride:  128
RAID stripe width:384
Filesystem created:   Mon Jul 25 12:23:50 2011
Last mount time:  Sat Feb 20 09:34:41 2016
Last write time:  Sat Feb 20 14:39:09 2016
Mount count:  0
Maximum mount count:  157
Last checked: Sat Feb 20 14:39:09 2016
Check interval:   15552000 (6 months)
Next check after: Thu Aug 18 15:39:09 2016
Lifetime writes:  1114 GB
Reserved blocks uid:  0 (user root)
Reserved blocks gid:  0 (group root)
First inode:  11
Inode size:   256
Required extra isize: 28
Desired extra isize:  28
Journal inode:8
Default directory hash:   half_md4
Directory Hash Seed:  ea4a0233-d8af-4c51-9302-140a4affacdf
Journal backup:   inode blocks

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

Title:
  systemd does not allow fsck to finish on ubuntu 15.10

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

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

[Bug 1547844] [NEW] systemd does not allow fsck to finish on ubuntu 15.10

2016-02-20 Thread kex
Public bug reported:


during normal boots, fsck runs fine with small partitions.  But I have two big 
partitions and systemd seems to abort fsck somewhere between 5 to 10 minutes 
from start.  This results in the partition being checked again at every boot.  
After manual run in recovery mode, everything is OK again. 

See e.g.

 sudo tune2fs -l /dev/mapper/xpcvg-home 
tune2fs 1.42.12 (29-Aug-2014)
Filesystem volume name:   
Last mounted on:  /home
Filesystem UUID:  db583624-afb4-41cb-8b2d-640bee2de61b
Filesystem magic number:  0xEF53
Filesystem revision #:1 (dynamic)
Filesystem features:  has_journal ext_attr resize_inode dir_index filetype 
needs_recovery extent sparse_super large_file uninit_bg
Filesystem flags: signed_directory_hash 
Default mount options:(none)
Filesystem state: clean
Errors behavior:  Continue
Filesystem OS type:   Linux
Inode count:  65536000
Block count:  262144000
Reserved block count: 13107200
Free blocks:  183474571
Free inodes:  65167292
First block:  0
Block size:   4096
Fragment size:4096
Reserved GDT blocks:  961
Blocks per group: 32768
Fragments per group:  32768
Inodes per group: 8192
Inode blocks per group:   512
RAID stride:  128
RAID stripe width:384
Filesystem created:   Mon Jul 25 12:23:50 2011
Last mount time:  Sat Feb 20 09:34:41 2016
Last write time:  Sat Feb 20 09:34:41 2016
Mount count:  166
Maximum mount count:  157
Last checked: Sun Nov 29 14:02:12 2015
Check interval:   15552000 (6 months)
Next check after: Fri May 27 15:02:12 2016
Lifetime writes:  1113 GB
Reserved blocks uid:  0 (user root)
Reserved blocks gid:  0 (group root)
First inode:  11
Inode size:   256
Required extra isize: 28
Desired extra isize:  28
Journal inode:8
First orphan inode:   65143018
Default directory hash:   half_md4
Directory Hash Seed:  ea4a0233-d8af-4c51-9302-140a4affacdf
Journal backup:   inode blocks

journalctl says:
helmi 20 09:30:21 xpc systemd-fsck[720]: /dev/mapper/xpcvg-home has been 
mounted 165 times without being checked, check forced.
helmi 20 09:34:40 xpc systemd-fsck[720]: fsck: Warning... fsck.ext4 for device 
/dev/mapper/xpcvg-home exited with signal 13.
helmi 20 09:34:40 xpc systemd-fsck[720]: fsck failed with error code 8.
helmi 20 09:34:40 xpc systemd-fsck[720]: Ignoring error.
helmi 20 09:34:40 xpc systemd[1]: Started File System Check on 
/dev/mapper/xpcvg-home.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: systemd 225-1ubuntu9
ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
Uname: Linux 4.2.0-27-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Feb 20 14:20:24 2016
InstallationDate: Installed on 2012-12-22 (1154 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic 
root=UUID=a21f1300-e2a3-44c9-a667-86fc6184627b ro nomdmonddf nomdmonisw 
libata.noacpi=1 irqpoll all_generic_ide=1 ide-pci-generic.all-generic-ide=1 
usbcore.autosuspend=-1 usbcore.old_scheme_first=1 libata.force=8:1.5G 
xhci_hcd.quirks=262144
SourcePackage: systemd
UpgradeStatus: Upgraded to wily on 2015-10-23 (119 days ago)
dmi.bios.date: 08/15/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1603
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MAXIMUS VI EXTREME
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIEXTREME:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS

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


** Tags: amd64 apport-bug wily

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

Title:
  systemd does not allow fsck to finish on ubuntu 15.10

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

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


[Bug 1452644] Re: NFSd does not start due to systemd ordering cycle with setserial

2015-06-11 Thread kex
I can confirm that the proposed package fixes the bug for me.

I did not have readahead-fedora package, but ureadahead.  However, I had
fedora-readahead with 14.04.  It is possible that some files were not
removed during upgrade to 15.04.  apt-get remove ureadahead; apt-get
purge readahead-fedora fixed this for me (in addition to using the
proposed setserial).  Now nfsd starts.

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

Title:
  NFSd does not start due to systemd ordering cycle with setserial

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

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


[Bug 1452644] Re: NFSd does not start due to systemd ordering cycle with setserial

2015-06-11 Thread kex
I can confirm that the proposed package fixes the bug for me.

I did not have readahead-fedora package, but ureadahead.  However, I had
fedora-readahead with 14.04.  It is possible that some files were not
removed during upgrade to 15.04.  apt-get remove ureadahead; apt-get
purge readahead-fedora fixed this for me (in addition to using the
proposed setserial).  Now nfsd starts.

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

Title:
  NFSd does not start due to systemd ordering cycle with setserial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/setserial/+bug/1452644/+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 1452644] Re: NFSd does not start due to systemd ordering cycle with setserial

2015-06-10 Thread kex
hello.

The fix removes setserial from the dependency loop, but there are other
dependencies, so nfsd is still not starting:

kesä 10 22:29:41 xpc systemd[1]: Cannot add dependency job for unit 
gssproxy.service, ignoring: Unit gssproxy.service failed to load: No such file 
or directory.
kesä 10 22:29:41 xpc systemd[1]: Cannot add dependency job for unit 
fancontrol.service, ignoring: Unit fancontrol.service is masked.
kesä 10 22:29:41 xpc systemd[1]: Found ordering cycle on 
remote-fs-pre.target/start
kesä 10 22:29:41 xpc systemd[1]: Found dependency on nfs-server.service/start
kesä 10 22:29:41 xpc systemd[1]: Found dependency on network.target/start
kesä 10 22:29:41 xpc systemd[1]: Found dependency on 
NetworkManager.service/verify-active
kesä 10 22:29:41 xpc systemd[1]: Found dependency on basic.target/start
kesä 10 22:29:41 xpc systemd[1]: Found dependency on sockets.target/start
kesä 10 22:29:41 xpc systemd[1]: Found dependency on cups.socket/start
kesä 10 22:29:41 xpc systemd[1]: Found dependency on sysinit.target/start
kesä 10 22:29:41 xpc systemd[1]: Found dependency on 
later-readahead.service/start
kesä 10 22:29:41 xpc systemd[1]: Found dependency on remote-fs.target/start
kesä 10 22:29:41 xpc systemd[1]: Found dependency on remote-fs-pre.target/start
kesä 10 22:29:41 xpc systemd[1]: Breaking ordering cycle by deleting job 
nfs-server.service/start
kesä 10 22:29:41 xpc systemd[1]: Job nfs-server.service/start deleted to break 
ordering cycle starting with remote-fs-pre.target/start
kesä 10 22:29:41 xpc systemd[1]: Dependency failed for pNFS block layout 
mapping daemon.
kesä 10 22:29:41 xpc systemd[1]: ureadahead.service failed.

sudo systemctl status setserial
● setserial.service - controls configuration of serial ports
   Loaded: loaded (/lib/systemd/system/setserial.service; enabled; vendor 
preset: enabled)
   Active: active (exited) since ke 2015-06-10 22:29:46 EEST; 31s ago
 Docs: man:setserial(8)
  Process: 862 ExecStart=/etc/init.d/setserial start (code=exited, 
status=0/SUCCESS)
 Main PID: 862 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/setserial.service

kesä 10 22:29:46 xpc systemd[1]: Starting controls configuration of serial.
kesä 10 22:29:46 xpc setserial[862]: Loading the saved-state of the serial.
kesä 10 22:29:46 xpc setserial[862]: /dev/ttyS0 at 0x03f8 (irq = 4) is a 16550A
kesä 10 22:29:46 xpc systemd[1]: Started controls configuration of serial ...s.
Hint: Some lines were ellipsized, use -l to show in full.
kex@xpc:~$ sudo systemctl status nfs-kernel-server
● nfs-server.service - NFS server and services
   Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor 
preset: enabled)
   Active: inactive (dead)
kex@xpc:~$ rpcinfo
   program version netid addressserviceowner
104tcp6  ::.0.111   portmapper superuser
103tcp6  ::.0.111   portmapper superuser
104udp6  ::.0.111   portmapper superuser
103udp6  ::.0.111   portmapper superuser
104tcp   0.0.0.0.0.111  portmapper superuser
103tcp   0.0.0.0.0.111  portmapper superuser
102tcp   0.0.0.0.0.111  portmapper superuser
104udp   0.0.0.0.0.111  portmapper superuser
103udp   0.0.0.0.0.111  portmapper superuser
102udp   0.0.0.0.0.111  portmapper superuser
104local /run/rpcbind.sock  portmapper superuser
103local /run/rpcbind.sock  portmapper superuser

Setserial 2.17-48ubuntu0.1


** Tags removed: verification-needed
** Tags added: verification-failed

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

Title:
  NFSd does not start due to systemd ordering cycle with setserial

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

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

[Bug 1452644] Re: NFSd does not start due to systemd ordering cycle with setserial

2015-06-10 Thread kex
hello.

The fix removes setserial from the dependency loop, but there are other
dependencies, so nfsd is still not starting:

kesä 10 22:29:41 xpc systemd[1]: Cannot add dependency job for unit 
gssproxy.service, ignoring: Unit gssproxy.service failed to load: No such file 
or directory.
kesä 10 22:29:41 xpc systemd[1]: Cannot add dependency job for unit 
fancontrol.service, ignoring: Unit fancontrol.service is masked.
kesä 10 22:29:41 xpc systemd[1]: Found ordering cycle on 
remote-fs-pre.target/start
kesä 10 22:29:41 xpc systemd[1]: Found dependency on nfs-server.service/start
kesä 10 22:29:41 xpc systemd[1]: Found dependency on network.target/start
kesä 10 22:29:41 xpc systemd[1]: Found dependency on 
NetworkManager.service/verify-active
kesä 10 22:29:41 xpc systemd[1]: Found dependency on basic.target/start
kesä 10 22:29:41 xpc systemd[1]: Found dependency on sockets.target/start
kesä 10 22:29:41 xpc systemd[1]: Found dependency on cups.socket/start
kesä 10 22:29:41 xpc systemd[1]: Found dependency on sysinit.target/start
kesä 10 22:29:41 xpc systemd[1]: Found dependency on 
later-readahead.service/start
kesä 10 22:29:41 xpc systemd[1]: Found dependency on remote-fs.target/start
kesä 10 22:29:41 xpc systemd[1]: Found dependency on remote-fs-pre.target/start
kesä 10 22:29:41 xpc systemd[1]: Breaking ordering cycle by deleting job 
nfs-server.service/start
kesä 10 22:29:41 xpc systemd[1]: Job nfs-server.service/start deleted to break 
ordering cycle starting with remote-fs-pre.target/start
kesä 10 22:29:41 xpc systemd[1]: Dependency failed for pNFS block layout 
mapping daemon.
kesä 10 22:29:41 xpc systemd[1]: ureadahead.service failed.

sudo systemctl status setserial
● setserial.service - controls configuration of serial ports
   Loaded: loaded (/lib/systemd/system/setserial.service; enabled; vendor 
preset: enabled)
   Active: active (exited) since ke 2015-06-10 22:29:46 EEST; 31s ago
 Docs: man:setserial(8)
  Process: 862 ExecStart=/etc/init.d/setserial start (code=exited, 
status=0/SUCCESS)
 Main PID: 862 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/setserial.service

kesä 10 22:29:46 xpc systemd[1]: Starting controls configuration of serial.
kesä 10 22:29:46 xpc setserial[862]: Loading the saved-state of the serial.
kesä 10 22:29:46 xpc setserial[862]: /dev/ttyS0 at 0x03f8 (irq = 4) is a 16550A
kesä 10 22:29:46 xpc systemd[1]: Started controls configuration of serial ...s.
Hint: Some lines were ellipsized, use -l to show in full.
kex@xpc:~$ sudo systemctl status nfs-kernel-server
● nfs-server.service - NFS server and services
   Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor 
preset: enabled)
   Active: inactive (dead)
kex@xpc:~$ rpcinfo
   program version netid addressserviceowner
104tcp6  ::.0.111   portmapper superuser
103tcp6  ::.0.111   portmapper superuser
104udp6  ::.0.111   portmapper superuser
103udp6  ::.0.111   portmapper superuser
104tcp   0.0.0.0.0.111  portmapper superuser
103tcp   0.0.0.0.0.111  portmapper superuser
102tcp   0.0.0.0.0.111  portmapper superuser
104udp   0.0.0.0.0.111  portmapper superuser
103udp   0.0.0.0.0.111  portmapper superuser
102udp   0.0.0.0.0.111  portmapper superuser
104local /run/rpcbind.sock  portmapper superuser
103local /run/rpcbind.sock  portmapper superuser

Setserial 2.17-48ubuntu0.1


** Tags removed: verification-needed
** Tags added: verification-failed

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

Title:
  NFSd does not start due to systemd ordering cycle with setserial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/setserial/+bug/1452644/+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 1452644] [NEW] vivid NFSd does not start due to systemd ordering cycle

2015-05-07 Thread kex
Public bug reported:

NFSd does not start due to systemd ordering cycle.

Manually starting with systemctl start nfs-kernel-server after boot
works fine.

here systemd lines from dmesg:

[2.559819] random: systemd-udevd urandom read with 8 bits of entropy 
available
[   43.181921] systemd[1]: Inserted module 'autofs4'
[   43.210140] systemd[1]: systemd 219 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS 
+ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
[   43.234042] systemd[1]: Detected architecture x86-64.
[   43.328158] systemd[1]: Set hostname to xpc.
[   43.434248] systemd-sysv-generator[337]: Overwriting existing symlink 
/run/systemd/generator.late/mdadm-waitidle.service with real service
[   43.569341] systemd[1]: Cannot add dependency job for unit gssproxy.service, 
ignoring: Unit gssproxy.service failed to load: No such file or directory.
[   43.595080] systemd[1]: Found ordering cycle on nfs-server.service/start
[   43.620748] systemd[1]: Found dependency on network.target/start
[   43.646476] systemd[1]: Found dependency on NetworkManager.service/start
[   43.672292] systemd[1]: Found dependency on basic.target/start
[   43.697952] systemd[1]: Found dependency on sockets.target/start
[   43.723381] systemd[1]: Found dependency on cups.socket/start
[   43.748530] systemd[1]: Found dependency on sysinit.target/start
[   43.773533] systemd[1]: Found dependency on setserial.service/start
[   43.798185] systemd[1]: Found dependency on remote-fs.target/start
[   43.822739] systemd[1]: Found dependency on remote-fs-pre.target/start
[   43.871768] systemd[1]: Found dependency on nfs-server.service/start
[   43.896442] systemd[1]: Breaking ordering cycle by deleting job 
network.target/start
[   43.921641] systemd[1]: Job network.target/start deleted to break ordering 
cycle starting with nfs-server.service/start
[   44.109024] systemd[1]: Reached target Encrypted Volumes.
[   44.135558] systemd[1]: Starting Encrypted Volumes.
[   44.189110] systemd[1]: Created slice Root Slice.
[   44.215900] systemd[1]: Starting Root Slice.
[   44.269513] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[   44.296806] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[   44.351462] systemd[1]: Listening on LVM2 metadata daemon socket.
[   44.378792] systemd[1]: Starting LVM2 metadata daemon socket.
[   44.459356] systemd[1]: Dependency failed for pNFS block layout mapping 
daemon.
[   44.486177] systemd[1]: Job nfs-blkmap.service/start failed with result 
'dependency'.
[   44.539816] systemd[1]: Listening on Delayed Shutdown Socket.
[   44.566481] systemd[1]: Starting Delayed Shutdown Socket.
[   44.619658] systemd[1]: Set up automount Arbitrary Executable File Formats 
File System Automount Point.
[   44.647063] systemd[1]: Starting Arbitrary Executable File Formats File 
System Automount Point.
[   44.702240] systemd[1]: Listening on Journal Socket (/dev/log).
[   44.730201] systemd[1]: Starting Journal Socket (/dev/log).
[   44.786161] systemd[1]: Listening on fsck to fsckd communication Socket.
[   44.814391] systemd[1]: Starting fsck to fsckd communication Socket.
[   44.870869] systemd[1]: Listening on udev Control Socket.
[   44.899276] systemd[1]: Starting udev Control Socket.
[   44.927774] systemd[1]: Started Forward Password Requests to Wall Directory 
Watch.
[   44.956547] systemd[1]: Starting Forward Password Requests to Wall Directory 
Watch.
[   45.013546] systemd[1]: Created slice User and Session Slice.
[   45.040955] systemd[1]: Starting User and Session Slice.
[   45.097664] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[   45.125626] systemd[1]: Starting Device-mapper event daemon FIFOs.
[   45.181619] systemd[1]: Listening on udev Kernel Socket.
[   45.209643] systemd[1]: Starting udev Kernel Socket.
[   45.263885] systemd[1]: Listening on Journal Socket.
[   45.290707] systemd[1]: Starting Journal Socket.
[   45.344645] systemd[1]: Listening on Journal Audit Socket.
[   45.371233] systemd[1]: Starting Journal Audit Socket.
[   45.423314] systemd[1]: Created slice System Slice.
[   45.449542] systemd[1]: Starting System Slice.
[   45.475703] systemd[1]: Started Kernel Module supporting RPCSEC_GSS.
[   45.502333] systemd[1]: Starting LSB: controls configuration of serial 
ports...
[   45.556425] systemd[1]: Mounting POSIX Message Queue File System...
[   45.639083] systemd[1]: Created slice system-getty.slice.
[   45.95] systemd[1]: Starting system-getty.slice.
[   45.694307] systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. 
using dmeventd or progress polling...
[   45.750548] systemd[1]: Mounting Debug File System...
[   45.808508] systemd[1]: Started Set Up Additional Binary Formats.
[   45.863949] systemd[1]: Started Braille Device Support.
[   45.891808] systemd[1]: Starting Braille Device Support...
[   45.974979] systemd[1]: Created slice 

[Bug 1452644] Re: vivid NFSd does not start due to systemd ordering cycle

2015-05-07 Thread kex
I wonder if some update arrived between the bug reporting...

After reboot:
[   43.777385] systemd[1]: Found dependency on nfs-server.service/start
[   43.803123] systemd[1]: Found dependency on network.target/start
[   43.828678] systemd[1]: Breaking ordering cycle by deleting job 
NetworkManager.service/start

the rpcinfo shows it started OK.

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

Title:
  vivid NFSd does not start due to systemd ordering cycle

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1452644/+subscriptions

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


[Bug 1452644] Re: vivid NFSd does not start due to systemd ordering cycle

2015-05-07 Thread kex
There is something weird going on, since every boot behaves a bit
differently:

[   44.264445] systemd[1]: Found ordering cycle on nfs-server.service/start
[   44.264447] systemd[1]: Found dependency on nfs-mountd.service/start
[   44.264448] systemd[1]: Found dependency on network.target/start
[   44.264449] systemd[1]: Found dependency on NetworkManager.service/start
[   44.264450] systemd[1]: Found dependency on basic.target/start
[   44.264451] systemd[1]: Found dependency on sockets.target/start
[   44.264452] systemd[1]: Found dependency on acpid.socket/start
[   44.264453] systemd[1]: Found dependency on sysinit.target/start
[   44.264455] systemd[1]: Found dependency on setserial.service/start
[   44.264457] systemd[1]: Found dependency on remote-fs.target/start
[   44.264460] systemd[1]: Found dependency on remote-fs-pre.target/start
[   44.264461] systemd[1]: Found dependency on nfs-server.service/start
[   44.264462] systemd[1]: Breaking ordering cycle by deleting job 
nfs-mountd.service/start
[   44.264463] systemd[1]: Job nfs-mountd.service/start deleted to break 
ordering cycle starting with nfs-server.service/start

This time NFS is not working.

rpcinfo
   program version netid addressserviceowner
104tcp6  ::.0.111   portmapper superuser
103tcp6  ::.0.111   portmapper superuser
104udp6  ::.0.111   portmapper superuser
103udp6  ::.0.111   portmapper superuser
104tcp   0.0.0.0.0.111  portmapper superuser
103tcp   0.0.0.0.0.111  portmapper superuser
102tcp   0.0.0.0.0.111  portmapper superuser
104udp   0.0.0.0.0.111  portmapper superuser
103udp   0.0.0.0.0.111  portmapper superuser
102udp   0.0.0.0.0.111  portmapper superuser
104local /run/rpcbind.sock  portmapper superuser
103local /run/rpcbind.sock  portmapper superuser

But sudo systemctl start nfs-kernel-server
starts nfs server beautifully

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

Title:
  vivid NFSd does not start due to systemd ordering cycle

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1452644/+subscriptions

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


[Bug 1451009] Re: kernel problems; cx23885 hangs

2015-05-05 Thread kex
: [82771.907162]  [812016c7] 
do_last+0x227/0x12c0
  May  1 13:16:47 xpc kernel: [82771.907164]  [81203d68] 
path_openat+0x88/0x610
  May  1 13:16:47 xpc kernel: [82771.907167]  [811a68fc] ? 
tlb_finish_mmu+0x1c/0x50
  May  1 13:16:47 xpc kernel: [82771.907169]  [8120550a] 
do_filp_open+0x3a/0xb0
  May  1 13:16:47 xpc kernel: [82771.907171]  [812122f7] ? 
__alloc_fd+0xa7/0x130
  May  1 13:16:47 xpc kernel: [82771.907172]  [811f254a] 
do_sys_open+0x12a/0x280
  May  1 13:16:47 xpc kernel: [82771.907174]  [811f26be] 
SyS_open+0x1e/0x20
  May  1 13:16:47 xpc kernel: [82771.907176]  [817c934d] 
system_call_fastpath+0x16/0x1b
  
  lsb_release -rd
  Description:  Ubuntu 15.04
  Release:  15.04
  
  kex@xpc:~$ apt-cache policy linux-image-extra-3.19.0-15-generic
  linux-image-extra-3.19.0-15-generic:
-   Asennettu: 3.19.0-15.15
-   Ehdokas:   3.19.0-15.15
-   Versiotaulukko:
-  *** 3.19.0-15.15 0
- 500 http://fi.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Asennettu: 3.19.0-15.15
+   Ehdokas:   3.19.0-15.15
+   Versiotaulukko:
+  *** 3.19.0-15.15 0
+ 500 http://fi.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  kex@xpc:~$ apt-cache policy linux-image-generic
  linux-image-generic:
-   Asennettu: 3.19.0.15.14
-   Ehdokas:   3.19.0.15.14
-   Versiotaulukko:
-  *** 3.19.0.15.14 0
- 500 http://fi.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Asennettu: 3.19.0.15.14
+   Ehdokas:   3.19.0.15.14
+   Versiotaulukko:
+  *** 3.19.0.15.14 0
+ 500 http://fi.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
+ 100 /var/lib/dpkg/status
  kex@xpc:~$
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-generic 3.19.0.15.14
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  kex2431 F pulseaudio
-  /dev/snd/controlC0:  kex2431 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  kex2431 F pulseaudio
+  /dev/snd/controlC0:  kex2431 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat May  2 13:42:04 2015
  HibernationDevice: RESUME=UUID=36e8bbe2-fb57-4154-aeaf-f5a4f3d1b467
  InstallationDate: Installed on 2012-12-22 (860 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  IwConfig:
-  eth1  no wireless extensions.
-  
-  lono wireless extensions.
+  eth1  no wireless extensions.
+ 
+  lono wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic 
root=UUID=a21f1300-e2a3-44c9-a667-86fc6184627b ro nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw
  RelatedPackageVersions:
-  linux-restricted-modules-3.19.0-15-generic N/A
-  linux-backports-modules-3.19.0-15-generic  N/A
-  linux-firmware 1.143
+  linux-restricted-modules-3.19.0-15-generic N/A
+  linux-backports-modules-3.19.0-15-generic  N/A
+  linux-firmware 1.143
  RfKill:
-  
+ 
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (8 days ago)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAXIMUS VI EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIEXTREME:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

Title:
  kernel problems; cx23885 hangs

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

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

[Bug 1451009] [NEW] kernel problems; cx23885 hangs

2015-05-02 Thread kex
Description:Ubuntu 15.04
Release:15.04

kex@xpc:~$ apt-cache policy linux-image-extra-3.19.0-15-generic
linux-image-extra-3.19.0-15-generic:
  Asennettu: 3.19.0-15.15
  Ehdokas:   3.19.0-15.15
  Versiotaulukko:
 *** 3.19.0-15.15 0
500 http://fi.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status

kex@xpc:~$ apt-cache policy linux-image-generic
linux-image-generic:
  Asennettu: 3.19.0.15.14
  Ehdokas:   3.19.0.15.14
  Versiotaulukko:
 *** 3.19.0.15.14 0
500 http://fi.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status
kex@xpc:~$

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-generic 3.19.0.15.14
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  kex2431 F pulseaudio
 /dev/snd/controlC0:  kex2431 F pulseaudio
CurrentDesktop: Unity
Date: Sat May  2 13:42:04 2015
HibernationDevice: RESUME=UUID=36e8bbe2-fb57-4154-aeaf-f5a4f3d1b467
InstallationDate: Installed on 2012-12-22 (860 days ago)
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
IwConfig:
 eth1  no wireless extensions.
 
 lono wireless extensions.
MachineType: ASUS All Series
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic 
root=UUID=a21f1300-e2a3-44c9-a667-86fc6184627b ro nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-15-generic N/A
 linux-backports-modules-3.19.0-15-generic  N/A
 linux-firmware 1.143
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to vivid on 2015-04-23 (8 days ago)
dmi.bios.date: 08/15/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1603
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MAXIMUS VI EXTREME
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIEXTREME:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS

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


** Tags: amd64 apport-bug vivid

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

Title:
  kernel problems; cx23885 hangs

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

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


[Bug 1451009] Re: kernel problems; cx23885 hangs

2015-05-02 Thread kex
another two excerpts from syslog

May  1 13:56:47 xpc kernel: [85171.089467] INFO: task section handler:2730 
blocked for more than 120 seconds.
May  1 13:56:47 xpc kernel: [85171.089470]   Tainted: G   OE  
3.19.0-15-generic #15-Ubuntu
May  1 13:56:47 xpc kernel: [85171.089471] echo 0  
/proc/sys/kernel/hung_task_timeout_secs disables this message.
May  1 13:56:47 xpc kernel: [85171.089472] section handler D 8800b31c7c08   
  0  2730   2590 0x
May  1 13:56:47 xpc kernel: [85171.089475]  8800b31c7c08 8801b5ee3ae0 
00014200 8800b31c7fd8
May  1 13:56:47 xpc kernel: [85171.089477]  00014200 8801b8278000 
8801b5ee3ae0 8800b31c7be8
May  1 13:56:47 xpc kernel: [85171.089478]  8801400bbf10 7fff 
8801400bbf08 8801b5ee3ae0
May  1 13:56:47 xpc kernel: [85171.089480] Call Trace:
May  1 13:56:47 xpc kernel: [85171.089486]  [817c49c9] 
schedule+0x29/0x70
May  1 13:56:47 xpc kernel: [85171.089489]  [817c7fac] 
schedule_timeout+0x20c/0x280
May  1 13:56:47 xpc kernel: [85171.089494]  [811811a7] ? 
__free_pages+0x27/0x30
May  1 13:56:47 xpc kernel: [85171.089496]  [811811f0] ? 
free_pages.part.67+0x40/0x50
May  1 13:56:47 xpc kernel: [85171.089497]  [81181213] ? 
free_pages+0x13/0x20
May  1 13:56:47 xpc kernel: [85171.089499]  [817c6384] 
wait_for_completion+0xa4/0x170
May  1 13:56:47 xpc kernel: [85171.089502]  [810a1dd0] ? 
wake_up_state+0x20/0x20
May  1 13:56:47 xpc kernel: [85171.089505]  [810949d3] 
kthread_stop+0x53/0x100
May  1 13:56:47 xpc kernel: [85171.089517]  [c06d1aa4] 
vb2_thread_stop+0x64/0xd0 [videobuf2_core]
May  1 13:56:47 xpc kernel: [85171.089519]  [c077113e] 
vb2_dvb_stop_feed+0x4e/0x70 [videobuf2_dvb]
May  1 13:56:47 xpc kernel: [85171.089524]  [c07156ab] 
dmx_section_feed_stop_filtering+0x4b/0xe0 [dvb_core]
May  1 13:56:47 xpc kernel: [85171.089527]  [c0712b5b] 
dvb_dmxdev_feed_stop+0xeb/0x100 [dvb_core]
May  1 13:56:47 xpc kernel: [85171.089530]  [c0712d5c] 
dvb_dmxdev_filter_stop+0x9c/0xe0 [dvb_core]
May  1 13:56:47 xpc kernel: [85171.089533]  [c0713248] 
dvb_demux_release+0x48/0x260 [dvb_core]
May  1 13:56:47 xpc kernel: [85171.089537]  [811f4f97] 
__fput+0xe7/0x250
May  1 13:56:47 xpc kernel: [85171.089539]  [811f514e] 
fput+0xe/0x10
May  1 13:56:47 xpc kernel: [85171.089541]  [81092d24] 
task_work_run+0xd4/0xf0
May  1 13:56:47 xpc kernel: [85171.089544]  [81014ff7] 
do_notify_resume+0x97/0xb0
May  1 13:56:47 xpc kernel: [85171.089546]  [817c95ef] 
int_signal+0x12/0x17

May  1 13:58:47 xpc kernel: [85291.048580] INFO: task section handler:2730 
blocked for more than 120 seconds.
May  1 13:58:47 xpc kernel: [85291.048584]   Tainted: G   OE  
3.19.0-15-generic #15-Ubuntu
May  1 13:58:47 xpc kernel: [85291.048585] echo 0  
/proc/sys/kernel/hung_task_timeout_secs disables this message.
May  1 13:58:47 xpc kernel: [85291.048586] section handler D 8800b31c7c08   
  0  2730   2590 0x
May  1 13:58:47 xpc kernel: [85291.048589]  8800b31c7c08 8801b5ee3ae0 
00014200 8800b31c7fd8
May  1 13:58:47 xpc kernel: [85291.048590]  00014200 8801b8278000 
8801b5ee3ae0 8800b31c7be8
May  1 13:58:47 xpc kernel: [85291.048592]  8801400bbf10 7fff 
8801400bbf08 8801b5ee3ae0
May  1 13:58:47 xpc kernel: [85291.048593] Call Trace:
May  1 13:58:47 xpc kernel: [85291.048599]  [817c49c9] 
schedule+0x29/0x70
May  1 13:58:47 xpc kernel: [85291.048601]  [817c7fac] 
schedule_timeout+0x20c/0x280
May  1 13:58:47 xpc kernel: [85291.048605]  [811811a7] ? 
__free_pages+0x27/0x30
May  1 13:58:47 xpc kernel: [85291.048607]  [811811f0] ? 
free_pages.part.67+0x40/0x50
May  1 13:58:47 xpc kernel: [85291.048608]  [81181213] ? 
free_pages+0x13/0x20
May  1 13:58:47 xpc kernel: [85291.048610]  [817c6384] 
wait_for_completion+0xa4/0x170
May  1 13:58:47 xpc kernel: [85291.048612]  [810a1dd0] ? 
wake_up_state+0x20/0x20
May  1 13:58:47 xpc kernel: [85291.048615]  [810949d3] 
kthread_stop+0x53/0x100
May  1 13:58:47 xpc kernel: [85291.048627]  [c06d1aa4] 
vb2_thread_stop+0x64/0xd0 [videobuf2_core]
May  1 13:58:47 xpc kernel: [85291.048629]  [c077113e] 
vb2_dvb_stop_feed+0x4e/0x70 [videobuf2_dvb]
May  1 13:58:47 xpc kernel: [85291.048634]  [c07156ab] 
dmx_section_feed_stop_filtering+0x4b/0xe0 [dvb_core]
May  1 13:58:47 xpc kernel: [85291.048637]  [c0712b5b] 
dvb_dmxdev_feed_stop+0xeb/0x100 [dvb_core]
May  1 13:58:47 xpc kernel: [85291.048640]  [c0712d5c] 
dvb_dmxdev_filter_stop+0x9c/0xe0 [dvb_core]
May  1 13:58:47 xpc kernel: [85291.048642]  [c0713248] 
dvb_demux_release+0x48/0x260 [dvb_core]
May  1 13:58:47 xpc kernel: [85291.048646]  [811f4f97] 
__fput+0xe7/0x250
May  1 13:58:47 xpc kernel: [85291.048647]  

[Bug 1019523] [NEW] unable to import photos (gthumb/shotwell/file system)

2012-06-30 Thread kex
Public bug reported:

I am unable to import photos from my canon camera.

Shotwell just crashes.

Gthumb gives the following error:

DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply.
Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.

The whole computer becomes unresponsive for about a minute, and the led
in the camera flashes.

Trying to look at .gvfs with ls: it is possible to cd to the DCIM
directory, but ls makes again the system unresponsive, and after a
minute or two, there is an I/O error

lsusb tells: 
Bus 009 Device 009: ID 04a9:3101 Canon, Inc.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gthumb 3:2.14.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Uname: Linux 3.2.0-26-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Sat Jun 30 09:56:43 2012
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
SourcePackage: gthumb
UpgradeStatus: Upgraded to precise on 2012-04-25 (65 days ago)

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug precise

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

Title:
  unable to import photos (gthumb/shotwell/file system)

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

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


[Bug 1019523] Re: unable to import photos (gthumb/shotwell/file system)

2012-06-30 Thread kex
-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1019523

Title:
  unable to import photos (gthumb/shotwell/file system)

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

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


[Bug 1019523] Re: unable to import photos (gthumb/shotwell/file system)

2012-06-30 Thread kex
a note; with a different Canon camera:

lsusb: 
Bus 009 Device 002: ID 04a9:314f Canon, Inc. Powershot SD1000

it works fine.  The problem seems to be with the Canon EOS camera driver
or some package controlling it?

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

Title:
  unable to import photos (gthumb/shotwell/file system)

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

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


[Bug 1019523] Re: unable to import photos (gthumb/shotwell/file system)

2012-06-30 Thread kex
Additional note; I tried the Printing/PTP mode in the camera settings
instead of PC-connection; with PTP mode the photos are transferred OK;
the problem only concerns the PC-connection mode.

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

Title:
  unable to import photos (gthumb/shotwell/file system)

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

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


[Bug 880266] Re: oneiric boot sequence very slow with lvm

2012-05-01 Thread kex
updated to precise pangolin and it seems that it does not have the boot
issue for me.  I don't know whether they fixed it or is it just a race
condition that is not triggered for some reason.

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

Title:
  oneiric boot sequence very slow with lvm

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

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


[Bug 880266] Re: oneiric boot sequence very slow with lvm

2012-04-06 Thread kex
Is there an option of switching to a different boot process, like SYSV
type init scripts etc. within Ubuntu?

I have a similar setup in a debian system and it has no such problem.  I
would not want to start switching to a different distribution.

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

Title:
  oneiric boot sequence very slow with lvm

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

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


[Bug 880266] Re: oneiric boot sequence very slow with lvm

2012-01-28 Thread kex
The workaround did not seem to work for me.  I guess the bug I am
experiencing is different, or the combination of RAID+LVM needs yet
another workaround to work.

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

Title:
  oneiric boot sequence very slow with lvm

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

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


[Bug 880266] Re: oneiric boot sequence very slow with lvm

2012-01-26 Thread kex
I was too hasty.  The problem is still here.  Is it possible to switch
to the old (sysV?) style boot sequence?

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

Title:
  oneiric boot sequence very slow with lvm

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

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


[Bug 880266] Re: oneiric boot sequence very slow with lvm

2012-01-23 Thread kex
After the updates of yesterday, the machine has booted much quicker now.
Only a couple of times of experience yet, though.

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

Title:
  oneiric boot sequence very slow with lvm

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

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


[Bug 880266] Re: oneiric boot sequence very slow with lvm

2012-01-13 Thread kex
the boot hangs indefinitely, but if I press ctrl-alt-del, the machine
reboots to grub.  Have to press enter, and the system then boots
normally, but asks if I want to boot with degraded raid.  If I say n,
busybox starts.  Then writing exit results in a nice rest of the boot.
A bit complicated, but works.

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

Title:
  oneiric boot sequence very slow with lvm

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

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


[Bug 880266] Re: oneiric boot sequence very slow with lvm

2012-01-08 Thread kex
I have also this problem with 11.10.

My root device is just a normal SSD, but the /home logical volume and an
additional logical volume is a lvm which currently only has /dev/md0 as
physical disks.  /dev/md0 is a raid 1 with /dev/sda1 and /dev/sdc1 in
it.


** Attachment added: bootchart
   
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/880266/+attachment/2662566/+files/xpc-oneiric-20120107-3.png

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

Title:
  oneiric boot sequence very slow with lvm

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

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


[Bug 531635] Re: Kernel oops with radeon module, kernel modesetting fails

2010-05-05 Thread kex

This bug is closely related to bug #531635.

Adding the kernel boot option: radeon.nomodeset=0
cures the problem.  Then the kernel boots properly.  This is for Radeon 9200SE 
and the final version of Lynx, also with the kernel 2.6.32-22.

-- 
Kernel oops with radeon module, kernel modesetting fails
https://bugs.launchpad.net/bugs/531635
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 531635] Re: Kernel oops with radeon module, kernel modesetting fails

2010-04-30 Thread kex
Still current with lucid and 2.6.32-21-generic #32-ubuntu .

here the kernel oops.  The same symptoms as in the original post.

Booting with the previous kernel Linux xpc 2.6.31-21-generic #59-Ubuntu
and the same packages, it works nicely.

The graphics card used is ATI Radeon 9200 SE.

** Attachment added: oops
   http://launchpadlibrarian.net/46624509/oops

-- 
Kernel oops with radeon module, kernel modesetting fails
https://bugs.launchpad.net/bugs/531635
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 224303] Re: update manager stops when update check is asked manually

2008-11-30 Thread kex
for me, it was the broken su.  After the update I already mentioned,
no problems.

-- 
update manager stops when update check is asked manually
https://bugs.launchpad.net/bugs/224303
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 221142] Re: crash - I don't know what did crash

2008-06-14 Thread kex
hi,

uninstalling Beagle (whatever that is) already solved my problem.

-- 
crash - I don't know what did crash
https://bugs.launchpad.net/bugs/221142
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 222940] Re: HP laserjet only prints the top of the page from Ecinve/Firefox, 8.04

2008-06-14 Thread kex

I tried connecting with USB instead of parport.  At least the first few 
printouts were fine, so I'll buy an USB cable for the printer and see if that 
solves the problem.

-- 
HP laserjet only prints the top of the page from Ecinve/Firefox, 8.04
https://bugs.launchpad.net/bugs/222940
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 222940] Re: HP laserjet only prints the top of the page from Ecinve/Firefox, 8.04

2008-06-03 Thread kex

I printed a document from OpenOffice.  First, it failed as expected, but then I 
looked at the dialog of OpenOffice Printer Settings (From the Print-dialog, on 
the right of the Printer name).  There was a setting for forcing to PostScript 
Level 1 instead of the level coming from the driver.  Setting that to Level 1 
suddenly made the document print properly.

I did not find that setting from the Foomatic/hpijs driver settings,
though.  Looking at that, I tried to find a new printer driver, which
seemed to be found (2.8.2), but the problem still exists.

-- 
HP laserjet only prints the top of the page from Ecinve/Firefox, 8.04
https://bugs.launchpad.net/bugs/222940
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 224303] Re: update manager stops when update check is asked manually

2008-05-10 Thread kex

the update of sudo that appeared yesterday or the day before seems to have 
fixed the problem.

-- 
update manager stops when update check is asked manually
https://bugs.launchpad.net/bugs/224303
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 222940] Re: HP laserjet only prints the top of the page from Ecinve/Firefox, 8.04

2008-05-02 Thread kex

hi,

it seems I still have a problem.  Currently Evince / Firefox /
Openoffice do print normally the first page OK (unless there are heavy
pictures), but for the second or third only the top comes, and the print
job gets stuck.  This happens even without fancy filters (like the ones
fitting several pages on a single one).

All these problems only started after updating to 8.04 (from 7.10).  How
can I help debugging this?

-- 
HP laserjet only prints the top of the page from Ecinve/Firefox, 8.04
https://bugs.launchpad.net/bugs/222940
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 224303] Re: update manager stops when update check is asked manually

2008-05-01 Thread kex

I think I found where the symptom comes from.

I had only host name but not domain set up in the network settings.
This results in sudo giving a warning in the text mode, but still
working.  For starting from menu, it means sudo simply does not work.

-- 
update manager stops when update check is asked manually
https://bugs.launchpad.net/bugs/224303
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 224303] Re: update manager stops when update check is asked manually

2008-04-30 Thread kex
addditional info I found:


[EMAIL PROTECTED]:~$ G_DEBUG=fatal_criticals update-manager
current dist not found in meta-release file
current dist not found in meta-release file

(I upgraded one day before 8.04 was released)

What was peculiar is that when starting from command line, like this,
sudo actually worked.

So I tried to update dist, but it said it is up to date already.  And
crashed when exiting:

[EMAIL PROTECTED]:~$ sudo G_DEBUG=fatal_criticals update-manager --dist-upgrade
sudo: unable to resolve host xpc
ERROR:root:not handled expection:
Traceback (most recent call last):

  File /usr/bin/update-manager, line 94, in module
if controler.askDistUpgrade():

  File /usr/lib/python2.5/site-packages/DistUpgrade/DistUpgradeController.py, 
line 818, in askDistUpgrade
self.cache.requiredDownload)

  File /usr/lib/python2.5/site-packages/DistUpgrade/DistUpgradeViewGtk.py, 
line 537, in confirmChanges
self.confirmChangesMessage +=  \n\nb%s/b %  \

AttributeError: 'DistUpgradeViewGtk' object has no attribute
'confirmChangesMessage'

ERROR:root:failed to import apport python module, can't report bug: No
module named python_hook

-- 
update manager stops when update check is asked manually
https://bugs.launchpad.net/bugs/224303
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 224303] Re: update manager stops when update check is asked manually

2008-04-30 Thread kex

yes, it always hangs.

the command line

[EMAIL PROTECTED]:~$ G_DEBUG=fatal_criticals /usr/bin/sudo -H -S -u root -- 
/usr/sbin/synaptic --non-interactive --update-at-startup
sudo: unable to resolve host xpc
[EMAIL PROTECTED]:~$

opens the synaptic window, and another smaller one where there is a
progress bar advancing, and then closes both of them.  When starting the
update manager from the menu, it shows that the packets have been
updated less than an hour ago.

Btw. a related thing seems that I sometimes I cannot start the synaptic
package manager from the menu at all.  Sometimes it does start.  This
(synaptic) bug I cannot reproduce reliably, it sometimes does not start,
sometimes does.

-- 
update manager stops when update check is asked manually
https://bugs.launchpad.net/bugs/224303
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 224303] Re: update manager stops when update check is asked manually

2008-04-29 Thread kex

** Attachment added: term.log
   http://launchpadlibrarian.net/14018766/term.log

-- 
update manager stops when update check is asked manually
https://bugs.launchpad.net/bugs/224303
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 224303] Re: update manager stops when update check is asked manually

2008-04-29 Thread kex

just an additional note.  Killing the GNOME_SUDO_PASS process immediately 
returns to the update manager window, which becomes responsive again.

-- 
update manager stops when update check is asked manually
https://bugs.launchpad.net/bugs/224303
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 224303] Re: update manager stops when update check is asked manually

2008-04-29 Thread kex

** Attachment added: apt.log
   http://launchpadlibrarian.net/14018751/apt.log

-- 
update manager stops when update check is asked manually
https://bugs.launchpad.net/bugs/224303
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 224303] Re: update manager stops when update check is asked manually

2008-04-29 Thread kex

** Attachment added: main.log
   http://launchpadlibrarian.net/14018763/main.log

-- 
update manager stops when update check is asked manually
https://bugs.launchpad.net/bugs/224303
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 224303] [NEW] update manager stops when update check is asked manually

2008-04-29 Thread kex
Public bug reported:

Binary package hint: update-manager

after updating from 7.10 to 8.04LTS

When starting update manager from the system menu, it looks normal.
When I press check updates (or whatever it is called in English), the
window turns gray, and stops responding.

[EMAIL PROTECTED]:~$ lsb_release -rd
Description:Ubuntu 8.04
Release:8.04

[EMAIL PROTECTED]:~$ apt-cache policy update-manager
update-manager:
  Asennettu: 1:0.87.24
  Ehdokas: 1:0.87.24
  Versiotaulukko:
 *** 1:0.87.24 0
500 http://fi.archive.ubuntu.com hardy/main Packages
100 /var/lib/dpkg/status

Processes:
 6275 ?Sl 0:05 /usr/bin/python2.5 /usr/bin/update-manager
 6287 ?S  0:00 /usr/bin/gksu --desktop 
/usr/share/applications/update-manager.desktop -- /usr/sbin/synaptic 
--hide-main-window --non-interactive --parent-window-id 50331651 
--update-at-startup
 6288 ?Ss 0:00 /usr/bin/sudo -H -S -p GNOME_SUDO_PASS -u root -- 
/usr/sbin/synaptic --hide-main-window --non-interactive --parent-window-id 
50331651 --update-at-startup

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

-- 
update manager stops when update check is asked manually
https://bugs.launchpad.net/bugs/224303
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 222940] Re: HP laserjet only prints the top of the page from Ecinve/Firefox, 8.04

2008-04-29 Thread kex

the problem returned after a couple of days...

(although not as bad as before - a couple of page were printed OK before
the problem appeared)

now setting the resolution to draft did not help.

I tried to print this file:  http://www.wingsgoclub.org/books/StrongerPlayer.pdf
with evince, printing 2 pages on a single page to preserve paper

This time the printer prints the first 2 pages OK with the high quality
option, but for the third paper only one third got out.

When I moved to draft quality, the first 4 pages came out OK, but the
fifth only contained the top part.

As before, the print job did not vanish from the printer control applet,
but stayed in the queue until manually removed.

-- 
HP laserjet only prints the top of the page from Ecinve/Firefox, 8.04
https://bugs.launchpad.net/bugs/222940
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 222940] [NEW] HP laserjet only prints the top of the page from Ecinve/Firefox, 8.04

2008-04-27 Thread kex
: unregistered pardevice
[ 6339.387015] ppdev0: registered pardevice
[ 6340.257484] sysctl table check failed: 
/dev/parport/parport0/devices/ppdev0/timeslice  Sysctl already exists
[ 6340.257774]  [c0132a59] sysctl_set_parent+0x19/0x30
[ 6340.257822]  [f8a0a90e] parport_device_proc_register+0xae/0xe0 [parport]
[ 6340.257851]  [f8a08e29] parport_register_device+0x139/0x260 [parport]
[ 6340.258074] ppdev0: registered pardevice
[ 6446.448463] ppdev0: released pardevice because user-space forgot
[ 6446.449233] ppdev0: unregistered pardevice
[ 6446.500801] ppdev0: unregistered pardevice
[ 6446.532073] ppdev0: registered pardevice
[ 6447.368576] sysctl table check failed: 
/dev/parport/parport0/devices/ppdev0/timeslice  Sysctl already exists
[ 6447.368797]  [c0132a59] sysctl_set_parent+0x19/0x30
[ 6447.368834]  [f8a0a90e] parport_device_proc_register+0xae/0xe0 [parport]
[ 6447.368859]  [f8a08e29] parport_register_device+0x139/0x260 [parport]
[ 6447.369029] ppdev0: registered pardevice
[ 6659.854473] ppdev0: released pardevice because user-space forgot
[ 6659.855265] ppdev0: unregistered pardevice
[ 6659.886853] ppdev0: unregistered pardevice
[ 6673.781911] ppdev0: registered pardevice
[ 6674.896031] sysctl table check failed: 
/dev/parport/parport0/devices/ppdev0/timeslice  Sysctl already exists
[ 6674.896321]  [c0132a59] sysctl_set_parent+0x19/0x30
[ 6674.896370]  [f8a0a90e] parport_device_proc_register+0xae/0xe0 [parport]
[ 6674.896400]  [f8a08e29] parport_register_device+0x139/0x260 [parport]
[ 6674.896623] ppdev0: registered pardevice
[ 6765.095026] ppdev0: unregistered pardevice
[ 6765.099407] ppdev0: released pardevice because user-space forgot
[ 6765.100158] ppdev0: unregistered pardevice
[ 6780.586337] ppdev0: registered pardevice
[ 6781.527504] sysctl table check failed: 
/dev/parport/parport0/devices/ppdev0/timeslice  Sysctl already exists
[ 6781.527785]  [c0132a59] sysctl_set_parent+0x19/0x30
[ 6781.527833]  [f8a0a90e] parport_device_proc_register+0xae/0xe0 [parport]
[ 6781.527865]  [f8a08e29] parport_register_device+0x139/0x260 [parport]
[ 6781.528085] ppdev0: registered pardevice
[ 6814.711283] ppdev0: unregistered pardevice
[ 6825.817594] ppdev0: unregistered pardevice

[EMAIL PROTECTED]:/var/log$  lpinfo -v
network socket
network beh
direct hal
direct hpfax
direct parallel:/dev/lp0
direct hp:/par/hp_LaserJet_1160_series?device=/dev/parport0
network http
network ipp
network lpd
file cups-pdf:/
direct scsi
network smb

***
/var/log/cupsys/error_log

D [27/Apr/2008:10:55:59 +0300] cupsdAcceptClient: 8 from localhost (Domain)
D [27/Apr/2008:10:55:59 +0300] Report: clients=1
D [27/Apr/2008:10:55:59 +0300] Report: jobs=69
D [27/Apr/2008:10:55:59 +0300] Report: jobs-active=0
D [27/Apr/2008:10:55:59 +0300] Report: printers=2
D [27/Apr/2008:10:55:59 +0300] Report: printers-implicit=0
D [27/Apr/2008:10:55:59 +0300] Report: stringpool-string-count=693
D [27/Apr/2008:10:55:59 +0300] Report: stringpool-alloc-bytes=8392
D [27/Apr/2008:10:55:59 +0300] Report: stringpool-total-bytes=13072
D [27/Apr/2008:10:55:59 +0300] cupsdReadClient: 8 POST / HTTP/1.1
D [27/Apr/2008:10:55:59 +0300] cupsdAuthorize: No authentication data provided.
D [27/Apr/2008:10:55:59 +0300] CUPS-Get-Default
D [27/Apr/2008:10:55:59 +0300] cupsdProcessIPPRequest: 8 status_code=0 
(successful-ok)
D [27/Apr/2008:10:55:59 +0300] cupsdAcceptClient: 11 from localhost (Domain)
D [27/Apr/2008:10:55:59 +0300] cupsdCloseClient: 8
D [27/Apr/2008:10:55:59 +0300] cupsdReadClient: 11 POST / HTTP/1.1
D [27/Apr/2008:10:55:59 +0300] cupsdAuthorize: No authentication data provided.
D [27/Apr/2008:10:55:59 +0300] CUPS-Get-Printers
D [27/Apr/2008:10:55:59 +0300] cupsdProcessIPPRequest: 11 status_code=0 
(successful-ok)
D [27/Apr/2008:10:55:59 +0300] cupsdAcceptClient: 8 from localhost:631 (IPv4)
D [27/Apr/2008:10:55:59 +0300] cupsdCloseClient: 11
D [27/Apr/2008:10:55:59 +0300] cupsdReadClient: 8 GET 
/printers/hp_LaserJet_1160_series.ppd HTTP/1.1
D [27/Apr/2008:10:55:59 +0300] cupsdAuthorize: No authentication data provided.
D [27/Apr/2008:10:55:59 +0300] cupsdCloseClient: 8
D [27/Apr/2008:10:56:02 +0300] cupsdAcceptClient: 8 from localhost (Domain)
D [27/Apr/2008:10:56:02 +0300] cupsdReadClient: 8 POST 
/printers/hp_LaserJet_1160_series HTTP/1.1
D [27/Apr/2008:10:56:02 +0300] cupsdAuthorize: No authentication data provided.
D [27/Apr/2008:10:56:02 +0300] Print-Job 
ipp://localhost:631/printers/hp_LaserJet_1160_series
D [27/Apr/2008:10:56:02 +0300] print_job: auto-typing file...
D [27/Apr/2008:10:56:02 +0300] add_job: requesting-user-name=kex
I [27/Apr/2008:10:56:02 +0300] [Job 70] Adding start banner page none.
D [27/Apr/2008:10:56:02 +0300] Discarding unused job-created event...
I [27/Apr/2008:10:56:02 +0300] [Job 70] Adding job file of type 
application/postscript.
I [27/Apr/2008:10:56:02 +0300] [Job 70] Adding end banner page none.
I [27/Apr/2008:10:56:02 +0300] [Job 70] Queued on hp_LaserJet_1160_series by 
kex.
D [27/Apr/2008:10:56:02 +0300] [Job 70

[Bug 222940] Re: HP laserjet only prints the top of the page from Ecinve/Firefox, 8.04

2008-04-27 Thread kex

** Attachment added: printingbuginfo
   http://launchpadlibrarian.net/13957350/printingbuginfo

-- 
HP laserjet only prints the top of the page from Ecinve/Firefox, 8.04
https://bugs.launchpad.net/bugs/222940
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 222940] Re: HP laserjet only prints the top of the page from Ecinve/Firefox, 8.04

2008-04-27 Thread kex

ah, I was too hasty.  disabling AppArmor does not help - only the top of the 
page gets out :)

-- 
HP laserjet only prints the top of the page from Ecinve/Firefox, 8.04
https://bugs.launchpad.net/bugs/222940
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 222940] Re: HP laserjet only prints the top of the page from Ecinve/Firefox, 8.04

2008-04-27 Thread kex

hi

I tried with changing the Printout Mode to draft, and it printed
perfectly fine.  Then I changed back to normal, and it printed fine.
Even reboot did not make the problem reappear.

I'll add a comment here again, if (when?) the problem returns.

-- 
HP laserjet only prints the top of the page from Ecinve/Firefox, 8.04
https://bugs.launchpad.net/bugs/222940
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