[Bug 1839237] Re: snapd disk write usage very high on 19.04 with snapd 2.39.3

2020-10-23 Thread sfc
This still happens on 20.10.

Now I'm using a proxy for faster downloads, but snapd is still writing
too much to disk (~9MB/s disk writes while ~1.5MB/s downloads).

snapd from journalctl -u with SNAPD_DEBUG=1 SNAPD_DEBUG_HTTP=7 is
attached.


** Attachment added: "snapd.log"
   
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1839237/+attachment/5426290/+files/snapd.log

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

Title:
  snapd disk write usage very high on 19.04 with snapd 2.39.3

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

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

[Bug 1839237] Re: snapd disk write usage very high on 19.04 with snapd 2.39.3

2020-10-23 Thread sfc
btw, this only happens when refreshing snaps, but not on installing a
new snap.

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

Title:
  snapd disk write usage very high on 19.04 with snapd 2.39.3

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

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

[Bug 1839237] Re: snapd disk write usage very high on 19.04 with snapd 2.39.3

2020-06-23 Thread sfc
sudo pidstat -d -T ALL -p `pidof snapd` 5

18时51分41秒   UID   PID   kB_rd/s   kB_wr/s kB_ccwr/s iodelay  Command
18时51分46秒 0  4326  0.00   7019.20  0.00   0  snapd

18时51分46秒   UID   PID   kB_rd/s   kB_wr/s kB_ccwr/s iodelay  Command
18时51分51秒 0  4326  0.00   7254.40  0.00   0  snapd

18时51分51秒   UID   PID   kB_rd/s   kB_wr/s kB_ccwr/s iodelay  Command
18时51分56秒 0  4326  0.00   7230.40  0.00   0  snapd

18时51分56秒   UID   PID   kB_rd/s   kB_wr/s kB_ccwr/s iodelay  Command
18时52分01秒 0  4326  0.00   7120.00  0.00   0  snapd

18时52分01秒   UID   PID   kB_rd/s   kB_wr/s kB_ccwr/s iodelay  Command
18时52分06秒 0  4326  0.00   7016.80  0.00   0  snapd
^C

平均时间:   UID   PID   kB_rd/s   kB_wr/s kB_ccwr/s iodelay  Command
平均时间: 0  4326  0.00   7128.16  0.00   0  snapd

snap changes

ID   Status  Spawn   Ready   Summary
91   Donetoday at 17:14 CST  today at 17:14 CST  Connect 
chromium:password-manager-service to core:password-manager-service
92   Error   today at 17:19 CST  today at 17:56 CST  Refresh snaps 
"gtk-common-themes", "core", "core18", "code", "intellij-idea-community", 
"gnome-3-26-1604", "gnome-3-28-1804", "chromium"
93   Error   today at 18:00 CST  today at 18:06 CST  Refresh snaps 
"gtk-common-themes", "core", "code", "intellij-idea-community", 
"gnome-3-26-1604", "gnome-3-28-1804", "chromium"
94   Error   today at 18:06 CST  today at 18:08 CST  Refresh snaps "core", 
"code", "intellij-idea-community", "gnome-3-26-1604", "gnome-3-28-1804", 
"chromium", "gtk-common-themes"
95   Doing   today at 18:09 CST  -   Refresh snaps "core", 
"code", "intellij-idea-community", "gnome-3-26-1604", "gnome-3-28-1804", 
"chromium", "gtk-common-themes"

snapd shows a ~7MB/s disk writes while the download is very slow (only
~50KB/s on nethogs).

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

Title:
  snapd disk write usage very high on 19.04 with snapd 2.39.3

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

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

[Bug 1839237] Re: snapd disk write usage very high on 19.04 with snapd 2.39.3

2020-05-27 Thread sfc
fnotifystat shows during snap refreshing chromium:

Total   Open  Close   Read  Write PID  Process Pathname
 53.2   15.7   15.7   21.90.0 1423 snapd   
/var/lib/snapd/assertions/asserts-v0/serial/generic/generic-classic/3e9f8cfc-6448-4ee5-a063-e6dca36cbd7b
 48.5   15.7   15.7   17.20.0 1423 snapd   
/var/lib/snapd/assertions/asserts-v0/model/16/generic/generic-classic
 47.0   15.7   15.7   15.70.0 1423 snapd   
