[Bug 351186] Re: [M76] [ubuntu 9.04] [ubuntu 9.10] slow unminimizing with ati card and desktop effects enabled
Solved my problems (slow maximizing, minimizing resizing) by getting the newest kernel 2.6.32. Which has 3D support for ATI Radeon HD3xxx and HD4xxx. Either upgrade your kernel or upgrade Ubuntu to Lucid and ditch the fglrx driver. -- [M76] [ubuntu 9.04] [ubuntu 9.10] slow unminimizing with ati card and desktop effects enabled https://bugs.launchpad.net/bugs/351186 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 351186] Re: [M76] [ubuntu 9.04] [ubuntu 9.10] slow unminimizing with ati card and desktop effects enabled
This is what I did. From 9.10 I disabled all desktop effects and purged my fglrx driver. Reebooted and got the message about disabled properetary drivers. Then I ran update-manager -d to update to Ubuntu Lucid alpha 2 containing the new kernel 2.6.32. When done the update- manager rebooted and I was booted into the new Lucid. From here I enabled desktop effects and without any of the bugs (slow minimizing, maximizing resiezing etc) I had before. Ta-da! Here is the official RadeonHD from ubuntu community documentation: https://help.ubuntu.com/community/RadeonHD Make sure to read what groups have 3D support in Lucid.. -- [M76] [ubuntu 9.04] [ubuntu 9.10] slow unminimizing with ati card and desktop effects enabled https://bugs.launchpad.net/bugs/351186 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 351186] Re: [M76] [ubuntu 9.04] [ubuntu 9.10] slow unminimizing with ati card and desktop effects enabled
my lspci -vvnn output: 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Mobility Radeon HD 3600 Series [1002:9598] Subsystem: ASUSTeK Computer Inc. Device [1043:01e4] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: radeon Kernel modules: radeon -- [M76] [ubuntu 9.04] [ubuntu 9.10] slow unminimizing with ati card and desktop effects enabled https://bugs.launchpad.net/bugs/351186 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 436755] Re: indicator-applet doesn't change icon when I recieve new e-mails via Evolution
installed new update (evolution-indicator 0.2.4-0ubuntu3) from karmic- proposed. Still having the same problem. I have 2 pop3 accounts (yahoo + google) both accounts show up in the indicator-applets list, both with a zero after. -- indicator-applet doesn't change icon when I recieve new e-mails via Evolution https://bugs.launchpad.net/bugs/436755 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 436755] Re: indicator-applet doesn't change icon when I recieve new e-mails via Evolution
I can confirm evolution-indicator_0.2.4-0ubuntu3.1 working for me too -- indicator-applet doesn't change icon when I recieve new e-mails via Evolution https://bugs.launchpad.net/bugs/436755 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 1800719] Re: missing conf files noted on apt upgrade after distribution upgrade
Upgraded from 16.04.5 to 18.04.3 and have noticed the same symptom -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800719 Title: missing conf files noted on apt upgrade after distribution upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1800719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575655] Re: the network indicator shows the wrong status
Yeah, I'd like to add that this definitely happens after suspend for me -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575655 Title: the network indicator shows the wrong status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1575655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580786] [NEW] abnormal CPU-usage
Public bug reported: Logged into my computer and Xorg was using 100% -140% of CPU ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 23:16:08 2016 InstallationDate: Installed on 2016-04-08 (33 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580786 Title: abnormal CPU-usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1580786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575655] Re: the network indicator shows the wrong status
Can confirm that that workaround works for me -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575655 Title: the network indicator shows the wrong status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1575655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567445] Re: ubi-prepare failed with exit code 255
I have the same issue, although checking or unchecking secure boot has no effect -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567445 Title: ubi-prepare failed with exit code 255 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1567445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567445] Re: ubi-prepare failed with exit code 255
However choosing to not enable third-party repos and not download along side installation seems to have solved the issue -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567445 Title: ubi-prepare failed with exit code 255 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1567445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575655] [NEW] the network indicator shows the wrong status
Public bug reported: Description:Ubuntu 16.04 LTS Release:16.04 indicator-applet: Installed: (none) Candidate: 12.10.2+15.04.20141127.2-0ubuntu1 Version table: 12.10.2+15.04.20141127.2-0ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages The network indicator sometimes shows the icon for wired connections and sometimes claims wifi without connection even though I'm consistently connected over wifi. I don't mean to say that it switches between these two or that always is wrong. But sometimes my connected to wifi symbol changes to wired. Other times it will change to the no connection wifi. The info is correct on boot, but switches over time, possibly after suspension. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: indicator-applet (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 27 14:54:42 2016 InstallationDate: Installed on 2016-04-08 (18 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) SourcePackage: indicator-applet UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-applet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575655 Title: the network indicator shows the wrong status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1575655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632363] [NEW] snapd fail on boot
Public bug reported: `lsb_release -rd` Description:Ubuntu 16.04 LTS Release:16.04 Running the BBB version of snappy ubuntu core. unable to attain package version. any snap command is met by "error: cannot list snaps: cannot communicate with server: Get http://localhost/v2/snaps?sources=local: dial unix /run/snapd.socket: connect: connection refused" with a few variation in the URL `systemctl list-units` shows that snapd.boot-ok.service snapd. service snapd.socket has failed to load. ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Tags: ubuntu-core -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632363 Title: snapd fail on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1632363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632363] Re: snapd fail on boot
The image was working fine, and although the sheer amount of experimentation and reinstalls makes my memory foggy, I do believe this particular install had gone through a ubuntu-core update without any issues. What caused the issue in the first place is a real networking issue. I had placed the install within a DMZ that was wrongly configured, so the clients of the subnet was unable to get a lease on an IP-address. It was left on this subnet for quite some time and over several boots. It now has internet access again, but the snap daemon fails continuously. For what reason I'm unsure. I've seen different reports of snap daemon failing because it starts before networking in the boot process, maybe I'm suffering the same problem. This bug then, would have surfaced due to a longer period of no network access for unknown reasons. @Michael I'm unfamiliar with journalctl and have yet to manage to get any form of relevant info from a query. Maybe you could help me with some suggestions as to what to search for in the journal? @Oliver The image is from https://people.canonical.com/~mvo/all-snaps/obsolete/, it was downloaded on the 19th of September. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632363 Title: snapd fail on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1632363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1604606] Re: snapd fails to start due to: could not unmarshal state entry "snaps": json: cannot unmarshal string into Go value of type int
*** This bug is a duplicate of bug 1632363 *** https://bugs.launchpad.net/bugs/1632363 ** This bug has been marked a duplicate of bug 1632363 snapd fail on boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1604606 Title: snapd fails to start due to: could not unmarshal state entry "snaps": json: cannot unmarshal string into Go value of type int To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1604606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632363] Re: snapd fail on boot
-- Logs begin at Thu 2016-10-27 13:49:19 UTC, end at Thu 2016-10-27 14:13:13 UTC. -- Oct 27 14:00:45 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:47 localhost.localdomain snapd[1823]: error: internal error: could not unmarshal state entry "snaps": json: cannot unmarshal string into Go value of type int Oct 27 14:00:47 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE Oct 27 14:00:47 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:47 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:48 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:48 localhost.localdomain snapd[1833]: error: internal error: could not unmarshal state entry "snaps": json: cannot unmarshal string into Go value of type int Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:48 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:48 localhost.localdomain snapd[1840]: error: internal error: could not unmarshal state entry "snaps": json: cannot unmarshal string into Go value of type int Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:49 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:49 localhost.localdomain snapd[1848]: error: internal error: could not unmarshal state entry "snaps": json: cannot unmarshal string into Go value of type int Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:49 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:50 localhost.localdomain snapd[1855]: error: internal error: could not unmarshal state entry "snaps": json: cannot unmarshal string into Go value of type int Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Start request repeated too quickly. Oct 27 14:00:50 localhost.localdomain systemd[1]: Failed to start Snappy daemon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632363 Title: snapd fail on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1632363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632363] Re: snapd fail on boot
`journalctl -u snapd.service` -- Logs begin at Thu 2016-10-27 13:49:19 UTC, end at Thu 2016-10-27 14:00:54 UTC. -- Oct 27 14:00:45 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:47 localhost.localdomain snapd[1823]: error: internal error: could not unmarshal state entr Oct 27 14:00:47 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, statu Oct 27 14:00:47 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:47 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:48 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:48 localhost.localdomain snapd[1833]: error: internal error: could not unmarshal state entr Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, statu Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:48 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:48 localhost.localdomain snapd[1840]: error: internal error: could not unmarshal state entr Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, statu Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:49 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:49 localhost.localdomain snapd[1848]: error: internal error: could not unmarshal state entr Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, statu Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:49 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:50 localhost.localdomain snapd[1855]: error: internal error: could not unmarshal state entr Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, statu Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Start request repeated too quickly. Oct 27 14:00:50 localhost.localdomain systemd[1]: Failed to start Snappy daemon. `journalctl -u snapd.boot-ok.service` -- Logs begin at Thu 2016-10-27 13:49:19 UTC, end at Thu 2016-10-27 14:00:54 UTC. -- Oct 27 14:00:53 localhost.localdomain systemd[1]: Starting Notify bootloader that boot was successful... Oct 27 14:00:54 localhost.localdomain snap[1874]: error: can not SyncBoot, failed to make ubuntu-core active: snap not active Oct 27 14:00:54 localhost.localdomain systemd[1]: snapd.boot-ok.service: Main process exited, code=exited, status=1/FAILURE Oct 27 14:00:54 localhost.localdomain systemd[1]: Failed to start Notify bootloader that boot was successful. Oct 27 14:00:54 localhost.localdomain systemd[1]: snapd.boot-ok.service: Unit entered failed state. Oct 27 14:00:54 localhost.localdomain systemd[1]: snapd.boot-ok.service: Failed with result 'exit-code'. `journalctl -u snapd.socket` -- Logs begin at Thu 2016-10-27 13:49:19 UTC, end at Thu 2016-10-27 14:00:54 UTC. -- Oct 27 13:49:40 localhost.localdomain systemd[1]: Starting Socket activation for snappy daemon. Oct 27 13:49:40 localhost.localdomain systemd[1]: Listening on Socket activation for snappy daemon. Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.socket: Unit entered failed state. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632363 Title: snapd fail on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1632363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349121] [NEW] Non-existent display detected using nouveau driver (Samsung Laptop Nvidia GeForce GT 520M) (Ubuntu 14.04.01)
Public bug reported: Samsung NP300V3A (Laptop) | Nvidia GF119M [GeForce GT 520M] | Ubuntu 14.04.01 LTS Xorg 1:7.7+1ubuntu8 | ubuntu-drivers-common 1:0.2.91.5 | xserver-xorg- video-nouveau 1:1.0.10-1ubuntu2 Unexpected 'ghost' display appears in settings when no extra display is connected. There is a non-existing display detected, known as "Unknown Display". The bug is all in all very similar, if not a duplicate, of bug #1296020. However, as I am using Nouveau rather than Nvidia-331 and have different hardware, I thought it better to make a new report. The bug renders GDM impossible to use while Lightdm works. When logging in to Gnome Shell, the screen goes black from time to time (upon loading the shell), this I can solve by using the laptop hardware keys for switching video output. I tried the proprietary drivers and the fix committed to trusty-proposed due to bug #1296020 (ubuntu-drivers-common 1:0.2.91.6) with no avail. It seems that whatever solved the issue for a non-existing display for Nvidia-331 users is not causing the problem for those who are using Nouveau. My 'xrandr -q' output Screen 0: minimum 320 x 200, current 2390 x 768, maximum 32767 x 32767 LVDS1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 293mm x 165mm 1366x768 60.0*+ 1360x768 59.8 60.0 1024x768 60.0 800x60060.3 56.2 640x48059.9 VGA1 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) DP1 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) VGA-1-2 connected 1024x768+1366+0 0mm x 0mm 1024x768 60.0* 800x60060.3 56.2 848x48060.0 640x48059.9 1024x768 (0x43) 65.0MHz h: width 1024 start 1048 end 1184 total 1344 skew0 clock 48.4KHz v: height 768 start 771 end 777 total 806 clock 60.0Hz 800x600 (0x44) 40.0MHz h: width 800 start 840 end 968 total 1056 skew0 clock 37.9KHz v: height 600 start 601 end 605 total 628 clock 60.3Hz 800x600 (0x45) 36.0MHz h: width 800 start 824 end 896 total 1024 skew0 clock 35.2KHz v: height 600 start 601 end 603 total 625 clock 56.2Hz ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sun Jul 27 16:07:03 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c0b6] Subsystem: Samsung Electronics Co Ltd Device [144d:c0b6] InstallationDate: Installed on 2014-07-26 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 2232:1008 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 300V3A/300V4A/300V5A/200A4B/200A5B ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro video=VGA-0:d quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2011 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04FI dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 300V3A/300V4A/300V5A/200A4B/200A5B dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04FI:bd09/02/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn300V3A/300V4A/300V5A/200A4B/200A5B:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn300V3A/300V4A/300V5A/200A4B/200A5B:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 300V3A/300V4A/300V5A/200A4B/200A5B dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimenta
[Bug 1349121] Re: Non-existent display detected using nouveau driver (Samsung Laptop Nvidia GeForce GT 520M) (Ubuntu 14.04.01)
** Summary changed: - Non-existent display detected using nouveau driver + Non-existent display detected using nouveau driver (Samsung Laptop Nvidia GeForce GT 520M) (Ubuntu 14.04.01) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349121 Title: Non-existent display detected using nouveau driver (Samsung Laptop Nvidia GeForce GT 520M) (Ubuntu 14.04.01) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1349121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296020] Re: [Asus U36JC] Non-existent display detected in both intel driver and nvidia driver (Optimus Laptop) (ubuntu trusty 14.04)
I am experiencing a very similar bug. ALthough I am using the nouveau driver. I made a separate bug report for my issues: #1349121 I also switched to the proprietary driver and tried the fix submitted, it did however not solve my issues. Are these different issues? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296020 Title: [Asus U36JC] Non-existent display detected in both intel driver and nvidia driver (Optimus Laptop) (ubuntu trusty 14.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1296020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349121] Re: Non-existent display detected using nouveau driver (Samsung Laptop Nvidia GeForce GT 520M) (Ubuntu 14.04.01)
I have since solved my issue by purging and reinstalling nouveau together with bumblebee. (http://www.bumblebee- project.org/install.html) My laptop was also, in addition to having the display issue, running abnormally hot since I installed 14.04. Bumblebee solved both issues in one go. How or why, I have no idea though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349121 Title: Non-existent display detected using nouveau driver (Samsung Laptop Nvidia GeForce GT 520M) (Ubuntu 14.04.01) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1349121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349121] Re: Non-existent display detected using nouveau driver (Samsung Laptop Nvidia GeForce GT 520M) (Ubuntu 14.04.01)
Seems the bumblebee package doesn't have any driver specific dependencies. The Nvidia package is purged and completely out of my system though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349121 Title: Non-existent display detected using nouveau driver (Samsung Laptop Nvidia GeForce GT 520M) (Ubuntu 14.04.01) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1349121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349121] Re: Non-existent display detected using nouveau driver (Samsung Laptop Nvidia GeForce GT 520M) (Ubuntu 14.04.01)
I'll have to admit that I was a bit confused in the end there after all purging, reinstalling and installing. Checked my gpu-manager log now and it says that neither nouveau nor nvidia are loaded. Just Intel. In the jockey or 'additional drivers' interface it says nouveau. As I understand it there is no xorg.conf file like there was in the good old days where the driver to use is specified. Seems the situation is all but clear at the moment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349121 Title: Non-existent display detected using nouveau driver (Samsung Laptop Nvidia GeForce GT 520M) (Ubuntu 14.04.01) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1349121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 601639] [NEW] Network-manager reports not connected even though computer is connected
Public bug reported: Binary package hint: network-manager-gnome Package: network-manager-gnome 0.8-ubuntu3 Ubuntu 10.04 LTS The network-manager connects to wireless without any problems, a information bubble appears stating that the computer is connected to the network, which is correct. I can reach the internet without any problems. However the same instant the connection is established the "trying to connect-icon" reverts back to a "no connection-icon". This bug can be re-created with all the different icon-themes present on my computer and is now present on two of my lucid netbooks running UNE ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- Network-manager reports not connected even though computer is connected https://bugs.launchpad.net/bugs/601639 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 601639] Re: Network-manager reports not connected even though computer is connected
** Description changed: Binary package hint: network-manager-gnome Package: network-manager-gnome 0.8-ubuntu3 Ubuntu 10.04 LTS - The network-manager connects to wireless without any problems, a information bubble appears stating that the computer is connected to the network, which is correct. I can reach the internet without any problems. However the same instant the connection is established the "trying to connect-icon" reverts back to a "no connection-icon". This bug can be re-created with all the different icon-themes present on my computer and is now present on two of my lucid netbooks running UNE + The network-manager connects to wireless without any problems, an information bubble appears stating that the computer is connected to the network, which is correct. I can reach the internet without any problems. However the same instant the connection is established the "trying to connect-icon" reverts back to a "no connection-icon". This bug can be re-created with all the different icon-themes present on my computer and is now present on two of my lucid netbooks running UNE -- Network-manager reports not connected even though computer is connected https://bugs.launchpad.net/bugs/601639 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 399937] Re: ubuntuone-syncdaemon crashed with ImportError in ()
same here on 10.10 last update. -- ubuntuone-syncdaemon crashed with ImportError in () https://bugs.launchpad.net/bugs/399937 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 625725] [NEW] package update-manager-core 1:0.142.11 failed to install/upgrade: error writing to '': Success
Public bug reported: Binary package hint: update-manager Cannot update ProblemType: Package DistroRelease: Ubuntu 10.10 Package: update-manager-core 1:0.142.11 ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1 Uname: Linux 2.6.35-15-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Sat Aug 28 10:50:13 2010 ErrorMessage: error writing to '': Success InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4) SourcePackage: update-manager Title: package update-manager-core 1:0.142.11 failed to install/upgrade: error writing to '': Success ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 maverick ubuntu-une -- package update-manager-core 1:0.142.11 failed to install/upgrade: error writing to '': Success https://bugs.launchpad.net/bugs/625725 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 625725] Re: package update-manager-core 1:0.142.11 failed to install/upgrade: error writing to '': Success
** Attachment added: "AptOrdering.txt" https://bugs.launchpad.net/bugs/625725/+attachment/1524641/+files/AptOrdering.txt ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/625725/+attachment/1524642/+files/Dependencies.txt ** Attachment added: "Df.txt" https://bugs.launchpad.net/bugs/625725/+attachment/1524643/+files/Df.txt ** Attachment added: "Dmesg.txt" https://bugs.launchpad.net/bugs/625725/+attachment/1524644/+files/Dmesg.txt ** Attachment added: "DpkgTerminalLog.gz" https://bugs.launchpad.net/bugs/625725/+attachment/1524645/+files/DpkgTerminalLog.gz -- package update-manager-core 1:0.142.11 failed to install/upgrade: error writing to '': Success https://bugs.launchpad.net/bugs/625725 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 622223] Re: telepathy-butterfly crashed with TypeError in __on_received()
** Visibility changed to: Public -- telepathy-butterfly crashed with TypeError in __on_received() https://bugs.launchpad.net/bugs/63 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 621349] Re: mutter crashed with SIGSEGV
** Visibility changed to: Public -- mutter crashed with SIGSEGV https://bugs.launchpad.net/bugs/621349 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 620731] Re: mutter crashed with SIGSEGV in unity_places_place_get_entries()
** Visibility changed to: Public -- mutter crashed with SIGSEGV in unity_places_place_get_entries() https://bugs.launchpad.net/bugs/620731 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 625757] Re: dconf-service crashed with signal 5 in g_closure_invoke()
** Attachment added: "CoreDump.gz" https://bugs.launchpad.net/bugs/625757/+attachment/1524760/+files/CoreDump.gz ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/625757/+attachment/1524761/+files/Dependencies.txt ** Attachment added: "Disassembly.txt" https://bugs.launchpad.net/bugs/625757/+attachment/1524762/+files/Disassembly.txt ** Attachment added: "ProcMaps.txt" https://bugs.launchpad.net/bugs/625757/+attachment/1524763/+files/ProcMaps.txt ** Attachment added: "ProcStatus.txt" https://bugs.launchpad.net/bugs/625757/+attachment/1524764/+files/ProcStatus.txt ** Attachment added: "Registers.txt" https://bugs.launchpad.net/bugs/625757/+attachment/1524765/+files/Registers.txt ** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/625757/+attachment/1524766/+files/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/625757/+attachment/1524767/+files/ThreadStacktrace.txt ** Visibility changed to: Public -- dconf-service crashed with signal 5 in g_closure_invoke() https://bugs.launchpad.net/bugs/625757 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
