[Bug 1833419] [NEW] apparmor profile denies logging of openntpd to rsyslog
Public bug reported: Hello, Can anyone backport openntpd-1:6.2p3-2 to the 18.04 as this https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904040 is annoying. ** Affects: openntpd (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/1833419 Title: apparmor profile denies logging of openntpd to rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openntpd/+bug/1833419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
Also affected by this bug on Xenial with linux-generic-hwe-16.04 4.15.0.24.46 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776887 Title: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)
Thanks @tyhicks. $ dmesg | grep microcode [0.00] microcode: microcode updated early to revision 0x1f, date = 2018-02-07 [0.843339] microcode: sig=0x306a9, pf=0x2, revision=0x1f [0.843412] microcode: Microcode Update Driver: v2.2. $ cat /proc/version_signature Ubuntu 4.13.0-38.43+lp1759920.1-generic 4.13.16 $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=/dev/mapper/lmvg-ubunturoot ro zswap.enabled=0 quiet -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux- image-4.13.0-37-generic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761121] [NEW] Latest intel ucode update halts my system during boot to graphic session
Public bug reported: It seems that this iucode_tool -lS /lib/firmware/intel-ucode/ iucode_tool: system has processor(s) with signature 0x000306a9 selected microcodes: 001: sig 0x000306a9, pf mask 0x12, 2018-02-07, rev 0x001f, size 13312 microcode update prevents me to boot to graphic session on any(4.13.0.38[37]) kernel. I can successfully boot to the recovery console. In some of failed attempts i got "NMI deadlock detected on CPU0,1,3 in mkswap" I guess nvidia-384 has some issues and conflicts with updated microcode. I have to disable microcode update with IUCODE_TOOL_EXTRA_OPTIONS="--date-after=2018-02-07" to get my unity session back. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 BootLog: lvmetad is not active yet, using direct activation during sysinit /dev/mapper/lmvg-ubunturoot: clean, 421309/1310720 files, 3715643/5242880 blocks CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 4 12:39:37 2018 DistUpgraded: 2016-04-19 13:48:02,030 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Не удалось выполнить процесс-потомок «./xorg_fix_proprietary.py» (No such file or directory) (8)) DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK107 [GeForce GT 640] [10de:0fc1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GK107 [GeForce GT 640] [1458:353e] InstallationDate: Installed on 2012-09-26 (2015 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=/dev/mapper/lmvg-ubunturoot ro nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off nvidia_drm.modeset=1 zswap.enabled=0 quiet SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-19 (714 days ago) dmi.bios.date: 10/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-DS2 DVI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/12/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-DS2DVI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Apr 4 11:56:19 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2~16.04.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761121 Title: Latest intel ucode update halts my system during boot to graphic session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761121/+subscr
[Bug 974480] Re: Notification area whitelist is obsolete
So, trusty is here and i'm desperately waiting for the ppa update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974480 Title: Notification area whitelist is obsolete To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/974480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974480] Re: Notification area whitelist is obsolete
@Stephen >Third-party software is free to implement the common specification or not. Should they choose to not implement it or use the functionality if available in their toolkit of choice, their software will not work well on Ubuntu or many of its flavours. We hope they would choose to work well with our product, but ultimately it's their decision and I assume they do not make it lightly. It would be true if you'd really removed systray support completely, however you left hardcoded exception for Wine and Java which say - we don't really care about user experience as it's obvious that hardcoding exceptions for two non-linux native toolkits could not pass any QA. So we are just reducing customizability of our DE to just force developers to take our specs if they wanted to run apps on our DE. Funny thing that this other DE, which has not been adopted your specs, do the same - insulting own users by removing customization options. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974480 Title: Notification area whitelist is obsolete To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/974480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974480] Re: Notification area whitelist is obsolete
@Stephen Thanks for the link. > design of one particular desktop environment that also happens to use code > that implements the specification which developed this specification, forcefully dropped support of previous specification with similar functionality and obviously lacking the direction on maintaining consistent documentation on it's own resources. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974480 Title: Notification area whitelist is obsolete To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/974480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974480] Re: Notification area whitelist is obsolete
Hey Mark, can you please comment on this. According to the origin of this bug "The application indicator system has been in place for two years now, which should be long enough for applications to adopt it." Ok, i asked one of the (Debian) developers to consider to support it in some tk app(so as you don't provide tk bindings they should be created first). So he asked me about, surprize, documentation. And the questions are: 1) Do you think that application indicator system so popular and mature enough, so 3 of 4 links from the https://unity.ubuntu.com/projects/appindicators/ could lead to 404 pages 2)Do you think it's so cool that it even not worth to mention it at http://developer.ubuntu.com/api/ 3) Is it really so hard to recognize your fail and revert the patch that breaks compatibility instead of forcing the world to play with your half supported/half abandoned API initiative? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974480 Title: Notification area whitelist is obsolete To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/974480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974480] Re: Notification area whitelist is obsolete
@milos-sd That's empty autobuild according to the diff from saucy version https://launchpadlibrarian.net/155818257/unity_7.1.2%2B13.10.20131014.1-0ubuntu1_7.1.2%2B13.10.20131014.1-0ubuntu1systray1.diff.gz. The old patch can't be applied to the new sources, as it seems whole com.canonical.Unity.Panel schema missing. I guess some manual work needed here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974480 Title: Notification area whitelist is obsolete To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/974480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974480] Re: Notification area whitelist is obsolete
Mark, meanwhile what do you think about tcltk and JavaFX toolkits. Shouldn't they exists in Ubuntu universe? To be precise i'm talking about tkabber and davmail packages which broken by this amazing decesion for more than a year now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974480 Title: Notification area whitelist is obsolete To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/974480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974480] Re: Notification area whitelist is obsolete
desperately waiting for timekillers PPA update since upgrade to 13.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974480 Title: Notification area whitelist is obsolete To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/974480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1220619] [NEW] stalonetray geometry height parameter strange behaviour
Public bug reported: According to the documentation --geometry geometry_spec, geometry geometry_spec Set tray`s initial geometry to geometry_spec, specified in standard X notation: widthxheight[+x[+y]], where width and height are specified in icon slot multiples. Default value: 1x1+0-0. But when i set it to: 5x1+100+100 i got single line of pixels string with no icons visible 5x2+100+100 i got 1 row of icons 5x3+100+100 i got 3 rows of icons Not that i miss 2 rows tray too much, but it really annoys me, when i edit it's configuration. ** Affects: stalonetray (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/1220619 Title: stalonetray geometry height parameter strange behaviour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stalonetray/+bug/1220619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1140716] Re: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge
Hit by the HUNG bug again on Raring. However it's reported differently, so could be the different from the originating one on precise and Quantal. dmesg [19492.484182] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [19492.484186] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state Xorg.log(EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7fcb2d7cb476] (EE) 1: /usr/bin/X (mieqEnqueue+0x26b) [0x7fcb2d7ac78b] (EE) 2: /usr/bin/X (0x7fcb2d61b000+0x6d472) [0x7fcb2d688472] (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fcb27aab000+0x5f44) [0x7fcb27ab0f44] (EE) 4: /usr/bin/X (0x7fcb2d61b000+0x96927) [0x7fcb2d6b1927] (EE) 5: /usr/bin/X (0x7fcb2d61b000+0xc0328) [0x7fcb2d6db328] (EE) 6: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fcb2c71e000+0xfbd0) [0x7fcb2c72dbd0] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x7) [0x7fcb2b43b747] (EE) 8: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7fcb2c516338] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fcb29ebd000+0x39010) [0x7fcb29ef6010] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fcb29ebd000+0x3a1f7) [0x7fcb29ef71f7] (EE) 11: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fcb29ebd000+0x60d51) [0x7fcb29f1dd51] (EE) 12: /usr/bin/X (BlockHandler+0x44) [0x7fcb2d677b94] (EE) 13: /usr/bin/X (WaitForSomething+0x114) [0x7fcb2d7c87f4] (EE) 14: /usr/bin/X (0x7fcb2d61b000+0x58811) [0x7fcb2d673811] (EE) 15: /usr/bin/X (0x7fcb2d61b000+0x4757a) [0x7fcb2d66257a] (EE) 16: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7fcb2b36bea5] (EE) 17: /usr/bin/X (0x7fcb2d61b000+0x478c1) [0x7fcb2d6628c1] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. (EE) [mi] EQ overflow continuing. 100 events have been dropped. repeated 3 times every 100 events dropped till 300 (EE) (EE) [mi] EQ overflow continuing. 300 events have been dropped. (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7fcb2d7cb476] (EE) 1: /usr/bin/X (0x7fcb2d61b000+0x6d472) [0x7fcb2d688472] (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fcb27aab000+0x5f44) [0x7fcb27ab0f44] (EE) 3: /usr/bin/X (0x7fcb2d61b000+0x96927) [0x7fcb2d6b1927] (EE) 4: /usr/bin/X (0x7fcb2d61b000+0xc0328) [0x7fcb2d6db328] (EE) 5: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fcb2c71e000+0xfbd0) [0x7fcb2c72dbd0] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x7) [0x7fcb2b43b747] (EE) 7: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7fcb2c516338] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fcb29ebd000+0x39010) [0x7fcb29ef6010] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fcb29ebd000+0x3a1f7) [0x7fcb29ef71f7] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fcb29ebd000+0x60d51) [0x7fcb29f1dd51] (EE) 11: /usr/bin/X (BlockHandler+0x44) [0x7fcb2d677b94] (EE) 12: /usr/bin/X (WaitForSomething+0x114) [0x7fcb2d7c87f4] (EE) 13: /usr/bin/X (0x7fcb2d61b000+0x58811) [0x7fcb2d673811] (EE) 14: /usr/bin/X (0x7fcb2d61b000+0x4757a) [0x7fcb2d66257a] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7fcb2b36bea5] (EE) 16: /usr/bin/X (0x7fcb2d61b000+0x478c1) [0x7fcb2d6628c1] (EE) [ 19491.810] (EE) intel(0): Detected a hung GPU, disabling acceleration. [ 19491.810] (EE) intel(0): When reporting this, please include i915_error_state from debugfs and the full dmesg. [ 19491.810] [mi] Increasing EQ size to 512 to prevent dropped events. [ 19491.810] [mi] EQ processing has resumed after 335 dropped events. [ 19491.810] [mi] This may be caused my a misbehaving driver monopolizing the server's resources. [ 19508.772] (II) AIGLX: Suspending AIGLX clients for VT switch [ 19513.181] (II) Open ACPI successful (/var/run/acpid.socket) [ 19513.181] (II) AIGLX: Resuming AIGLX clients after VT switch Linux 3.8.0-22-generic #33-Ubuntu i915_error_state is clear from ERROR after S3 suspend/resume or because i mounted debugfs only now. Will add it next time this happend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1140716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
The issue mostly gone after cold reboot via suspend to disk. I managed to reproduce it only once after reboot and it grubs CPU for only minute or two while i checking it and than returned to normal CPU usage. I've checked both distribution and the trunk version. So suspend this bug until someone can stably reproduce it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174654 Title: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974480] Re: Notification area whitelist is obsolete
So, just updated to 13.04 and don't see Java icons from davmail. What should i do?! Hipotetically, as i come here from this page https://launchpad.net/~timekiller/+archive/unity-systrayfix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974480 Title: Notification area whitelist is obsolete To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/974480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073900] Re: glue points turns invisible just right after addition
** Attachment added: "example file to test vsd export of simple objects" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1073900/+attachment/3421765/+files/gluepoints.vsd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073900 Title: glue points turns invisible just right after addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1073900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073900] Re: glue points turns invisible just right after addition
I think i localized the problem. The problem that objects imported from .vsd as groups of background and border. So the problem appears only while trying to put gluepoints to grouped object. That problem persist in ODG too. In the attach .odg is the stripped version of original file where i found the problem and .vsd is a test of how objects are imported by Draw. Btw, visio connection points and connections is not converted to Draw connections and gluepoints. ** Attachment added: "overview of the problem" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1073900/+attachment/3421764/+files/gluepoints.odg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073900 Title: glue points turns invisible just right after addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1073900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073900] Re: glue points turns invisible just right after addition
This only happens with shapes existed in original .vsd created with Visual Studio and taken from some library(like rectangles from Flowchart library). Native Draw simple objects and simple .vsd objects doesn't have such problem. Changing fill type/color on "special" rectangle objects doesn't help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073900 Title: glue points turns invisible just right after addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1073900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073900] [NEW] glue points turns invisible just right after addition
Public bug reported: The glue points dissapear just right after addition. The only way to find them later is to remember their location and do region select of the surrounding space. Description:Ubuntu 12.10 Release:12.10 libreoffice-draw: 3.6.2~rc2-0ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libreoffice-draw 1:3.6.2~rc2-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Thu Nov 1 15:45:46 2012 InstallationDate: Installed on 2012-09-26 (35 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: Upgraded to quantal on 2012-10-19 (13 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073900 Title: glue points turns invisible just right after addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1073900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969576] Re: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init]
With the kernel from http://people.canonical.com/~acelan/bugs/lp969576/ asus_wmi doesn't crash at boot and doesn't prevent system to boot normally to DM what is more important :) Seems there is another problem with init, upstart or whatever, as if i enable recovery or just text mode it drops me to tty login and i could run 'start lightdm' without problems, even with crashed asus_wmi. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969576 Title: BUG: unable to handle kernel NULL pointer dereference at (null) [asus_wmi_rfkill_init] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/969576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