/var/lib/snapd/assertions/asserts-v0/model/16/generic/generic-classic/active
 47.0   15.7   15.7   15.70.0 1423 snapd   
/var/lib/snapd/assertions/asserts-v0/serial/generic/generic-classic/3e9f8cfc-6448-4ee5-a063-e6dca36cbd7b/active
 37.6   18.8   18.80.00.0 1423 snapd   /var/lib/snapd
  6.31.61.60.03.1 1423 snapd   
/var/lib/snapd/state.json.3JyPRpSX9Wny~
  6.31.61.60.03.1 1423 snapd   
/var/lib/snapd/state.json.6nB3FqVxvjFb~
  6.31.61.60.03.1 1423 snapd   
/var/lib/snapd/state.json.D1LhKm5mlyGy~
  6.31.61.60.03.1 1423 snapd   
/var/lib/snapd/state.json.Dq4TVRJVvRG1~
  6.31.61.60.03.1 1423 snapd   
/var/lib/snapd/state.json.FMNtFS8YYlng~
  6.31.61.60.03.1 1423 snapd   
/var/lib/snapd/state.json.hGy5jX2syq49~
  6.31.61.60.03.1 1423 snapd   
/var/lib/snapd/state.json.j8Xyb0TqmhmH~
  6.31.61.60.03.1 1423 snapd   
/var/lib/snapd/state.json.qVC5sVR5pfg3~
  6.31.61.60.03.1 1423 snapd   
/var/lib/snapd/state.json.r4v1vtQDQxX6~
  6.31.61.60.03.1 1423 snapd   
/var/lib/snapd/state.json.rKJwFbvPDkW4~
  6.31.61.60.03.1 1423 snapd   
/var/lib/snapd/state.json.xS543gv26pD2~
  6.31.61.60.03.1 1423 snapd   
/var/lib/snapd/state.json.y8GgXRcY3xmk~
  1.60.00.00.01.6 1423 snapd   
/var/lib/snapd/snaps/chromium_1165.snap.xdelta3-1143-to-1165.partial

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

Title:
  snapd disk write usage very high on 19.04 with snapd 2.39.3

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

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

[Bug 1839237] Re: snapd disk write usage very high on 19.04 with snapd 2.39.3

2020-04-24 Thread sfc
This still happens on 20.04, could anyone tell me how to get some debug
logs?

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

Title:
  snapd disk write usage very high on 19.04 with snapd 2.39.3

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

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

[Bug 1839237] Re: snapd disk write usage very high on 19.04 with snapd 2.39.3

2019-11-02 Thread sfc
This still happens to me on 19.10 when snapd performing auto refresh.

snapd version: 2.41+19.10.1

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

Title:
  snapd disk write usage very high on 19.04 with snapd 2.39.3

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

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

[Bug 1760377] [NEW] Ubuntu 17.10 freezes on login with kernel 4.13.0-37-generic

2018-03-31 Thread sfc
Public bug reported:

I updated kernel to 4.13.0-37-generic, and after reboot, it freezes on
the kde login screen. Even sysrq keys does not work. I rebooted again,
and be able to enter password, then it freezes again on plasma loading
screen. I finally selected 4.13.0-36-generic kernel from grub, and my
computer booted normally. I guess there was a kernel panic, but it
didn't show on screen, nor in system logs, or I cannot find it.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
Date: Sun Apr  1 11:14:39 2018
DistUpgraded: 2017-10-02 23:05:26,340 DEBUG icon theme changed, re-reading
DistroCodename: artful
DistroVariant: kubuntu
DpkgLog:
 
EcryptfsInUse: Yes
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: QUANTA Computer Inc 2nd Generation Core Processor Family 
Integrated Graphics Controller [152d:0875]
 NVIDIA Corporation GF106M [GeForce GT 555M] [10de:0dce] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: QUANTA Computer Inc GF106M [GeForce GT 555M] [152d:0875]
InstallationDate: Installed on 2012-12-20 (1927 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: Hasee QTH6
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=5e2d0528-b52e-4165-9c44-c18ef0338b43 ro quiet splash video=VGA-2:d
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to artful on 2017-10-02 (180 days ago)
dmi.bios.date: 12/16/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: SU272
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: HM65
dmi.board.vendor: Hasee
dmi.board.version: TBD
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hasee
dmi.chassis.version: US
dmi.modalias: 
dmi:bvnINSYDE:bvrSU272:bd12/16/2011:svnHasee:pnQTH6:pvr03:rvnHasee:rnHM65:rvrTBD:cvnHasee:ct10:cvrUS:
dmi.product.family: Intel_Mobile
dmi.product.name: QTH6
dmi.product.version: 03
dmi.sys.vendor: Hasee
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sun Apr  1 11:07:30 2018
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug artful fonts kubuntu

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

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

Title:
  Ubuntu 17.10 freezes on login with kernel 4.13.0-37-generic

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

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

[Bug 1730152] Re: Internal microsd card reader does not work in Ubuntu 17.10

2018-01-24 Thread sfc
@funicorn Yes. Put that dkms.conf in the same ampe_stor directory and
use "dkms add" to add it. Please refer to
https://help.ubuntu.com/community/DKMS and https://github.com/dell/dkms
for detailed instructions.

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

Title:
  Internal microsd card reader does not work in Ubuntu 17.10

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

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

[Bug 1730152] Re: Internal microsd card reader does not work in Ubuntu 17.10

2018-01-24 Thread sfc
Also see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270676/comments/80
to install it with DKMS.

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

Title:
  Internal microsd card reader does not work in Ubuntu 17.10

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

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

[Bug 1730152] Re: Internal microsd card reader does not work in Ubuntu 17.10

2018-01-24 Thread sfc
You could try this driver: https://github.com/josch09/ampe_stor. From
the code, it seems supporting AU6601, AU6621, and AU6625, but it's not
working on my envy 13 ad110tu (AU6625). It can detect the card, and get
the capacity, but then many errors will occur and finally the reader
dies. Maybe it will work on your device.

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

Title:
  Internal microsd card reader does not work in Ubuntu 17.10

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

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

[Bug 1730184] Re: org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad address

2018-01-10 Thread sfc
Today I got the coredump, but ubuntu-bug cannot upload it, saying
"ValueError ('not enough values to unpack (expected 2, got 1)',)". So I
use "ubuntu-bug xwayland" command, and attached the generated report.
This crash now seems only happens when the system is under load for some
time (in my case high cpu usage).

gdb stacktrace of this coredump, if anything helpful:

Reading symbols from Xwayland...Reading symbols from 
/usr/lib/debug/.build-id/65/efba1189e8c1122d2e74c13bf7e54825c3e367.debug...done.
done.
[New LWP 3455]
[New LWP 3460]
[New LWP 3461]
[New LWP 3462]
[New LWP 3463]
[New LWP 3464]
[New LWP 3465]
[New LWP 3466]
[New LWP 3467]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/Xwayland :0 -rootless -terminate -core -listen 
4 -listen 5 -displayfd'.
Program terminated with signal SIGABRT, Aborted.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51  ../sysdeps/unix/sysv/linux/raise.c: 没有那个文件或目录.
[Current thread is 1 (Thread 0x7f97acaffa80 (LWP 3455))]
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x7f97a9b8ff5d in __GI_abort () at abort.c:90
#2  0x555ce6faf13a in OsAbort () at ../../../../os/utils.c:1361
#3  0x555ce6fb4c53 in AbortServer () at ../../../../os/log.c:877
#4  0x555ce6fb5a75 in FatalError (f=f@entry=0x555ce6fbd640 "failed to read 
Wayland events: %s\n") at ../../../../os/log.c:1015
#5  0x555ce6e3b43f in xwl_read_events (xwl_screen=0x555ce8f96a40) at 
../../../../../hw/xwayland/xwayland.c:594
#6  0x555ce6faccb1 in ospoll_wait (ospoll=0x555ce8f8ba20, 
timeout=) at ../../../../os/ospoll.c:412
#7  0x555ce6fa5cbb in WaitForSomething (are_ready=) at 
../../../../os/WaitFor.c:226
#8  0x555ce6f719f3 in Dispatch () at ../../../../dix/dispatch.c:422
#9  0x555ce6f75c90 in dix_main (argc=11, argv=0x7ffce0ab28c8, 
envp=) at ../../../../dix/main.c:287
#10 0x7f97a9b781c1 in __libc_start_main (main=0x555ce6e3aa60 , 
argc=11, argv=0x7ffce0ab28c8, init=, fini=, 
rtld_fini=, stack_end=0x7ffce0ab28b8) at 
../csu/libc-start.c:308
#11 0x555ce6e3aa9a in _start ()


** Attachment added: "apport.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730184/+attachment/5034904/+files/apport.txt

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

Title:
  org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad
  address

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

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

[Bug 1730184] Re: org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad address

2017-12-21 Thread sfc
As for the log timestamp, mine is the same order as the themusicgod1's,
first intel_do_flush_locked, then xwayland connection lost. I'm using
journalctl -r to print the log, so the order is reversed.

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

Title:
  org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad
  address

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

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

[Bug 1730184] Re: org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad address

2017-12-21 Thread sfc
Thanks for your reply. Sometimes the crash will produce a huge coredump
in my home (~200MB), but I cannot find anything useful in it with gdb. I
will attach it when the next time it occurs.

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

Title:
  org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad
  address

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

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

[Bug 1730184] Re: org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad address

2017-12-20 Thread sfc
Same here, sometimes the system will just freeze (even caps lock led not
working), and after about 1 minute, the gnome-shell crashed to login
screen, with all running apps crashed. Happens two or more times a day.

It's really annoying because sometimes this causes some lines of code I
just wrote in IDE lost.

journalctl:

...
12月 21 15:30:37 sfc-HP-ENVY13 gsd-wacom[19116]: gsd-wacom: Fatal IO error 11 
(资源暂时不可用) on X server :0.
12月 21 15:30:37 sfc-HP-ENVY13 chromium-browser.desktop[24804]: 
[24876:24876:1221/153037.848583:ERROR:x11_util.cc(89)] X IO error received (X 
server probably 
12月 21 15:30:37 sfc-HP-ENVY13 gsd-xsettings[19120]: gsd-xsettings: Fatal IO 
error 11 (资源暂时不可用) on X server :0.
12月 21 15:30:37 sfc-HP-ENVY13 gsd-keyboard[19146]: gsd-keyboard: Fatal IO error 
11 (资源暂时不可用) on X server :0.
12月 21 15:30:37 sfc-HP-ENVY13 chromium-browser.desktop[24804]: 
[24804:24804:1221/153037.848637:ERROR:chrome_browser_main_extra_parts_x11.cc(62)]
 X IO error r
12月 21 15:30:37 sfc-HP-ENVY13 kerneloops-applet.desktop[19608]: 
kerneloops-applet: Fatal IO error 11 (资源暂时不可用) on X server :0.
12月 21 15:30:37 sfc-HP-ENVY13 gsd-clipboard[19136]: gsd-clipboard: Fatal IO 
error 11 (资源暂时不可用) on X server :0.
12月 21 15:30:37 sfc-HP-ENVY13 org.a11y.atspi.Registry[18957]:   after 74933 
requests (74933 known processed) with 0 events remaining.
12月 21 15:30:37 sfc-HP-ENVY13 org.a11y.atspi.Registry[18957]: XIO:  fatal IO 
error 11 (Resource temporarily unavailable) on X server ":0"
12月 21 15:30:37 sfc-HP-ENVY13 gsd-a11y-keyboa[19129]: gsd-a11y-keyboard: Fatal 
IO error 11 (资源暂时不可用) on X server :0.
12月 21 15:30:37 sfc-HP-ENVY13 wmsystemtray.desktop[19619]:   after 1043 
requests (1043 known processed) with 0 events remaining.
12月 21 15:30:37 sfc-HP-ENVY13 wmsystemtray.desktop[19619]: XIO:  fatal IO error 
11 (Resource temporarily unavailable) on X server ":0"
12月 21 15:30:37 sfc-HP-ENVY13 gnome-shell[18907]: Connection to xwayland lost
12月 21 15:30:37 sfc-HP-ENVY13 guake.desktop[19617]: guake: Fatal IO error 11 
(资源暂时不可用) on X server :0.
12月 21 15:30:37 sfc-HP-ENVY13 org.gnome.Shell.desktop[18907]: 
intel_do_flush_locked failed: Bad address
12月 21 15:30:35 sfc-HP-ENVY13 wmsystemtray.desktop[19619]: wmsystemtray: Tray 
icon 54d was destroyed, removing
12月 21 15:30:35 sfc-HP-ENVY13 wmsystemtray.desktop[19619]: wmsystemtray: A 
poorly-behaved application tried to unmap window 540000d!
12月 21 15:30:03 sfc-HP-ENVY13 gnome-shell[18907]: value "-1.00" of type 
'gfloat' is invalid or out of range for property 'height' of type 'gfloat'
12月 21 15:30:03 sfc-HP-ENVY13 gnome-shell[18907]: value "-1.00" of type 
'gfloat' is invalid or out of range for property 'width' of type 'gfloat'
12月 21 15:30:03 sfc-HP-ENVY13 gnome-shell[18907]: value "-1.00" of type 
'gfloat' is invalid or out of range for property 'height' of type 'gfloat'
12月 21 15:30:03 sfc-HP-ENVY13 gnome-shell[18907]: value "-1.00" of type 
'gfloat' is invalid or out of range for property 'width' of type 'gfloat'
12月 21 15:30:03 sfc-HP-ENVY13 gnome-shell[18907]: value "-1.00" of type 
'gfloat' is invalid or out of range for property 'height' of type 'gfloat'
12月 21 15:30:03 sfc-HP-ENVY13 gnome-shell[18907]: value "-1.00" of type 
'gfloat' is invalid or out of range for property 'width' of type 'gfloat'
12月 21 15:29:30 sfc-HP-ENVY13 systemd[1]: Started Cleanup of Temporary 
Directories.
12月 21 15:29:30 sfc-HP-ENVY13 systemd-tmpfiles[301]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
...

Ubuntu 17.10 amd64, kernel 4.13.0-19-generic #22-Ubuntu, gnome-shell
3.26.2, running on wayland, Intel i5-8250U cpu, no discrete graphics
card

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

Title:
  org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad
  address

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

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

[Bug 1219786] Re: Frantic disk activity by check-new-release makes system temporarily almost unusable

2017-03-08 Thread sfc
Just ran into this problem on a Ubuntu 16.04.2 server, the check-new-
release process occupied the whole disk, causing 99+% iowait in top and
100+MiB/s disk read in iotop (normal HDD, not SSD), which almost freeze
the server.

kernel 4.4.0-33-generic

11:48:21 up 209 days, 16:33,  2 users,  load average: 0.01, 0.77, 0.68

  totalusedfree  shared  buff/cache   available
Mem:990 790  65  30 134  34
Swap:   495 495   0

After killed the check-new-release process, the server recovered from
freezing.

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

Title:
  Frantic disk activity by check-new-release makes system temporarily
  almost unusable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1219786/+subscriptions

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


[Bug 1333140] Re: Fix udev rules to consider mmc rpmb partitions

2015-04-28 Thread sfc
Could you please tell us how to interrupt the boot process of the
install iso and give a command shell to run this command? The boot
process never ends even after 20+mins.

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

Title:
  Fix udev rules to consider mmc rpmb partitions

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

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


[Bug 1445732] [NEW] Fix udev rules to consider mmc rpmb partitions (LP:#1333140) in vivid

2015-04-18 Thread sfc
Public bug reported:

Ubuntu 15.04 vivid still has this bug fixed in #1333140, so please port
the fix to vivid.

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

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

Title:
  Fix udev rules to consider mmc rpmb partitions (LP:#1333140) in vivid

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

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


[Bug 1310023] Re: 14.04: Nvidia Prime is unable to switch to the Nvidia card

2014-05-04 Thread sfc
Today I purged bumblebee and installed nvidia-prime again and found the 
solution.
The key is DO NOT REBOOT after changing video card in nvidia-settings. If you 
want to reboot right after the change, you MUST LOGOUT AND LOGIN then reboot, 
or, at least on my laptop, the discrete card will disappear from lspci and 
cannot be switched.
Purging nvidia-prime and a shutdown will recover the discrete card.

nvidia-prime 0.6.2
Ubuntu 14.04
kernel 3.13-0-24-generic
nvidia-331 331.38-0ubuntu7

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

Title:
  14.04: Nvidia Prime is unable to switch to the Nvidia card

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1310023/+subscriptions

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


[Bug 1245621] Re: cryptkeeper crashed with SIGSEGV in __libc_start_main()

2014-04-29 Thread sfc
14.04 64bit. still segfault on startup...

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

Title:
  cryptkeeper crashed with SIGSEGV in __libc_start_main()

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

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


[Bug 1310023] Re: 14.04: Nvidia Prime is unable to switch to the Nvidia card

2014-04-20 Thread sfc
Same here.
Using HD3000 and GT555M.
When firstly installed nvidia-prime, the nvidia-settings show correct setting 
of using Nvidia card.
But when I switched to integrated HD3000 and relogined, the discrete card is 
still working (laptop became really hot) and I cannot switch back to integrated 
card. After reboot the discrete card even disappeared from lspci and still 
working.

prime-select gives the same error:
Error: alternatives are not set up properly
Error: nvidia mode can't be enabled

Bumblebee works well.

Ubuntu 14.04
nvidia-prime 0.6.2 with nvidia-331
kernel 3.13.0

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

Title:
  14.04: Nvidia Prime is unable to switch to the Nvidia card

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1310023/+subscriptions

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


[Bug 1307875] [NEW] GUI is not usable saying module gui is not installed on scilab

2014-04-15 Thread sfc
Public bug reported:

When starting up scilab, it says GUI module is not installed and I cannot use 
almost any function on the GUI.
Plotting doesn't work as well, saying graphics module is not installed.

scilab 5.5.0-1
Ubuntu 14.04 (updated to newest version)

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

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

Title:
  GUI is not usable saying module gui is not installed on scilab

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

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


[Bug 1279792] [NEW] Wrong timezone offset given by java.sql.ResultSet.getTime()

2014-02-13 Thread sfc
Public bug reported:

When I'm using java to read a time from MySQL:
  ResultSet r = (SQL query);
  ..
  r.getTime(open_time).getTime()
and this sentence gives different time (1 hour delta) on my server and my 
laptop (which got wrong time).
The only difference between my server and laptop is timezone. When I changed 
timezone of my laptop from Asia/Chongqing to Asia/Shanghai as on the server, 
the time reads correctly.
Then I used r.getTime(open_time).getTimezoneOffset() to check the timezone 
between Asia/Chongqing and Asia/Shanghai, it gives -420 and -480.
In fact, the whole China is GMT+8, which means Asia/Chongqing and Asia/Shanghai 
should be the same time.
Other java time functions don't have this problem.

Server:
mysql-server 5.5.35-0ubuntu0.12.04.1
java version 1.7.0_51
OpenJDK Runtime Environment (IcedTea 2.4.4) (7u51-2.4.4-0ubuntu0.12.04.2)
OpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode)

Laptop:
mysql-server 5.5.35-0ubuntu0.13.10.2
java version 1.7.0_51
OpenJDK Runtime Environment (IcedTea 2.4.4) (7u51-2.4.4-0ubuntu0.13.10.1)
OpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode)

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

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

Title:
  Wrong timezone offset given by java.sql.ResultSet.getTime()

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

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


[Bug 1265929] Re: scilab missing libscisignal_processing.so

2014-01-25 Thread sfc
The same here with scilab 5.4.1-1~exp1
when calling corr() in scilab, it says A previous error has been detected 
while loading libscisignal_processing.so: libscisignal_processing.so: 
无法打开共享对象文件: 没有那个文件或目录
 !--error 999 
Impossible to load libscisignal_processing.so library: (null)
While no libscisignal_processing.so in either scilab-minimal-bin or 
scilab-full-bin

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

Title:
  scilab missing libscisignal_processing.so

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

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

[Bug 1174205] Re: Using pyopencl doesn't work and spits our ImportError

2013-11-22 Thread sfc
13.10 amd64 here, also the same problem.
After force installed ocl-icd-libopencl1 and replaced libopenCL.so.* in 
nvidia-319-updates, pyopencl benchmark shows:

Execution time of test without OpenCL:  0.0963661670685 s
Traceback (most recent call last):
  File benchmark.py, line 29, in module
for platform in cl.get_platforms():
pyopencl.LogicError: clGetPlatformIDs failed: platform not found khr

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

Title:
  Using pyopencl doesn't work and spits our ImportError

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

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


[Bug 747719] Re: kded4 eats memory like mad

2011-05-08 Thread sfc
I'm also suffering from this bug since kde 4.6.1... now i tried kde 4.6.3 and 
found that adding noapic acpi=off to grub and the kded4 is calm now.(disable 
ACPI)
---
1912 sfc   20   0  619m  29m  16m S0  3.4   0:00.80 kded4 
---
Maybe the problem is in PowerDevil?

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

Title:
  kded4 eats memory like mad

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